How I got here.

I came to code the way most builders do: through a problem I wanted solved and a feedback loop I couldn't put down. Type something, run it, see what happens. By the time it stopped surprising me, it was already too late. The field had taken.

In January 2024 I moved from India to the United States for an M.Sc. in Computer Science at the University of North Texas. The curriculum on paper was AI, data mining, software engineering, advanced analytics. The curriculum in practice was harder. I graduated in December 2025 with more side-project code in my GitHub than coursework, and a stronger conviction that the best way to learn how to build something is to build it.

I graduated in December 2025 and have been building since. Five projects so far: an orchestration platform, a deterministic memory engine, a learning assistant, a workforce app, a news aggregator. They started as a way to keep building while I look for the right next step. They ended up being the most useful thing on this site. They're all on the work page. They all run.

The first time I watched three language models debate each other into a working pipeline. Claude planning, Gemini building, Codex auditing. I sat there for forty minutes without touching the keyboard, and five years of learning got rewritten. AI doesn't build anything we can imagine. It still makes plenty of mistakes, still needs us to catch them. But the distance between an idea and a working prototype has never been shorter. That's the part that keeps me building.

I'm looking for engineering work, ideally where full-stack and AI-systems meet. Software engineer, AI engineer, or founding-engineer roles, full-time or contract. If you're hiring and this sounds like a fit, the inbox is on the contact page.