My first job in technology was a QA internship. The summer between
my freshman and sophomore years, I tested the first release of
Paradox for Windows at Borland.
As an intern, I started by following someone else’s QA test plan
— dutifully checking each test off the list. After a few weeks, I
knew my particular area inside and out. A new build would show up,
which I’d install via 3.5-inch floppies, and in ten minutes of
usage, I’d have a sense — is this a good or bad build?
In QA, there is a distinct moment. It comes once you’re deeply
familiar with your product or product area; it comes when you’re
lost in your testing, and it comes in an instant. You find a
problem, and because of your strong context about your product,
you definitely know: Something is seriously wrong here.
A good QA engineer is worth their weight in gold.