I build systems
that don't break
under pressure.
Backend and distributed systems — caching, real-time engines, concurrency. 18 months in production, three systems shipped solo since.
Experience
LMNAs Cloud Solutions
Software Engineer · Jun 2024 – Nov 2025 · Chennai, Tamil NaduEighteen months shipping backend systems that couldn't afford to fail.
A distributed lock collapsed concurrent cache misses into a single database read, instead of letting them stampede it.
A transactional outbox re-checked SAP before every retry, so hours of downstream downtime never meant lost data.
Event-ID dedup and unique constraints on email and phone kept the merge honest.
A reusable template re-priced per customer at creation, so no stale pricing slipped through.
Toolbox
What I build with.
Languages & frameworks
Data & messaging
Distributed systems
Tools & practices
Timeline
The build log.
Slipstream — real-time decisioning engine
Immutable snapshot hot-swapped atomically; a lock-free, allocation-free read path under concurrent traffic. Live storefront and console.
TaskMesh — distributed task engine
Kafka + Redis coordination, at-least-once consumption with idempotent handlers — a worker lost mid-batch triggers redelivery, never a drop or a double-apply.
Shortly — URL shortener
Optimistic locking on the write path, so click counters stay correct under concurrent writes without serializing the redirect path.
Left LMNAs Cloud Solutions, started building solo
Eighteen months in production taught me what breaks under load. Since then: three distributed systems, built and shipped independently.
Get in touch
Got something that needs to stay correct under load?
Open to backend engineering roles. Based in Bengaluru, India — happy to work remote.