We’re building a payment aggregation and orchestration platform for e-commerce merchants, so we’re specifically looking for candidates with strong FinTech and payment domain experience. Hands-on experience with payment providers, payment processing, transaction flows, or financial systems is a key requirement for this role.
What You’ll Be Doing 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 first. ● You 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.
What We’re Looking For ● You’ve shipped production-grade backend systems and have the scars to show for it. Distributed systems, high-volume APIs, and third-party integrations are familiar territory. ● TypeScript/Node.js is your primary language and you know it deeply. Async patterns, event-driven architecture, performance trade-offs; you’re not learning on the job. ● You’re comfortable with PostgreSQL in production. Schema design, query optimisation, indexing, transactions, caching strategies; you’ve made real decisions here. ● You understand microservices in practice, not just in theory. Service boundaries, async communication, and the operational reality of running multiple services. ● You’re familiar with cloud infrastructure and solutions. Having expertise with AWS or at least a solid, basic understanding of its common services, is a strong plus. ● CI/CD and Docker are part of how you work, not things you hand off to someone else. ● You own the operational reality of your code. You leverage observability tooling to monitor, debug, and investigate production issues on your own. You take ownership of system maintenance, on-call support, and finding
