Engineering background
I was born in Nepal at a time when access to computers was limited. I was fortunate to attend a school that introduced computer education in sixth grade, where I learned DOS and QBasic. In high school, I learned C; that curiosity later led me to JavaScript and a bachelor’s degree in Software Development, with minors in Network Administration and Information Security.
Over 12 years, I have worked across desktop, web, API, database, and cloud systems. That breadth allows me to move from a business conversation to system boundaries, from a frontend workflow to an API or SQL issue, and from implementation through migration, release, and production support.
How I operate
I take ownership beyond the code change: clarifying requirements, identifying constraints, choosing an appropriate design, supporting the release, and investigating what happens in production. I am not tied to one framework; I learn unfamiliar systems quickly and choose tools according to the business problem, operational constraints, and capabilities of the team.
I lead projects, review code, mentor and onboard developers, document systems, and explain technical tradeoffs to business stakeholders. I also use structured AI-assisted workflows while keeping architecture, security, validation, and production decisions under human review.
What I value
I care about product usefulness as much as technical quality. The best architecture is not the most elaborate one—it is the one that fits the problem, constraints, team, and stage of the product. Good senior engineering leaves the system and the people working on it more capable than before.