Software Engineer II

Senior Frontend Engineer

Software Engineer II with 5 years building backend services for a high-traffic food delivery platform in Bengaluru. Owns the order-allocation service in Go, handling peak dinner-hour load across 40+ cities.

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.

on GitHub · 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

Senior frontend engineer with six years building React and TypeScript applications for SaaS and fintech products. Leads the web platform for a B2B procurement tool, owns its component library and performance budgets, and reviews code for a squad of five.

// 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

3 years · current

Senior Frontend Engineer

Series-B B2B procurement SaaS company

Lead frontend architecture for a React and TypeScript web app used by around 600 enterprise buyers, reviewing work for five engineers.

2 years 6 months

Software Engineer – Frontend

Digital payments company

Developed merchant dashboard features for settlement reports and refunds, serving thousands of small merchants across India.

1 year

Associate Software Engineer

IT services company

Maintained Angular screens for an insurance client’s policy portal and resolved production tickets within agreed service levels.

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.

Emailyou@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