HireVue Practice: Free Mock Questions and Walkthroughs

The honest answer about HireVue practice is that reading sample questions on a list is not practice. Practice means speaking out loud, on camera, with a 30-second prep timer and a 90-second answer cap, against the AI rubric HireVue actually uses in 2026. Candidates who do that for a week beat candidates who memorise scripts by a wide margin. This article gives you 8 mock questions in the exact format HireVue uses, full STAR walkthrough sample answers for each, a 5-day plan, and the recurring mistakes the AI flags.

Quick takeaways

• Real HireVue assessments give you 30 seconds to read and prep, then up to 2 minutes to record. Most strong answers land at 75 to 100 seconds.
• The AI scores verbal content and structure, not your face. HireVue retired facial analysis in 2021.
• The STAR framework (Situation, Task, Action, Result) is the structure the AI is explicitly tuned to parse.
• Record yourself on your laptop camera. Phone audio and laptop audio score differently because the reference group uses laptops.
• 8 mock questions in this article cover the 8 competencies HireVue rotates: impact, judgment, leadership, influence, failure, teamwork, execution, motivation.
• Companies running HireVue interviews in 2026 include JPMorgan, Goldman Sachs, Bain, BCG, IBM, Capital One, Microsoft, Amazon, Unilever, Vodafone, and 700-plus more.

What HireVue practice should actually involve

HireVue practice is not list-reading. It is camera-on, timer-on, voice-out, scored. Three constraints make a practice session worth doing:

Constraint one: the timer. Real HireVue gives you 30 seconds of prep and up to 2 minutes to answer (some employers configure 90 seconds, a few configure 3 minutes). Practice with the same constraint. If you give yourself 5 minutes to think and 4 minutes to talk, you are practicing a different skill.

Constraint two: the camera. Read out loud and on camera, not in your head. The verbal content scoring the AI uses parses what comes out of your mouth, including filler words, pauses, restarts. You only catch those by recording and reviewing.

Constraint three: the rubric. The AI in 2026 rewards STAR-structured answers. Situation sets the scene in one or two sentences. Task is what you specifically owned, not what the team did. Action is 60 to 80 percent of the answer. Result is the outcome with numbers when possible. Practice without that structure and you are training the wrong shape of answer.

The 8 mock questions HireVue rotates

Below are 8 mock questions in the exact pattern HireVue actually uses, drawn from candidate write-ups across 2025 and 2026. Each one has a full STAR walkthrough answer underneath. The answers are deliberately concrete, with numbers, so you can see what "good" looks like in the rubric.

Mock 1. Tell me about your best work achievement to date. What made it important?

STAR walkthrough. Situation: "Last year I led the rollout of a customer onboarding flow at my company. The old flow had a 38 percent drop-off in the first three days." Task: "I owned the redesign end to end across product, engineering, and customer support, with a 6-week deadline before the next sales push." Action: "I shadowed 12 onboarding sessions to identify the three drop-off points, prototyped two alternative flows with the design team, ran a 4-week A/B test on 8,000 new users, and pushed the winning version to all new accounts." Result: "Drop-off in the first three days fell from 38 percent to 17 percent. The sales team closed 22 percent more annual contract value in the quarter after launch. The work mattered because it directly affected revenue, not just a UX score."

Why the AI rewards this. Specific numbers (38 to 17 percent, 8,000 users, 22 percent ACV). First-person ownership (I, not we). Result is tied to a business outcome the recruiter cares about.

Mock 2. Tell me about a time you had to make a difficult decision without all the information you needed.

STAR walkthrough. Situation: "Two months into my product manager role, our largest client threatened to churn unless we shipped a feature within 3 weeks. The engineering team estimated 7 weeks for a clean build." Task: "I had to recommend either delaying the client launch, building a stripped-down version on the timeline, or pulling resources from a strategic project to accelerate." Action: "With incomplete data on whether the stripped version would satisfy the client, I called three reference customers in the same segment to test the feature scope, then proposed the stripped build with an explicit 90-day plan to upgrade to the full feature. I documented the assumptions I could not verify and the rollback plan if the client rejected the stripped version." Result: "Client accepted the stripped version, renewed at 110 percent of the prior contract. The upgrade shipped at week 11. The decision held because I had ranked the unknowns and committed to a recovery path, not because I had perfect information."

