HireVue behavioral interview
HireVue behavioral questions
This page is about the questions. Its companion on the format — what a HireVue interview is, how the recording works, what your employer configures — is linked at the foot of the page, and the two are deliberately separate.
One thing first, because it is probably why you are here. We do not publish a list of HireVue behavioral questions, and you should be wary of pages that do. HireVue does not write the questions; the employer hiring you selects them. A list scraped from someone else's interview describes their employer's configuration, not yours, and rehearsing against it trains you for questions you will not be asked while leaving the ones you will be asked unprepared.
What is genuinely predictable is the small set of competencies behind almost all behavioral prompts, and the shape of an answer that survives a capped recording. That is what this page covers: how to find the competencies in your own invitation, how many stories to prepare, and why the STAR structure everyone teaches spends your window in the wrong place.
HireVue behavioral interview at a glance
- What varies most
- The wording, not the competency underneath
- What they are asking for
- Evidence of what you did, not what you would do
- Stories to prepare
- About four, each covering two or three areas
- Where STAR misfires
- The setup eats the window; lead with the result
How to prepare, step by step
Read the invitation next to the job description~10 min
These are the only two documents that describe your interview rather than someone else's. The invitation states the shape — how many questions, how long, whether there is a retake. The job description states what the company decided it is hiring for, in its own words, and those words are what the questions will be built on.
Turn the job description into a short list of competencies~15 min
Underline every phrase describing behavior rather than a tool: works across teams, manages competing deadlines, handles ambiguity, takes ownership. Five or six will usually cover it. This list is the thing worth preparing against, because it survives any rewording of the prompt sitting on top of it.
Choose four stories, not ten~30 min
Pick episodes you can tell in two minutes without notes and where you can say plainly what you personally did. Map each one to the two or three competencies it can evidence. Ten half-remembered examples is worse than four solid ones, because the cost of hunting for the right story is paid live, out of the window you are being timed in.
Write the outcome first, then compress everything before it~30 min
For each story, write the last thing that happened as your opening sentence. Then cut the background to a single line that makes it make sense. What remains in the middle is what you did, which is the only part with your name on it and the part most answers run out of room for.
Say each one out loud against a timer~25 min
Silently, every story fits. Spoken, most people discover their comfortable version runs well past two minutes, and that the overrun is almost entirely in the setup. This step is not optional preparation for a recorded format; it is the only way to learn what your answer actually costs.
Prepare the one you are avoiding~20 min
There is always one — usually a failure, a conflict, or a gap in your history. It is also the question most likely to be asked, because it is the one that separates candidates. Deciding in advance what you will say, and what you learned, is what stops you improvising it into a recording that cannot be taken back.
What this interview assesses
Evidence, Not Intention
These prompts ask what you actually did. Answering with how you would handle such a situation is a different answer to a different question, and it is the most common way a well-prepared candidate misses.
Outcome First
Live interviewing quietly relies on somebody prompting you for whatever you left out. A recording does not, so an answer saving its result for the end frequently loses it to the timer.
Checkable Detail
A story with no number, no date and nothing you were specifically responsible for is hard to tell from one that was made up. Detail is what makes an example checkable rather than merely plausible.
Sample HireVue behavioral interview questions
A feel for the kind of questions you’ll face. The real interview reacts to your answers with live follow-ups — these are examples, not the exact set.
1.Tell me about a time you worked with a difficult colleague.
What lands: Lead with how it resolved, then compress the background to one line. Told in order, the setup regularly eats the window and the result arrives as the timer does.
2.Describe a time you failed or missed a deadline.
What lands: Answer the question that was asked. A disguised success — caring too much, working too hard — reads as an evasion of a prompt that wanted evidence you can be honest.
3.Give an example of a time you took initiative without being asked.
What lands: Put a number, a date or a named responsibility in it. Detail is what makes an example checkable rather than merely plausible.
4.Tell me about a time you handled competing priorities.
What lands: Say what you chose not to do. An answer describing only what got done has described being busy rather than choosing.
5.Why do you want to work for this employer specifically?
What lands: Answer with something you did — read, applied, attended, spoke to someone. This is a behavioural question wearing different clothes, and praise is not evidence.
About this screening
Platform
HireVue — the questions are chosen by the employer, not the platform
Format
Recorded answers to behavioural competency questions, no interviewer present
What it checks
- Whether you can evidence a competency with a specific past example
- Whether the outcome arrives before the window closes
- Whether the detail is concrete enough to be checkable
GoRehearse is independent interview-practice and is not affiliated with, authorised by, or endorsed by HireVue. “HireVue” and any product names are trademarks of their respective owners. We do not obtain, sell or reproduce any employer's interview questions, and no question list on this page is taken from a real interview.
HireVue behavioral interview — the specifics worth knowing
- HireVue does not write the questions. The employer selects them along with the timings and the question count, which is why no published "HireVue question list" describes your interview.
- How we know: The platform is configured per employer. Your invitation and the job description are the only sources that describe your own interview rather than somebody else's.
- A behavioral question is asking for evidence, not intention. An answer describing what you would do in such a situation has answered a different question from the one asked.
- How we know: This is the stated premise of structured behavioural interviewing, which is why the prompts begin "tell me about a time when". A hypothetical answer can be checked against nothing.
- STAR was built for a live conversation, where an interviewer can prompt you for the part you left out. A recording cannot, so told in order it routinely spends the window on setup and loses the result.
- How we know: Follows from the format rather than from a study, and you can confirm it in ten minutes: time one of your own answers told in STAR order, then told outcome-first.
- The wording of a prompt varies far more than the competency underneath it. Preparing stories against competencies survives a rewrite; preparing memorised answers to specific wordings does not.
- How we know: Employers configure the interview against the competencies they wrote into the job description. Read that document and the underlying list is usually named in plain language.
- An answer with no number, no date and no named responsibility reads the same as an invented one. Concrete detail is the main thing separating a real story from a plausible one.
- How we know: Reviewers work through many recordings against the same competency. Specificity is the feature that distinguishes them, and it is the thing a fabricated answer cannot supply.
- "Why do you want to work here" is a behavioral question wearing different clothes, and is answered with something you did — read, applied, attended, spoke to someone — rather than with praise for the company.
- How we know: Praise is available to every candidate at no cost, so it carries no information about you. An action taken before applying is specific and checkable.
Common mistakes — and what to do instead
Searching for a list of HireVue questions and rehearsing against prompts that came from a different company's configuration.
Build your list from your own invitation and the job description. Those describe the interview you are actually sitting, and no scraped list does.
Telling the story in order, so that the background and the context consume most of the window and the outcome arrives as the timer runs out.
Open with what happened in the end, give the background in one sentence, and spend the middle on what you personally did.
Choosing the most impressive project rather than the one that can be told clearly in two minutes.
Choose by how well it compresses. A modest example told completely evidences the competency; an ambitious one cut off halfway evidences nothing.
Answering the failure question with a disguised success, such as caring too much or working too hard.
Name a real one, say what it cost, and say what you changed afterwards. The question is testing whether you can assess your own work, and the disguised version answers no.
Preparing so many examples that the recording is spent choosing between them.
Keep four and know which competencies each can cover. Choosing is the expensive thing to do live, and it is the part you can do entirely in advance.
Preparation checklist
- Read your invitation and the job description side by side
- Write down the competencies those two documents name
- Pick four stories that between them cover the list
- Rewrite each story so its first sentence is the outcome
- Cut the background of each one to a single sentence
- Put a number, a date or a named responsibility in every story
- Say each answer out loud against a two-minute timer
- Decide your failure answer in advance and say it once out loud
- Have a reason for wanting this employer that describes something you did
HireVue behavioral interview — FAQs
What behavioral questions does HireVue ask?
HireVue does not ask them — your employer does. The platform is what delivers and records the interview; the company hiring you chooses the questions, the number of them and how long you get. This is why two people who have both "done a HireVue" can compare notes and find they had almost nothing in common. It is also why we do not publish a question list here, and why lists you find elsewhere are describing one employer's setup as though it were the product. Your own invitation is the only document that describes your interview, and the job description tells you which competencies the questions will be built on.
Should you use the STAR method in a HireVue interview?
Use it to check that an answer is complete, not as the order to say it in. STAR comes from live interviewing, where a human can prompt you for the part you left out. A recording cannot. Told in order, a full situation-and-task preamble regularly eats most of a two-minute window and the result — the only part that is actually evidence about you — arrives just as the timer does, or after it. Say the outcome first, compress the situation into a line, then spend the middle of your window on what you personally did. Time one of your own answers both ways and the difference is not subtle.
Can you use the same story for more than one question?
Yes, and with a short career you will have to. Each answer is recorded and reviewed against the question it was given, so what matters is that each telling is angled at what was actually asked — the same project can evidence taking initiative in one answer and handling conflict in another, provided each version leads with the part that fits. Four stories you can tell well, each covering two or three competencies, is stronger preparation than ten you half-remember and then hunt through while the timer runs.
How many stories should you prepare for a HireVue behavioral interview?
Four you can tell well, each covering two or three competencies, beats ten you half-remember. The reason is mechanical: the window is capped and nobody is waiting while you decide, so preparation that leaves you choosing between examples spends the recording on the choice. Build the set from the competencies named in your own invitation and job description rather than from a generic list, then check that between them they cover it. One story can serve more than one prompt, as long as each telling leads with the part that answers what was actually asked.
How long should a HireVue behavioral answer be?
Aim to be complete inside about two minutes, and confirm the actual cap from your invitation, since the employer sets it rather than the platform. Completeness matters more than filling the window — an answer that ends deliberately at ninety seconds is stronger than one still describing background when the timer stops. The practical test is to say each answer out loud against a timer beforehand, because the length of an answer in your head and the length of it spoken are reliably different, and the gap always runs the same way.
What if you have no example for a behavioral question?
Use the nearest real situation and say how it differs, rather than inventing one or freezing. A smaller example told concretely is evidence; a large invented one is not. Situations from study, volunteering or part-time work count, and the competency underneath a prompt is usually broader than its wording suggests — a question about managing a team is often asking about responsibility for an outcome rather than about headcount. Answering the competency honestly beats answering the wording falsely.
Will you give me the real questions or a way to beat the AI?
No — and we wouldn't want to. These interviews adapt to each candidate and carry integrity scoring, so a 'question bank' would be inaccurate and against the point. We rehearse the format and your fluency, not a script. The honest edge is walking in calm and clear, not memorised.
How is talking to an AI interviewer different?
It doesn't nod, smile or fill silences, it can interrupt, and it just waits. That silence rattles people the first time. The whole value of rehearsing is getting that novelty out of the way before it costs you the opening minutes.
Should I have my résumé ready?
Yes — especially for the full rehearsal. These screens check whether your spoken answers match your CV, and our résumé claim-check is built to catch exactly the gaps they flag. Bring the résumé you'll actually submit.
How long is it?
The free taster is about five minutes and focuses on your self-introduction and fluency. A full rehearsal runs 15 or 30 minutes and adds résumé-consistency checking.
Related interviews
How to rehearse this exact thing
Leading with the outcome instead of the setup
The report quotes your own opening back to you, so you can see what a reviewer meets in the first fifteen seconds rather than what you meant to convey by the end.
Landing a complete answer inside the window
You answer under time and the feedback shows where the answer actually finished. This is the specific thing silent preparation cannot tell you, because nothing runs over in your head.
The failure question, out loud, at least once
Most people have never said theirs aloud to anything. Doing it once in a rehearsal is what stops the first telling from being the recording an employer keeps.
Being asked something you did not prepare
The follow-ups here are generated from what you just said rather than read off a list, so you get practice at the exact moment a prepared answer stops helping.
Not your employer's actual questions
Said plainly, because it is what most visitors came for: we do not know them, nobody publishing a list knows them either, and a rehearsal that claimed to would be selling you the same fiction.
Ready to rehearse for real?
Start a free five-minute HireVue behavioral interview now. You’ll get a spoken interview with live follow-ups and a feedback report that quotes your own answers back.