Nitesh Ranjan Engineering & Delivery Lead

Jaipur, India · Remote · Contract or full-time

I build the systems that move other people’s money.

Engineering & Delivery Lead · 16+ years · Payments, settlement and real-time platforms

For the last two years I have been the sole engineering owner of a multi-tenant, white-label platform: one backend serving fifteen brands, five payment rails, a house-run live casino, four in-house games and a sports data pipeline that publishes prices in under a second. Before that, sixteen years of delivery — an eight-engineer HIPAA healthcare team, national government data programmes, and fourteen engineers building for global clients.

Server-authoritative money Multi-tenant by domain Settlement & reconciliation Realtime at scale HIPAA · Government · Fintech
Production, verified SEP 2026
Years in software
16+
Systems on this page
57
Live consumer brands
15+
Containers in production
114
Mapped live domains
100+
Payment rails deployed
5
Largest team led
14
Industries delivered in
  • Healthcare (HIPAA)
  • Government
  • Fintech & payments
  • Real-money gaming
  • SaaS
  • E-commerce
  • Logistics

Engagements

Three ways I work with clients

Remote, IST, with routine overlap into UK, EU, Gulf and US-East hours. Tell me the shape of the problem and I will tell you which of these fits.

Ongoing

Engineering & delivery lead

I own a platform or a workstream end to end — scope, estimation, release sequencing, production accountability, and the team where there is one. The single point of contact between your stakeholders and the people writing the code, technical enough to challenge an estimate rather than relay it.

Good fit ifYou have engineers but nobody holding the dates, or a platform with no clear owner.
2 – 6 weeks

Product rescue & takeover

A product that is late, unstable, or inherited from whoever left. I audit the running system rather than the documentation, hand back an architecture and a delivery plan with real dates, then execute the first slice myself — so the plan is proven instead of promised.

Good fit ifThe last estimate slipped twice and nobody can say why with confidence.
Fixed scope

Payments & settlement audit

I read the money paths — deposit, credit, exposure, settlement, payout — reproduce every hole against a disposable copy of your database, and hand back written findings with the reproduction and the fix beside each one. Built from defect classes I have found in live production, not from a checklist.

Good fit ifYour ledger and your bank statement disagree and nobody has found the reason.

Career

Sixteen years, five chapters

Every role below is delivery accountability, not advisory. The current engagement is solo by design; the three before it were teams.

Portfolio

Everything I have built and shipped

57 systems. Filter by domain or search the stack. Open any card for the full account — what it does, how it is built, and what went wrong on the way.

Production screens

Real screens, captured from live servers

Captured through each product’s own demo login, so no customer data appears. Client logos and wordmarks are blurred — the work is the point, not the brand on it.

How I work

Rules I hold when money is on the line

These are not slogans. Each one comes from a production defect that cost real money before it was closed.

The client never computes a price

Quote, exposure, book position and payout are derived on the server from one definition and one endpoint. Every time a UI has been allowed to re-derive a payout, it has eventually disagreed with the ledger — and the ledger is what pays out.

Money rules live in the database, not the convention

On the referral platform, one function is the only writer of the ledger and execute is revoked from every client role. A withdrawal takes a row lock, proven by two real concurrent sessions rather than by reading the code.

Measure it; do not assume it

The crash game’s multiplier curve was read off sixteen timestamped samples of the reference game, then pinned as a unit test. When a second method suggested a different constant, I kept the one that rested on fewer assumptions and turned both sample sets into tests.

A credit must be single-use

One bank notification can approve exactly one deposit order. Getting this wrong is not a display bug — it is one payment crediting several accounts, and it is the single most expensive class of defect I have found in payments.

Roll back by routing, not by redeploy

The gateway redesign ran as a second container against the same database. A host moves between the old and new interface by changing one routing target. No deploy to go forward, no deploy to come back.

Verify before claiming it works

A green mirror proves nothing about the thing it mirrors. I check the running system — the response on the wire, the row in the table, the money actually moved — before saying a thing is done.

The path every rupee takes: quote→ place→ exposure→ result→ settle→ book P&L→ payout server-authoritative at every step

Toolkit

What I actually ship with

Listed because I have shipped production systems on them, not because I have read the documentation.

Contact

Available for contract and consulting work

I take on senior engineering and delivery work: owning a platform end to end, leading a team through a delivery that has slipped, or a fixed-scope audit of a settlement, reconciliation or payment flow that someone suspects is leaking money. Remote, IST, with routine overlap into UK, EU, Gulf and US-East hours.

The fastest way to judge whether I am useful to you is to pick any card above and ask me what broke in it. There is a specific answer for every one.

BasedJaipur, India · IST
NoticeImmediate