You own collections, the revenue split between station and network, payouts, reconciliation and the ledger. Every rupee a farmer pays passes through your code. This is the one service where a defect is a loss rather than an inconvenience, and it is reviewed by two people every single time.
Key responsibilities
- Own settlement and payments end to end, with the Technical Lead as your named backup and your reviewer on every merge
- Hold every monetary value in integer paise, enforced by a check in the pipeline
- Make every settlement run idempotent and replayable, producing a byte-identical statement from the same inputs
- Double-enter every monetary write into an append-only ledger — rows are never updated, only compensated
- Run a nightly invariant job that asserts collections minus payouts minus escrow equals zero, and pages when it does not
- Build the reconciliation engine and the variance escalation ladder
- Reach full branch coverage on the split, rounding and ledger paths
Eligibility
- Four to six years in backend engineering on a Spring-class framework
- You have shipped money code — settlement, payouts, reconciliation or order-to-cash
- You can talk about a rounding or reversal bug you personally caused or fixed
- Robust SQL on a Postgres-class database
- You write the negative tests unprompted
What you get
- The single most consequential service in the platform, owned outright
- A review culture that takes your work as seriously as you do
How the process runs
- Fill in the short form on this page.
- We read it ourselves. Every application is read.
- If we want to meet you, we call you.