Skip to main content

How to choose a QA specialist for your team?

To be honest interviewing for any position it is a hard task and QA is no different. Interviewer have to know what is the set of required qualities to do the requested tasks and what is the set of qualities that should be placed in "Nice to Have" category. From that perspective QA is the most complicated position in IT market as two general approaches are gaining ground in the field: "Technology View" and "Quality View". So which one of those two is more efficient in finding highly rated QA professionals?

Technology View
In this approach interviewer assumes that Quality Assurances its all about familiarity with a specific technology or business field, so if a person worked for 3 years in banking industry this person will be a perfect candidate for any banking position, or if a person performed nicely for several years testing in JAVA environment this person will be a terrific match for any QA position in JAVA development environment, unfortunately live are not so simple and those assumptions are usually incorrect and harmful for the company.
Quality View
In this approach the goal is to find quality oriented specialist which is interested in understanding how the required system working, interested in finding out what are the weak and breakable points of each feature, has a great attention to details and seas each test cycle as a new challenge. This person should have a technical set of mind, terrific understanding of SDLC, QA`s place in the company, and finally see his (or her) work as mission, a quest for better quality and product.

So when we are looking for QA  specialist his (or her) technical set of mind and a passion for quality should be the mandatory skills for any QA position. Don't get me wrong, a previous experiences in a specific business field is a nice-to-have advantage and can be a discussion maker on final stages of a selection process, but its completely wrong to use those factors as requirements in the initial selection process.
Some time ago I consulted a company that was in a process of creating a new QA department they started by hiring a new QA manager which came from development department and was all about hiring by using a Technology View approach (which is very useful and popular in development departments). His approach was all about mirroring the hiring process in development, so if the company planning to develop a trading system in .NET environment - developers should have .NET experience and QA should have trading experience, which led to poor quality results in QA. My suggestion was to switch to Quality View in the hiring process. I instructed the HR team accordingly and the result was terrific, in 6 months since my arrival the new QA team performed faster and better then their predecessors.
My suggestion to both HR and the hiring managers is to use Quality View as the candidate selection method for QA position.

If you are interested in hiring quality assurance specialist please visit Broad Sky Inc


Popular posts from this blog

7 Most Popular Test Types in Software Testing

Today we are going to return back to basics of software testing and discuss the 7 most popular test types that are being used in every software testing effort. Those different test types cover all the levels of the software to make sure that the final result matching the expectations from every possible angle. Here is our list: Unit testingSmoke testingRegression testingFunctional testingIntegration testingUser Acceptance TestingPerformance Testing

Now let’s have a deeper dive into each one of those by using a simple example of an imaginary system that was created in order to manage warehouse activity including shipments, inventory and goods receptions from suppliers.
Unit Testing This type of testing is usually performed by the developers and is covering the very basic development component. In this test developers are testing the straight forward functionality of a functional piece of code to make sure that it is performing according to their expectations. In our example: This test w…

Story Points estimation for Scrum with Fibonacci vs Shirt Sizes vs Linear - 7 minute guide

It is all began long time ago when Development Teams were constantly asked to provide estimate and they were having a hard time to properly face the task. Let's admit it, there are so many things that can change, happen, and simply go wrong during the development process that one can hardly expect a proper estimation of hours for each task. That why a relative estimation with Story Points came along.

Story Points Estimation
Its a different way to estimate the effort of the Scrum Development Team with-in Agile methodology, which means that instead of estimating hours of work the team estimates each effort relatively to other efforts in the project.
Let's assume that a developer knows that specific 'Task 1' is much harder than another 'Task 2' it is hard for him/her to quantify that harder feeling in hours of additional work but it is possible to say that it much more work. This situation is being address by Story Points when each story point is representing som…

5 Steps to Install Robot Framework for Web Testing Automation - 7 minute Guide

Lately, I found myself helping several people to begin their automation testing journey. And what a better place to do it then a nice new installation of a Robot Framework with its Selenium2Library on a Windows OS.

Why Robot Framework with Selenium2Library? While you are probably here because you are looking for a quick installation guide for Automation Testing platform for you web project, I still need to do my do diligence and explain in couple of words why we need it.
Robot Framework it's a Python framework that allows for a less development oriented Manual QA professionals to do a quick switch into Test Automation. This can be achieved by allowing for easy English phrases (e.g. Click Element, Wait, etc) to replace a more complex Python syntax.
Selenium2Library it's additional add on on top of Robot Framework that allows easy interaction with web elements during the automation process.

That's it..... DONE with the talking now the installation....

Installation process Ro…