← Back to blogs

Are we hiring the right person?

qahiringleadership

I think most people will agree with me when I say that hiring is difficult. Over the years, I have been involved in hiring from different perspectives. I have applied for jobs, been interviewed, interviewed candidates myself and made decisions about who should join a team or not.

Companies often spend a lot of time creating their interview process. They discuss the number of interview rounds, the type of assessments, the scoring system and who should be involved.

What often receives much less attention is understanding what they actually need from the person they are trying to hire. Before creating interview questions, scorecards or deciding how many interview stages are needed, there is a question that should come first:

What problem are we trying to solve by hiring this person?

I have seen companies with very organised and well prepared hiring processes. Technical assessments, panel interviews, culture interviews, take-home assignments and detailed feedback forms.

But when I asked about the needs of the team, what is working and well and isn't or what they are looking for exactly, I often didn't get a proper answer. It would either stay quite vague, way too specific (unicorns) or they mentioned they didn't really know.

Whichever of the three scenarios, it is going to make it really hard to find the right candidate. Even with all the processes and stages in place.

Start with the problem, not the interview itself

Something I see a lot, and that in my eyes is a mistake, is that teams prepare the questions they will ask. They will ask every candidate the exact same questions and they are looking for specific answers as well.

In some cases, this happens very last minute as well. Someone realises an interview is coming up, opens an old document, searches online for example questions or asks a colleague what questions they normally use.

I'm not saying you should join an interview unprepared. There is nothing wrong with preparing questions. A consistent process is also useful, especially when multiple people are involved. But the questions should come from understanding what the team you are trying to find someone for actually needs.

Some useful questions to answer first are:

  • "What is the team struggling with today?"
  • "Where do we need someone to make an impact?"
  • "What is working well in the team and what isn't??"
  • "Which skills and characters do we already have in the team?"
  • "What would make us look back after six months and think: hiring this person was the right decision?"

Those answers should shape the interview, and not the top 10 questions to ask a QA that you can find on Google or the niche technical questions that you prepared.

Without that understanding, it is quite likely you will find someone with great skills, but that aren't necessarily relevant to the role at all.

The role you need versus the role you assess

I saw a good example of this through someone in my own circle (yes, QA people do occasionally socialise with other QA people!).

The company was hiring for a role focused on shift-left quality, coaching teams and improving collaboration. Automation was mentioned as part of the role, but it was clearly not the main goal.

Looking at the job description, I would have expected discussions around influencing teams, working with developers, improving engineering practices and helping teams take more ownership of quality.

However, the interviews focused on something else. Most of the conversations were about technical implementation details: frameworks, tools, programming questions, testing approaches and edge cases.

Something else that was strange was that the candidate never really got the chance to speak with someone they would actually work with after joining.

To be clear, there was nothing wrong with the interviewers or the way they ran the sessions. But they weren't aware of the needs of the team they were hiring for and because of this were assessing a different set of skills than the role description suggested.

That creates a difficult situation for candidates as well, as they might now ask themselves what the role will actually be:

"Is this what the company values most, or is the job advert leading and is this just what they happen to test during the interview?"

Technical assessments should have a purpose

Years ago, before I started interviewing candidates myself, I had a QA interview where I was asked to implement a graph in Java from memory.

The exercise was done on a whiteboard. No documentation, no Javadoc, no internet and no IDE. Alternative solutions were also not accepted.

I understand why companies use exercises like this. They can show how someone approaches a technical challenge and how they think through a problem when they do not immediately have all the answers. That it was a difficult exercise was also not a problem. It was still quite common in those days to program and do technical interviews on paper.

So the interview itself, apart from it being a bit too strict maybe, wasn't that strange by itself. What was a bit odd to me though was that afterwards, during the feedback conversation, I learned that the company did not actually use this kind of work in their day-to-day environment at all. They had never used a graph in the company.

Looking back at it now, I really question the value of the exercise. Did it actually assess if I had the skills to the job? I discussed the exercise with a senior Java architect afterwards and even they weren't so sure they could have done it.

There are definitely roles where algorithms, data structures or coding without assistance are important. In those cases, testing those skills makes sense. In this case, it wasn't that type of role at all.

The problem here was that some assessments stay in hiring processes simply because they have always been part of them and I see something similar in QA interviews.

Many technical assessments ask candidates to build a complete automation framework from scratch. As someone who genuinely enjoys building frameworks, I understand why people like these exercises. They are a good way to explore someone's technical thinking. However, most QA engineers do not join a company and start with an empty repository (unless you are like I was and you actually look for these roles).

It is much more common that they inherit an existing environment. They need to understand what is already there, decide what needs improvement and figure out where automation will actually help.

That is why I prefer to do code-review style interviews with my own candidates. Assessing how they think, what they would keep or do differently, what they find important, how they handle push back or different opinions, etc. Those discussions often tell you much more about how someone will act and work in the role.

Technical exercises can absolutely be useful, but the question is if they help you understand the skills the person will actually need.

Conversations teach you more than question lists

Good interviews obviously need some structure. Without it, it is difficult to compare candidates fairly or make sure important topics are covered.

