The Web2 Saga
Before I turned web3
I didn't plan to work in startups. I just enjoyed building things and watching them exist outside my laptop.
My first real exposure to that was in my 3rd year, when I joined Aiisma. It was a small startup, and roles weren't clearly defined. I worked on Android features, backend endpoints, QA, and release cycles, whatever was needed at the time. The app eventually crossed 10,000 downloads. That was the first time I understood what it meant to ship something people actually use.
After that, I joined Medzgo. This is where engineering became less about features and more about systems. I worked on backend services, authentication flows, WebSocket-based communication, access control, and API integrations for telemedicine use cases. It was the kind of work where nothing looks impressive on the surface, but everything depends on getting it right.
Side Projects & Explorations
Outside of work, I kept exploring ideas on my own.
RFID-based Robot
I built an RFID-based robot using NodeMCU and Firebase, mostly to understand how hardware and software interact in real environments. It wasn't perfect, but it taught me how unpredictable physical systems can be.
View Code on GitHubVulnerability Scanner
Around the same time, after my first bug bounty, I built a vulnerability scanner to understand how security issues are actually discovered, not just documented.
View Code on GitHub🚀 NASA Space Apps: Moon Landing AR Simulator
One project that still stands out was a Moon landing AR simulator built for NASA Space Apps. We built it in five days, using Apollo 11 data, audio, and AR controls. It ended up winning the zonal round, which gave me a lot of confidence in my ability to build and ship under tight constraints.
Watch Demo VideoBuddyWeb: Running a Business
I also spent time running a small hosting business called BuddyWeb. I handled infrastructure, customer support, billing, and operations. That experience quietly taught me responsibility. When something goes down, you don't look for process, you fix it.
None of this felt like a "career path" at the time. It was just a sequence of things I was curious enough to build. Looking back now, it's clear that this phase gave me a strong foundation: how systems behave, how users react, and how much discipline it takes to keep something running.
That foundation ended up mattering more than I expected.