Senior Backend Engineer

• Review and harden AI-generated backend code daily — mandatory type-check gates, no empty catch blocks, no parseFloat on monetary values (everything is integer cents)
• Own production monitoring, alerting, and incident response — Sentry, structured logging (zerolog), on-call
• Manage database performance — query optimization, migration safety, connection pooling on Neon serverless (dual-driver: HTTP reads, WebSocket transactions)
• Operate and upgrade Hyperswitch — our open-source payment orchestrator running on Docker/Railway
• you'll manage the service lifecycle and eventually own its Kubernetes migration
• Make infrastructure decisions — scaling strategy, service boundaries, deployment pipeline improvements
• Ensure payment flow correctness — idempotency, state machine transitions, settlement reconciliation, ledger integrity
• Own secrets and environment management — Doppler sync across Railway, Vercel, and AWS
• Keep engineering documentation current — architecture decisions, runbooks, API contracts live in Outline and must stay in sync with the code

• 5+ years backend engineering
• TypeScript — advanced: you can read Hono.js routes, Drizzle schemas, and Zod validators without ramp-up time
• PostgreSQL — deep: query tuning, transaction isolation levels, zero-downtime migrations, connection pooling
• Production operations — you've been on-call, triaged multi-service incidents, built monitoring and alerting from scratch
• Docker — comfortable managing and debugging containerized services
• CI/CD — GitHub Actions or equivalent
• you understand what happens when a deploy breaks
• Monorepo experience — pnpm workspaces or equivalent
• you know how to work cleanly across package boundaries
• Comfortable reviewing AI-generated code — not just "using Copilot," but auditing code that AI wrote from spec to production: catching type gaps, missing error paths, incorrect assumptions about external APIs

• Go — our API gateway is Go
• you don't need to be expert but readable is the bar
• Payments / fintech domain — PSP integrations, idempotency patterns, ledger design, reconciliation
• Temporal or any workflow engine — Temporal Cloud is core to our async flows
• Kubernetes — Hyperswitch migration to ECS/K8s is on the roadmap
• Cloudflare Workers — we're expanding edge usage
• Hyperswitch or any open-source payment orchestrator experience

Equity that means something. First engineering hire at an early-stage payments company. Generous allocation, standard vesting, priced at the ground floor.