For example, do you have a âSenior Test Managerâ, a âHead of Qualityâ, a âPrincipal Testerâ or something else?
I am looking for titles of specialists - if at some point, you move to generalists, âSoftware Development Managersâ managing âTest Managersâ for instance, the answer would be âTest Managerâ. I also recognise test managers may well not be the senior testing professional in an org, just picking one title to use as a worked example.
If in doubt I am looking for the most senior test/quality specialist in your org. If you have a Test Manager and a Lead Tester in the same hierarchical, er, rung, feel free to mention both
Disclaimer to say - I hate job titles and hierarchy in general, but I am required to engage with it sometimes and feel itâs interesting to take the temperature of other organisations in doing so!
Well I work in consultancy so to be honest, I donât know for sure. We donât call ourselves " expert test automator" or âprincipal/senior testerâ. I donât think we do anything fancy with job titles since for us itâs more about how you deal with stuff compared to what fancy job title you have XD
Moving to consultancy company soon, my next role title is like a standard one âtesting consultantâ and the role can differ it depends on the project needs management, leading a team, tester, test automation architect ⌠as @kristof said.
In my previous company, we have levels/titles like
My current org is a consulting company with a matrix organization - with line hierarchy and customer projects in each direction.
Independent of that is the job bands/levels - and that goes for all job titles in the company (even in HR ): Junior, Advanced, Senior, Principal, Subject Matter Expert.
The highest individual contributor/testing specialist is a: Subject Matter Expert (in Test).
All testing specialists refer to a (line) manager, who then refers to a director and then all the way up.
Although I did met a âQuality Catalystâ called Hannah yesterday, that was a great title, somehow, that happened on the MOT google chat thingy bit.ly/testerhangout I think it is called.
As a senior QA I find it interesting that the most senior in your organisation is the architect. Itâs a great role, but is normally project/programme oriented - so the planning and decisions are about the project in hand, not the QA team in general. Architects are usually incredibly talented test gurus, but would normally be a âCâ in the RACI matrix for QA team management, recruitment and overall team strategy.
We have Principals - so a Principal Test Analyst and a Principal Developer in Test.
The Principal Test Analyst role is a very new role and so I am still trying to settle on exactly what they are wanting from this role as it is very different from the Junior to Senior Test Analyst roles on our product.
We have s simple structure with QAs, a test manager (doin the structure part of test plan ing) and then a few senior testers have s role as QA coach, and join the QA manager and test manager in various discussions along with guiding the rest of the QAs.
In my company we try to have a really flat structure, there is really only 3 levels of hierarchy.
(1) top of hierarchy
(3) bottom of hierarchy
We have roles of:
Quality Engineers (3)
SDET (3)
Prinicle Quality Engineers (2)
PET (Platform engineer in test) (3)
Priniciple platform engineer(2)
Performance Engineer (3)
Principle Performance Engineer (2)
Head of Quality (1)
Basically there is 1 Head of Quality, 6 Principles that reporting to HoQ and then around 40 different engineers that report into the principles.
Although knowing we not all on the same level, it certainly feels like we are. Props to the head of quality for creating this culture itâs fantastic.