Codex
Software Engineer
- Confirmed live in the last 24 hours
- No salary listed
- Mid level
- Full-time
- Remote · Flexible
- 6+ yrs exp
- Added 1 month ago
About this role
Join Codex as a Software Engineer to design and own financial partner integrations and operational automation for a stablecoin-based cross-border payments platform. You'll build robust systems connecting fiat and crypto rails, eliminate manual workflows, and establish engineering standards for money movement infrastructure.
What you'll do
- Own end-to-end integrations with banks, payment providers, and liquidity venues from API design through production hardening and reconciliation
- Build messaging systems with signature verification, replay protection, and multi-layer failure handling for real-world vendor scenarios
- Maintain reconciliation logic across all payment rails, managing fees, settlement windows, and exception handling
- Systematically replace manual operational workflows with automation and self-service tooling for compliance and back-office teams
- Design and implement treasury and liquidity automation including position management, routing, and risk controls
- Set engineering standards for payment integrations: idempotency, audit trails, fail-closed design, and deterministic orchestration
What they're looking for
- Durable workflow orchestration (Temporal preferred)
- TypeScript/Node.js and PostgreSQL for financial systems
- Cross-border payments, stablecoins, or FX infrastructure
- Both crypto (Ethereum, Tron, Solana, DeFi) and fiat rails (SWIFT, SEPA, FPS, CHATS)
- Third-party API integration with unreliable vendors
- Exact decimal arithmetic and append-only audit trail design
- Webhook reliability and schema versioning
- Security hardening and fail-closed system design
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Codex
- Industry
- Technology & Software
Likely interview questions
- Describe a complex third-party API integration you've built where documentation was incomplete or schemas changed post-launch — how did you handle the instability?
- Walk us through your experience with Temporal or similar durable orchestration frameworks — what patterns have you used for safe workflow versioning and compensation logic?