I'm a software engineer who's spent the last five years elbow-deep in the kind of backend systems where "it mostly works" isn't good enough — payroll and tax compliance for millions of people, where a bug doesn't just break a feature, it breaks someone's paycheck. That's kept me close to distributed systems, event-driven architecture, and the unglamorous work of making a pipeline trustworthy under real load.

I did my Master's at NIT Calicut, and these days most of my thinking goes into Java, Spring Boot, and the gap between "elegant" and "actually ships." I recently wrote a book — Java Interviews: Beyond the Boilerplate Questions — mostly because I got tired of watching good engineers get tripped up by interview questions that have nothing to do with how the job actually works.

• 👨‍🏫 I like mentoring more than I expected to — there's something satisfying about watching someone go from "how does this even work" to explaining it back to you better than you did.
• 🌙 Night owl. My best debugging happens after 11pm, for reasons I haven't investigated.
• 🎬 Serious movie person. 🎶 Even more serious about old Bollywood music.
• ☕ Runs on coffee and chai, roughly in that order depending on the hour.
• 🌍 I like contributing to open source when I get the chance, and write about system design and distributed systems on LinkedIn.
• 🤔 Perpetually curious about what AI tooling actually changes in day-to-day engineering, as opposed to what it's supposed to change.

Building distributed, event-driven systems for enterprise payroll — pipelines that move millions of records a day across a dozen-plus countries — and lately, AI-assisted developer tooling that's been quietly saving my team real hours every week. Picked up a couple of cloud certs along the way too (Oracle OCI Multicloud Architect Professional, SnowPro Associate) if that's your thing.

Languages

Frameworks & data

Cloud & ops

AI tools I actually use

Java Interviews: Beyond the Boilerplate Questions — a field guide to the Java and Spring Boot interviews that actually happen at the senior level: past the LeetCode round and into JVM internals, distributed-systems tradeoffs, and the follow-up questions that separate a pass from an offer.