TODO — replace with a real 2-3 sentence description of what the project does, why you built it, and what was technically interesting about it.
- TODO
- TODO
Hi, I'm
Software Engineer
I like building reliable systems and understanding what happens underneath them — the backend services, the infrastructure they run on, and everything that keeps them up at 3am.
// main quests: backend systems, distributed systems, infrastructure
// side quests: birdwatching, half marathons, and stubborn calisthenics goals
I'm drawn to the parts of software that most users never see — the services underneath a product, the way they talk to each other, and what breaks when they don't. Most of my time goes into backend systems, distributed systems, and the infrastructure that keeps them running.
Funny enough, both my parents taught computer science — and still steered me toward Bio-Maths in school. Right before college, I taught myself C out of curiosity anyway, and that was that. The rest is history.
Outside of work, I'm usually outdoors — birdwatching and wildlife photography get me up early on weekends, and running and lifting take up the rest of it. I recently ran my first half marathon, and calisthenics is my current strength-training obsession.
B.Tech, Electronics & Communication Engineering
Mar Athanasius College of Engineering, Kerala · Aug 2019 — June 2023
B.Sc, Data Science & Applications (Online)
Indian Institute of Technology, Madras · Jan 2021 — Present
Software Engineer II
Trivandrum, India
Feb 2026 — Present
Associate Software Engineer
Kochi, India
Sept 2023 — Feb 2026
TODO — replace with a real 2-3 sentence description of what the project does, why you built it, and what was technically interesting about it.
TODO — replace with a real 2-3 sentence description of what the project does, why you built it, and what was technically interesting about it.
TODO — replace with a real 2-3 sentence description of what the project does, why you built it, and what was technically interesting about it.
Things I'm actively reading about, building small projects around, or otherwise trying to get better at right now.
I'm always happy to talk about backend systems, infrastructure, or interesting engineering problems. The easiest way to reach me is by email.