🇬🇧 London + willingness to travel (100% in-person)
💰 Competitive (incl. equity)
We're looking for a Member of Technical Staff to own our API-based inbound payments product end-to-end. You'll get institutional clients live, keep them transacting reliably, and scale across new corridors, clients, and use cases.
This is a backend-heavy, full-stack role at the core of our payments infrastructure. You'll be building on top of third-party payment provider APIs that are often unreliable and poorly documented — and making them work seamlessly for our clients. You'll ship provider integrations fast, diagnose live transaction failures in real time, and build the monitoring and resilience layers that let us scale with confidence.
A few reasons why you might find this exciting:
Who you are
- You've built payment systems before — experience with provider integrations, fintech products, or transaction processing in production.
- You're backend-heavy and full-stack — TypeScript, React, Node, and Postgres preferred but not rigid. What matters is that you can ship production code across the stack.
- You thrive under pressure — comfortable debugging live transaction failures, being on-call, and communicating directly with clients and providers.
- You build for resilience — retries, idempotency, fallbacks, and graceful degradation are second nature, not afterthoughts.
- You ship fast — comfortable with 7-day iteration cycles and managing multiple provider integrations in parallel.
- You're a clear communicator — can talk to institutional clients and payment providers without jargon, and keep the team informed without noise.
- Bonus: Experience with IT security compliance (e.g. DORA, GDPR), or familiarity with African payment providers.
Some topics you'll think about
- How do we build a resilient integration layer when every provider has different APIs, failure modes, and documentation quality?
- What monitoring and alerting do we need to detect and resolve transaction failures before clients notice?
- How do we scale from one corridor and one client to many of each without re-architecting everything?
- How do we balance speed of shipping new integrations with reliability of existing ones?
- What does a great developer experience look like for institutional clients consuming our APIs?
💸 Competitive salary + meaningful equity
🏢 Central London office (potential NY relocation)
🌐 Global exposure & impact
🍹 Team off-sites & regular socials