PurPassionDigital / Everywhere

Software Tester / QA Engineer

The pull to understand what isn't yet understood

Discovery · Unknown → Known

The shape of the work

Pace
  • A hard push you keep up for a long stretch
  • A steady rhythm with room to breathe
What your week looks likeQuiet stretches, then deadline storms
How much you move around at workScreen and chair, almost all day
Whether you can work from anywhereWork from anywhere with a signal or internet connection
How quickly you receive feedback on your workGive it a few days
What you're actually working withNumbers, measurements, records — things you read on a screen / Concepts, theories, designs, stories — things you think up

Behaviours this work is made of

Core
  • Locating the specific point of failure in a complex system. The detective work of dysfunction.
  • Careful, sustained attention to what's actually happening.
  • Verifying whether something is true or works as claimed.
Also present
  • Breaking something into its real components.
  • Making processes run without constant human input.
  • Exchanging meaning — both transmitting and receiving, adjusting in response.
  • Creating the record that allows others to understand later.

In words

A software tester, also called a QA (quality assurance) engineer, checks that software does what it should before real users meet it. They read what the software is meant to do, try it in the ways users will and the ways users should not, and write up every fault they find so a developer can reproduce and fix it. Many testers also write automated tests: code that runs the checks again every time the software changes. The main pull is Discovery, because the job is finding out what is true about the software and not what the team hopes is true. Protection sits behind it: a bug found before release is one that does not lose a user's data, money or trust.

The title varies. Software tester, QA engineer, QA analyst and test engineer are common, and SDET (software development engineer in test) means a tester who mostly writes code. The work exists in most countries with a software industry, and the same skills apply to games, banking systems, medical software and mobile apps [official / sector 2026]. It differs from a developer in focus: the developer builds the feature, and the tester looks for how it breaks.

There's a guide here if you want one

Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.

Testing is often seen as a lower-status job than development, and in some companies testers are the first to be cut when there is a deadline. The people who last are the ones who find the important problems, and who can explain clearly why they matter without annoying the developers. In the US the median pay for software quality assurance analysts and testers was about $104,300 in May 2025 [official 2025].

The field is changing quickly. Automation and AI tools now generate and run many routine tests, and manual click-through testing is shrinking. The work that stays human is deciding what is worth testing, spotting what a script would never think of, and judging whether a behaviour is a problem for a real user.

Many people get in with a degree in computer science or a related subject, others with a coding bootcamp, or from a support or other technical role inside a company, since manual testing is one of the more accessible first jobs in software. Useful skills are careful attention to detail, writing clear bug reports, some scripting or programming, and knowledge of test tools. The ISTQB certificate is widely recognised and optional. Testers often move into test automation, SDET, developer, security testing, product or engineering management roles.

Before you go