Mock 3. Tell me about a time you led a team through a challenging situation.

STAR walkthrough. Situation: "I led a team of 4 engineers on a payment infrastructure migration. Two weeks before the cutover, our primary processor announced API deprecation that would break our staging environment." Task: "I had to decide whether to pause the migration, switch processors mid-flight, or build a compatibility shim in 10 days." Action: "I called a working session to map the three options against risk and engineering hours, picked the shim path because rollback was cleaner, paired with the most experienced engineer on the architecture, and reassigned the other three engineers to test coverage. I ran daily 15-minute syncs to catch blockers within 24 hours." Result: "We shipped the shim in 9 days, completed the migration on the original date, and the shim ran clean for 7 months before we deprecated it. The team rated the project 4.6 out of 5 on the post-mortem retro, citing clarity of role assignment as the differentiator."

Mock 4. Tell me about a time you persuaded someone or changed their mind.

STAR walkthrough. Situation: "Our head of marketing wanted to triple ad spend on a channel that had shown 14-day return-on-ad-spend of 0.6, well below the 1.8 cutoff our finance team had set." Task: "I had to convince him to either pause the channel or attribute his hypothesis to a testable change." Action: "Instead of arguing the numbers down, I asked him what he expected the channel to do that the data was not capturing. He said view-through conversions on display. I pulled the view-through data, found it accounted for an additional 0.4 ROAS, still under cutoff. I proposed a 2-week test at 30 percent of his requested budget on a refined audience segment, with a kill criterion at week 1." Result: "He agreed to the test. Week 1 ROAS hit 0.9, below kill criterion, and he killed the channel himself. Saved roughly 180k in misallocated ad spend. The mind change held because I made the cutoff his to enforce, not mine."

Mock 5. Tell me about a time you failed and what you learned.

STAR walkthrough. Situation: "Six months into my analyst role, I shipped a quarterly forecast model that overstated revenue by 14 percent for the next quarter." Task: "I had to surface the error before the executive review used the model, then explain what changed." Action: "I caught the error on a re-validation pass three days before review. I emailed the CFO and head of FP&A within 90 minutes with the corrected number, the source of the error (a stale assumption on a customer cohort I had not refreshed), and three checks I had added to my workflow to prevent recurrence. I led the executive review with the corrected number on slide 2." Result: "The CFO told the team I had bought trust by surfacing it cleanly. The three workflow checks (cohort refresh confirmation, peer review on the variance line, automated alert on greater-than-10-percent quarter-over-quarter swings) became standard for the team. What I learned: speed of disclosure matters more than the size of the miss."

Mock 6. Tell me about a conflict you had with a coworker and how it resolved.

STAR walkthrough. Situation: "A peer designer and I disagreed sharply on the navigation pattern for our new app. He wanted a hamburger menu, I wanted a bottom tab bar. The disagreement stalled the project for 2 weeks." Task: "I had to either escalate, defer, or find a structured way to settle it." Action: "Instead of arguing preferences, I proposed we both write a one-page memo with two user research findings supporting our pattern and one trade-off our pattern accepts. We swapped memos, then booked a 30-minute working session with our PM. He had stronger data on tablet usage. I had stronger data on one-handed phone use. We landed on a hybrid: bottom tab bar on phone, hamburger on tablet." Result: "The hybrid shipped, conversion on the new flow lifted 9 percent across platforms. The peer designer and I went on to ship two more projects together. The conflict resolved because we replaced opinions with shared evidence."

Mock 7. Tell me about a project you delivered under a tight deadline.

STAR walkthrough. Situation: "Two days before our largest client's board meeting, they asked for a custom data export that did not exist in our product." Task: "I had to scope, build, validate, and deliver the export by Friday end of day, with the client's board meeting on Monday morning." Action: "Friday 9 am I scoped the data the client actually needed (only 4 of the 11 fields they originally asked for, after a 15-minute call with their analyst). Friday 10 am to 4 pm I built a one-off SQL query and exported to CSV, then verified the numbers against three reference periods. Friday 5 pm I delivered the CSV with a one-page note explaining each field's calculation." Result: "Client used the export in their board deck. They renewed the contract at 140 percent of the prior year and named the export as one of the reasons. The pattern (scope down before building) became how I handled urgent requests after that."

