status: open to senior/staff backend roles · Pune / remote

I write boring code that survives 3 a.m.

Backend engineer, eight years. Payment and logistics systems doing 40M requests a day, 99.98% uptime on services I own — built by choosing dull, proven tools and deleting more code than I write. Clever is a liability at scale; boring is a feature.

Hire me git log ↓

40M/dayRequests served

99.98%Uptime owned, 2 yrs

8yrsProduction backend

-38%Infra cost, last role

ls ./systems

Things I've built that stayed up

fintech · 2023–now

Payments core

Rebuilt a settlement pipeline handling ₹900Cr/month from a nightly batch job into an event-driven system. Reconciliation went from T+2 to same-hour.

40M req/day · p99 41ms

logistics · 2020–23

Routing & allocation engine

Order-to-rider allocation for a 14-city fleet. The interesting part wasn't the algorithm — it was degrading gracefully when GPS data lied.

120k orders/day · 3-person team

side project · open source

ledgerdiff

A CLI that diffs double-entry ledgers and finds where reconciliation broke. Built for my own debugging; other fintech teams found it.

1.1k GitHub stars · MIT

cat stack.md

Tools, with honest depth

"Familiar with everything" means expert at nothing. Here's the real distribution.

Tool	Depth	Evidence
Go	██████████ daily, 6 yrs	Everything at current role; I've read the runtime scheduler source
PostgreSQL	█████████░ deep	Query plans, partitioning, logical replication in production
Kafka	████████░░ production	Event backbone at 2 jobs; know exactly where it hurts
Kubernetes / AWS	██████░░░░ operator	I run services on it well; I don't administer clusters
Python	█████░░░░░ tooling	Scripts, data jobs, glue — not my production language
Frontend	███░░░░░░░ survival	Can ship an internal dashboard; please don't ship my CSS

Deliberately missing: the framework-of-the-month. I adopt tools after their second major version, not their launch post.

grep -i incident war-stories.log

Three incidents that taught me

SEV-1 · payment gateway · 2:47 a.m.

The retry storm that DDoSed ourselves

A partner bank slowed to 30s responses; our aggressive retries tripled the load and took down our own gateway. I led the call: circuit breakers in by 4 a.m., and the blameless postmortem produced our now-standard backoff library. The bug wasn't the code — it was that nobody owned retry policy.

MTTR 84 min · runbook born

SEV-2 · silent data drift · found on a Sunday

The reconciliation that was off by ₹4

Four rupees, out of ₹30Cr daily. Everyone wanted to ignore it; I didn't. Three days of digging found a float-rounding bug that would have compounded to lakhs by year-end. Wrote the ledgerdiff tool from this. Small discrepancies are big bugs with good manners.

Bug class eliminated

the one I caused · migration · 2019

The DELETE without a WHERE clause (staging, barely)

Early career: ran a cleanup script against what I was sure was staging. It was staging — but only because a VPN quirk saved me. I built myself a guardrail harness that day (read-only prod by default, typed confirmation for writes) and I've carried it to every job since. Fear is a fine teacher, once.

Paranoia, institutionalised

Photograph — desk setup acceptable, hoodie optional

whoami

Why backend

I got hooked in second year of college when my hostel's mess-menu website crashed under load — 400 concurrent users, all checking if it was paneer day. I spent a weekend learning why, and that question — "why did it fall over, and what would make it not?" — has quietly paid my rent for eight years.

I like the parts of engineering with truth in them: latency numbers, ledgers that balance, postmortems without blame. I write design docs before code, delete code without sentiment, and believe the best on-call week is a boring one.

// the system isn't done when there's nothing left to add.// it's done when there's nothing left to page you.

B.E. Computer Science · COEP PuneAWS SA AssociateCKA (expired, honestly)EN · HI · MR

experience

2023 — NOW

Senior Backend Engineer

Fintech (payments), Pune

Own settlement + refunds services · p99 220→41ms · infra cost −38% · mentor 3 engineers.

2020 — 2023

Backend Engineer II

Logistics startup, Bengaluru

Routing engine, 120k orders/day · led the monolith→services split that we did NOT regret (we split 4 services, not 40).

2018 — 2020

Software Engineer

IT services, Pune

Java + Postgres for a European bank. Unfashionable, and where I learned transactions properly.

code reviews of me

engineering manager

"Rohan's superpower is saying 'we don't need this' in design reviews and being right. His services are the ones nobody thinks about — which in infrastructure is the highest compliment there is."

EM, payments platformCurrent manager · reference on request

junior engineer he mentored

"He reviewed my PRs like they mattered — questions, not verdicts. A year in, my code stopped needing his questions. That was the point, he said."

SDE-1 → SDE-2 under his mentorshipNow owns a service herself

ping rohan

Open a connection

Senior/staff backend roles — Pune, or remote with async-friendly culture. Code samples, design docs (redacted) and references ready. No take-home longer than 4 hours, respectfully.

Emailrohan.builds@example.comFastest · replies within a day

GitHubgithub.com/rohan-buildsledgerdiff + green squares, mostly

LinkedInlinkedin.com/in/rohanverma-dev

RésuméDownload PDFOne page, no logos

Notice60 days · includes proper handover docs