How do we balance championing the Quality Assistance model with the reality that many early‑career quality engineers haven’t yet experienced working this way?
21 Apr 2026
In this moment:
Jesse Berkeley
Interesting question from Jesse Berkeley on quality assistance model - https://www.ministryoftesting.com/moments/ama-about-transitioning-to-quality-assistance-model
I took a few days to think about this question and honestly I do not know exact answer to that. I didn't work with early career quality engineers for a while and I have little insights what knowledge and skills they own today. I think I would experiment with that.
If I had to do that, I think I would start from showing them that tester aren't only breakers, they are also builders, partners and supportive colleagues to developers. We aren't the one who are slowing team down by bringing bad news, we are the ones who communicate to the team where gaps are and what risks are waiting for us if we don't take actions. It's also being proactive, opinionated about testing, persistent and have ability to question the state of things if they look weird or off. That what is the role in essence that is not that different from quality engineer role per se.
I think I would start from championing mindset rather than the model. Mindset that brings early careers testers closers to whole quality engineering principles. Once you have it, it's easier to work out the model. Quality Assistance is a model you can operate while exercising and balancing some practices, but it's the mindset that drives outcomes.
I took a few days to think about this question and honestly I do not know exact answer to that. I didn't work with early career quality engineers for a while and I have little insights what knowledge and skills they own today. I think I would experiment with that.
If I had to do that, I think I would start from showing them that tester aren't only breakers, they are also builders, partners and supportive colleagues to developers. We aren't the one who are slowing team down by bringing bad news, we are the ones who communicate to the team where gaps are and what risks are waiting for us if we don't take actions. It's also being proactive, opinionated about testing, persistent and have ability to question the state of things if they look weird or off. That what is the role in essence that is not that different from quality engineer role per se.
I think I would start from championing mindset rather than the model. Mindset that brings early careers testers closers to whole quality engineering principles. Once you have it, it's easier to work out the model. Quality Assistance is a model you can operate while exercising and balancing some practices, but it's the mindset that drives outcomes.
Nataliia Burmei
Lead Quality Engineer
I am Nat, Lead Quality Engineer who loves travelling, running, quality coffee with a book on the side. Totally unbiased, I love quality.
Sign in
to comment
Jira Issue Connect brings live, real-time Jira data directly into TestRail, eliminating tab-switching and stale fields.
Explore MoT
Explore the boundaries of AI-generated software by live-testing a word search tool and using collaborative techniques to identify gaps in logic despite passing all initial automated tests.
Learn with me about what Accessibility is, why it's important to test for and how to get your team started with an Accessibility testing mindset
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.