For students and early-career professionals

Quality Assurance Engineer

Tests software to find bugs early and improve reliability before release.

13 chapters · About 5–6 months · 15–30 min a day

Start this plan free →

Chapter 1 is free.

Skills

14 skills, and what you'll learn in each

Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.

Core to the job

Chapter 2

Test planning

Plan tests, report bugs and recommend whether to release

What you'll learn

  • What to test first
  • Test case selection
  • Testing without a script
  • Reproducible bug report
  • Release evidence

Practice

  • Split an input into groups, then test only the edges20 min
  • Run a 30-minute exploratory test session with a charter30 min
  • Write a one page test plan and say what you will not test30 min

Chapter 2

Writing tests

Write tests for small functions, including odd and wrong inputs

What you'll learn

  • Testing pyramid
  • Behaviour test
  • Test isolation
  • Regression test

Practice

  • Write unit tests for a small function20 min

Chapter 3

Debugging

Use error messages to find bugs and explain your fixes

What you'll learn

  • Hypothesis before keyboard
  • Reliable reproduction
  • Root cause, not symptom
  • Narrow it down
  • Reading a stack trace

Practice

  • Find the Bug Using an Error Message10 min

Chapter 3

Code quality

Review code for unclear names, then tidy a messy function

What you'll learn

  • Clear names
  • Single responsibility
  • Review the risk
  • Explain the reason
  • Proportionate change

Practice

  • Review Code for Quality Issues15 min

Chapter 5

Git

Save clear changes to a project's history and request review

What you'll learn

  • Change states
  • Short-lived branches
  • Merge conflict
  • Useful commit message
  • Pull request review

Practice

  • Rewrite 5 bad git commit messages15 min

Chapter 6

APIs

Check requests and replies between programs, and design clear ones

What you'll learn

  • API resource
  • HTTP status codes
  • API contract
  • Idempotent request
  • API style choice

Practice

  • Test an API's error replies, not just its happy path25 min

8 more in the plan

Programming languagesBuild small programs in one language, handling input and errorsCh 5

What you'll learn

  • Types and values
  • Control flow
  • Error handling
  • Asynchronous work

Practice

  • Trace a Function and Predict Its Output10 min
Automated releasesExplain what each automatic check on a code change catchesCh 5

What you'll learn

  • CI and CD
  • Pipeline stages
  • Release gate
  • Pipeline logs
  • Pull or push
  • Reconciliation loop
  • Where the check runs
  • Environments and promotion

Practice

  • Read a Continuous Integration Workflow and Trace What Happens15 min
Databases and SQLWrite SQL to filter and join data, and design tablesCh 6

What you'll learn

  • Tables and relationships
  • Joins and groups
  • Index trade-offs
  • Query plan
  • Lock behaviour

Practice

  • Write 4 SQL queries against a sample schema20 min
Problem solvingTest each possible cause of a problem instead of guessingCh 8

What you'll learn

  • Problem vs symptom
  • Clean problem splits
  • Root cause
  • Deciding under uncertainty

Practice

  • Separate the Problem from the Symptom10 min
Critical thinkingSpot a weak assumption and ask where numbers come fromCh 8

What you'll learn

  • The hidden assumption
  • Argue the other side
  • The base rate
  • Fact vs inference
  • Wanting it to be true

Practice

  • Decide which of six manual tests are worth automating20 min
CommunicationRewrite an update for two different readers, cutting extra linesCh 9

What you'll learn

  • Lead with the point
  • Match detail to the reader
  • Said versus heard
  • Specific feedback

Practice

  • Write a Status Update for a Non-Tech Manager10 min
Working with othersContribute to group work, ask for help and credit teammatesCh 9

What you'll learn

  • Early team friction
  • Clear ownership
  • Challenge ideas, not people
  • Lead or follow

Practice

  • Write a Request That Makes It Easy to Say Yes10 min
Adapting to changeTry a new tool and describe how you handled changeCh 9

What you'll learn

  • Change vs your response
  • The messy in-between
  • Not there yet
  • Real change vs a feeling

Your plan

Chapter by chapter.

13 chapters, in this order. Chapter 1 is free.

1~2 wks

See the work of a Quality Assurance Engineer

StartFree
2~2 wks

Plan and automate tests that catch bugs

Skills
3~2 wks

Write clear code and find bugs

Skills
4~2 wks

Build and deploy a tested web app

Project
5~2 wks

Write code and run it through pipelines

Skills
6~2 wks

Build APIs backed by a database

Skills
71–2 wks

Talk to two working quality assurance engineers

People
8~2 wks

Find the cause before you fix it

Skills
9~2 wks

Communicate and work together through change

Skills
10~2 wks

Capstone: build a tested habit tracker API

Project
111–2 wks

Answer the questions interviewers ask

Interview
121–2 wks

Decide how you will get in

Decide
13on your timeline

Send your first applications

Apply

The job

What a Quality Assurance Engineer does

Tests software to catch bugs and risks early, so users get reliable features and teams can release with confidence.

The work

  • Design test plans from requirements and user stories
  • Write and run manual tests across devices and browsers
  • Build automated tests to speed up repeat checks
  • Report bugs with clear steps, evidence, and impact
  • Verify fixes and prevent the same issue from returning
  • Review product changes to spot edge cases and risks
  • Track quality metrics and share release readiness status

A typical day

  1. Join standup, review changes, and pick tests for the day
  2. Test new features, log bugs, and follow up with developers
  3. Update automated tests and run the test suite
  4. Review results, retest fixes, and sign off on releases

Tools

Test management: TestRail, ZephyrBug tracking: Jira, Azure DevOpsAutomation: Selenium, PlaywrightAPI testing: PostmanCI pipelines: GitHub Actions, JenkinsDatabases: SQLDevice testing: BrowserStack

Ways in

There is more than one route.

Ways to study

  • Computer science or software engineering degree
  • Information technology diploma or certificate
  • Software testing bootcamp or online QA program
  • Apprenticeship or employer training in software testing

How people get their first job

  • Apply for QA internship or software testing trainee roles
  • Start in IT support and move into testing for internal tools
  • Build a small test portfolio with test cases and bug reports
  • Earn a testing certification and practice on sample apps
  • Contribute test cases or bug reports to open source projects

How the work is changing

What AI is doing to this role

How AI is changing this role · one of 6 tasks we track

Write test cases from requirements

Sped up a lot

What AI does

AI drafts test cases straight from a user story or ticket.

Still yours

You decide what is worth testing and where the real risk sits.

Reviewed September 2026

In the app · Premium

The rest is in the app

  • How AI affects the other 5 tasks
  • Whether this job is growing or shrinking
  • How hard the first job is to get
  • Similar roles that are easier to get into
  • Updated every month, with sources
See it in the app →

How we rate a job →

Already working

Already a Quality Assurance Engineer?

Plan your move to QA Engineer: 9 chapters that end with a strong case for your next review.

Grow in the role →

Other roles in Manufacturing & Quality Engineering

Questions

Questions about this plan

How long does it take to become a quality assurance engineer with Welica?

The plan is 13 chapters, 5–6 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.

Do I need a degree?

Not always. Common routes are computer science or software engineering degree, information technology diploma or certificate, software testing bootcamp or online QA program, or apprenticeship or employer training in software testing.

What is free?

Chapter 1, See the work of a Quality Assurance Engineer, is free for good. Premium unlocks the rest of the plan.

Start the Quality Assurance Engineer plan.

Chapter 1 free. About 15 to 30 minutes a day.

Start on web Continue your session Download for MacMac Get the iPhone appiPhone Get it on Google PlayAndroid