Senior/Lead Backend Developer - TypeScript/Node.js, AWS, PostgreSQL

Project about building the payments infrastructure that merchants have been waiting for. A single integration, intelligent routing, and the kind of reliability that lets businesses stop thinking about payments and get back to running their business.
The platform is real, the merchants are real, and the problems are hard. We're integrating multiple payment providers, routing transactions intelligently across them, and doing it in a way that's secure, scalable, and maintainable.

Core Development
● You build the services that make payments move. Sessions, routing, provider adapters, webhooks; you work across the core of the platform, end-to-end, from database schema through to deployment.
● You integrate payment providers properly. Clean adapter patterns, consistent error handling, and abstractions that make the tenth integration as maintainable as the firstYou write code that handles real money. That means understanding the failure modes, thinking about idempotency, and never cutting corners on correctness because correctness is the product.
● You contribute to architecture, not just implementation. You raise design concerns early, engage in technical decisions, and leave things better than you found them.

Quality & Performance
● You test what you build. Unit tests, integration tests, E2E tests, and an understanding of what each is actually for. You don't hand things to QA hoping for the best.
● You debug with rigour. When something goes wrong in production, you trace it, understand it, and fix the root cause, not just the symptom.
● You review code seriously. You give feedback that improves the codebase, and you take feedback the same way. Collaboration
● You work closely with the Tech Lead. You implement architectural decisions together and contribute meaningfully to technical design conversations.
● You engage with the product function. You take time to understand what you're building and why. Acceptance criteria exist to be understood.
● You show up to Agile ceremonies and contribute to them. Standups, sprint planning, retros; they only work if people engage honestly.
● You support the team across deployment, observability, and incident response. Shipping doesn't end at the PR merge.

How You’ll Be Successful
● What you ship works, and keeps working. Test coverage is real, regressions are rare, and you're not the source of production surprises.
● Provider integrations are clean and maintainable. The team can extend them without unpicking your decisions six months later.
● You raise concerns before they become problems. Whether it's a design risk, dependency, or edge case, you flag it early with context for the team to act.
● Your code reviews make the codebase better. Not just caught bugs, but clearer thinking, better abstractions, and a higher collective bar.
● The team trusts you across time zones. Async communication is clear, commitments are kept, and you don't go quiet when things get complicated.