5 Toxic Attitudes That Can Destroy a QA’s Career

Juliano Niero Moreno
2 min readMay 13


The goal of this text isn’t to discuss the technical knowledge required of QAs today, but rather to highlight behaviors that often make us unpopular in teams and even companies.

In my almost 15 years in this profession, I’ve seen and experienced many situations that have made me feel embarrassed in front of my colleagues. Without further ado, let’s go over the 5 attitudes that bother me the most in a QA:

1- Arrogance

When someone comes to you with a question or request for help, treat them with respect. Disparaging your professional colleagues only contributes to a deteriorating work environment. Even if you’re swamped with work and tight deadlines, explain your situation and offer to help as soon as possible, always in a respectful manner.

2- Becoming an Island

A QA does not work alone but is a member of a team, where everyone has to work together towards a common goal: delivering a quality product that adds value to the client. A good QA is accessible to the team, offers to exchange information, and most importantly, shows humility in learning, as there’s always something to learn from other team members.

3- Not Setting Traps

I still don’t understand the satisfaction some QAs get from not reporting problems or possible causes of problems as soon as they’re found. As absurd as it may seem, I’ve seen QAs hold on to bugs to release them when it’s more convenient for them. Never do this, as the biggest loser won’t be a specific person, but the entire team and the client. Understand that work is not where you should vent your feelings of inferiority. If you have self-esteem issues, seek appropriate treatment, don’t dump your frustrations on your colleagues.

4- Not Reporting Clearly

I know that for many QAs, opening a bug report is a moment of ecstasy, something they’ve been waiting for, a chance to show what they’re made of. However, when reporting a bug, be as clear and concise as possible. Opening a bug report that the developer doesn’t understand is like swearing at someone in another language. You may feel like you’re the ‘top dog,’ but to the rest of the team, you’re someone who doesn’t express themselves clearly. Remember that you’re writing so that others can understand. As a QA, you should have read articles on how to report a bug, so follow best practices.

5- Not Providing Evidence of Bugs

Ever heard the saying ‘a picture is worth a thousand words?’ As difficult as it may be to collect, remember that an image, a video, or even a log file can be crucial for the bug fix team to understand and correct the bug, as well as avoiding a lot of rework.

The goal isn’t to give a lecture or moral lesson but to serve as a warning to QAs starting their careers. I know I may have caused discomfort for many people, but I hope I’ve provoked self-analysis in you.

Do you disagree with any of the points mentioned above? Do you have anything to add?



Juliano Niero Moreno

Squad Leader with almost 20 years of QA experience, worked on diverse projects. Sharing insights and interacting with the QA community.

Recommended from Medium


See more recommendations