Where’s the Career Path?

One of the major downsides to quality assurance is the lack of a career advancement path.

On a project nowadays, you may have forty to sixty temporary testers, after which maybe two or three are brought on as full-time testers.  In a department of forty to sixty full-time testers, you may have maybe five leads that cycle between products or ten leads that vacillate between leads and individual contributors.  Finally, you’ve usually only got a single QA Manager, although some organizations are splitting it up so that there is a manager per fifty testers or so.

In short, you have a major funnel from temp to tester to lead to manager and if any level is filled, your opportunities for advancement are severely restricted.

The question is…why should the funnel exist?  There are many ways that organizations can allow testers to grow without forcing them through the funnel.  These are a few of the possible ways that your organization can allow growth within QA without “breaking” the funnel.

Specialization: As time goes on, testers often find that they excel at testing a certain type of feature.  It may be console certification testing, it may be localization/globalization testing, it may be multiplayer testing, it may be UI automation…the point is that this person has shown that they excel at it.  If the workload allows it, it may benefit all projects to have a person be a specialized tester.  Another advantage of specialization is that if your testers are allowed direct access to your development team, the tester and developer of certain features are going to be interacting more often and the communication channels between these individuals will be a lot smoother, resulting in more bugs found and fixed.

Tiers: In many companies, there are only four levels a person can be: temp, tester, lead and manager.  This makes it very difficult for someone to advance, but you can also have sublevels or tiers within these levels.  After all, not every tester can or should be a lead, but that’s no reason to minimize their chances for career advancement.  Some companies have recognized this and have a “V” type system at each level where a tester can go be a lead, or become a Senior Tester or a mentor or something else.  It means an increased amount of responsibility and a structured career path.  People can choose to grow into their current tier or try to advance to the next tier without having to worry about being “managed up or managed out.”

Split Positions: Not everyone goes into QA to stay in QA.  Often, people go into QA as a stepping stone into other positions.  QA Managers can work with other departments to try to allow their testers who want to migrate to other departments to essentially let them “intern” in other departments for 2-3 days a week, usually interning Monday and Tuesday and test the remainder of the week.  In exchange, the other departments absorb the costs for those days.  This way, the employee gets a chance to grow, the departments get cheap labor and the QA manager still gets a tester without having to fund the entire position.

What other ways do your companies allow testers to grow when they hit a tier ceiling?

5 Comments

  • ckreitz wrote:

    Really nice ideas ! I’ll try to use them for my QA Team as it’s not always easy to give opportunities to those who deserve one !!!

    cyrille k / qa manager somewhere in France

  • Personally, I think management is just that bad. Gaming for a living is many a dreamer of young men and women that will work for pennies hence there will always be plenty of 1st level workers. The top should care about the bottom but that rarely happens.

  • Game QA Blog…

    I have witnessed the truth of that in my career as a game tester – truly each and every company I have worked for or with had its own approach to testing….

  • pure_orange wrote:

    I think this is partly our own fault though. Game QA does not have a unified approach or standard, so the quality of QA at different companies varies immensely. Many QA Managers hire complete idiots to test (espeically publishers) and thus developers get used to not taking us seriously.

    If you’re a QA Manager, it’s your job to make sure your department is taken seriously and seen as a talent pool, which can be done with good hiring and training. Due to the nature of the job, testers often don’t have time to do much outside of work, so again, we should ensure they have a have a good work/life balance and encourage them to learn on their own (personal projects, courses, etc).

    I’m working on an MMO at the moment, so it’s easier to keep testers and help them progress. Since console development usually ends when you ship, there’s not much we can do (shipping bonuses are good as they give testers some time to do their own thing before having to find another job).

    qa manager

  • gary wong wrote:

    from what i have read of the above comments its very very true.
    maybe we should employ what the industry standards are. get istqb/iseb. have teaching course on how to write prepare correct test plans/defect reports. ONly then is when i feel qa in game will mean Qaulity.
    my exp in games have left me with a bad taste. no training, yet full accounterbility when things go tits up.

Leave a Reply

Your email is never shared.Required fields are marked *