What behavioral interview questions are
Behavioral interview questions ask a candidate to describe a situation that actually happened in their previous work, instead of asking what they would do in a hypothetical one.
The whole of the technique sits in that substitution, and its consequences run further than the phrasing suggests. A question about something that happened has an answer with dates, names, decisions and an outcome, all of which can be probed. A question about something imagined has an answer that is a position, and positions are easier to hold than events are to have had.
The two forms, side by side
- Behavioral: tell me about a time you disagreed with your manager about the priority of a piece of work. What did you do?
- Hypothetical: what would you do if you disagreed with your manager?
The first asks for an event with details that can be checked and followed. The second asks for an opinion, and it is answered best by whoever has read about interviews rather than by whoever has done the work.
That asymmetry is the practical argument for the behavioral form, and it is worth stating precisely, because it is regularly overstated. The behavioral form does not make an answer true. It makes an untrue answer expensive, because an invented event has to survive questions about its particulars, and the particulars multiply as the questioning continues. An invented position costs nothing to maintain, because it has no particulars at all.
The four elements that make an answer scorable
A useful answer carries four things: the situation and its context, the task assigned to this candidate specifically, what this candidate did, and the outcome.
The third of those is the one most often missed, and the reason it is missed is that its absence is comfortable for everybody in the room. A candidate who describes an achievement in the first person plural throughout has told you about a team and told you nothing about their part in it. The account is fluent, it is usually accurate, and it answers a question that was not asked. Interviewers let it pass because interrupting a good story feels rude, and because the story is interesting.
So three probes belong in the interviewer’s hand at all times: what specifically was your part, who took the decision, and what would you do differently now. The first recovers the missing element. The second separates the person who made the call from the people in the room when it was made. The third is the only one of the three whose answer cannot be prepared in advance, which is why it is worth keeping for last.
The follow up is the instrument, not the opening question
The opening question is the cheapest part of this technique and the part that receives almost all the attention. Opening questions can be written once, shared, and reused for years without losing much. What actually separates two interviews using the same list is what happens in the ninety seconds after the candidate stops talking.
That has an awkward consequence for anyone building a process around this. The follow up is where the evidence is gathered, and the follow up is also the part that varies most between interviewers, which is exactly the property that breaks comparability. A candidate probed by an interviewer who asks three good follow ups produces a much richer account than the same candidate in front of an interviewer who nods and moves on, and the difference between their two scores is a difference between interviewers.
There is a workable line here, and it is the same one a structured interview draws. The follow up has to remain a clarification of the answer already given rather than a new question that enters the score. Once a follow up is scored in its own right, candidates are no longer being scored on the same instrument. Keeping the score sheet limited to the fixed questions, and recording follow up material as notes that inform the discussion rather than the number, preserves both the depth and the comparison.
How structure and content are two different choices
Structure describes how an interview is run: fixed questions, a fixed order and a defined scale. Behavioral describes what kind of question is asked: questions about events that actually occurred.
They are independent, and running them together is the most common confusion in this area. An interview can be rigorously structured and consist entirely of knowledge questions. It can be behavioral throughout and have no structure at all, which is in fact the usual case, since asking everybody to tell you about a time when is not the same as asking everybody the same question and scoring it the same way.
The practical reading of that is that adopting behavioral questions buys you nothing on comparability by itself. It changes what the conversation is made of. Whether the resulting scores can be added together is settled by an entirely separate decision, and an organisation that made the first change and believes it made the second has a set of numbers it should not be averaging.
Where the questions come from
The questions are not invented at the desk. They are derived from what the role requires, which means starting from the same material a situational judgement test starts from: events that recur in the role, collected and reviewed with the people who perform it.
What distinguishes the two is what is extracted from that material. The situational form turns the event into a hypothetical with supplied options and asks the candidate to choose. The behavioral form uses the event only to decide what to ask about, and then asks the candidate for one of their own. So the same underlying inventory of recurring situations supports both, and the choice between them turns on whether the candidates have a record to draw on.
What it cannot do on its own
It does not suit every role, and it fails in two distinct directions rather than one.
The first is the obvious one: a candidate applying for their first job has no professional events to describe. The usual repair is to accept events from study, volunteering or unpaid work, and it is a partial repair rather than a complete one, because the situations available there differ in what they demanded. Naming that limit is better than pretending the question worked.
The second is less obvious and is the more expensive. Technical ability is demonstrated by performance, not by description. A candidate can give a clear, well ordered and entirely accurate account of how they rebuilt a broken reconciliation, and the account is evidence that they can describe the work. Whether they can do it is what a work sample test is for, and the gap between describing and doing is exactly the gap that instrument exists to close.
So this is used alongside other instruments rather than in place of them, and the reason is not caution. It is that the two failure modes above are not failures of execution that a better interviewer could fix.
How it differs from a competency question
The boundary is narrow and it is operational. A behavioral question starts from a situation and extracts the behaviour from it. A competency question starts from a defined competency in the role profile and asks for evidence of that competency.
The first is wider in what it explores and the second is tighter in what it connects to. Which one is right depends on how far the role has already been analysed. An organisation that has a competency set for the role, with each one described in observable behaviour and at a defined level, can ask the tighter question and know what it is scoring against. An organisation that has not done that work will produce competency questions against labels rather than against descriptions, and a label is not something evidence can be weighed against, so the wider behavioral question is the honest choice until the analysis exists.
What spoils it in the room
- Asking the question and accepting the first version of the answer. The first version is the rehearsed one for any question a candidate could have anticipated, and every common behavioral question has been anticipated.
- Leading inside the follow up. Asking whether the candidate escalated it tells them that escalating it was the answer, and everything after that point is worthless as evidence.
- Scoring the story rather than the conduct. A vivid account of a small action outscores a flat account of a large one unless the scale deliberately separates the two.
- Asking for an event so specific that no one has one. A question narrow enough that most candidates have to invent something has converted itself into a hypothetical without anybody noticing.
- Treating a bad outcome as a bad answer. The element being scored is what the candidate did, and a sound decision can be followed by a poor result. An interviewer who rewards outcomes teaches candidates to bring only the events that ended well, which removes from the interview every event worth hearing about.
What the candidate experiences on the other side
These questions are harder to answer than hypothetical ones, and that difficulty is worth handling deliberately rather than treating as a filter. Telling candidates in advance that the interview will ask about specific past situations costs nothing and does not compromise the method, because the difficulty is in having the events rather than in knowing they will be asked for. It gives a candidate time to recall genuine examples instead of producing whichever one surfaces under pressure, which improves the evidence rather than diluting it.
The version of this that does compromise the method is publishing the questions themselves, which converts the exercise into a test of preparation. The line runs between telling candidates the form and telling them the content, and that distinction is one of the cheapest improvements available to candidate experience in the whole hiring process.
What this page does not establish
We did not find, in our sources, figures establishing how far this form of questioning predicts performance, nor a ranking for it among selection methods, nor a recommended number of questions or probes. Figures circulating outside our sources are not reproduced here.
This page also does not set out any regulatory position on how an employer conducts selection interviews in the Saudi private sector. Our sources record a search for such a rule that did not find one, which is a statement about our sourcing rather than about the statute book. Anyone needing an answer there should go to the competent authority and its own published document.
The example questions above illustrate the difference between the two forms. They are not a recommended question set and are not taken from a source.
A standalone Saudi HR system
One employee file holding the contract, the documents and their expiry dates, the attendance record, leave, salary and end-of-service entitlements. End-of-service, overtime and leave-balance calculations are built into the system.
A standalone system on its own subscription. The connection to Qoyod Accounting is now available.