Subscribe
.svg){kind=small}
The Outdated Job Title That’s Hurting Your Software Quality
Have you ever been in that project meeting where another member of the project team, whether a Project Manager in a rush to ‘get the feature out’ or a Product Owner who maybe doesn’t get the technical complexity of a seemingly simple change asks ‘does this need to be tested?’ ‘Testing’ is often seen as an unnecessary overhead by some in a project team or a wider organisation. However, if we reframe the question I think we can remove that roadblock.
5 mins
In the fast-paced world of software development, titles and roles are evolving as quickly as the technology itself. Once upon a time, the role of a software tester was clearly defined: ensure the application works as expected, find bugs, and report them. However, as methodologies like Agile and DevOps revolutionise the way software is built, the responsibilities of testers have expanded dramatically. This evolution has led to a growing consensus within the industry that the job title of "software tester" is outdated and may be detrimental to the perception and effectiveness of the role. Enter the Quality Engineer.
The traditional software tester was largely seen as a gatekeeper, positioned at the end of the development cycle, tasked with catching defects before the product reached the customer. While this role was crucial, it often led to a siloed approach where developers and testers worked independently of each other. This separation can result in communication breakdowns and a lack of shared responsibility for the product's quality.
In addition, this approach leads to a perception that the ‘tester’ is being spoon-fed the information to test against, when in fact we all know that the role of ‘tester’ has always been much more than that. There has always been a considerable need for upfront analysis, and understanding of features, followed by the development of methods of verification before the ‘tester’ gets to the point of ‘testing’.
'Anyone can Test!'
Stay Ahead with the Latest in Software Quality!
Unlock expert insights, industry trends, and proven tips to enhance your software quality processes. Whether you’re a QA professional, developer, or project manager, our newsletter delivers actionable strategies straight to your inbox.
- Exclusive articles on testing best practices
- New tools and frameworks to boost your workflow
- Case studies from top-performing teams
- Pro tips from industry leaders
Join a community of innovators who prioritise software excellence. Sign up now and start building better, more reliable software today!
Subscribe to the Newsletter Now!
This perception leads others to think that ‘anyone can test’ and demeans our profession considerably.
So I believe that we need to reduce the term ‘testing’ to a mere task in the pipeline of activities that Quality Engineers undertake.
This approach allows us to reframe the original question that the project member asked from ‘Does this need to be tested?’ to ‘Does this need to be a quality delivery?’ - find me a Project Manager or Product Owner who would say ‘No’ to that question.
Reframing our roles to Quality Engineers directly feeds into the notion that quality activity takes place earlier in the delivery cycle - now I know that in reality testers are engaged in a delivery project as early as they can be - the notion of Shift-Left (which I hate as a Buzz Word) has been around for far longer than the Quality Engineer role term.
I am not trying to take credit for the creation of the role ‘Quality Engineer’ - it has been around for far longer than this blog post, but I am suggesting that it needs to be adopted far more widely than the current renaming of Automation roles that it seems to align with. Those in the profession that focus on Manual verification efforts are just as equally Quality Engineers in my view, and often gain a deeper business understanding of a feature as a result of the Manual approaches that are taken than some Automation Engineers.
Quality Engineers are integrated throughout the development process. Their role is not only to test the final product but to ensure quality is built into every stage of the development cycle. This shift in perspective transforms them from gatekeepers to facilitators of quality, fostering a culture where quality is everyone's responsibility.
One of the key reasons for this transition is the adoption of Agile and DevOps practices, which emphasise continuous integration and continuous delivery (CI/CD). In these environments, waiting until the end of the development process to perform testing is no longer viable. Quality Engineers work alongside developers from the outset, implementing automated testing solutions and monitoring tools that ensure quality is maintained at every step.
Moreover, Quality Engineers are involved in designing test cases and strategies, developing test automation frameworks, and even writing code alongside developers. This technical involvement requires a broader skill set than traditional testers, blending software development skills with testing expertise. As a result, Quality Engineers serve as a bridge between development and operations teams, ensuring seamless collaboration and communication.
Beyond technical skills, Quality Engineers also play a vital role in advocating for the user experience. They bring a user-centric perspective to development discussions, ensuring that the software not only functions correctly but also delivers value to the end user. This holistic approach to quality considers factors such as usability, performance, and security, all of which contribute to a superior user experience.
Another significant advantage of adopting the Quality Engineer title is the shift in mindset it promotes within organisations. By acknowledging the expanded role and responsibilities of these professionals, companies signal their commitment to quality as a fundamental aspect of their development process. This change in nomenclature helps break down silos, encourages collaboration, and fosters a shared sense of ownership for the product's success.
In conclusion, the transition from software tester to Quality Engineer is not simply a rebranding exercise but a reflection of the evolving nature of software development. As the industry continues to embrace Agile and DevOps practices, the role of Quality Engineers will be instrumental in driving innovation, improving collaboration, and ultimately enhancing software quality. By recognising their contributions and adopting a more accurate job title, organisations can better align their teams and processes with the demands of modern software development.
Build Quality, Scale with Confidence!
As a startup or scale-up, every line of code matters. Achieve flawless software from the ground up with expert guidance tailored to your growth stage. Our consultancy specialises in helping ambitious teams like yours:
- Speed up development without sacrificing quality
- Implement scalable testing strategies that grow with you
- Avoid costly bugs and ensure seamless user experiences
- Get personalised advice from industry experts
Don’t let quality hold back your momentum. Book a free consultation and let us help you deliver reliable software, faster.
Book a Free Software Quality Consultation!