Mock 8. Why this role, why this company?

STAR walkthrough. Situation: "I have spent the last three years in product analytics at a B2B SaaS company. I learned how to translate user behaviour into roadmap input, and I learned where I want to specialise next." Task: "I want to move into a senior product role at a company where the product is the marketing engine, not a feature factory bolted onto a sales motion." Action: "I looked at the last 18 months of your product launches and noticed three patterns: you ship narrow, deep features rather than broad shallow ones; you publish your roadmap publicly, which signals confidence in customer-led product; and you hire from a small list of companies that value engineering quality. I read the three engineering blog posts from your VP of Product on customer interviewing, and the approach matches how I have run my own customer research." Result: "I want this role because the work fits my next 5-year skill bet, and the company fits how I want to work. The role specifically, because the product analytics-to-product transition you are hiring for is exactly the bridge I have been preparing for. What I bring: 3 years of moving the metrics that matter, and a customer interview habit that has shaped 2 of our last 3 launches."

The chart below maps these 8 mocks against the competencies HireVue's rubric explicitly targets in 2026.

How to actually run a practice session

The mechanics matter more than the question list. A useful HireVue practice session looks like this:

Set up. Laptop on a desk at eye level, ring light or a window behind the camera, quiet room, neutral background. Same conditions you will use on the real test.

Open a stopwatch or a free interview-timer site. Read the question, hit start, 30 seconds to prep, then up to 2 minutes recording. Phone camera is not enough; you need the laptop view because that is what the recruiter sees.

Record. Use Loom, QuickTime, or any built-in screen recorder. Do not pause. Do not restart. If you mess up the answer, finish it anyway. Real HireVue does not let you re-record beyond the limit some employers set (usually 1 to 3 retakes maximum).

Review. Watch the playback at 1.0x, then at 1.5x. At 1.5x you spot pacing problems faster than at normal speed. Check three things: did you start with Situation or did you ramble? Did you spend at least 50 percent of the answer on Action? Did you land a Result with a number in it?

Rinse. 3 to 5 questions per session, 20 to 25 minutes total. Daily for 5 days beats weekly for 5 weeks because muscle memory on pacing is what the camera is grading.

A 5-day HireVue practice plan

The 5-day version assumes you have an upcoming interview and roughly 60 minutes per day.

Day 1 (60 min). Audit your story bank. Open a doc, write the bullets for 10 STAR stories from your work and academic history: 2 leadership, 2 failure or recovery, 2 teamwork or conflict, 2 impact, 2 ambiguity or judgment. One sentence per S, T, A, R. This becomes your raw material for any HireVue question.

Day 2 (60 min). Record 3 mock questions cold, no prep beyond the official 30 seconds. Review the playbacks. Mark every "um," every restart, every time you opened with "so basically." These are the patterns the AI penalises as low-fluency.

Day 3 (60 min). Record the same 3 questions again, having fixed the day-2 issues. Then add 2 new questions from the mock list above. Watch the contrast between day-2 and day-3 takes; the gap is what 24 hours of conscious practice closes.

Day 4 (60 min). Full simulation. 8 questions in a row, no breaks, real timer, full recording. Treat it like the real assessment. Do not let yourself stop mid-block. Review the entire 25-minute block afterwards.

Day 5 (60 min). Light. Two re-takes of your worst day-4 answers. Re-watch your three best day-4 answers to lock in the pacing. Sleep early. The test is execution day, not learning day.

What candidates get wrong in HireVue practice

The recurring patterns from candidates who score in the bottom third:

Scripts instead of structure. Memorising a 90-second answer word for word looks unnatural to the AI's content scoring and to any human reviewer who reads the transcript. Practice the STAR structure and rough beats, not the exact words.

Starting with the conclusion. "So this taught me the importance of resilience" as the opening line costs points because the AI is parsing for sequence: Situation first, Result later. Open with the scene.

