I thought this would be an interesting share, this has never happened to me. A few days ago I received a recruitment email from a local recruiter who found me on LinkedIn. I figured it couldn’t hurt to see where the exchange might lead. I’m always curious to learn what’s happening in other parts of our industry. I’ve learned that often times you can distinguish what values are implicitly expressed and valued by an interviewers questions. You can also learn a lot by what is not asked in an interview.
<Insert Recruiter Name>
Here are the responses that you requested. I realized while answering the questions that there is perhaps a significant difference between <My Company Name> and <Company Seeking Groovy Peoples>. Our organization is fairly flat when it comes to our Professional Services QA team. There are no test leads per say, we act as a collective body who critique each other. As a generalization each person on the team tends to specialize in areas of the product. I was brought onto the team to focus on automation and push the team towards best practices.
But what does a test plan at <My Company Name> consist of?
The short answer is the level of granularity in a test plan at <My Company Name> varies depending on the specific project, the amount of risk introduced into the system by the changes, the module being tested, and time constraints. Often times these begin as broad-stroked outlines of tests that we aggregate into test suites. Due to the nature of our interpretation of the agile process a story’s implementation often evolves throughout the sprint. It is up to the tester to work closely with the developers, customer, product owner, and system architect to understand and guide the test plan appropriately. I should note that I believe it falls on the tester to play the role of understanding the largest picture of the system that is being developed for and helping the team keep that picture freshly oriented during the different development phases.
