TL;DR
Our client, a FinTech in Gurugram, is hiring software engineers at several levels, from mid-level through senior. The work is backend and platform engineering on systems that move money, which means correctness matters more than velocity and the bar on testing is higher than most product engineering.
The client is confidential at this stage. We will tell you who it is before your profile goes anywhere.
What the work is
Backend services in a regulated money-movement environment. Depending on level and interest, that means transaction processing, ledger and reconciliation systems, integrations with banking and network partners, or the platform layer underneath all of it.
The distinguishing feature of this kind of engineering is that being wrong is expensive and often irreversible. A double-posted entry or a silently dropped webhook is not a bug you fix next sprint, it is money in the wrong place and a reconciliation break someone has to chase. Engineers who enjoy that constraint tend to do well here; engineers who find it slow do not.
What the client is looking for
Strong fundamentals in a backend language, with Java, Go or Python the most common routes in. Real distributed systems experience, meaning you have dealt with partial failure, idempotency and ordering rather than only read about them.
For senior hires, the client wants people who have designed systems rather than only built to someone else's design, and who can reason about failure modes before they happen.
Financial domain experience is useful but not required. Several of the strongest engineers we have placed into money movement came from other high-correctness domains and learned the finance quickly. What does not transfer is a background where approximate correctness was acceptable.
Levels and process
Hiring runs from mid-level through senior, and we will place you at the level the evidence supports rather than the one on your current title. A conversation with us, then a technical round with the client, then a system design discussion for senior profiles.
Related reading
Engineering in a regulated environment explains what changes when your code is in scope for an audit, and ledger architecture covers the correctness problems above in depth.
Interested in this role?
Apply once, to us. We confirm the client with you before anything is submitted. Because of application volume, only shortlisted candidates are contacted.