The Origin of QA Captain
From red pen to regression testing. From chaos to confidence.
Before Lee ever wrote a line of code, he was editing essays. In school, peers who dreaded writing essays/research papers would come to him for help. Lee would grab a red pen and go to work—highlighting spelling errors, tightening grammar, checking if the conclusion matched the thesis, and making sure the flow made sense. The result? Better grades. More confidence!
Sound familiar?
That’s software testing. That’s QA.
It’s not just about finding bugs. It’s about helping others succeed. About checking functionality, syntax, user flow, and alignment with purpose. About making sure what’s built actually works—for the business and the people who use it.
Lee didn’t set out to become a QA Engineer. He studied computer science to build software—drawn to the power of technology to help people. But once he discovered software testing, it was like a duck to water! That magic reignited! This time, it’s not in essays, but in software. Not with red pens, but with test cases, user flows, and systemic processes.
He became obsessed.
QA isn’t just a job. It’s a craft. A purpose! A place where all of Lee’s education and interests come out to play: engineering blended with empathy, psychology, creativity. Where hunting bugs becomes the avenue to help software teams ship high-quality products. Lee fell in love with the art of testing. Okay, in reality, Lee is *obsessed* with software testing! You mean there’s a job that combines bug hunting, process improvement, creativity, engineering, and care? Sign us up!
Lee is driven by a deep sense of excellence. If you’re going to do something, aim for the A+, the gold stars. For the past 20+ years, Lee has been mastering the craft of software testing—across industries, platforms, and chaos levels. And he’s seen the same patterns repeat.
The Challenges
Why QA Captain exists.
Lee founded QA Captain to solve the problems he saw over and over again:
- Teams being reactive to software testing when they need to be proactive in software testing. High quality takes intention, not luck!
- Too many bugs being created, when bugs can be prevented with clarity and care from the start.
- Teams relying too much on blackbox testing, which feels like guesswork. You’ll miss bugs.
- QA treated as an afterthought, not an engineering discipline. Quality can be engineered into software!
- Software developers frustrated by testing, seeing it as boring or beneath them. Hi, 👋, we love testing! It’s fun! We want to help!
- Businesses afraid to deploy software. We can help reduce the risks of production deployments!
- QA seen as expensive—while downtime, reputation loss, and broken trust cost far more!
Lee knew there had to be a better way. A way to make QA proactive, not reactive. A way to engineer quality with intention. A way to help teams ship with confidence!
The Invitation
If your team is tired of bugs, chaos, and reactive testing… If you want software testing that’s engineered with care… If you believe software should work for people…
QA Captain is here. Let’s build clarity together.