Senior Software Engineer (Payments)
Confirmed on the employer's own hiring board on Oct 10, 2026. First seen by Alion on Aug 6, 2026.
Join GovWell, a company dedicated to improving local government operations. As a Senior Software Engineer (Payments), you will design and build the financial architecture that serves as the backbone of our platform. You will have the opportunity to shape the core architecture, establish technical standards, and work directly with finance teams and municipal staff. This role offers autonomy, ownership, and the chance to make a real impact in the world of local government.
Missions
- Design and build the financial architecture for GovWell, establishing a system of record for every dollar municipalities collect, refund, or hold.
- Develop a fully auditable, mathematically consistent ledger from the ground up, ensuring trust from finance teams.
- Lead the migration of payments to the new system, collaborating with finance teams, municipal staff, and engineers.
Profil recherché
- You align closely with our Core Values- You think in terms of invariants and edge cases - what happens when a webhook fires twice, when a fee schedule changes mid-invoice, when a refund needs to partially reverse a payment that's already been partially paid
- You have real opinions about how a payments system should be architected, and you want a role where you can bring them, not just implement someone else's spec
- You're excited to work with the latest AI models, both in the product and in your own development workflow
- You've owned a large product area end-to-end and can point to something specific you shipped and stayed accountable for
- Experience designing financial or transactional systems where correctness isn't optional - payments, billing, ledgers, or similar domains where an unbalanced number is a real problem, not a bug ticket
- Strong product instincts: you ask questions until you actually understand the customer's problem, not just the ticket description
- Experience with idempotency, webhooks, and payment processor integrations (Stripe, Finix, or similar) is a strong plus
- Comfortable with ambiguity at the domain-design level: this isn't "build this feature," it's "help decide what the right abstraction is," and you find that exciting rather than uncomfortable