Why Test Engineers Fail Interviews (A Hiring View)

I interview candidates for my QA team, and many of them fail on the same three things: language basics, fit with the team, and how they react to a problem they haven’t seen before. Here is what I see from the other side of the table.

Weak programming language basics

Test engineers who write automation need to know the basics of their language. Knowing how to write a test is not enough.

Most of my work is writing tests, which is repetitive and easy. But now and then we have to build something custom, like our runner based on jest, or TestKeeper, an application that handles tests across micro-services. I’m fairly sure many candidates could write something like that. I’m also sure the code would be hard to maintain.

One of my questions is very simple: what’s the difference between let, const, and var? It is a standard JavaScript interview question. Many candidates couldn’t answer it, and that surprised me.

The short answer: var is function-scoped and can be redeclared, let and const are block-scoped, and const can’t be reassigned (an object declared with const can still be changed inside). The MDN pages on let and const cover the details. Another basic worth knowing is destructuring, which shows up constantly in test code.

Fit with the team

If your approach or personality doesn’t fit the team, you won’t get to the next stage. That’s not your fault, and it’s nothing to take personally. As a leader I care about it a lot, because one wrong fit changes how the whole team works.

These are the traits I look for in a tester:

  • proactivity
  • problem-solving
  • business point of view
  • flexibility
  • quick learning
  • collaboration and social skills
  • communication skills

Problem-solving in a QA interview

The trait I value most is a problem-solving attitude, in interviews and in daily work. A good tester doesn’t back away from problems. People come to us with hard questions all the time. If you don’t know the answer, ask around and find it. That usually means doing something, so treat it as a challenge.

In recent interviews, some candidates tried to solve the task even though they had never seen anything like it. Others said “I don’t know” and stopped there. That second answer is the wrong one. If you have no experience with a topic, say so, then tell me what you think it could be. It isn’t the right move for every question. But I like it when someone reasons out loud in their own words, because that shows me how they handle a challenge.

How to prepare for a test engineer interview

Interviews are stressful. Preparation helps: learn the language basics properly and go in ready to reason through unknowns. These are the fundamentals only. The rest depends on the position, your seniority and your experience.

Some articles that helped me think about job hunting:

To see what the job involves beyond the interview, read who a QA engineer is and what they should know. If you are early in your path, first steps in test automation tells you what I would learn first.