Payment Engineering
About the role
We are looking for a backend engineer who treats payment infrastructure as a system-design discipline. You will build Go services across on- and off-ramping, payment rails, KYC, disbursement, and partner integrations where correctness, traceability, and recovery matter as much as throughput.
This is a high-ownership role for an engineer who can move from an ambiguous product requirement to explicit invariants, failure modes, APIs, data models, and production telemetry. You will work with the existing Go platform and help evolve its architecture without losing operational clarity.
We work AI-first, with engineering judgment firmly in the loop. You should be able to set up a repository for effective AI collaboration, use tools such as CodeGraph to trace impact, generate and challenge test cases, and review every material change before it ships.
What you will do
- Design, build, and operate modern payment infrastructure with Go and TypeScript, applying strong system-design principles across distributed services, event-driven workflows, caching, logging, observability, and production reliability.
- Model payment lifecycles as explicit state machines with idempotent commands, durable events, safe retries, and clear recovery paths.
- Build reconciliation, ledger-adjacent, KYC, disbursement, and webhook workflows that remain diagnosable when partners or networks fail.
- Define service boundaries, API contracts, data ownership, and migration strategies through concise system-design documents.
- Strengthen security controls, observability, incident readiness, automated tests, and infrastructure practices across the payment platform.
- Use AI-assisted trace, implementation, test, and review loops while protecting secrets and keeping human approval at critical engineering gates.
What you bring
- 3+ years of backend experience for mid-level or 5+ years for senior, supported by clear production ownership and impact.
- Production experience with Go and TypeScript across distributed, event-driven systems, caching, logging, and observability.
- Strong system-design judgment around consistency, concurrency, queues, retries, ordering, backpressure, and partial failure.
- A correctness-first approach to payment infrastructure: precise money handling, idempotency, reconciliation, secure integrations, and auditable state.
- Disciplined testing and AI-first development with traceable context, critical review, and safe handling of credentials and customer data.
- Mid-level engineers deliver services independently; senior engineers lead architecture, cross-service execution, mentoring, and incident outcomes.
Strong additions
- Experience with payment processors, banking integrations, KYC providers, or disbursement platforms.
- Experience operating NATS JetStream, distributed locks with RedSync, or OpenTelemetry in production.
- A track record of simplifying a complex financial workflow without weakening its correctness guarantees.
What you can expect
- Direct ownership of consequential product and architecture decisions.
- A builder-led environment with short feedback loops and access to the full business context.
- Time and trust to improve engineering foundations, not only deliver feature tickets.
- A team that expects thoughtful use of modern AI tools and invests in making that workflow effective.
Core stack and skills
- Go
- TypeScript
- Payment Infrastructure
- System Design
- Distributed Systems
- Caching
- Observability
- AI-assisted Development