Senior Backend Engineer – Payments

CXM Direct

. Build and own the connector and adapter layer so providers can be added or replaced through configuration and thin adapters .

Posted 9/24/2026full-timeRemote • Cyprus, Poland, Georgia, Bulgaria, Armenia, BelarusSeniorWebsite

Core Competencies

Role fit

Core Competencies

Use this summary to align your resume positioning with the role.

Demonstrates expertise in backend engineering with a strong focus on TypeScript and Node.js, alongside a solid understanding of payment systems and transaction management. Capable of leading integration efforts and ensuring reliable transaction status through effective architecture and observability.

Highest-signal resume keywords

Backend EngineeringTypeScriptNode.jsPayment SystemsIdempotency

ATS Keywords

Tailor your resume

Applicant Tracking System Keywords

Tip: use these terms in your resume and cover letter to boost ATS matches.

Hard Skills

Relational DatabasesAsynchronous Status HandlingTransaction State MachinesIntegration of Third-Party APIsEvent-Driven PatternsBank Transfer RailsVirtual AccountsQR-Based MethodsMobile MoneyAI Tooling

Soft Skills

Proactive MindsetIndependent Decision-MakingOwnership of Service

Tools & Technologies

.NETAPM

Industry Keywords

BrokerageCrypto PaymentsOrchestrationHigh-Volume PaymentsPayment Service ProviderPayment Gateway

Tech Stack

Tools & technologies

JavaScriptNode.jsRuby on RailsTypeScript.NET

About the role

Key responsibilities & impact

Build and own the connector and adapter layer so providers can be added or replaced through configuration and thin adapters
Migrate payment methods from redirect flows to server-to-server and embedded flows where supported, and measure the results
Own reconciliation, transaction status handling, method configuration and payment flows into the client portal downstream of the orchestration layer
Make transaction status reliable end to end through active polling, idempotent processing and reconciliation
Build observability over transaction status and provider performance
Specify and review orchestration platform behavior including transaction state machines, idempotency, polling, routing and cascading rules
Support integration work for the card programme
Extend the integration set to acquired entities through configuration rather than new builds
Take over the integration codebase, strengthen transaction status handling and ship a first server-to-server integration
Establish the adapter layer, launch providers against it and make transaction status and provider performance observable
Lead migration to server-to-server and embedded flows across payment methods and extend integrations to other entities

Requirements

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
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
Ability to own a service rather than close tickets: architecture decisions, standards and root cause fixes
English and Russian at a working communicative level
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

Benefits

Comp & perks

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