// software qa engineer · kathmandu, nepal
I spend my days trying to break software before your users get the chance to — across web apps, mobile, APIs, and the real-time systems holding them all together.
3+ yrs QA
// about
I've spent the last three years finding the things nobody wants to find — race conditions in real-time syncs, broken auth flows, push notifications that quietly fail on Android but work fine everywhere else. My background covers manual testing, API validation, automation, security testing, and performance work, and I'm just as comfortable writing a test plan as I am explaining to a client why a release slipped by a day.
What I actually enjoy is the process side of things: building regression suites that catch issues before they ship, setting up documentation that makes handovers painless, and mentoring junior testers so the whole team gets a little faster with every release.
// experience
A quick run-through of the roles, from earliest to most recent — think of it as a build history.
// skills
Grouped by what they're actually used for, not how impressive they sound.
// highlights
Handled QA communication directly with clients — explained defect status in plain terms, managed expectations during tense phases, and made sure test outcomes matched what was agreed on.
Ran regular walkthroughs with junior testers on test design, defect tracking, and working within Agile teams. Watching them grow into independent contributors was genuinely satisfying.
Audited existing test cases, filled in the gaps with new scenarios, and standardized documentation across the team — fewer issues slipped to production, less firefighting after releases.
// education
Coursework spanning software development and systems fundamentals, which gave me the technical grounding I now use to read code, reproduce bugs, and have useful conversations with developers.
// contact
Open to QA roles, contract work, or just a conversation about testing strategy. Drop a message and I'll get back to you.