Software engineer in Pune. I build things end to end, and stay with them after they ship.
Now
I'm interning at Bajaj Finserv Health Limited, where I own five production services. One of them is the storage layer — the place every prescription, lab report and claim on the platform ends up. Around 209,000 uploads an hour, around the clock.
I inherited it running five different ways for five different teams. It runs one way now. Every upload is authenticated, scoped and audited, and when something goes wrong, I get the first call.
I don't really have a layer. Frontend, backend, the pipeline, the pod — wherever the problem is, I try to understand it the way someone who has lived there for years would.
On engineering
Engineering is closer to philosophy than most people admit. There are perfect ideas, but never a perfect implementation — so you think, you build, it breaks, and you build again.
Built to understand
- Servy
A reverse proxy, load balancer and static server in Go. I wanted to know what happens to the bytes.
- Incident engine
Listens to 10,000 failure signals a second over UDP, quiets the duplicates, keeps an immutable record of the rest.
- AWS, in Terraform
A multi-AZ environment with Kafka, Redis and DocumentDB. Nothing clicked in a console.
- temple
A key-value store in C++, written from scratch.
- TenderFlow
Role-based access and an auditable state machine for B2B tenders.
Off the clock
Mostly books about ships — marine engines, navigation, and how large machines stay reliable at sea.
Jamnagar, then Pune. A diploma in computer engineering, now a B.Tech at Symbiosis. Before this, backend work for a studio in Dubai, remotely.