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 with strong Frontend experience 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
- 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
This is a fully fullstack role, and the bar on the frontend is as high as the bar on the backend. We are not looking for a backend engineer who tolerates UI work, and not a frontend specialist who avoids the services. You should be equally credible shipping a React and Next.js surface and changing the Java service behind it. You will own the merchant-facing surface of Paymend: the dashboard where merchants see which payments failed, what we recovered, and what they were paid for. You will also work in our Java and Spring Boot services, because a good merchant experience usually requires changing what the backend exposes, not just how it is displayed. We are being direct about the context: our dashboard currently spans React, Next.js, a Java BFF, and Java services, which means features get implemented several times over and UI work bottlenecks on one person. Simplifying that path is live work, and we want a senior engineer who will help lead it rather than inherit it. Key Responsibilities
- Build and own merchant-facing product surfaces in TypeScript, React, and Next.js: recovery reporting, transaction views, onboarding, and account management.
- Help simplify the dashboard architecture, including moving authentication into the Next.js layer and removing redundant layers between the frontend and our services.
- Raise the frontend bar: component patterns, state management, accessibility, performance, and testing that let more of the team contribute UI confidently.
- Work in our Java and Spring Boot services to shape the APIs the dashboard depends on, so a feature does not need four separate implementations.
- Turn dense payments data into interfaces a CFO or head of billing can act on. Clarity is the product here.
- Take part in architecture discussions and write proposals that the team reviews and decides on together.
Key Requirements
- 5+ years in professional software engineering, with deep frontend experience in TypeScript, React, and a modern framework such as Next.js.
- Equally strong backend experience in Java and Spring Boot. You should be able to add an endpoint, change a data model, reason about what belongs on which side of the boundary, and own the service you changed.
- Strong product instincts for data-heavy interfaces: tables, filters, reporting, and states that are empty, loading, partial, or wrong.
- Experience improving or reducing frontend architecture in a live product, not only greenfield builds.
- Hands-on experience with BFF or comparable patterns, and with designing frontend architecture for multi-team UI ownership: modular boundaries that let several teams contribute in parallel without the product losing cohesion.
- Experience shaping backend architecture in service of UI performance. What the API returns, how it is aggregated, and where work happens all decide how the interface feels.
- Comfortable operating in a containerized cloud environment: Kubernetes or a comparable orchestrator, and at least one major cloud provider (AWS, GCP, Azure, or similar). You should be able to deploy and debug what you build, on both sides of the stack.
- Working understanding of high availability: redundancy, graceful degradation, safe deploys, and how a backend failure should surface in the interface instead of breaking it.
- Fluent use of AI tools across the development lifecycle, well beyond autocomplete: exploring an unfamiliar codebase, prototyping interfaces, drafting implementations, refactors, test coverage, code review, and documentation. We also expect judgment about where these tools help and where their output has to be verified, on the UI as much as in the services behind it.
- Fluent English, spoken and written, is a mandatory requirement. You will work daily with colleagues and merchants across time zones, and much of our technical decision making happens in writing.
Nice to have
- Payments, fintech, or B2B SaaS experience, particularly dashboards used by finance and operations teams.
- Design system experience, or comfortable working closely with design and filling gaps where there is no dedicated designer.
- Experience being the person who unblocked UI contribution for a wider team.
- Familiarity with observability and frontend performance monitoring.
- 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. On the product surface this means moving from idea to a working interface quickly, then hardening it.
- We are equally clear about the limits. Generated code still gets reviewed, tested, and reasoned about, 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.
- Genuine ownership of the merchant experience, with room to set the direction rather than follow someone else's.
- Our founders built and scaled payment infrastructure before this. Engineering is not a support function here.
- Atividades de serviços financeiros e Desenvolvimento de software