My Story.

My first professional glimpse of that world came at Citytech Global. As a Backend Developer Intern, I worked with Java and Micronaut to build REST APIs. It was my introduction to backend engineering in a professional environment, and it made the systems I had been curious about feel tangible.

At around the same time, I co-founded Autovity Tech. Suddenly, software was not just a technical exercise. I was thinking about product strategy, system design, development, and the business problem underneath all of it. That experience gave me an idea I still carry: good engineering starts with understanding what actually needs to be solved.

Waterflow Technology gave me the opportunity to put that idea into practice on enterprise applications. I worked across ASP.NET Core, React, Next.js, and SQL databases, but my role quickly grew beyond implementing features.

I became involved in architecture, requirements, testing, deployment, maintenance, stakeholder communication, and project management. I started seeing software as a complete lifecycle rather than a collection of tickets and code changes.

Later, as a Product Engineer at ITsutra, I moved closer to the realities of running enterprise software in production. Working with .NET, Azure, and Dynamics 365, I improved performance through caching and database optimization, introduced centralized logging and monitoring, built secure integrations with JWT and MSAL, and diagnosed issues that only reveal themselves in real systems.

That role also changed how I thought about engineering teams. Through mentoring junior developers and conducting code reviews, the question was no longer only whether my own code worked. I began thinking about how the whole team could make better decisions and build software that was easier to understand and maintain.

Today, I work as a Full Stack Developer at Tekkon Nepal, partnering with Plancare Australia on enterprise healthcare management systems. The stack includes C#, ASP.NET Core, React, Angular, and Microsoft SQL Server, but the technology list is not the part that keeps the work interesting.

What interests me is everything underneath it: designing scalable APIs, making complex business workflows understandable, running background work reliably, improving database performance, troubleshooting production behaviour, and translating conversations with international stakeholders into solutions people can depend on.

Over time, I have realised that the problems I enjoy most rarely end with “write another endpoint.” I want to know why something is slow, why it behaves differently under load, which query is doing too much work, where a background process can fail, and how a growing application can remain clear to the people responsible for it.

My career has followed that curiosity. I began by learning how to build software, then learned how to build complete applications, and eventually started thinking more deeply about architecture, performance, reliability, production, and the teams behind those systems.

The direction I want to keep moving in is clear: toward taking ownership of complex systems from the first conversation about the business problem through design, development, optimization, and day-to-day operation in production.