Solutions Engineer, Payout Rails

We're looking for a solutions engineer to join our Payout Rails team, owning the technical connections that move money into banks, wallets, and aggregators worldwide.
What you will get to do :

Own technical onboarding for new payout partners: API review, environment setup, credential exchange, certification, and launch
Translate partner API specifications into internal configuration: corridor and rail setup, field mappings, account and alias validation, error code mappings
Solution the integration per corridor and produce the specs delivery runs on: sequence diagrams, field mappings, validation rules, test matrices
Stay on the connection after launch: keep SLAs where they need to be and drive every failure through to a fix, whether the cause sits with the partner or with us
Build evidence based escalations on rejection rates, error code accuracy, and SLA misses, and hold partners to their commitments
Keep the critical path visible across partner, platform, Compliance, and Commercial teams, and feed recurring friction into the platform roadmap instead of absorbing it as manual work

Who you are :
You own a connection end to end and follow it into production. You can explain a payment rail to an engineer and an API contract to a business lead in the same meeting. You would rather remove the cause of a recurring problem than keep handling each instance of it.
Technical Skills:

4+ years in solutions engineering, integration engineering, technical account management, or platform engineering, in payments, fintech, or banking
Strong practical command of REST and JSON APIs: OAuth 2.0, mTLS, JWT, API keys, webhooks, idempotency
Comfortable with Postman and reading raw request and response traces
Hands on SQL for investigation, able to query transaction data and turn it into an argument
Working knowledge of payment rails and message standards: ISO 20022, ISO 8583, instant versus deferred batch clearing, alias and account resolution, settlement versus clearing
Clear writing: specifications, diagrams, escalation notes, and status updates that partner teams and internal stakeholders can both read
Demonstrated ownership of external technical relationships

Nice to have:

Domestic rails or wallet ecosystems in one or more of India (UPI, IMPS, NEFT, RTGS), Philippines (PESONet, InstaPay), Mexico (SPEI), Bangladesh (NPSB, BEFTN), East or West Africa mobile money, GCC, or SEPA
Applied cryptography in payments: AES 256 (CBC versus GCM), RSA, HMAC, hex versus Base64 encoding pitfalls, key rotation
Scripting or development ability enough to prototype, validate, and debug independently
Exposure to AML and sanctions screening, name matching, and how compliance controls surface as technical rejections