Senior Software Engineer, Payments

• We have a hybrid work culture that combines regular in-person collaboration at our New York City office (3+ days per week) with flexibility to work remotely.
• This role reports directly to our CTO and Co-Founder, Ben Cohen.
• WHY GOVWELL?
• Design the financial architecture GovWell runs on — the system of record for every dollar municipalities collect, refund, or hold on someone's behalf.
• Build a real ledger from the ground up: one that's fully auditable, mathematically consistent, and trusted by finance teams without a second look.
• Turn fee calculation into a system that computes with precision, instead of something staff track by hand or reconstruct after the fact.
• Make partial payments, deposits, and refunds first-class citizens of the platform, not workarounds bolted on after the core system was built.
• Own the migration from where payments live today to where they need to be — with real customers, real money, and no room for a clean-slate do-over.
• Partner directly with the people who depend on this system being right: finance teams, municipal staff, and the engineers building the workflows this ledger will support.
• Set the technical standard other engineers build against once this domain exists — you're not implementing someone else's design, you're establishing it.
• 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.
• 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.
• 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.
• Experience with idempotency, webhooks, and payment processor integrations (Stripe, Finix, or similar) is a strong plus.
• 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'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.
• Strong product instincts: you ask questions until you actually understand the customer's problem, not just the ticket description.
• Finix (payments processing)

None flagged.