Interview questions for hiring managers to identify specific job requirements

You’ll be given a job description packed with words like “proactive”, “hands-on” and “stress-resistant”. Sounds great, until you have to decide who to approach and who not to. A good initial interview with the hiring manager turns vague terms into measurable job requirements, so that you can make fair selections later on and reach decisions more quickly.

Why the initial interview often goes wrong

Many initial interviews get bogged down in the job advertisement and a list of “what we’re looking for”. The result: everyone has a different idea of what the role entails, and the interview turns into a competition to impress.

The biggest pitfall is that you don’t get a clear picture of what “good” means in this role. You’ll then end up selecting candidates based on gut feeling, and that compromises both quality and speed.

• The ‘must-haves’ aren’t rigid enough (or turn out to be flexible after all).
• Success in the role is not reflected in behaviour and output.
• There is no agreed definition of “sufficient” versus “strong”.
• The hiring manager expects “the ideal candidate” rather than a suitable profile.

If this sounds familiar, it helps to approach intake questions as a design exercise: you establish the benchmark before you start measuring. A structured follow-up interview then almost naturally falls into place. See also how to put this into practice in How to conduct a structured interview in 8 steps.

Preparation: what you need to know in advance

Don’t go into the interview just saying, “Tell me about the role”. Take a short checklist with you and supplement it with context from the business.

Three things that will instantly make your intake process more effective:

• Current situation: Why is this role vacant, and what went wrong – or right – with the previous appointment?
• Achievements in 90 days: So what must a person have demonstrably achieved?
• Prerequisites: working hours, location, qualifications, physical requirements, shift work, travelling time.

If your organisation uses several interviewers, this is also the time to agree on who will assess which aspects. This prevents duplication and discussions afterwards.

Interview questions for hiring managers that really get to the heart of the matter

Use the questions below as a starting point. They are phrased in such a way as to force you to be specific: tasks, outputs, evidence and risks.

1) What is the real problem that this recruitment is intended to solve?

Ask about the “why” behind the vacancy. Not as a story, but as a situation with consequences.

• What happens if the vacancy remains open for 8 weeks?
• What is the team currently struggling with: quality, safety, planning, turnover, customer complaints?
• Which tasks are now left undone, and who will take them on?

This helps you set priorities. Everything can seem important until you link it to its impact.

2) What does a typical working week actually look like?

Ask the hiring manager to “walk you through” a typical working day and probe for further details. This will prevent you from selecting candidates based on a profile that is too generic.

• Which 5–8 core tasks take up the most hours?
• Where are the peak times, deadlines or disruptions?
• What systems, machines or tools does a person use on a daily basis?
• Who does this role liaise with on a daily basis (and on what matters)?

Please note down words that are measurable: numbers, lead times, quality standards, safety procedures.

3) What are the essential skills, and what can be learnt?

This question lies at the heart of “hiring manager interview questions”. You want to know in black and white what’s a deal-breaker and what you can work on.

• Which certificates or qualifications are required on day 1?
• What kind of experience really cannot be replaced by training (and why)?
• What else can someone learn in the first three months?
• Where do you draw the line: how much support can the team provide?

Tip: let the hiring manager choose a maximum of three ‘must-haves’. If everything is a ‘must-have’, then nothing is a ‘must-have’ anymore.

4) When is someone “good” as opposed to “top” in this role?

Ask for examples of behaviour and results. This will help you come up with better interview questions and assessment criteria later on.

• What does a high achiever do that an average performer doesn’t?
• What mistakes do you see in people who don’t make it?
• What signs are you already seeing in week 2 (both positive and negative)?

You can often gather input for a scorecard here. If you wish to formalise this on a regular basis, this ties in with creating a selection scorecard for hiring managers.

5) What situations should we simulate during the interview?

An intake is also the time to determine which case study or real-life situation is the most representative. That way, you’re not testing “general intelligence”, but relevant behaviour.

• Which 1–2 situations occur frequently and make all the difference?
• What choices does one have to make in this regard (speed versus quality, safety versus output)?
• What constitutes an acceptable solution, and what is unacceptable?

For blue-collar or technical roles, this might involve troubleshooting. For sales, it might involve dealing with requests such as “just send a quote”. For logistics, it might involve prioritising tasks during peak periods.

6) What are the risks of a mismatch?

This can feel a bit awkward at times, but it makes your selection process fairer. You identify in advance where things could go wrong.

• What usually causes people to drop out of this role?
• What is difficult about your culture or way of working, specifically in terms of behaviour?
• Which working hours, commute or physical demands put candidates off?

By discussing this at an early stage, you can screen candidates more effectively and avoid taking on those who are unlikely to succeed.

From initial assessment to objective selection in 3 quick steps

If the intake process is sound, you can make the transition to selection almost automatic. Keep it simple, so that the team actually uses it.

Step 1: Write the functional requirements as testable statements

Replace words such as “proactive” with observable behaviour.

• Not: “proactive”. But: “identifies deviations in the process and takes action without being instructed to do so”.
• Not: “stress-resistant”. But: “continues to prioritise during peak periods and communicates risks in good time”.
• Not: “team player”. But: “hands over work thoroughly and actively seeks feedback”.

Step 2: Link each requirement to a measurement method

If you cannot assess it, it should not be included as a criterion in the selection process.

• Behavioural question (STAR) for real-life examples.
• Case study or task involving reasoning and decision-making.
• Knock-out check for strict preconditions.

Step 3: Set out how you store your data and for how long

Job application data is subject to privacy regulations and must be handled with care. Keep your notes factual and do not keep them for longer than necessary.

For guidance on retention periods and transparency, please refer to the Dutch Data Protection Authority’s guidance on Job application details and privacy.

Common mistakes made during the intake (and what you’re missing out on)

The hiring manager lets “gut feeling” guide their decision

If the intake interview ends with “I’ve got a feeling about type X”, you’re failing to link that to evidence. Your interview will then automatically become more subjective.

Everyone wants to test something different

Operations assesses professional competence, HR assesses motivation, and the team lead assesses whether there’s a “click”. Without agreed criteria, you’ll end up comparing candidates against different benchmarks.

Must-haves adapt to the candidate

If a good candidate isn’t quite the right fit, the bar is lowered. If a less suitable candidate meets the same criteria, the bar stays the same. That’s exactly the sort of confusion you want to avoid from the outset.

This ties in directly with the pitfalls that FosFor frequently observes in the selection process. The brief summary in These 4 mistakes are costing you your best candidates is a good reality check for teams that want to improve quickly.

Practical input and output (what you want to have achieved after 30 minutes)

If, by the end of the conversation, you are still unable to produce a tangible document, the initial consultation was too vague. Aim for the following outcome:

• 5–8 core tasks specifying how time is spent.
• 3 must-haves (knock-outs) and 3 key takeaways (can be developed in 90 days).
• 4–6 success criteria with brief behavioural cues (what do we see with a 3 and with a 5?).
• 1 case study which is just like the real thing, with “right” and “wrong” clearly defined.
• Process agreements: Who conducts the interviews, who scores the points, and when do you make your decisions?.

A gentle next step

If your intake interviews tend to rely too much on gut feeling, you can become much more objective with just a few small adjustments: one clear ‘must-have’ list, one case study, and one scorecard. If you’d like to set this up together for your roles (blue-collar, sales or maritime) and link it directly to a rigorous selection process, this fits in well with FosFor’s data-driven approach.