Lead Software Engineer, Payments & Banking
Gravie, Remote
The role
We’re building the payments, banking, and financial accounting platform behind ICHRA NextGen, Gravie’s next-generation Individual Coverage Health Reimbursement Arrangement product. Our team owns obligations, scheduled payments, wallets, ACH processing, banking integrations, and the ledger that tracks every dollar. We are launching a new platform, migrating existing clients onto it, and continuing to ship new functionality at the same time.
We’re looking for a lead engineer who will own the technical health of this team. You will set the standard for how we design, build, review, and operate, and you will be the person the team and its partners rely on to get complex work across the line. You will write code and designs alongside the team while raising the quality of everything we ship.
What you will do
- Lead the team’s agentic engineering practice: how we write specifications, set guardrails and acceptance criteria, validate agent output, and keep ownership of quality, including guardrails for agents that touch money movement
- Own the technical direction and delivery quality of the team, and set the standard for design documents, code review, testing, and release discipline
- Lead the technical approach for migrating existing clients onto the new platform, including sequencing, risk identification, rollback planning, and data validation, while new functionality continues to ship
- Design and build distributed backend services, event-driven workers, REST APIs, and ledger and relational data models, with idempotency, retries, and failure handling designed in from the start
- Own banking and payment partner integrations, including third-party APIs, webhooks, and reconciliation
- Direct the day-to-day technical work of the engineers and contractors on the team, including onboarding, review, and knowledge transfer
- Partner with Product, QE, and other engineering teams to make tradeoffs visible, resolve cross-team dependencies, and keep commitments realistic
- Participate in the team’s on-call rotation, triage production issues, and drive the follow-up that prevents repeat incidents
What you need
- 8+ of software engineering experience, including technical leadership of a team and delivery of large, high-stakes initiatives such as platform launches or customer migrations
- Production work shipped mainly by directing AI agents, and the ability to walk us through how you specified, constrained, and validated it, and what went wrong
- Spec-first practice with explicit guardrails and acceptance criteria, and rigorous review of agent-written code for correctness. For money movement, you know that idempotency, ledger invariants, and reconciliation are where agent output cannot be trusted unreviewed