Mock Interview and Your Preparation Plan

You have now seen the whole series: how behavioral interviews work, the common opening questions, failure and conflict stories, ownership and leadership stories, tricky questions, questions to ask them, salary and offers and remote work and managers. Now we practise.

For the technical-interview version of mock practice (scoring sheets, a mistake log and how to run a mock with a friend), see career lesson 2. For how interviewers think from the other side of the table, see Team Lead lesson 9 on mentoring, onboarding and hiring. For the resume and the study plan that sit around this, see career lesson 0 and career lesson 1.

Words used in this lesson

• Mock interview is a practice interview, with a friend, a mentor, a paid service or an AI tool, run like the real one.
• Scorecard is a sheet with the things being scored and a number for each.
• Focus area is one thing interviewers look for, such as proactivity or growth.
• Story bank is your short list of 4 to 6 real work stories you can reshape to answer many questions.
• STAR means Situation, Task, Action, Result. STAR(R) adds Reflection, what you learned.
• Probe (or follow-up) is the extra question an interviewer asks to dig into a detail.
• Filler words are "um", "like", "you know" and similar, used to fill silence.
• Debrief is the talk after the interview, where you or the interviewers review what happened.
• Scope is the size of the problem or group you worked with (one task, a team, many teams).

The story bank first

Before any mock, build your bank. The handbook's advice is: do not try to memorise 50 answers. Pick 3 to 5 projects with high impact, complexity and your own involvement, and write each as a STAR(R) story. Most questions can be answered by reshaping one of these.

Fill in this table once. I recommend a notebook or a document.

(The stories above are made up. Use real ones.)

Then check the gaps: do you have a story for failure, conflict, leadership, ambiguity, pressure, learning something new, and a decision with missing information? If any is empty, think about your past year again. A small story is better than none.

For each story, write the numbers you remember (users, minutes, money, tickets, percent). Numbers make a story believable. If you are not sure of a number, say "about" and give a range. Never invent one.

What the interviewer scores

The handbook's rubric page lists eight focus areas. Here they are with the question that usually checks each and what the interviewer wants in plain words:

The page also says interviewers look at the scope of each story. Roughly: a junior story is about a task or one coworker, a senior story is about a project that affected the whole team and needed several people, a staff story is about work across teams. So use your biggest honest story for each question, and say who else was involved and how big the effect was.

The scorecard

Use this for a mock, or to review a recording of yourself. Score each row from 1 to 4 right after each answer, then total at the end. Write a short piece of evidence for each score. A number without evidence is a mood.

BEHAVIORAL SCORECARDCandidate: __________  Date: ______  Level aimed at: junior / mid / seniorInterviewer/Scorer: __________Focus area                 Score (1-4)   Evidence (quote or note)1 Motivation               ____          ______________________2 Proactivity              ____          ______________________3 Unstructured work        ____          ______________________4 Perseverance             ____          ______________________5 Conflict resolution      ____          ______________________6 Empathy                  ____          ______________________7 Growth                   ____          ______________________8 Communication            ____          ______________________TOTAL                      ____ / 32Delivery checks (tick):[ ] Every answer 1.5 to 3 minutes   [ ] "I" for my actions, "we" for the team[ ] A number in the result           [ ] A reflection (what I changed)[ ] No blame on named people         [ ] I answered the question askedBiggest fix for next time: ____________________________

My score bands (rules of thumb, not from the handbook):

• 28 to 32: strong. Polish and keep practising.
• 24 to 27: good. Fix the lowest row.
• 20 to 23: borderline. Work on the story bank and structure.
• Below 20: not ready. Do the plan below, then mock again.
• Any row of 1 is a red alert on its own, whatever the total.

A full mock round

Here is a mock round with a fictional candidate. The candidate is a developer with four years of experience applying for a mid-level backend role. The interviewer is fictional. I show the question, the answer as it could be spoken, then the score with evidence. Read each answer out loud. Spoken answers sound different from written ones.

Question 1: Tell me about yourself. (Motivation, Communication)

Score: Motivation 3, Communication 3. Evidence: about 60 seconds; present, past, future structure; one number (twelve to zero); a clear link to the company. To get a 4: add one more sentence on why checkout, with a specific thing learned from the company's public engineering posts.

Question 2: What project are you most proud of? (Motivation, Perseverance)

Score: Motivation 3, Perseverance 3, Growth 3. Evidence: STAR(R) shape; numbers (twelve to zero, 90 to 20 seconds); a reflection. To get a 4: say how many people the work affected and mention the cross-team teammate, to show scope above one person.

Question 3: Tell me about an unclear task. (Unstructured work, Proactivity)

Score: Unstructured 4, Proactivity 3. Evidence: asked for a measure, collected facts, wrote assumptions, set a deadline for objections, a result (six days to two). Scope: team level.

Question 4: Tell me about a conflict with a coworker. (Conflict resolution, Empathy)