However, the interviews I remember most are usually the ones where the conversation moved beyond the prepared questions or where it went completely off script.

A candidate might mention a decision (or opinion) they made in a previous role. If that sounds interesting, I usually want to understand why they made that choice. What alternatives did they consider? What would they do differently now (if anything at all)?

Those moments often tell you more than a prepared answer to a question they have probably already heard many times before.

You see how someone thinks when there is no obvious answer, how they communicate their ideas and how open they are to different perspectives.

I have also been in interviews where the interviewer was so focused on getting through the question list that they stopped asking follow up questions and in some cases barely listened to the answers. The next question was already waiting, even though the previous answer could have opened a door to a much better conversation.

The questions, and especially the follow up questions, you did not plan to ask are often the ones that give you the most insight.

Not everyone should interview

A potentially controversial opinion, but I do not think everyone should automatically be involved in hiring.

Being good at your job does not automatically mean you understand how to evaluate someone for a different role (or even the same role). Interviewers need context, they need to understand why the role exists, what challenges the team has (and company overall), what the long term plans are and what success should look like after someone joins. Without that, people naturally judge candidates based on their own experience or personal preference.

Different interviewers naturally notice different things. A developer might dig deeper into technical decisions, while a manager may focus more on ownership or communication. Both views are useful, but only if they connect back to what the team actually needs.

The goal of an interview is not to prove that the interviewer knows more than the candidate, but to understand if this person could succeed in the role. This is another problem I have seen a lot. To find the right candidate, you need an interviewer with the right positive mindset. You are looking for evidence to support your initial assumption that this candidate is a good match for the company, not the other way around.

But unfortunately there are quite a few interviewers that are trying to find things to make candidates fail. In fact, some people actually seem to enjoy it more when they found something that makes the candidate fail than if they make them pass. It might be because it makes them feel better, because they have a good time or just an unconscious wrong mindset.

You can often recognise these by the reasons for not passing the candidate, like: they answered one question 'wrong' (in many cases there isn't even a right or wrong answer), they work differently from us, they said one strange thing, they were nervous, they have an accent, etc. None of these are reasons to reject a candidate immediately and you will be missing out on great candidates if you don't have the right people doing the interviews.

The problem with hiring more of the same

Another pattern I have seen is teams hiring people who look very similar to the people who are already successful. It can work out, but it is more likely that a team genuinely needs more experience in a specific area. This can actually become a real problem later on.

A very technical team might actually benefit from someone who is strong at communication and coaching, while a team with good technical skills but weak quality ownership might need someone who can start conversations and challenge assumptions. The best person for one team is not automatically the best person for another.

The same applies to cultural fit. I like the idea of cultural fit when it means someone can work well with the team. But it shouldn't mean hiring people who think and behave exactly like everyone already there.

I prefer not to ask:

"Do they fit our company?"

But:

"Can this person help this team become better?"

Hiring is also about knowing what you can teach

Over time, I have become much more aware that not every requirement has the same importance. Depending on the role and team situation, some skills are needed immediately, while others can grow. A company that treats every requirement as equally important can easily reject people who could have become excellent team members.

For example, many technical skills can be learned. Someone can learn a new programming language, improve their automation skills or become familiar with a new tool.

However, changing someone's interests, preferences and attitude towards learning, communication or collaboration is usually much harder. Obviously, I am not saying that technical skills are unimportant, but hiring teams need to be honest about what they actually need on day one and what they are willing to help someone develop.

These days I think I can say that I mostly hire based on character and potential, not on current ability (for long term hires in farily stable to stable teams).

Every interview stage should have a reason

Hiring processes have a tendency to become too long. A technical assessment gets added because it was part of the process before. Another interview appears because someone feels they need more confidence before making a decision. A culture round gets introduced because other companies do something similar. But are you still sure that all these stages are adding value?

Like with everything else in this post, having multiple stages is not automatically a problem by itself. For many roles, several conversations with different people are extremely useful. As long as you ensure that each part of the process helps you understand something important about the candidate.

So before adding another step, it is worth asking:

  • What are we trying to learn from this?
  • Is this the best way to find that out?
  • Does this person need to be involved?
  • Is it still respectful of the candidate's time?

Conclusion

Hiring has taught me that the hardest part is usually not finding people to interview, but to define what you actually need right now.

I have of coures made hiring mistakes myself, and I am sure I will make more in the future. Hiring always involves uncertainty as you are trying to predict how someone will work in an environment they have not experienced yet.

But if look back at all the hiring processes I have been part of or that I had to lead, then the most succesful ones are the ones where I spend a lot of time on collecting requirements. What is the roadmap, what are the technical challenges, where did we see quality issues this/last year, what came out of the 1:1s with team members, etc.

The team always knows where they need help. They knew what is already working, what is missing and what kind of person would complement the team. When that understanding is there, the interview process becomes much easier to shape. The questions have a purpose now as they are connected to the reality of the role.

So, the conclusion of this all is that:

Many hiring mistakes are not caused by a lack of good candidates, but because companies never became clear enough about what they needed someone to do.

Finding the right person starts with understanding the problem first.


Alex Hovenkamp