Senior Backend Engineer, Payments

Job description

Location: Remote (GMT to GMT+4) Department: Payments Employment Type: Full-Time About the Role 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 – Payments who will own our connector layer and everything downstream of it. You will build a canonical adapter layer so that providers plug in rather than being built one by one, move payment methods toward server-to-server and embedded flows, and make transaction status reliable and observable across the estate. You will also act as the payments function's technical counterpart to the orchestration platform team. The behaviour we need from the platform will be specified, discussed, challenged, and reviewed by you. Key Responsibilities Build and own the connector and adapter layer, ensuring that adding or replacing a provider becomes a matter of configuration and a thin adapter rather than a completely new integration. Migrate payment methods from redirect flows to server-to-server and embedded flows where supported by the provider, and measure the results. Own everything downstream of the orchestration layer, including: Reconciliation Transaction status handling Payment method configuration Payment flows into the client portal Make transaction status reliable end-to-end through active status polling, idempotent processing, and reconciliation. Build observability around transaction status and provider performance across the estate. Specify the behaviour required from the orchestration platform, including: Transaction state machines Idempotency Polling Routing Cascading rules Design these requirements, argue for the appropriate approach, and review the resulting implementation. Support integration work for our card programme. Extend the same integration set to acquired entities through configuration rather than rebuilding integrations for each entity. What You'll Need 5+ years of backend engineering experience, with strong expertise in TypeScript and Node.js and confidence working with relational databases. Production experience with payment systems, including: Authorisation Callbacks Refunds Reconciliation Retry behaviour Practical understanding of: Idempotency Asynchronous status handling Transaction state machines Designing for partial failure These are at the core of the role rather than secondary considerations. You will both build against these principles and help define how they should work. Experience integrating third-party APIs of uneven quality, including working directly with provider integration teams to resolve issues that documentation does not answer. Ability to own a service end-to-end, including architecture decisions, engineering standards, production issues, and root-cause fixes. English and Russian at a working communicative level. Significant Advantages The following experience would be highly valuable: Exposure to .NET, particularly for work involving the client portal. Experience with APMs and local payment rails across Asia, Africa, or LATAM, rather than cards alone. Experience with: Bank transfer rails Virtual accounts QR-based payment methods Mobile money Production experience with event-driven patterns such as: Transactional outbox Idempotent consumers Sagas Background in brokerage, crypto payments, payment orchestration, or another high-volume payments environment. Experience working on the provider side at a PSP, gateway, or payment company. Active use of AI tooling in daily engineering work. Ability to work independently and make decisions without constant oversight. A proactive mindset and willingness to propose improvements, fixes, and new approaches. What the First Year Looks Like First Months You will take over the integration codebase through a documented handover, strengthen transaction status handling, and ship your first server-to-server integration. By Mid-Year The adapter layer will be in place, and new providers will go live against it rather than being implemented as one-off integrations. Transaction status and provider performance will also be observable across the estate. Second Half of the Year The migration to server-to-server and embedded flows will run as a programme across payment methods. The same integration set will begin extending to our other entities. As the team grows, a Systems Analyst will take over instrumentation and verification, while integration engineering remains with you. Recruitment Process HR Interview – Background, motivation, and overall fit. Technical Interview – Backend engineering and payments-domain expertise. Home Task – A practical case based on real business needs. System Design & Problem-Solving Interview – Integration design, failure handling, and transaction status modelling. Final Interview – Discussion with senior stakeholders. What We Offer Fixed monthly compensation 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 over how the orchestration platform evolves. Engineering challenges that go far beyond CRUD, including: Asynchronous transaction statuses across dozens of providers Partial failures Local payment rails in emerging markets A scope that grows with the business, including a card programme, new entities, and new payment products. Corporate AI tooling as part of the everyday engineering workflow.