The Ticket is Just the Start

QA, for me, usually starts with incomplete information and ends with a clearer picture of how things actually work. That clarity comes from the work; day by day, test by test.

Some days the job is writing automation tests for a new feature. Other days it’s updating API tests because the payload changed or a new query param was added. I might be fixing flaky tests that passed last week. And a lot of times, I’m exploring; looking for what feels off and trying to break things before users do.

Most of that work starts with a ticket.

But what’s written down is usually not the full picture. Details shift, plans evolve, and things get built faster than they get documented. My job is to figure out what changed, what matters, and how to make sure it works the way it should.

I start with the PR and whatever context I have. I check what’s supposed to happen and what actually changed. Then I test against what’s written, and I go further. I test how it behaves, not just how it was designed. My experience helps me see where things might break outside the expected flow.

I find bugs by following the checklist, and even more by going beyond it. I do things out of order, skip steps, and test what users are likely to try but wasn’t accounted for. I’ve missed things too. Sometimes the context changed, and sometimes I just got it wrong.

I’m good at noticing the stuff that gets missed. I catch flows that feel off and features that technically pass but don’t hold up when you actually use them. That’s the value I bring. It helps users trust what they’re using, stick with your product, and actually enjoy it. I’m ready to bring that to the right team.

Connect with me 📎
https://www.linkedin.com/in/jeffthoensen
https://jeff-thoensen.medium.com/
https://x.com/jeffthoensen