As a software testing professional, would you describe yourself as a generalist or specialist?
- Generalist
- Specialist
- Something else, please comment
Bonus points for community commentary.
As a software testing professional, would you describe yourself as a generalist or specialist?
Bonus points for community commentary.
Generalist, in the general systems sense. An understanding of systems and relationships in a broad sense that can be applied to anything new. Building mental modals that draw from general experience, varied heuristic approaches to tackle complex systems quickly and build understanding. How to be stuck in that world between detailed analysis and statistical significance and come to useful conclusions.
In a more common sense, a generalist when it comes to software development, because it applies throughout the lifecycle and requires general understanding of a lot of topics. Knowledge of design, coding, deployment, databases, business, sales, support, software in general, platforms, anything that can affect the value of how we consider, uncover and evaluate risk.
Specialist, in the sense of specific skills of exploration or certain tooling or critical approach or intent. Focus/defocus, branch and backtrack, progressive mismatch, risk analysis, investigation and reporting, automation tools, database diffing, scripting; each could be considered a specialism.
Added together to mean âtesterâ, that could be seen as a specialism of specialisms. Who else specialises in all those particular specialisms? Only a specialist could be a generalist about all those specialisms.
Mostly I think itâs a matter of perspective, depending on the situation. A tester might be a generalist from the perspective of a âweb performance testerâ, or a specialist from the perspective of a âpersonâ.
Both probably. Mostly a generalist, but I do have a specific area of expertise within the general field of testing.
Weâre genspecialists
I describe myself as software engineer with a specialization in testing, so I picked âspecialistâ.
In my experience, when you just meet a person you want to provide enough high-level labels for them to put you somewhere on their map of professions. Yes, software development, and software testing, are extremely complex, nuanced and messy. So is that person discipline. But we hide these internal complexities from each other until they actually become relevant.
In tech, the term âgeneralistâ gets thrown around a lot, and often without much substance behind it. People add âgeneralistâ to their titles like âQA Generalistâ or âSoftware Testing Generalistâ but realistically, it doesnât add any clarity or value beyond âQA Specialistâ or âSoftware Testing Professional.â In fact these âgeneralistâ labels sometimes sound more like fluff than a real indicator of skill or expertise.
Being a QA Engineer or Software Testing Professional is already about having a broad range of skills across tools, methodologies, and testing strategies, a deep understanding of quality principles. Adding âgeneralistâ as a tag doesnât enhance that - it just muddles the picture. If youâre serious about quality, your expertise should speak for itself without relying on buzzwords
Personally, Iâm a QA Engineer, a software testing professional, so I can say that Iâm a specialist even after reading the definition of âgeneralistâ I wonât use it to describe myself because it doesnât make sense, itâs like a principal QA engineer. I donât even see any point in discussing this matter
I consider myself a mix of both. I am a generalist but also I specialize in different areas. The mix is 80% broad knowledge, 20% specialized focus. I like the term âgenspecialistsâ @rosie
My day to day work is testing a very specialised area, but I also try to stay flexible enough to do a deep dive in another area if needed
I see myself as a technology professional, specialising in quality and testing. Why would someone want me on their team? What do I bring? Specialist knowledge and skills in quality and testing. That doesnât mean that others donât also have knowledge and skills in this area, but it might not be their main focus, whereas it is for me.
That being said, there are degrees of specialism. I wouldnât say that being a quality and testing specialist automatically makes me a specialist in performance testing, for example. One might be a generalist in the field of quality and testing. Or one might have a sub-specialism, such as exploratory testing.
Generalist software and system developer, with a speciality in quality and testing?