Welcome!
Hey there, and welcome to QAJourney.net.
This blog is where I share my thoughts, lessons, and experiences from the world of Quality Assurance — and where my journey from QA to leadership continues.
Whether you’re just starting out, a seasoned pro, or simply curious about how real QA works (and how it evolves into project leadership), you’ll find something here to learn from — or at least relate to.
My Journey
I’ve always wanted to be a software engineer.
To kickstart that dream, I attended a bootcamp for full-stack development and was eager to land a dev job.
But life had other plans.
Instead of stepping directly into development, I was offered a position as a QA.
At the time, with zero experience, it felt like a downgrade — just a stepping stone toward something “better.”
When I failed my first dev assessment, that hit hard.
But it also flipped a switch.
If QA was my road in, I wasn’t going to coast through it.
I was going to own it.
I dove into QA headfirst — studying QA processes, writing test cases, learning Gherkin, collaborating with developers, picking up Scrum fundamentals from PM mentors, and understanding UX from senior designers.
I wasn’t content being just “okay” — I wanted to build systems that worked.
That mindset shaped my career.
Over time, I moved from tester to QA Lead, where I realized leadership wasn’t about pointing at bugs — it was about building the teams and systems that caught problems before they mattered.
Eventually, I became Head of QA, leading multiple QA teams across multiple projects — embedding quality deeper than just last-minute test cycles.
The Shift Into Project Management
When our company faced challenges, I didn’t have the luxury of staying in one role.
I transitioned into a dual role — Head of QA and Project Manager.
Some would call it a downgrade — “only” managing a project instead of leading an entire QA organization.
They’re wrong.
Project Management didn’t replace my QA mindset — it expanded it.
- Instead of just testing features, I test strategies, timelines, and workflows.
- Instead of just reporting bugs, I prevent breakdowns in planning, communication, and delivery.
- Instead of just managing a QA team, I manage the battlefield — developers, designers, testers, and stakeholders — aligning chaos into something that ships.
QA taught me to find problems early.
PM taught me to stop them before they even start.
I don’t just lead QA anymore.
I lead the system that holds everything together.
Why I Started This Blog
I created QAJourney.net because QA deserves a voice that isn’t sanitized by corporate checklists or certification factories.
Real QA isn’t just automation scripts, Jira tickets, or sprint retros.
Real QA is survival.
Real QA is leadership under fire.
Real QA is why bad products get saved — and good products don’t die quietly.
Whether you’re here to pick up automation tips, figure out how to transition into leadership, or simply survive another sprint without burning out, this blog is built for you.
If my lessons help you avoid a few headaches — or make you realize you’re not crazy for caring about quality — then this site is doing its job.
My Core Values
Integrity: Doing what’s right, even when it’s hard.
Respect: Treating every contributor as critical to the process.
Honesty: Communicating what’s possible — and what’s broken — without sugarcoating.
Common Sense: Prioritizing solutions that work over theoretical perfection.
Make It Work Mentality: If it’s broken, fix it. If there’s a wall, find a way over or around it.
These values drive my work, my teams, and this blog.
Let’s Connect
Want to dive deeper into my blog network, see my YouTube projects, or find the other content hubs I’m building?
➔ Visit the Links Page