The problem with titles for testers

Why focussing on titles is an anti-pattern that should stop in the Testing world.

Titles for testers

A very common problem with the software industry is the use of titles to describe the function, someone, in that position performs.

Take the testing space, for example, below is the innumerable no of titles that I have heard so far in my career. More to come I am sure as something new and shiny is invented or the domain evolves.

Wow, I am imagining if people with all these titles hypothetically came into a room and start talking to each other, How would they describe their role and what do they do on a day to day basis?

Do we as testers ever stop for a moment and think.

The difference

The answer IMHO is Not much

People with all these different titles essentially do similar activities on a typical software development team.

Yes, the scope or nature of work changes a bit based on how experienced you are and the project and team requirements. But they are roughly in the same ballpark.

There are some titles that add gravitas to a person based on their experience level and the organization’s hierarchy but for the sake of arguments lets just divide them into two broad roles.

Titles don’t matter — Alan page

How should I apply for testing positions?

If you are a person who is chasing after the next suffix or prefix in your title, then you are probably chasing after the wrong thing. Any such addition is not going to add much value to you as a tester in your career.

If you are someone who is looking for a testing role in any organization. Go ahead and apply to any of these titles (if you have the relevant experience and skills) and do not pay much attention to the innumerable no of suffixes and prefixes that come with it. Chances are this title confusion is present even in the organization with everyone having a different understanding of the terms based on their current or past thought models.

You’re on the ground role would be dynamic and as per team/project/company requirements and would anyways change as the company evolves.

What does a tester really do?

Hmm. With the above discussion, the most common question that comes to mind

If Titles do not make much sense? What does a tester really do / should do?

In a few words, Many things.

Testing as a role requires people who are generalists, in most cases T-Shaped and can wear multiple hats.

There is a whole set of activities that they do on a day to day basis that is all aimed at increasing the quality levels of the team. The domain/project/company that they work on might cause small shifts but these activities are largely inline.

Broadly a person with tester role does the following.

This list is not really meant to be exhaustive and should evolve based on your reality

In fact, I made a mind map to capture the set of activities that a tester does:


Phew. That’s a lot for a single individual to accomplish in a given timeline right?.

So naturally, we need people to specialize in a few of these areas while generalizing in others and that’s fine.

Expecting a title to be the clean separation between these activities might not be the best idea. The lines are always going to be a bit blurry.

So instead of sweating too much about the title.

Why not think about how you can learn more about these areas and improve. There are a ton of resources out there and going through these would most definitely add much more value for you in the long term.

Further, read

Apparently, I am not alone in this thought and there are many excellent articles already written about this, If this sparked something in your mind. Might as well go and read up a bit more:

Originally published at on February 29, 2020.

Manager SDET at Gojek, Bengaluru, I ❤️ to build scalable test automation frameworks and teams. Blog at 🇮🇳

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store