Hi, I'm Aakrit Subedi 👋
I build systems from idea to production.
I like figuring out how systems should work, getting into the code, and solving the problems that come with running them at scale. From engineering leadership at Naamche through its acquisition, to building LLM products for real users and a study platform trusted by 14K+ engineering students.
- AiChatacquired by reAlphamost recent
- Led the rebuild of AIChat around LLMs, working with a cross-country team across India, Nepal, Singapore, and the US. Expanded capabilities across WhatsApp, Messenger, and Instagram, built internal tools, ran product experiments, handled client issues, and solved scaling challenges as usage and clients grew.
- Naamche → reAlphaengineering leadership
- Joined as a founding team member of 7 and grew with the company to 75+ employees through its acquisition by reAlpha. Led engineering across multiple products, staying hands-on with architecture, code, and US clients. Mentored engineers, built teams, and interviewed new talent.
- BCTNotespersonal project14K+ students
- Started it because, as a student, I couldn't find decent notes and past papers in one place. Designed and built the whole thing; it has grown into a platform where 14K+ engineering students share and use study materials.
01
02
03a bit more
My first website was in grade 9 ... loud colours, marquee text scrolling in both directions, and too many photos. It was terrible, but I had a lot of fun making it. At grade 10, a small school management system in QBASIC for my final project, mostly because I was curious to see how far I could take it.
That habit followed me into engineering college. Every semester meant a few more projects — some for coursework, most just for myself because building the thing was the only way the fundamentals ever really stuck. A few of them made it to intra-college competitions, and a few came back with prizes — a nice cherry on top of something I was going to build anyway.
I started interning right after college. That's where the basics got sharpened and where I learned how the industry actually works: shipping to real users, reviews, deadlines, and everything that happens after the code is merged.
Two years in, I joined Naamche as a founding engineer — bringing what I'd picked up from industry while keeping the startup instinct alive: move fast, own the problem, figure it out. Learning new things, shipping new features, and taking on new challenges. The company grew, and I grew with it.
Weekends still go to side projects. Something I learn at work finds its way into a personal project, and something I built on a weekend finds its way back into work. I like pulling new tools and frameworks apart to understand how they actually work and where they make sense.
And whatever I pick up, I try to pass on through meetups, talks, and long conversations with engineering students who are somewhere around where I started.