First, a weak answer, as many people give it:

Score: Conflict 1 or 2, Empathy 1. Evidence: blame ("stubborn"), no specific story, no action that resolved it, the result was "I won", and the lesson is "avoid". An interviewer learns that this person may not work well with others.

Now a strong answer to the same question (a different, honest story):

Score: Conflict 4, Empathy 3. Evidence: named a clear conflict, asked to understand, used data, found a result that satisfied both, a lasting relationship change. To keep a 4, make sure the story did not make the other person look foolish; here Sam's point was valid and said so.

Why the weak answer failed: it had no specific event, it used a label ("stubborn") instead of a behavior, the candidate did nothing to understand the other person, and the lesson was avoidance. The strong answer fixed each of these.

Question 5: Tell me about a mistake you made. (Growth)

Score: Growth 4. Evidence: a real mistake, ownership, speed to tell and to fix, concrete changes in process, results over time. It did not blame anyone. (Do not pick a fake mistake like "I work too hard". Interviewers see through it.)

Question 6: Tell me about a project that took longer than expected. (Perseverance)

Score: Perseverance 3. Evidence: kept going, told early, learned about estimates. To get a 4: a larger scope (blockers affecting several people) and a number for impact.

Question 7: Do you have any questions for us? (Motivation, Communication)

Score: Motivation 3 (adds to the earlier). Evidence: tied to what the interviewer said; open questions; short. More examples in lesson 5.

The scorecard for this mock

I took the best score evidence per row across the whole round (one row can be seen in more than one answer):

Using my bands, 27 is in "good". If the candidate had given the weak conflict answer, Conflict would be 1 or 2 and Empathy 1, so the total would drop to about 22 to 23: "borderline", and a row of 1 would be a red alert. That one answer could change the result.

Probes (follow-up questions) to practise

Interviewers love to dig. Practise answers to these on each story:

• "What was your exact role? What did others do?"
• "What would you do differently?"
• "What was the hardest decision, and what else did you consider?"
• "How did you measure success? How do you know it was the result of your work?"
• "What did your manager (or the other person) say about it afterwards?"
• "Tell me more about that." (Give another detail, not the same sentence again.)

A sample probe-and-answer:

Spoken delivery: the part people forget

Written text is not speech. Some practice rules:

1. Length: most answers should be 1.5 to 3 minutes. Under one minute is too thin, over four loses the listener. Time yourself.
2. Pause before you answer. Two or three seconds to think looks calm. Say "Let me think of a good example" if you need it.
3. Start with the point. "A time I disagreed with a teammate was last March." Then the story.
4. Say "I" for what you did. Say "we" for what the team did. Many candidates say "we" for everything, and the interviewer cannot tell what they did.
5. Slow down at the result. The result is what people remember. Say the number clearly.
6. Avoid reading notes. Use bullet points of 3 to 5 words, not sentences.
7. Keep filler words small. Record yourself once and count them. A few are normal.
8. On video: look at the camera at the key moments, have light on your face, and test the sound.
9. Do not blame. Describe behaviors and facts. Never name a person in a bad light.
10. Be honest. If you do not have a story, say so and offer the closest one: "I haven't led a team, but I did lead a small project, and here is what I did."

How to run a mock

With a friend or a mentor

