Guest Speaker & Workshop Instructor
I help engineering students and early developers build real intuition for how the internet, backends, and production systems actually work—so they can stop memorizing and start understanding.
I'm a backend software engineer from India. I studied engineering at an NIT, but what really shaped me wasn't competitive programming—it was curiosity. I kept asking how things like Google Meet, payment gateways, and large web platforms actually work under the hood.
Today I work as a backend developer. My day job is about APIs, databases, server-side architecture, and understanding how production systems behave. I'm not a celebrity engineer or a FAANG name. What I offer is clarity: I've spent a lot of time turning hard concepts into something a beginner can hold in their head.
While preparing for interviews and teaching myself, I noticed a pattern. Most students can write code, but they can't explain how the internet works. They don't really get HTTP vs HTTPS, concurrency, or how databases are used in real systems. System design interviews feel like a mystery. So I went deep—how HTTP evolved, how SSH works, what Docker is doing internally, what happens when you type a URL, how distributed systems behave—and I started explaining it in simple language to anyone who'd listen.
I now spend a large part of my time breaking down backend and systems topics for beginners: through posts, small tools, and teaching friends and juniors. I try to give mental models and real-world analogies, not another list of definitions to memorize.
Topics I'm comfortable covering for beginner to intermediate audiences (1st–4th year engineering students and early developers):
Academic CS often teaches syntax and theory. Students leave knowing how to write a loop or implement a data structure, but not how a request reaches their server, why HTTPS is different from HTTP, or what "concurrency" means when a thousand users hit an API at once.
That gap shows up in interviews, in first jobs, and in confidence. I focus on closing that gap: building intuition for how systems work in the real world, so students can reason about design, debug with purpose, and speak about backend and systems without panic.
I'm happy to adapt to what works for your college or community:
Students don't need more tutorials. They need clarity.
I aim for mental models, intuition, and real-world analogies—not memorization. Once you have a clear picture of how something works, the details stick. I'd rather your students leave with one solid mental model than with a page of notes they'll forget.
Engineering colleges, technical societies, cybersecurity clubs, and developer communities—I'd be glad to join and share what I know.