From curious kid to
shipping products people use.

It started in high school with basic HTML and CSS. Tiny static sites, nothing fancy. Then academics took over and I put it down. In the first year of engineering we learned C. I spent nights on HackerRank just to see if I could make the green checks show up.

Second year introduced DSA. I practiced almost every day on LeetCode for about three months and solved roughly 250 problems. Somewhere in that grind something felt off. I was getting better at puzzles, but I wasn't building anything people used. No users. No product. Just math dressed up as code. So I stopped treating interviews as the destination and started treating shipping as the point.

Near the end of fourth semester I relearned the web from scratch: HTML, CSS, JavaScript, TypeScript, React, Next.js, Node, whatever I needed to make something real. Theory wasn't enough anymore.

Through personal connections I landed a hybrid internship at Expora Database Consulting Servicesin Bangalore. Every two weeks I'd go into the office; the rest was remote. I built an internal ticket product that replaced Jira, helped on their platform, and shipped client work they brought in. When it ended, I wanted to get closer to users myself.

So I started posting every day on X (Twitter). No audience strategy. Just "here's what I learned today." In a month or two I crossed 2k followers. I'm at 7.5k+ now.

The first inbound freelance client came from those posts. A mobile app. I had never even touched React Native before. I learned it in about fifteen days, delivered, and the app is still on the App Store. Seeing a stranger trust you with money, and then seeing the product live, changed how serious this felt.

I posted harder. I also walked into local businesses in my city and asked if they wanted a website, mobile app, or any other digital services. From X (Twitter) and local outreach I worked with 12+ clients, most in India, a few abroad. One was a trading practice platform for a founder in Dubai; I built it with another freelancer in the Philippines. Vague requirements, tight timelines, timezone chaos. We still shipped.

Then I built NameHunt, a domain-pricing tool that uses headless browsing to pull live prices across registrars. I tweeted the launch and it reached ~35k views. A Canadian founder in a related niche reached out, interviewed me based on what I'd built, and hired me. I joined as a founding engineer on their live-streaming product and spent roughly eight months helping take it from zero to something people actually used, shipping alongside a real engineering team. As graduation approached, balancing final-year academics with full-time work stopped being sustainable, so I stepped away to finish my degree properly. My goal after graduating was still the same: to keep building ambitious products while finding a challenging full-time engineering role where I could continue learning from experienced engineers.

Today, NameHunt is still live, but because it relies on headless browser automation, it requires ongoing maintenance whenever registrars redesign their sites. After nearly ten months without active maintenance, some providers still work while others have broken as their interfaces changed.

During that job, early 2026, AI agents started becoming mainstream. Developers suddenly wanted their tools to publish content and automate workflows across social media. Most scheduling tools felt expensive for what they offered, so I decided to build my own. That became Social0. I started in February, alone, and spent months building everything from authentication and billing to publishing across nine different platforms.

Like most of my projects, it began with "this shouldn't be too hard..." and quickly turned into weeks of debugging problems I didn't even know existed. Publishing reliably across multiple platforms taught me that real software isn't just about making something work once. It's about making it keep working when networks fail, tokens expire, jobs get interrupted, and users still expect everything to "just work."

More than any project before it, Social0 changed how I think about engineering. I stopped seeing features as isolated pieces of code and started thinking in terms of systems that have to work together reliably. That's the part of software engineering I enjoy the most now.

Launching taught me a harder lesson. I assumed interest would turn into paying users on its own. It didn't. That gap taught me more than the happy path: shipping gets you in the room, but product and distribution are separate skills. So I kept talking about Social0 in public until someone found it useful enough to pay. One customer isn't a business, but it's proof the work is worth something to someone else. That was the validation I needed. I still added MCP and CLI, so an LLM can post to Twitter from OpenClaw or Instagram from Claude Code. I want Social0 to become infrastructure developers can build on, not just another dashboard.

Today I'm looking for a challenging full-time engineering role where I can own products end to end and learn from engineers who have solved problems at a much larger scale.

I'll continue maintaining Social0 in my free time, but when I join a team, that work always comes first. I'm also in Super30 right now. I just graduated B.Tech CSE from KLE Technological University Hubli. I enjoy problems that require learning unfamiliar systems quickly, and I don't expect that to change anytime soon :)