A behavioral mock interview is a timed practice round of “tell me about a time” questions that you answer out loud, in full, while someone (or something) scores you against a fixed rubric. It needs three parts: a script that covers the competencies interviewers probe, follow-ups that test whether each story holds up, and a scoring sheet you fill in right after every answer. This page gives you all three for free, plus how to run the round alone, with a friend or with an AI interviewer, and how to review it.
If you haven't built your stories yet, do that first. Our story-bank method for behavioral interviews takes about a week. A mock interview tests your stories; it doesn't write them for you.
What a behavioral mock interview should test
Behavioral questions use your past behavior as evidence of how you'll work. The wording varies by company far more than the signal does, so a good mock round covers the same spread of competencies a real loop does.
| Competency | What the interviewer listens for | The story you need |
|---|---|---|
| Ownership | You took responsibility without being asked and followed through | A problem you fixed that wasn't strictly yours |
| Conflict and collaboration | You disagree about the work, not the person, and commit once a decision is made | A real disagreement with a peer, PM or manager |
| Failure and learning | You own mistakes and changed something afterward | A mistake with consequences and a concrete change |
| Influence and leadership | You moved people with evidence, not rank | A decision you changed without formal authority |
| Ambiguity and prioritization | You made progress with unclear goals and said no to something | A vague project or an overloaded sprint |
| Impact and judgment | You tie decisions to users, data or business results | A trade-off you made and how you measured it |
Companies weight these differently; see our guides to the Amazon behavioral interview and the Meta behavioral interview for two examples. The script below is company-neutral.
The 12-question behavioral mock interview script
The script has two questions per competency, each with a follow-up the interviewer asks after your first answer. Ask all twelve for a full round, or take only the odd-numbered (or only the even-numbered) questions for a six-question round. We wrote these questions in the standard “tell me about a time” style; they aren't taken from any company's question bank.
| # | Competency | Question | Follow-up probe |
|---|---|---|---|
| 1 | Ownership | Tell me about a time you fixed a problem that wasn't officially yours. | What would have happened if you had left it alone? |
| 2 | Ownership | Walk me through a project you drove from start to finish. | Which decision in that project was yours alone? |
| 3 | Conflict | Tell me about a disagreement with a teammate over a technical decision. | What was their strongest argument? |
| 4 | Collaboration | Tell me about working with someone whose style was very different from yours. | What did you change about how you worked? |
| 5 | Failure | Tell me about a mistake you made that affected other people. | What do you do differently now, specifically? |
| 6 | Feedback | Tell me about critical feedback you received. | How did you check that you had actually improved? |
| 7 | Influence | Tell me about a time you changed a decision you didn't own. | Who disagreed, and what changed their mind? |
| 8 | Leadership | Tell me about a time you helped someone else get better at their work. | How did you know it worked? |
| 9 | Ambiguity | Tell me about a time you started work with unclear requirements. | What did you assume, and how did you check it? |
| 10 | Prioritization | Tell me about a time you had more work than time. | What did you drop, and who did you tell? |
| 11 | Impact | Tell me about a decision you made using data or user feedback. | What would have changed your mind? |
| 12 | Judgment | Tell me about a trade-off you made between speed and quality. | Looking back, was it the right call? |
Open with an unscored warm-up, “tell me about yourself,” since many rounds open with it (our tell me about yourself guide for engineers has templates). Close with two minutes of your own questions to the interviewer. If you need worked answers for individual questions, the conflict with a coworker answer guide and tell me about a time you failed cover two of the hardest.
How to run the round: timing and rules
Budget about three to four minutes per question: two to three minutes for your answer, a minute for the follow-up, and 30 seconds to score it before the next question. Amazon's own interview guide describes STAR answers as typically lasting 2-3 minutes each, which is a sensible target anywhere.
| Block | Six-question round | Twelve-question round | Notes |
|---|---|---|---|
| Warm-up: tell me about yourself | 2 min | 2 min | Not scored |
| Questions and follow-ups | About 21 min | About 42 min | Two to three minutes per answer, one per follow-up |
| Scoring after each answer | 3 min | 6 min | 30 seconds each, while it's fresh |
| Your questions to the interviewer | 2 min | 2 min | Practice the close too |
| Total | About 25–30 min | About 50–55 min | Leave 15 minutes after for review |
Four rules make the round realistic:
- Answer every question out loud and in full. Stopping to restart is a habit you can't use for real.
- Keep notes to one line per story. Written-out answers turn practice into reading practice.
- Record the audio. A phone is enough to judge delivery and length honestly.
- Stay in role until the end. No feedback between questions.
Score it: a STAR rubric for behavioral answers
Score each answer from 1 to 5 on six criteria. The anchors below describe a 1, a 3 and a 5; use 2 and 4 for answers in between. This is our rubric, built around the STAR structure (Situation, Task, Action, Result) plus a reflection and a follow-up check. It isn't any company's official scale.
| Criterion | 1: weak | 3: adequate | 5: strong |
|---|---|---|---|
| Situation and task | Long setup, unclear stakes | Clear context, stakes only implied | Two or three sentences, stakes explicit: who was affected and by when |
| Actions | “We” throughout, vague verbs | Some specific steps, some “we” | Your own decisions and steps, in order, with the reason for each |
| Result | No outcome, or “it went well” | Outcome stated but not measured | A measurable or observable outcome you can defend |
| Reflection | None | A generic lesson | A specific change you made afterward |
| Fit to the question | The story answers a different question | It fits, but the key moment is buried | The competency asked about is the center of the story |
| Follow-up | The story falls apart | It holds, with hesitation | You add new detail and stay consistent |
That gives a total out of 30 per answer. As a rule of thumb, 25 or more means the story is ready, 18 to 24 means fix the single lowest criterion, and under 18 means rebuild the story from scratch. Those bands are our suggestion for practice, not a hiring bar.
The result line is the easiest part of an answer to leave vague. Two example lines we wrote: a weak one is “The release went fine.” A strong one is “We shipped on the original date, and support tickets about exports dropped from about a dozen a week to two.” Use numbers only if they're real; if you never measured, say what you watched instead.
Three ways to run a behavioral mock interview
| Method | Best for | Weak spot | Cost |
|---|---|---|---|
| Solo, with a recording | Volume, timing and delivery habits | No real follow-ups or interruptions | Free |
| With a friend | Pressure of a person listening, honest reactions | Scheduling; feedback quality varies | Free |
| With an AI interviewer | Questions built from your résumé and target job, instant scores, any time of day | Doesn't fully reproduce a person watching you | Free plan available |
Solo, with a recording
Shuffle the cards, read a question aloud, start a three-minute timer and answer to your phone. Flip the card and answer the follow-up immediately. Score both from the recording, not from memory. Our guide to mock interview practice without a partner has more solo methods.
With a friend
Give your friend the script table, the rubric and three instructions: interrupt once per round (“Sorry, what did you do, specifically?”), always ask the follow-up even when the answer was good, and hold all feedback until the end. Then swap roles: playing the interviewer teaches you fast what a vague answer sounds like.
With an AI interviewer
CoPilot Interview's Mock Interview mode (we make it) runs in the desktop app for Windows and macOS. You paste the job description and your résumé, choose the level, pick 3, 5 or 8 questions, set the mix to behavioral, and optionally add a focus such as “leadership.” It reads each question aloud, listens to your spoken answer and scores it out of 10, with what worked, what to improve, a model answer and the follow-up a real interviewer would ask. After the last question you get a report card with your average and the top three things to work on.
The free plan gives you 15 minutes every day, in sessions of up to 15 minutes, which fits a three-question round with time to read the feedback. If you can't install anything, the free AI mock interview in the browser has a behavioral track among its 113 real questions across 9 tracks. Use the AI's score and your own rubric side by side; when they disagree, the recording settles it.
How to review a behavioral mock interview
Review within an hour of the round, while you still remember what you meant to say.
- Find the pattern, not the worst answer. Add up each criterion across all your answers. The lowest total is your fix for the next round.
- Match the symptom to a fix using the table below.
- Rebuild the weakest story in the free STAR story builder, as bullets rather than a script.
- Redo that question within 24 hours, then run a fresh round with different questions to check that the fix carries over.
| Symptom in the recording | Likely cause | Fix for the next round |
|---|---|---|
| Answers run past three minutes | Setup is too long | Cap the situation at two sentences; start with a one-line headline |
| “We” in every sentence | Your role is unclear | Rewrite actions as “I decided,” “I wrote,” “I asked” |
| Vague result | You never pinned down the outcome | Find a number or an observable change; if none exists, say what you checked |
| Follow-ups stall | The story was rehearsed only at the surface | Note three extra details per story: alternatives, who disagreed, what broke |
| One story used three times | Your story bank is thin | Add stories for the missing competencies |
| Long pauses before you start | You're choosing a story on the spot | Map each story to two or three competencies in advance |
Work on one fix per round; five fixes at once rarely stick. For a sense of how much a single AI score tells you, see what a score out of 10 means.
Mistakes that waste a mock interview
- Reading prepared answers. It sounds fine until the first follow-up. Prepare bullets, then speak.
- Skipping the follow-ups. They're the part of the round that tells you whether a story is real enough to survive probing.
- Running mocks before you have stories. Build six to eight stories first; our behavioral STAR examples show what a finished one looks like.
- Polishing details you invented. Never add experience you didn't have. A story you didn't live won't survive a second follow-up.
For the full set of question types, see our behavioral interview help page.
Run your behavioral mock interview out loud
Paste a job description and your résumé, set the mix to behavioral, and answer an AI interviewer out loud. Each answer gets a score out of 10 with what to fix and a model answer, free for 15 minutes a day with no credit card.
Try a free AI mock interviewFAQ
What is a behavioral mock interview?
It is a practice round of “tell me about a time” questions that you answer out loud and score against a rubric. A useful one covers several competencies, includes follow-up questions, and runs about 25 to 55 minutes, either alone with a recording, with a friend, or with an AI interviewer.
How many questions should a behavioral mock interview have?
Six questions fit a 30-minute round with follow-ups and scoring. Twelve cover six core competencies twice in about 50 minutes. On CoPilot Interview’s free plan, a three-question AI round fits inside one 15-minute session.
Can I do a behavioral mock interview for free?
Yes. The script and rubric on this page are free, and practicing with a friend or a phone recording costs nothing. CoPilot Interview’s free plan includes Mock Interview with 15 minutes every day and no credit card, and the browser version needs no install.
How long should each behavioral answer be?
Aim for about two to three minutes for the first telling. Amazon’s own interview guide describes STAR answers as typically lasting 2-3 minutes. Keep the setup short and let follow-up questions pull out the extra detail.
How do I score my own behavioral answers?
Right after each answer, score it from 1 to 5 on situation, actions, result, reflection, fit to the question and how it held up under the follow-up. Add up each criterion across the round and fix the lowest one first.
Should I memorize my behavioral answers?
No. Memorize a short bullet outline for each story, not the wording. Memorized paragraphs tend to sound recited and break when the interviewer asks a follow-up you did not expect.