What does a QA engineer do?
By the Compass Careers team · Updated 6 November 2026
A QA (quality assurance) engineer helps a software team find problems before users do. They test new features, write down what breaks and how to repeat it, and often write small programs that run the same checks automatically. They are not there to blame anyone. They are there to make the product more dependable.
A typical week
- Reading what is being built: going through the plan for a feature and asking what could go wrong, such as an empty form or a slow connection.
- Testing by hand: using the new feature the way real people might, including in unexpected ways.
- Writing clear bug reports: the steps, what happened, what should have happened, so a developer can repeat it quickly.
- Automating repeat checks: in many teams, writing scripts so the same tests run every time the code changes.
- Checking fixes: confirming that a fix works and has not broken something else.
Manual and automated testing
| Manual testing | Automated testing | |
|---|---|---|
| What it is | A person uses the product and observes | A script runs the same checks on its own |
| Good at | Spotting things that feel confusing or odd | Repeating the same checks quickly, every time |
| Skills | Curiosity, patience, clear writing | Programming, plus an eye for what is worth checking |
| Risk | Slow and easy to skip when rushed | Checks only what someone thought to write |
One real decision from the job
A new payment screen is due to ship tomorrow. You have time to check only part of it.
What do you test first?
Reasonable options include the main path that most people take, the places where mistakes cost the most, or the unusual cases that are easiest to miss. The one you reach for first says something about how you weigh risk. Try a free decision on Compass to practise making a call like this. Nobody scores you.
Signs you might enjoy it
- You enjoy finding the one case that does not work.
- You like writing things down clearly and precisely.
- You care about the person who will use the product.
Signs it might frustrate you
- You prefer creating new things to checking existing ones.
- Repeating similar checks bores you.
- You dislike bringing bad news to a team.
How to test it in a week
- Pick an app you use and try to break one feature: leave fields blank, type very long text, go back mid-way.
- Write up two problems you find in the form of steps, actual result and expected result.
- Ask someone who works in testing what a good bug report looks like, and compare it to yours.
Common questions
Do QA engineers need to code?
Some roles are mostly manual testing and some involve a lot of programming. Read the job description to see which one is on offer.
Where can I read more?
See what a software engineer does and how to read a job description.
Try the work before you choose it
Compass lets you try a realistic decision from each path you’re weighing, notice how it felt, and choose your next step with evidence. The preview on our home page is free.
Weighing two or three paths seriously? See our packages, each prepared and reviewed by a person.