DEV Community

Saarathi Academy for Saarathi Academy

Posted on Originally published at linkedin.com

A QA engineer in Nepal writes more bug reports than code

A junior QA engineer in Nepal spends most of the week reading requirements, running test cases and writing bug reports. Automation shows up in the job posts, but for junior roles it is usually a "nice to have", and the bug report is the work you are judged on.

We read four QA job posts from Kathmandu companies, listed on Semesteria, JobsNepal and merojob in 2025 and 2026. This article puts their duties into one normal week, so you can see the job before you train for it.

What does a QA engineer in Nepal do in a normal week?

QA means quality assurance: checking that software works before users get it. Many Kathmandu software teams work in sprints, which are short cycles of one or two weeks. The week below follows that shape. It is built from the duties in the posts, not from one person's diary.

Monday: read before you test

The week starts with a planning meeting. The intern post from BrahmaByte Lab lists "participate in test planning meetings" as a duty. The CodeBee Nepal post asks the tester to "review requirements, specifications, and technical design documents to provide timely feedback".

So on Monday you read the user stories for the sprint. A user story is a short note that says what a feature should do. You look for the gaps. What happens if the OTP expires? What if the user taps "Pay" twice? A question asked on Monday costs much less than a bug found on Friday.

Tuesday and Wednesday: write cases, run them, report bugs

Next you write test cases. A test case is a set of steps with an expected result, clear enough that a stranger can run it again. Then you run the cases on the new build, usually in Chrome and Firefox.

When something breaks, you write a bug report in Jira or a similar tool. Every post we read asks for this in some form: "identify and document bugs", "report bugs and issues accurately", "identify, document, track, and verify software defects". A good report has a short title, the steps, the expected result, the actual result, and the browser or device. A developer should be able to fix the bug without calling you.

Thursday: check the fixes, then check everything else

Developers fix the bugs and send them back. You test each fix again. Then you run regression testing, which means checking that the fix did not break something that worked yesterday. The Infi Loop junior post and the CodeBee post both name regression testing as a duty.

Friday: the release decision

Before a release, the team asks QA one question: is it ready? The CodeBee post asks the tester to "track QA metrics such as defect density and open defect counts". In plain words, you count how many bugs are still open and where they cluster. Then you say if the build should ship or wait.

The boring parts of QA jobs in Nepal

Most of the week is repeat work. You run the same login and payment checks before every release. You test one bug three times because it only fails on one phone. You fill in a sheet of test results, because many teams still share test cases in Excel files.

This is the part that decides whether you will like the job. If you enjoy finding the one input that breaks a form, the repeat work feels like a hunt. If you want to build new features all day, you will be happier as a developer.

Where automation fits for a junior

Automation means writing code that runs the test for you. It matters, but look at how the posts rank it. The Infi Loop junior post lists Selenium and Jira as "nice to have". The BrahmaByte intern post asks only for "familiarity with manual testing". The GCG International post on merojob asks for Selenium, Cypress and Postman, but it is a mid level role that wants more than 2 years of experience.

Our pick is clear. Learn manual testing and bug reports first, then automate the checks you repeat every week. A tester who automates a weak test case only runs a weak test faster.

QA engineer job description: what the posts ask for

Across the four posts, the same skills come back:

  • Writing test plans and test cases from requirements
  • Bug tracking in Jira or GitHub Issues
  • Functional, regression and end-to-end testing of web apps
  • Working in Agile or Scrum teams
  • SQL, to check that the database matches the screen
  • API testing with Postman, and basic scripting for automation

Most posts also ask for a bachelor's degree in computer science or IT. The CodeBee post says freshers and interns can apply to its paid internship, so a first QA role does not always need experience.

How to become a QA engineer in Nepal

Learn in the same order the job uses you, and check that any QA engineer course you look at follows that order week by week. At Saarathi Academy in Old Baneshwor, Kathmandu, the QA course runs 8 weeks, Monday to Friday, 2 hours a day, with up to 10 students in the classroom. Weeks 1 to 3 are testing basics: test design, bug reports, Jira and a test management tool called Qase. Week 2 also covers the payment cases that Nepal apps need, such as OTP expiry and one tap that causes two debits.

Week 4 adds Postman for API testing and SQL for checking the database. Weeks 5 to 7 cover automation with Playwright and Selenium in TypeScript, a first Cypress test, GitHub Actions and JMeter. The course ends with a certification exam taken online at home. For why automation is the next step after manual testing, read our guide to QA automation training in Nepal.

Try a free bug hunt tonight

You can practise the core of this job without paying anyone. Practice Software Testing is a demo tool shop made for testers, and this version has bugs left in on purpose.

Open the site in Chrome and use the shop like a customer: search, open a product, and try to check out. Then press Ctrl+Shift+J (Command+Option+J on a Mac) and click the Network tab. A status like 404 or 500 next to a request is a clue, and Chrome's guide to the Network panel explains each column.

Find one bug and write one report: title, steps, expected result, actual result, browser. If writing that report felt like the fun part, look at our software quality assurance course in Nepal and its week-by-week syllabus.

Common questions

Do QA jobs in Nepal need coding?

Junior and intern QA posts in Nepal mostly ask for manual testing, with basic programming as a plus. Mid level posts ask for automation with tools like Selenium or Cypress. You can start without code, but plan to learn some scripting before you aim for a mid level role.

Which certificate should a QA engineer get first?

The first certificate for a QA engineer is usually ISTQB Certified Tester Foundation Level (CTFL). ISTQB lists CTFL as the prerequisite for its certificates that require Foundation Level, and as of November 2026 the exam is 40 questions in 60 minutes, with 26 of 40 needed to pass. It is optional, and your bug reports and test cases show an employer more about how you work.

Where are software testing jobs in Nepal posted?

Software testing jobs in Nepal are mostly posted on merojob, JobsNepal, KumariJob and Semesteria. Search for both "QA" and "tester", because companies use both titles. Check the deadline, since many posts stay online after they close.

Is a QA engineer the same as a software tester?

In most Nepal job posts, a QA engineer and a software tester do close to the same job, and companies mix the titles. Strictly, QA is about preventing defects in the process, and testing is the hands-on checking. A junior does mostly the testing part either way.

Top comments (0)