What I Thought QA Was
When I first started learning Quality Assurance, I thought I understood the job. Or at least… I thought I did.
I believed QA meant clicking every button. Typing strange inputs into forms. Reading long requirement documents. Writing endless bug reports. Creating hundreds of test cases for the same placeholder simply to prove it behaved correctly.
I imagined long meetings where the QA engineer existed only to ask, “What happens if the customer breaks this?” In my mind, Quality Assurance was mostly about finding problems. And if I’m honest…
It sounded a little boring.
Then Something Changed
As I started working with startups, something unexpected happened.
I stopped seeing products. I started seeing people. Behind every application was a founder excited to explain an idea. Someone who had invested months—sometimes years—trying to solve a real problem. I also watched a talk that completely changed the way I thought about software quality. Instead of asking,
“How do we find more bugs?”
it asked something much simpler.
“What does Quality Assurance actually mean?”
Quality Assurance
Two words. Simple words. But surprisingly difficult to define.
Is QA…
a person?
a team?
software testing?
building the product correctly?
making a promise to customers?
My answer today is… Yes. But it’s also much more than that.
The Founder Changed Everything
One of my favorite parts of this job isn’t discovering bugs.
It’s listening. I genuinely enjoy hearing founders explain why they built something. Watching their eyes light up when they describe an idea. Understanding the problem they’re trying to solve. Because once I understand that… My work changes completely.
Instead of saying,
“This button is broken.”
I find myself saying,
“I think this small change could make the experience much clearer for your users.”
That conversation feels completely different. It’s no longer QA versus Development. It’s people improving a product together.
The Small Things Matter
A few days ago I reviewed a startup whose landing page taught me something. There were several feature cards. Normally those sections are just marketing. Static text. Nothing more.
But each card was actually clickable. Instead of repeating marketing copy, every one of them opened the exact documentation explaining how that feature worked. Such a small interaction. Yet it completely changed how I experienced the product.
Moments like that are why I love QA. Because users don’t remember software only because it works. They remember how it made them feel.
Why People Stay
Think about the applications we use every day.
Take X, for example. Millions of people understand almost immediately how to like a post. Reply. Share. Bookmark. Those interactions feel obvious today.
But someone had to design them. Someone had to ask, “Will users understand this without thinking?”
That’s user experience. And that’s where Quality Assurance becomes much larger than testing.
My Definition of QA
Today, if someone asked me what Quality Assurance means… I wouldn’t start by talking about test cases. Or automation. Or bug reports.
I’d say this. Quality Assurance is helping founders deliver the best product they can build. And helping users receive the best product they can experience.
That’s why I love this profession. Because my job serves both sides. The people creating software. And the people who trust it.
My Philosophy
That’s why my personal philosophy has become incredibly simple.
Understand first. Test second. Explain always.
Understanding comes before testing. Testing comes before reporting. And reporting should always leave the product better than it was before.
That’s what Quality Assurance means to me.
