Job description
Senior Backend Engineer, Payments
We are an international broker. Our clients fund and withdraw through roughly 60 payment methods across Asia, Africa, LATAM and the Middle East.
Payments is now a standalone function, and we are building the team around it.
We are looking for a Senior Backend Engineer who will own our connector layer and everything downstream of it: building a canonical adapter layer so that providers plug in rather than get built one by one, moving payment methods to server-to-server and embedded flows, and making transaction status reliable and observable across the estate.
You will also be the payments function's technical counterpart to the orchestration platform team: the behaviour we need from the platform is specified here, argued here and reviewed here.
Your responsibilities will be:
Building and owning the connector and adapter layer, so that adding or replacing a provider becomes configuration and a thin adapter rather than a new integration each time
Migrating payment methods from redirect flows to server-to-server and embedded flows where the provider supports it, and measuring the result
Owning everything downstream of the orchestration layer: reconciliation, transaction status handling on our side, method configuration and payment flows into the client portal
Making transaction status reliable end to end, through active status polling, idempotent processing and reconciliation
Building observability over transaction status and provider performance across the estate
Specifying the behaviour we need from the orchestration platform: transaction state machine, idempotency, polling, routing and cascading rules. You design it, argue for it and review what comes back
Supporting integration work for our card programme
Extending the same integration set to acquired entities as configuration rather than a new build each time
What you'll need:
5+ years in backend engineering, strong in TypeScript, Node.js, comfortable in relational databases
Production experience with payment systems: authorisation, callbacks, refunds, reconciliation and retry behaviour
Practical understanding of idempotency, asynchronous status handling, transaction state machines and designing for partial failure. This is the core of the role rather than a detail, and you will both build against it and specify it
Experience integrating third-party APIs of uneven quality, including working directly with a provider's integration team to resolve what the documentation does not answer
The ability to own a service rather than close tickets: architecture decisions, standards and root cause fixes
English and Russian at a working communicative level
Will be a significant plus:
Exposure to .NET for work touching the client portal
Experience with APM and local rails in Asia, Africa or LATAM rather than cards alone
Experience with bank transfer rails, virtual accounts, QR-based methods, mobile money etc.
Event-driven patterns in production: transactional outbox, idempotent consumers, sagas
Background in brokerage, crypto payments, orchestration or another high-volume payments environment; on the provider side, at a PSP, gateway or payment company
Active use of AI tooling in daily work
Ability to work independently and make decisions without constant oversight
Proactive mindset: willingness to propose improvements, fixes, new approaches
What the first year looks like:
In the first months you take over the integration codebase with a documented handover, strengthen transaction status handling, and ship your first server-to-server integration.
By mid-year the adapter layer is in place, new providers go live against it rather than as one-off builds, and transaction status and provider performance are observable across the estate.
In the second half the migration to server-to-server and embedded flows runs as a programme across methods, and the same integration set starts extending to our other entities. As the team grows, a Systems Analyst takes over instrumentation and verification while integration engineering stays with you.
Recruitment process:
HR interview, covering background, motivation and fit
Technical interview on backend engineering and the payments domain
Home task as a case from the real needs
System design and problem-solving interview, covering integration design, failure handling and status modelling
Final interview with senior stakeholders
We offer:
Fixed monthly compensation of [based on experience]
Fully remote work within GMT to GMT+4, with no relocation required
Ownership of the connector layer and everything downstream, with direct influence on what the orchestration platform becomes
Engineering problems that are not CRUD: asynchronous status across dozens of providers, partial failure, and local payment rails in emerging markets
Scope that grows with the business: a card programme, new entities and new payment products
Corporate AI tooling as part of the working process
Originally posted on Himalayas
Who can apply
The source lists worldwide eligibility. Accepted UTC offsets: UTC-11, UTC-10, UTC-9.5, UTC-9, UTC-8, UTC-7, UTC-6, UTC-5, UTC-4, UTC-3.5, UTC-3, UTC-2, UTC-1, UTC+0, UTC+1, UTC+2, UTC+3, UTC+3.5, UTC+4, UTC+4.5, UTC+5, UTC+5.5, UTC+5.75, UTC+6, UTC+6.5, UTC+7, UTC+8, UTC+8.75, UTC+9, UTC+9.5, UTC+10, UTC+10.5, UTC+11, UTC+12, UTC+12.75, UTC+13, UTC+14. Review the full description for employer-specific work authorization, residency and schedule requirements.