Home » Forums on this site » Testing Industry Discussions

What would you expect from a Systems Test Analyst Role

I have recently been approached by and agent representing a financial services organisation. This is not uncommon as I tend to keep my CV online as I like to keep one eye on the market.

The role sounded quite interesting (Test Analyst role, local, decent money) but the actual job description and what is expected seem a little optimistic for an analyst position - it sounded more in line with Lead or Management Position.

As I understand it this role involves systems analysis as well as taking complete control of a test process. Working at component level I (potentially) would be responsible for the entire test process from end to end; including chairing walk-throughs, and defect resolution via developer contact.

It doesn't seem like a problem. However, this is a little high end from what I am used to. I am happy discussing this role but feel that it should re-numerate me on a par with a test lead at my current company.

What are your thoughts on this? What would you expect from your test analysts? Am I right in thinking this level of duty in an analyst role is fairly uncommon?

Any comment appreciated..

‹ Cable & Wireless Worldwide is looking for a Test Manager in London! Introducing Keyword-driven Test Automation ›

Interesting problem. What is

Interesting problem. What is expected from a Test Analyst depends a lot on the size of the team. I have worked in a company of 14 people and in that situation they just required a small test team of one initially who reported to the Operations Director. The tester here was expected to do pretty much what you've just described. In my current company we have analysts for each stage of the lifecycle a number of Team Leads managing each phase and work package and a Test Manager managing the whole lot. Around 150 testers doing everything you describe. For the role you've described I'd ask a few questions if I was you. e.g. How big is the team? What are the actual day to day activities performed by the current analysts? What is the command structure? In a larger team this would really just be full lifecycle testing. i.e. Unit through to UAT. The rest could just be describing an Analyst trying to do their job. e.g. Talking to a developer to find out what the release is about, chairing walkthroughs is all about which team takes responsability, managing the defect lifecycle suggests they don't have a Defect Manager so the person who has most interest in defects, i.e. the tester who want's to verify it, chases it through the system.

The description can be interpreted mulitple ways. Ask some questions. Clarify the real responsabilities. I bet you'll find you do most of it already in your normal job.

  • By SteveAN at 25 May 2011 - 13:01