Burying the Action. Candidates spend 40 seconds on Situation and Task, then sprint through Action in 15 seconds. The Action is what the AI grades for competency. Aim for 60 to 80 percent of your runtime in Action.

No numbers. "I improved sales" beats "I delivered" but loses to "I lifted close rate from 18 percent to 26 percent across 80 deals in Q2." If you have numbers, use them. If you do not, give scale ("a team of 8," "across 3 markets," "over a 4-month rollout").

Practicing without the timer. Without the 30-second prep and 2-minute cap, you are practicing storytelling, not HireVue. The timer is the practice.

Phone-only practice. If you only practice on your phone but the assessment is on your laptop, you will be surprised by your own framing on the real test. Practice on the device you will use.

FAQ

How many questions are in a HireVue interview?

Most HireVue interviews have 5 to 8 questions. Some banking screens hit 8 to 10. The invitation email or the practice link the employer sends usually states the count. The 8 mocks in this article cover the most common competencies, so practicing them gives you template answers for 90 percent of what you will face.

Can you retake a HireVue question?

Sometimes. Some employers allow 1 to 3 retakes per question; others lock you to a single take. The configuration is set by the employer in HireVue Studio. Treat each take as your only one in practice so that on test day a single-take configuration does not blindside you.

Does HireVue practice on the official site help?

The official HireVue candidate practice tour shows you the interface and the timing. It does not give you employer-specific questions or feedback on your answers. Use it once to learn the UI, then run real timed practice with the mocks in this article or a paid simulator that scores against the AI rubric.

How long should each answer be?

Aim for 75 to 100 seconds. Under 60 seconds reads underdeveloped to the AI and to a recruiter. Over 110 seconds reads padded, and you risk being cut off by the timer mid-Result, which damages the structure score the AI parses.

Should I write notes during the 30-second prep?

Yes, if the platform allows pen and paper. Most do. Write the four STAR beats as one or two words each: scene, my-task, action-1, action-2, result-with-number. Five short tokens is enough to anchor a fluent answer. Do not write full sentences; you will end up reading.

Does the AI score eye contact or smiling?

Not in 2026. HireVue retired the facial analysis component of its scoring in early 2021. The AI now scores verbal content and the structure of the answer. Eye contact and a relaxed expression still matter for the human who eventually watches the recording, but they are not what the AI is measuring.

What companies use HireVue interviews?

In 2026, over 700 companies use HireVue across investment banking (JPMorgan, Goldman Sachs, Citi), consulting (Bain, BCG, occasionally McKinsey), big tech early-career (Microsoft, Amazon), financial services (Capital One, Wells Fargo), consumer goods (Unilever), telecoms (Vodafone), and accounting (PwC, EY, KPMG, Deloitte). The specific configuration varies by company. The STAR rubric and the timing constraints do not.

What if I freeze on camera?

Practice on the camera, not just with the timer. Most freezes are camera-induced, not knowledge-induced. Three sessions of recording yourself drops the freeze rate noticeably. If you still freeze on the real test, use the prep 30 seconds to write down the first sentence of your answer; saying that sentence aloud breaks the freeze.

Related on PrepClubs

• Pillar. The HireVue Hub: assessment, interview, and games. Everything HireVue in one place.
• Deep practice. Practice HireVue with timed simulations and AI rubric scoring. $39 one time. Pass Guarantee.
• Format. HireVue in 2026: assessment, interview, games, and companies. The brand-level overview.
• Interview side. HireVue Interview: format, questions, and how to pass. For the on-demand video portion specifically.
• Games side. HireVue Games explained: every game and how to score well. For the cognitive games portion.

Practice on PrepClubs

Run real-timed HireVue mocks with the same 30-second prep, 2-minute answer cap, and STAR rubric scoring.

The official HireVue practice tour shows you the UI. PrepClubs runs full mock sessions: 8 questions in a row, real timing, recorded playback, and an AI-scored rubric that maps to the 2026 verbal content and structure model the platform uses. Every mock comes with a sample STAR walkthrough answer at three score bands so you can see what good and great look like before you record. $39 one time. Pass Guarantee.

Start free HireVue practice