1. Give them your scorecard and the list of questions (use the common questions in the handbook's list, or the ones in lessons 1 to 4).
2. They ask 6 or 7 questions, with probes, in a time of 45 to 60 minutes.
3. They write evidence under each row. They do not give hints.
4. Afterwards you talk for 15 minutes: first what you think went well, then their notes.
5. Write your top two fixes. Next mock, check those two first.

For tips on how to run mocks (roles, time limits, notes), career lesson 2 has a longer routine you can reuse for behavioral rounds.

Alone

1. Record audio or video on your phone.
2. Ask yourself a question from a random list (write 20 on slips of paper and draw one).
3. Answer out loud for up to 3 minutes without notes.
4. Play it back once. Score yourself with the scorecard. Note filler words, length and missing numbers.
5. Re-record the weakest answer. Compare.

With an AI tool

The handbook says it is natural to use a chatbot to ask you questions and give feedback, and to encourage it to ask follow-ups. If you do, a prompt like this helps (it is mine):

Act as an interviewer for a mid-level backend developer role. Ask me onebehavioral question at a time. After my answer, ask one follow-up probe.Then score my answer from 1 to 4 on: clarity, my own actions (I vs we),result with a number, and reflection. Say what is missing. Do not give mea model answer unless I ask.

An AI tool does not replace a human. It cannot see your face, hear your tone or judge scope like a real manager would. And never paste private company data or secrets into it.

The one-week preparation plan

Assume your interview is in 7 days and you have about one hour a day (two on the weekend). Adjust the days. If you have more time, stretch it. If you have less, do days 1, 3, 5 and 7.

If the interview is in a month, do the same plan but spend a week on each step, and do three mocks, with at least one with a person who does not know you well.

Checklist for the day

The night before

[ ] Interview time, place or link, and time zone confirmed (and written in the calendar)[ ] Name and role of each interviewer noted[ ] Resume and job post printed or open[ ] Story bank bullets and your 8 questions in a notebook[ ] Clothes chosen; for video, background and light tested[ ] Laptop charged; charger, headphones, backup phone data[ ] Phone on silent for tomorrow[ ] Route or travel time checked (arrive 10 to 15 minutes early)[ ] Sleep 7 or more hours (this matters more than one more hour of study)

One hour before

[ ] Light meal; water[ ] Read the one-page summary: 3 values, 5 story names, 3 numbers[ ] Say the "tell me about yourself" answer once out loud[ ] For video: open the link 5 minutes early, test camera and sound[ ] Breathe slowly: in for 4 seconds, out for 6, five times

During the interview

[ ] Smile and greet by name[ ] Pause two seconds before answering[ ] Start each answer with the point[ ] "I" for what I did, "we" for what the team did[ ] A number in the result[ ] Check: "Does that answer your question? I can go deeper on X."[ ] Use my notebook for questions[ ] Ask 3 to 5 questions at the end; ask about next steps

After the interview (same day)

[ ] Send a thank-you email (see lesson 5)[ ] Write down every question I was asked and how I felt about my answer[ ] Score myself with the scorecard[ ] Add any new stories or fixes to my bank[ ] If salary comes up, stay calm and use lesson 6[ ] If I get rejected, ask for feedback (script in lesson 7) and treat it as data

When it goes badly

You will, sometimes, give a bad answer or have a rough round. It happens to everyone. What matters:

1. During the interview: if you realise you gave a weak answer, you can say, "Can I try that again? I think I can explain it better." Most interviewers allow it.
2. If you freeze: say "Give me a moment to think." Drink water. Start with the situation.
3. After: write down what happened and what to fix. Don't spiral. One round is one data point.
4. After a rejection: thank them, ask for feedback once (script in lesson 7), and move on. A rejection is rarely about one answer.

Try it

Exercise. Take the question "Tell me about a time you had to learn something new quickly." Do this in 25 minutes:

1. Pick a story from your bank (or a real one from the past year).
2. Write 5 bullet points: Situation, Task, Action (3 things you did), Result (with a number), Reflection.
3. Say the answer out loud and time it. Aim for 2 minutes.
4. Score it with the scorecard rows Growth, Proactivity and Communication, with evidence.
5. Write one probe the interviewer might ask, and your answer.

Sample answer (made up).

• Situation: our team had to move from a manual deploy to an automated pipeline, and I had never built one.
• Task: set up a pipeline for the invoicing service in three weeks.
• Action: (1) I read the tool's official guide and built a tiny pipeline for a test service first. (2) I asked a colleague from another team to review my plan for 20 minutes. (3) I wrote a runbook as I went, so others could follow.
• Result: deploy time fell from about 40 minutes to 8, and two other teams copied the setup.
• Reflection: starting with a tiny test service made mistakes cheap; now I do that with any new tool.
• Spoken time: about 1 minute 50 seconds.
• Score: Growth 3 (learning plan clear), Proactivity 3 (asked for review, wrote runbook), Communication 3. To reach 4: say how many people used the runbook and what changed in their work.
• Probe: "What was the hardest part?" Answer: "Handling secrets safely. I learned how the tool stores them and asked the security person to check my setup."

Interview questions

This final lesson has more questions, covering the whole series.

Key takeaways

• Build a small story bank (4 to 6 real stories) with numbers. Reshape stories for each question. Don't memorise scripts.
• Interviewers score eight areas: motivation, proactivity, unstructured work, perseverance, conflict resolution, empathy, growth and communication. Use them as your scorecard rows, with evidence.
• Spoken answers: 1.5 to 3 minutes, start with the point, "I" for actions, a number in the result, a reflection at the end.
• One weak answer (blame, no action, no lesson) can drop a total from the 'good' band to 'borderline'. Fix the weakest row first.
• Mocks give the best feedback. Record yourself, or use a friend with the scorecard. Use AI tools only as an extra.
• Follow the one-week plan, use the checklist, and treat a bad round as data. Thank-you email, self-score and feedback request afterwards.
• All names, companies and numbers in this series' examples are made up. Check current local data for salary.

What's next

You have finished the series. Your next steps: today, fill in your story bank table. Tomorrow, say your "tell me about yourself" answer out loud three times. This week, run your first mock and fill in the scorecard. If your interviews also include coding, go to career lesson 1 for the study plan and career lesson 2 for coding mocks. If you want to see the other side of the table, read Team Lead lesson 9 on hiring. Good luck. You have prepared, and that is the part you control.