Senior Backend Engineer, Payments

Job not on LinkedIn

🔥 2 minutes ago

🇺🇸 United States – Remote

⏰ Full Time

🟠 Senior

🔙 Backend Engineer

👻 Ghost score 11%

What it means: how likely this posting is sitting open without active hiring.How to read it: 60% or higher means we think this is a ghost. Lower scores are less of a worry.How we score it: age, reposts, open roles vs team size, how fast jobs close, and whether pay is listed.Fine print: an estimate from public data, not a judgment of the company. Real jobs can score high, so treat it as a hint, not a fact.

Apply Now

Find Similar Remote Jobs

Set Up Email Alert For New Jobs

📊 Check your resume score for this job

Improve your chances of getting an interview by checking your resume score before you apply.

Upload Resume

CXM

WebsiteLinkedInAll Job Openings

201 - 500 employees

Founded 2015

💸 Finance

💳 Fintech

Finance • Fintech

CXM is an online financial services firm that operates as a brokerage platform offering Forex and CFD trading to clients. The company enforces regional access restrictions for regulatory compliance and provides risk warnings about the high-risk nature of leveraged trading. CXM also offers customer support for access and compliance inquiries.

📋 Description

• 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 results • Own downstream orchestration responsibilities including reconciliation, transaction status handling, method configuration and payment flows into the client portal • Make transaction status reliable end to end through active status polling, idempotent processing and reconciliation • Build observability over transaction status and provider performance across the estate • Specify, design, argue for and review orchestration platform behaviour 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, onboard providers against it and make transaction status and provider performance observable • Run the migration to server-to-server and embedded flows across payment methods • Collaborate with a Systems Analyst as the team grows while retaining integration engineering ownership

🎯 Requirements

• 5+ years in backend engineering • Strong in TypeScript and 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 • Ability to own a service, including architecture decisions, standards and root cause fixes • English and Russian at a working communicative level • Exposure to .NET for work touching the client portal is a significant plus • Experience with APM and local rails in Asia, Africa or LATAM rather than cards alone is a significant plus • Experience with bank transfer rails, virtual accounts, QR-based methods and mobile money is a significant plus • Event-driven patterns in production: transactional outbox, idempotent consumers and sagas is a significant plus • Background in brokerage, crypto payments, orchestration or another high-volume payments environment is a significant plus • Active use of AI tooling in daily work is a significant plus • Ability to work independently and make decisions without constant oversight is a significant plus • Proactive mindset and willingness to propose improvements, fixes and new approaches is a significant plus

🏖️ Benefits

• Fully remote work within GMT to GMT+4, with no relocation required • Corporate AI tooling as part of the working process • 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