Skip to main content

The Software Testers Job Title... Meaningless!

Question: What does a “job title” actually mean?

Answer: A job title is the name used to describe a specific group of tasks performed by an individual for a business or another enterprise. A job title is an efficient way to tell what a person does.

Phil’s Answer: Nothing

As a software tester, does a job title really identify what you do day to day? Probably not!

Now – you are looking for a new role because your company just made you redundant, you go and search on a recruitment website with the search criteria of “Test” and get thousands of results?!?!

How many different job titles could you possibly uncover?

  • Test Engineer (and Test Engineer II, Test Engineer III, etc.)
  • Quality Analyst
  • Testing Analyst
  • Automation Engineer
  • Test Architect
  • Test Automation Developer
  • Test Manager
  • Director of Test
  • Senior Test Engineer
  • many, many more…

If you had to define your job title based on what you actually do what would it be? I think mine would be something along the lines of:

“Software Exploring Testing Mentor Coach Leader Planning Estimator Automation Engineer Lead Analyst”

Sounds ridiculous right? That’s because it is!

What is wrong with “Software Tester”?

Now let’s fast forward. You have a new job, the work is challenging, and you’re kicking ass. Your job title is merely tester, and you’re worried that people will look down on you because you don’t have a more prestigious title like Senor Test Engineer, or Senior Software Quality Specialist, or Super Tester from Mars!

I’ve recently moved from a company where I had progressed through the ranks, Test Analyst, Senior Test Analyst then on to a Principal Test Lead. I am now working as a Senior Test Engineer in my new role.

I was once told that you had to be in a specific role for a certain period before you could progress and that the end of the road was "Test Manager" Why?

Going from a "Test Lead" to a Test Analyst" doesn’t mean you have taken a step back in your career! You should never feel you are taking a step back when all you are really doing is progressing in your career. Different companies see the same job title as very different roles. This is important to remember.

Progression in a career should be judged by performance, and is generally judged by performance in their current role not the role they aspire to.

An individual’s performance will give a view of the level any software tester is working at, the key is not to let the role define you! You define the role J

Take the job title you are assigned with a pinch of salt... and roll with it, do what you do best !


Popular posts from this blog

My Testbash Brighton 2017 Notes

This was my second Testbash... if you ever get the chance in the future these conferences are a must!
I took copious amounts of notes from the 9 talks and tried to highlight my key takeaways here... hope they make sense but please comment if you have any questions :-)
Amy Phillips - Continuous Delivery
A survival guide to joining a fast paced environment/project…
Where does testing fit within Continuous delivery:

As highlighted, basically from start to finish…
There are lots of things we can do when joining a project that is using Continuous Delivery but one of the main points from this talk was to do your research! There should be an element of "Continuous" in every aspect of the project.
·Learning the ling, what's the difference Continuous Delivery, Continuous Deployment, Continuous Integration, Continuous design, Continuous Improvements etc.? ·Understand what your role in the project is going to be ·Understand the teams values, What's going well and maybe what the team p…

Is TestBash an Invaluable experience?

Over the last few years, I’ve attended four single track conferences at TestBash Brighton and Manchester. Most recently, September 2018 and April 2019.

One of the most common questions I get after the conference is, Was it worth it? Especially now given, I’m a contractor, and I attend at my own expense.

In short, Yes It’s definitely worth the trip!

That leads me into my question; does a single-track conference work for me, or could I get more out of TestBash?

Of course, there are pros and cons, some talks may not be as engaging, but this is no disrespect to the speakers, for me, it’s because I probably favour certain subjects and I’m pretty sure others will think the same.

Do I make the most of what’s on offer at TestBash? It pains me to say, No! I don’t make the most of the events leading up to and post the single-track conference so I could get more from the week.

TestBash offers master classes on automation. A full day of workshops. Test.bash() with talks on automation and technica…

The way we work shouldn’t be ‘Alien’ anymore, Should it!?!?

It’s been a good while since I have written anything (Mainly because I’m not that good a writer) but given my 16 months in the public sector I thought it was time… 
For a good number of years now the DevOps trend has given rise of buzzwords and methods aiming to speed delivery and it’s now an assumption of mine that most organisations are au fait with the term ‘Continuous Delivery’.
I was wrong…
Within the organisation that I am currently placed I believe I have a high-functioning collaborative team who work flexibly and in continuous cycle. We also involve the users which is a huge benefit to the development teams, but that’s not saying we get everything right 100% of the time! Teams must continue to learn and evolve to remain productive.
Our team work in one of several delivery groups and with this comes multiple challenges; Silos No single environment strategy lack of communicationsVaried ways of working.  And thats just to name a few, which is interesting when all delivery groups …