A Life in Code, Ownership, and the Habit of Starting Again
“Close enough to be true, far enough to be useful.”
I have spent most of my adult life building things that other people use without ever thinking about the person who built them. A form loads in under a second, an exam runs without a single glitch, a support ticket gets answered before the customer has finished their coffee, and nobody claps. That is what "it works" means. The absence of complaint is the applause, and you learn, slowly, to hear it that way.
This is not a story about a straight line. There is a college placement season that went better than I expected, a first job that taught me more than any course did, a pandemic that became an opening instead of a setback, a genuine detour into cybersecurity that never became my career but shaped how I think about every system I've built since, a leadership role I grew into rather than arrived in fully formed, two products I built and own outside of anyone else's permission, and one startup that did not survive a year. I'm including that startup in as much detail as the ones that worked, because leaving it out would make this a highlight reel instead of a record.
“Surat never taught me that a good product sells itself. It taught me the opposite, every single day.”
Surat's business instinct — build it, sell it, improve it, build the next thing — was the air I grew up in. I didn't come from a family of engineers. I had ordinary access to a computer and an unreasonable amount of patience for staring at a broken thing until it worked.
“A 9.0 CGPA didn't make me employable. Four straight years of refusing to cut corners did.”
B.E. in Information Technology, CGPA 9.0/10, First Class with Distinction — and the highest placement package offered in my batch. Not from one brilliant semester, but from treating consistency, quietly, as a competitive advantage.
“I didn't beat my first interview with talent. I beat it with the same handful of problems, solved two hundred times, until none of them looked new anymore.”
DSA prep was repetition with attention — pattern recognition across arrays, trees, graphs, and dynamic programming until a "novel" problem was just a familiar shape in a different costume. Landed the first offer at HQ Infosystem.
“Fifteen client projects taught me the same lesson fifteen times: edtech, logistics, and fintech are the same problem, wearing three different costumes.”
Fifteen-plus full-stack applications across edtech, logistics, fintech, and e-commerce. Payment integrations with Stripe, Razorpay, and Twilio. REST APIs handling 50K+ daily requests. The years where scale stopped being a textbook idea.
“A crisis doesn't ask if you're ready. It only asks what you do next.”
Instead of waiting out one of the worst hiring environments in recent memory, I went deeper into frameworks and tools I'd only used at a surface level — no deadline, no client, just depth. The difference showed up later, when the market recovered.
“I fell in love with breaking things a full year before it occurred to me that someone might pay me to do it.”
A self-directed pull toward understanding how systems fail. Top 6% Global Rank on TryHackMe in 2021, Advent of Cyber certified in 2022. Never became the career — became a permanent second lens underneath every architecture decision since.
“Nobody promoted me into leadership. I just started making the decisions nobody else wanted to own, and the title eventually agreed with me.”
The shift from developer to lead isn't a shift in code difficulty — it's a shift in how many decisions other people are waiting on you to make, and how far a wrong one travels. Mentored 5+ engineers, scaled systems to 100K concurrent users at 99.8% uptime.
“401,000 users don't know or care that I own this product. They only notice when the page loads in 1.2 seconds instead of 3.2.”
A Google Forms analytics and AI extension platform, now at 401K+ users, 579K forms, 8.7M respondents, 3x revenue growth. Every architecture, performance, and roadmap decision starts and ends with me.
“I gave a machine the job of writing exam questions. It took thirty seconds. It used to take thirty minutes, and none of those minutes were mine to spare.”
An AI-first exam and quiz platform with proctoring, now handling 400K+ student exams. No employer's budget, no one else's decision — it exists because I decided it should, and then built it, model-agnostic across OpenAI, Claude, and Gemini.
“Nobody assigned me a support ticket problem. I just couldn't stand watching a customer wait two days for something a weekend could fix.”
A multi-tenant AI support agent platform, built entirely on weekends for no reason except curiosity. Cuts support engineer time by ~90%; tickets resolved in hours instead of one to two days.
“A startup doesn't fail in one dramatic moment. It fails the same quiet way it almost succeeds: one ordinary week at a time.”
A startup studio in Surat, run alongside the full-time role at ExpressTech. Built the BPS crypto trading platform (10K+ users, $2M+ volume) and trained 6–7 interns, all now well-settled. The studio closed after about a year. It did not survive — and I'm not going to pretend otherwise.
“A chart that lags is the only kind of slow database a user can actually see with their own eyes.”
Years with Highcharts rendering millions of points without grinding to a halt, Mapbox geofencing and live tracking, Three.js for embedded 3D, Framer Motion and Lenis for interface feel. The skill that compounds isn't any one tool — it's becoming fluent in the next one, fast.
“The fastest way to help someone is to hand them the answer. The only way to actually help them is to resist that urge.”
Good mentorship isn't transferring your own solution to someone else's problem. It's building the muscle in someone else to arrive at solutions like it on their own — even when, especially when, it would be faster to just tell them.
“I don't know what I'm building next. I know exactly how I'll start: badly, immediately, and without waiting to feel ready.”
ExtendedForms.io keeps growing. Quzo.ai keeps handling more exams every term. MB Systems is closed, and its lessons are still being processed with each new decision. No tidy resolution — just a clear statement of what comes next.
Chapters XIV and XV break format on purpose — instead of telling the story, they talk directly to whoever is reading this while preparing for their own interviews or first job search.
Open the field guideOpen to the next thing
If you're hiring for something senior and technical, want a sole owner's eye on your product, or just want to talk about charts that lag, I read every email myself.