Skip to main content

How to hire a tester

Being a tester is quite confusing: you write code, but you’re not a Programmer. You perfectly know business requirements, but you’re not a Product Owner. You handle test environments, but you’re not an DevOps. Role of technical testers in modern agile development teams is significantly different, and requires knowledge in many fields: software engineering, programming, test automation, environment management, …etc. Result? Hiring good and experienced testers becomes more and more difficult, since being one often means to be in temporary state before turning into programmer or product owner role. So, how to hire dedicated testers?

Screening job candidates 

We’re lucky ones working in IT, since it’s employee market, and usually you don’t have to search for a job – you receive the offers. For recruiter, first and most obvious phase of searching an ideal candidate is screening LinkedIn profiles. I’m not a recruiter, but from candidate perspective it’s looks too often like sending an offer whenever one will see ‘testing’ in profile. It really makes difference whether candidate is manual tester or automation engineer, or if he has one or seven years of experience. Proper screening will not only save your time, but also will help you to build future relations with candidates.

Role description 

“If you’re interested in changing job, send me your cv” – it’s not a joke, it’s a real message I receive often from the recruiters. Although above it’s an edge case scenario, there are still some more common issues. The bottom line is the more detailed offer you would provide, the better are chances for it to succeed. If you’re searching for a technical tester, it really makes difference if you’re in jvm or .net. Personally I have a habit of always replying (despite that I’m not actively searching for a job) for offers that are well described. Another thing is salary spread. Although I’m big fan of providing salary min & max values, it’s still a taboo. I have no doubt that providing full job details will be an advantage and I look forward for market to adapt.


I’ve noticed that Interview questions for testers’ interviews are causing some concerns. I want to focus on interviewing test automation engineers, since I consider myself one. If your company claims to hire some of the best programmers, you should treat test engineers like so. You can’t ask programmers during interviews for solving complex algorithmic problems, and then ask people who would test their implementations “how would they test a pencil”. Tester’s mindset is one thing, but you can’t fake technical abilities. Good practice for technical testers’ recruiting is providing a home work task of implementing some test automation code, or even better – pair programming during the interview.


“Here’s your laptop, and somewhere there is a pendrive with ubuntu. We have a full list of task so tell me when you’ll be ready” – another real life example, and you’d be surprised by the maturity of IT in this company. I think everybody in your team will get advantage of quick learning architecture, workflow and corporate procedures by the new teammate. Guess what – you can accelerate that process by providing new comers some kind of introduction. Whether it will be one day training or week of some peer assistance, both team and new worker will get profit. Although this blog is 100% independent, I can certainly recommend my current company in this field. In every new employee passes through one and a half month bootcamp, during which you spend every two weeks in different team, and then you choose your final one.

Skills development 

Every geek likes to develop his skills and knowledge. Company should provide proper environment to keep their workers hungry for learning. Conferences and trainings are must, because that’s how you ensure they are up to date with newest technologies and solutions. Besides that, rummy idea is r&d day once a while. Yes, this is a cost for the company, but it’s still cheaper than recruiting for resigned positions.


In above points I intentionally omitted salary issues, but for sure – valuable and experienced employees needs to be appreciated. Worth to noticed is despite the fact I wanted to point out core aspects, that would help to recruit good technical test engineers, in most cases if you change word testers to programmers, thoughts would be still valid.

Popular posts from this blog

Test Automation: Good, Bad and Ugly

The modern approach to software quality and software development life cycle requires that business guys, developers and testers understand that the long manual test phase, although often still necessary, must be reduced to a minimum and replaced by test automation. Working in continuous delivery and continuous integration environment requires us to create automated tests that run on demand, checking our application integration and it’s core functionality correctness. However, there are still many problems with designing and writing automated tests, resulting in their costly maintenance or abandonment in favour of a return to manual processes.
In this article I will focus on describing common good practices of test automation. This post is more than an overview than complete reference guide. Broader aspects, such as the Page Object pattern or Page Factory will be described in detail in a separate article on this blog. Although most practices apply for every types of automated tests, thi…

REST-Assured framework overview

In modern software development, REST services becomes most popular choice for implementing distributed and scalable web application. They are light and easy to maintain, which results in faster and more effective implementation and system integration.
I recommend you also my other posts about REST-Assured and building microservice’s test automation frameworks: REST-Assured: going deeperBuilding microservices testing framework
With the increase popularity of RESTful services, there is a need for fast and lightweight tool for REST webservices testing automation. One of the most popular choice is Rest-Assured framework from Jayway. It introduces simplicity of testing web services from dynamic languages like groovy or ruby to java. In this post we will get our hands dirty and write automatic test in Rest-Assured framework.
In order to create complete implementation of automated tests in Rest-Assured framework, we need to write our code against some example API. We’ll use standalone Wiremock m…

REST-Assured: going deeper

In my previous post I described the basic REST-Assured usage – the lightweight framework for testing RESTful services. Despite the fact that described range of functionalities would be enough in most cases,REST-Assured has a lot more to offer. In this post I would like to bring some more advanced examples of the framework usage.

I recommend you also my other posts about REST-Assured and building microservice’s test automation frameworks:

REST-Assured – framework overviewBuilding microservices testing framework
Object Mapping Sending request’s body as string is easy and straightforward, but it can be inconvenient in the case of more complex operations on request / response properties. Proven solution for this is a good-known serialization of request/response body to objects. REST-Assured supports object mapping to (and from) JSON and XML. For JSON you need either to have Jackson or Gson in your classpath and for XML you need JAXB. Here is an example of request object serialization using J…