Curri · posted · checked
Senior Software Engineer, Finance
Node.jsPostgresReactRedisTypeScript$185k – $215kRemote · United StatesSenior
Who can apply
Remote · United States
Location: Remote - United States
About the role:
Curri is seeking a Senior Software Engineer, Finance to own the systems behind how money moves through the company, from the price a customer is quoted to what lands in our ERP. Every Curri delivery is a financial transaction: a customer gets billed, a driver gets paid, and finance closes the books. As we grow, our hardest problems are about money: getting paid faster, paying drivers accurately and on time, and giving finance numbers they can trust. This engineer will sit with the finance team, scope the problem directly, and ship the fix in weekly loops with AI as a force multiplier.
What you will do:
Own finance problems end to end, working directly with finance, ops, sales, customers, and drivers to scope, ship, measure, and iterate on fixes.
Map and improve how financial data flows from quote and booking through invoicing, collections, and driver payouts into our ERP and reporting.
Build and expand integrations with payment processors, ERP and accounting tools, invoicing, and driver payout systems.
Ship smarter invoicing and billing options that make it easier for customers to pay on time and bring down DSO.
Build reconciliation, audit trails, and automated checks so every cent is accounted for and problems surface before finance finds them.
Ship full-stack in weekly loops across Go, TypeScript, Node, Postgres, NATS, Redis, and React/React Native, using Claude Code, Cursor, and Claude daily, and partner with Platform and Infrastructure on architectural decisions that scale.
What you need to have:
5+ years of full-stack engineering experience across backend services (Go, Node, TypeScript, Postgres) and React, with a product engineer mindset that owns outcomes rather than tickets and is comfortable starting from a Slack message instead of a fully written spec.
Strong systems thinking for money flows, including designing for retries, duplicate payment prevention, and data consistency across systems, with judgment about when to move fast and when to build for scale.
Rigorous attention to financial data quality, treating numbers as something that has to be right rather than roughly right and building in checks, reconciliation, and audit trails by default.