What I build, end to end
At 2 years in, most engineers have touched one slice of one codebase. I've shipped a whole product — from the database to the deploy to the customer call that changed it.
Maahita Technologies · School ERP
An early-stage SaaS product run by three founders investing in the idea directly. No big roadmap handed down, no perfect process. We learn from real schools, evolve the product, and ship. I've been on it since my 4th year of BTech, across every layer above.
Maahita Technologies · Vinodam
Born from a principal's challenge: TV-show-style quizzes for school events. I built the prototype in secret — three synchronized screens (admin control, projector display, participant phones) with real-time scoring, timers, and leaderboards. The team adopted it as an official product, and it ran its first live event with 300 students without breaking.
Client and product work with a dedicated breakdown — the problem, the build, and where it landed.
A centralized operations platform that turns shift handovers, testing, and production updates into one structured, auditable system.
Helping child care centers stay connected with parents through real-time updates and automated communication.
I came in with basic programming and almost no production experience. I learned by shipping — and by getting my PRs rejected by engineers with 10 to 14 years in the industry.
I build with AI in the loop (Gemini, Claude) but never blindly. Every line goes through senior review. The AI gets me moving fast. The reviews are where I actually understand what I built.
They taught me code reviews, architecture thinking, tradeoffs, maintainability, and product thinking. The kind of thing you only learn standing next to someone who's seen it break before.
Built for my father
My father is a paint contractor. Every time he finished painting a bank branch, someone had to make the bill for the owner — material lists, work measurements, totals. That someone was me: typing every line into MS Word, colouring fonts, adjusting sizes, running each calculation on a phone calculator, exporting a PDF. I made calculation mistakes more than once, and my father let me know about it.
So I built the proper fix: an Android app (Kotlin, Jetpack Compose) and a web app (Next.js) sharing one Firestore database in real time — multi-section bills, work measurements, per-day rates, advances, and a one-tap PDF whose maths is never wrong. A bill that used to eat an evening now takes minutes.
Built for myself — now my friends use it
I was spending a lot, lending money to friends and forgetting about it. My system was a notepad app on my phone and redoing the maths by hand — who owes me, what I owe, constant confusion.
Roots is the fix: a simple expense tracker that also tracks lent and borrowed money per person, with repayments, budgets, recurring expenses, and charts — offline-first, installable on Android. I kept it simple enough that my friends now use it daily too.