$ whoami
Nahyan M · @nahyan0077
Software Engineer & AI Engineer — I pivoted from an MSc in Physics into software, taught myself the stack, and now build production systems at the intersection of engineering and applied AI.

A bit about me
I'm a self-taught Software and AI engineer. My path into tech didn't follow the typical script — I completed an MSc in Physics at Central University of Tamil Nadu, then made a deliberate pivot into software. Not because I had to, but because I was already spending more time writing code than doing anything else. That pull was the signal.
I went through an intensive full-stack program at Brototype, but the real learning happened the way it always does: by building things, breaking them, and figuring out why. I went deep on the MERN stack — not just the happy path, but the architecture underneath it. Clean architecture, microservices, real-time systems with WebRTC and Kafka, cloud deployments on Azure and AWS. I wanted to understand how production software actually holds together, not just how to make a demo work.
Now I work as a Software Engineer at an AI company in Bangalore, which is exactly where I wanted to be. The intersection of solid engineering and applied AI is where the most interesting problems live. I write TypeScript and Node.js daily, I care about systems that are maintainable and testable, and I'm constantly exploring how LLMs can be wired into real products — not just as demos, but as things people actually rely on.
The physics background is more useful than it sounds. It trained a way of thinking — breaking a problem down to fundamentals before reaching for a tool, staying skeptical of the first answer, and sitting with uncertainty until something actually makes sense. That mindset travels well into engineering.
A few moments
The short timeline
Software Engineer at an AI company
Joined an AI-focused product company in Bangalore. Working across the full stack — TypeScript, Node.js, React — on tools that wire LLMs and intelligent automation into real workflows. Exactly where the interesting problems are.
First professional role
Landed my first engineering job after completing Brototype's intensive MERN program. Went from building projects to owning features in a real codebase, real users, real consequences. The gap between training and production turned out to be where most of the learning happens.
Brototype — going deep on the stack
Joined Brototype's intensive full-stack program and treated it as a launchpad, not a course. Built EduVerse — a full e-learning platform with microservices, Kafka, WebRTC video calls, and a CI/CD pipeline on Azure. Built DropShip — a production e-commerce platform deployed on AWS EC2. The goal was always: understand the architecture, not just make it work.
MSc Physics → decided to pivot
Completed a postgraduate degree in Physics at Central University of Tamil Nadu. By the time I finished, I was already spending more hours writing code than studying physics. The pivot wasn't a backup plan — it was where the energy was pointing.
Self-taught from zero
Started learning to code independently — no bootcamp, no formal CS degree, just documentation, projects, and stubbornness. JavaScript first, then Node.js, then everything else. Built small projects, broke them, understood why, rebuilt them better.
Currently
AI-powered tools that ship to production
Wiring LLMs into real workflows — not just demos, but things people rely on.
System Design Interview by Alex Xu
Sharpening the architecture muscle. Patterns that scale.
RAG pipelines and vector search
Building context-aware AI systems with embeddings and retrieval.