I was asked recently to describe in my own words what qualities a good performance engineer would have, as they were trying to make a decision on hiring a resource for their company. I came up with some stuff and thought it might be good to share it with you and offer it up as a discussion topic in the Forums for the site. Perhaps you can add your own input and help businesses make informed hiring choices. This is not for use with an official job description, but more about principles and concepts.
Those of you following my columns know that I have laid out in some detail how to begin building a Center of Excellence (COE) around performance testing, and centralizing it. Now I want to expound on three models that performance testing groups generally follow. Encapsulation refers to a silo approach. Enablement means allowing resources from other groups to self-govern their performance.
It is unfortunately clear that everyday more and more people enter our quality assurance profession with very little software architecture of engineering background to draw from. This is bad enough on the functional side, but is getting darn near catastrophic on the performance side. And, by the way, this is for all vendors, not just Mercury. It just may be more apparent here due to Mercury’s dominant market presence in this arena.