Paymend is an ambitious, remote-first fintech. We are profitable, growing, and focused on building with scalability and quality front-of-mind.
We are looking for a Senior Fullstack Software Engineer to join our highly motivated, remote-first team. We value high-velocity decision-making, technical excellence, and the conviction to move projects forward at pace. This is a role for someone who prefers owning outcomes to managing tasks and thrives in an environment where mission always comes first.
If you are a self-directed professional who wants to work as part of a great team and build for the future, we’d love to hear from you.
About Paymend
Paymend is a payments platform focused on recovering failed transactions and unlocking lost revenue for online merchants.
We operate at the end of the payment lifecycle, working alongside existing PSPs, gateways, and billing platforms to recover transactions that would otherwise be lost.
Through our infrastructure and payment routing capabilities, we help merchants:
- Recover 5–20% of declined revenue
- Increase approval rates
- Improve LTV without changing their checkout
We’ve processed over $1B+ in failed payments, supporting leading merchants across eCommerce, subscription, and digital verticals. We serve ecommerce, subscription, and health and wellness merchants processing $500K+ in monthly card volume, including over 100 brands across the US. Paymend was founded by the team behind Rebills, an orchestration platform for high-volume card transactions that was acquired in 2024.
About the Role
You will work across our payment platform: the Java services that handle transaction processing, decline analysis, routing, and retry logic, plus the interfaces merchants use to see what we recovered for them. This is a hands-on senior role with real ownership. The systems you build move money, so correctness, observability, and resilience matter more here than in most product engineering jobs.
You will join a small team that is actively reshaping its architecture. We are consolidating a four-layer path from the dashboard to our backend services and we want senior engineers who can push that kind of work forward, not just consume the outcome.
Key Responsibilities
- Design, build, and operate Java and Spring Boot services that process transactions, apply routing decisions, and drive adaptive retry logic.
- Build and maintain integrations with processors, acquirers, and connectors, including the reason code and response handling that recovery decisions depend on.
- Improve the reliability of our processing path: alerting, capacity limits, idempotency, reconciliation, and failure handling.
- Contribute across the stack when a feature needs it, including the TypeScript and React and Next.js layers of our merchant dashboard.
- Take part in architecture discussions and write proposals that the team reviews and decides on together.
- Work directly with payment operations and with merchants' technical teams when something needs investigating.
Key Requirements
- 5+ years building and running production backend services, with strong Java and Spring Boot experience.
- Solid grounding in relational databases, API design, asynchronous processing, and testing practices that hold up under real traffic.
- Comfortable owning a service end to end: you write it, you deploy it, you get paged for it, you improve it.
- Able to work in a fullstack codebase. You do not need to be a frontend specialist, but you should be able to ship a UI change without waiting for someone else.
- Comfortable operating in a containerized cloud environment: Kubernetes or a comparable orchestrator, and at least one major cloud provider (AWS, GCP, Azure, or similar).
- Practical experience designing and running high availability systems: redundancy, graceful degradation, health checks, safe deploys, and recovery when a dependency goes down. Our processing path cannot be offline while a merchant's customer is trying to pay.
- Fluent use of AI tools across the development lifecycle, well beyond autocomplete: exploring an unfamiliar codebase, drafting implementations, refactors and migrations, test coverage, code review, and documentation. We also expect judgment about where these tools help and where their output has to be verified before it goes anywhere near a service that moves money.
- Clear written communication in English. Much of our technical decision making happens in writing.
- Pragmatic judgment about tradeoffs. We move quickly, and we are honest about what that costs.
Nice to Have
- Payments experience: card processing, PSPs, gateways, acquirers, chargebacks, decline reason codes, or subscription billing.
- Experience with high-volume transactional systems where financial correctness is non negotiable.
- Experience reducing architectural complexity in a live system rather than only building new services.
- Familiarity with observability tooling and incident response practices.
How we work with AI
- AI-assisted development is a standing expectation for every engineer here, not the job of a specialist team. We are small, we ship payment infrastructure, and leverage per engineer is what lets us compete with much larger companies.
- We are equally clear about the limits. An AI-drafted change to a service that settles transactions gets the same review, testing, and reasoning as any other change, and a fast prototype is not evidence that a production feature is done. We want engineers who hold both of those at once, and who raise the team's practices rather than wait for someone else to define them.
Why Paymend - The problem is concrete and measurable. Every transaction we recover is revenue a merchant already earned and would otherwise have lost.
- Our founders built and scaled payment infrastructure before this. Engineering is not a support function here.
- Small team, direct access to decisions, and no six-month approval chains.
Paymend