I am a QA professional, and I have helped ship some of the biggest console and PC titles out there. My focus is functional testing, hands on dev QA, and the day to day leadership it takes to keep a test team sharp when a deadline is bearing down.
Console and PC releases I supported in a quality assurance capacity, from feature-complete builds through release.
My role on every title here was Quality Assurance, and I am not claiming any other credit. All development, design, art, and intellectual property belong to their respective studios and publishers.
It really comes down to two things for me: the hands-on testing itself, and the work of keeping a team pointed in the same direction.
I make sure features actually do what they are supposed to do. I write and run test cases, but I also go off script, because the bugs that really hurt are usually the ones a checklist would never catch.
I like working right next to the developers. I verify builds, confirm fixes, and when something breaks I track down exactly how to reproduce it, so an engineer can sit down and fix it without having to guess what I saw.
I have led test teams through the messy parts, triaging what matters first, keeping coverage organized, and helping testers write reports people can actually act on. When a deadline starts closing in, that is when good communication matters most.
A bug report is only useful if someone can follow it, so I keep mine clear, honest about severity, and easy to reproduce. Then I make sure the things we already fixed stay fixed all the way to release.
I would rather catch it than have a player find it.
To me, testing was never just about finding bugs. It is about protecting something a team has poured years into, and giving the developers an honest, clear picture of where a build actually stands.
Leading a team meant keeping the coverage honest, helping testers write reports a developer could act on right away, and making sure the issues that mattered got attention before a deadline instead of after it.