Course

Practicing

A progressive practice plan from solo recording to AI tools to peer mocks to professional coaching, with scripts and exercises to build interview confidence.

If you're watching this course and certainly if you're listening to this

Practice Roadmap: Solo, AI, Peer, Then Professional

0:00

10:01

Video Content

Once you have a story catalog and you've learned to decode questions and select the right responses, the step that will really make a difference is practicing. In the moment, in the interview, there can be a lot of cognitive load to select the right details, organize them, adapt to the interviewer's reactions, all while trying to sound natural. Practice helps you close the gap between what you mean to communicate and what actually comes out under pressure.

Some candidates fear this kind of practice will make them sound robotic or rehearsed. If you do it right, by drilling the key points to get across instead of exactly what to say, it won't. Instead it will instill confidence.

Progressive Practice

The key to efficient preparation is progressive practice: start with controlled, low-pressure environments where you can focus purely on content and structure, then gradually introduce the complexity and pressure of real interview conditions.

Practice by yourself: Get your core stories and basic delivery down in private
Practice with AI: Test yourself with unpredictable questions and get immediate feedback
Practice with peer mock interviewers: Experience real conversation dynamics and human feedback
Polish with professional mock interviewers: Calibrate against experts in company expectations

Progressive Practice

Each stage serves a purpose, and skipping stages tends to waste both time and money.

Solo Practice

When you're practicing by yourself, you are literally talking to yourself, or to a camera, which can be a little awkward. But this is where you get a chance to try out different approaches in a safe environment and build muscle memory that makes live interviews feel natural.

Recording Your Core Stories

Start with your core stories and set up your phone or laptop to record video of yourself, then deliver each story in CARL format as if speaking to an interviewer. Don't worry about perfection on your first take. The goal is to start putting in reps.

When you review your recordings, watch for these specific elements:

Pacing: Are you rushing through actions or lingering too long on context? Most candidates spend way too much time setting up the situation and not enough time on what they actually did. Aim for spending about 10% of your time on Context, 60% on Actions, and 30% on Results and Learnings. If you find yourself three minutes into a story and you haven't described a single action you took, that's a problem.

Clarity of ownership: Count how many times you say "I" versus "we." Are your specific actions clear, or do they disappear into team accomplishments? This is one of the most common issues, especially for collaborative candidates who are uncomfortable claiming credit. But interviewers need to know what you did, not what your team accomplished.

Verbal fillers: Notice patterns in your filler words. "Um," "like," "you know," "basically." Everyone has them, but excessive fillers signal nervousness and reduce credibility. You might be surprised how often you use certain words once you actually watch yourself on video.

Energy and engagement: Do you sound genuinely interested in your own story? If you're boring yourself, you'll definitely bore an interviewer. This doesn't mean being artificially enthusiastic, but it does mean conveying that this story matters to you.

Organization: Can you follow your own narrative? If you're jumping around chronologically or between different aspects of the project, your listener can't follow either. A clear beginning, middle, and end makes a huge difference.

Record yourself 2 to 3 times for each core story, applying lessons from each review. You'll notice dramatic improvement by the third take as you build fluency.

Watch your recordings at 1.5x speed. You'll get through them faster and you'll still catch all the important issues with pacing and filler words.

Mastering the Big Three

Your responses to "Tell Me About Yourself," "Tell me about your favorite project," and "Tell me about a conflict" deserve extra attention since they appear in virtually every interview loop. These three questions are so common that you can essentially guarantee you'll face them, which means they deserve more preparation than any other questions. See our previous article for more.

Practice these until you can deliver them conversationally without notes. Record yourself, watch the playback, refine, and repeat.

Pay special attention to:

Your TMAY opening: The first 20 seconds establish your first impression. Do you sound confident and engaging? Or are you stumbling through "So, um, I've been a software engineer for about, like, seven years..." This opening sets the tone for the entire interview.

Transitions in your project story: Are you clearly calling out the most important contributions to the project? For complex projects, consider whether you need organizational techniques like Table of Contents to help your interviewer follow along.

Emotional tone in your conflict story: Are you balancing professionalism with whatever real emotional content is present the story? Conflict stories require showing that you handled a difficult situation maturely, but they also need genuine conflict to be believable.

Practicing Decode, Select, Deliver

Once your core stories and Big Three feel solid, practice the pattern-matching you'll do in real interviews: hearing a question and quickly selecting the best story to answer it. As we've discussed before, the best way to prepare is not to drill all possible questions, but you do want to test your ability to apply the Decode, Select, Deliver framework quickly while leveraging your Story Catalog.

Pull up a list of behavioral questions. For each question:

Decode: What signal area is this testing? What is the interviewer actually trying to learn about you?
Select: Which story from your catalog fits best? Don't overthink this. Go with your gut, then evaluate afterward.
Deliver: Give the full CARL response out loud, as if you're in an actual interview.

The goal is to build the reflex of hearing a question and quickly mapping it to the best story you already have.

This exercise is a good one to reveal gaps in the previous preparation steps. Look for signal areas where you don't have ready-made stories. For example, if you hit a question about stakeholder management and realize you don't have a good story for that, you need to return to your story identification process and fill that hole before your interview.

Practicing with AI

Large language models are available all the time and never get tired of practicing with you. After you've done your solo practice, AI tools should be your next stop.

Use AI to test yourself with unfamiliar questions. After you've practiced with standard question banks, prompt an AI to identify additional questions based around your target company's values. AI can help you generate company-specific practice questions that push you out of your comfort zone.

Generate common follow-up questions for your stories. Share your stories with the AI and ask about common follow-up questions. This is incredibly valuable because follow-ups are where most candidates get tripped up. They've rehearsed the initial story but haven't thought about what comes next. "What would you do differently?" "How did you measure success?" "What was the hardest part?" Having thought through these follow-ups in advance makes a significant difference.

Simulate company-specific interview styles. You can prompt AI to roleplay as an interviewer for a specific company: "Act as a Meta behavioral interviewer focused on the Leadership signal area. Ask me questions and follow up based on my responses."

This article won't attempt to recommend specific tools because they change so quickly. Explore what's available and find what works for you. The principles of how to use AI for practice remain consistent even as the tools change.

Recognize AI's limitations. AI can't replicate nonverbal feedback like facial expressions and body language. It can't simulate the conversational flow of a real interview with interruptions and tangents. It can't create genuine pressure. And it can't evaluate how you're coming across emotionally. These limitations are why you also need mock interviews with a human.

Peer Mock Interviews

Unlike coding problems, behavioral interviews are fundamentally subjective, so your next step should be feedback from another human. When you practice with a real interviewer, even a peer mock interview with someone who's not necessarily a hiring manager, it gives you a lot of value:

Pressure: Telling stories on the spot, to a real human who's evaluating you, is fundamentally different from writing them down, going over them in your head, or even responding to an AI. The experience of sitting across from someone who's waiting for you to answer creates pressure that no solo practice can replicate.

Follow-ups: A real person will push you on the parts of your story that seem weak or unclear. This is especially important for those nuanced stories, like the ones about weaknesses or failures.

Coaching: A good mock interviewer will give you actionable feedback to improve your stories. Not just "that was good" or "that was weak," but specific observations about what worked and what didn't.

Accountability: If you have more than one mock scheduled, you'll be held accountable to make necessary changes to your stories between sessions. Preparing for behavioral interviews is hard work, and external accountability helps you actually do it.

Encouragement: Preparing for interviews can be a slog. Having a human who cares about you express interest in your process provides genuine support for your mental health during what can be a stressful time.

Finding Peer Interviewers

You don't need a professional for this stage. Grab a friend or someone from the community:

Leverage your network: Reach out to friends or former colleagues who work at your target companies. They often have insight into the company culture and interview process and might be willing to spend 45 minutes doing a mock interview with you. Many people are happy to help if you ask directly.

Mock interview communities: Many online communities have peer networks designed to pair you with other people who are also preparing. You interview each other, trading off as interviewer and candidate. The Hello Interview Discord's #peer-mock-interviews channel is one option.

Phone a friend: Even a non-technical friend could ask you questions using standard behavioral question lists. They might not give great follow-ups or provide amazing feedback, but the pressure of answering on the spot is valuable on its own.

Preparing Your Peer Interviewer

Give your peer some guidance before you begin to maximize the value of the session.

Cover the signal areas: A comprehensive mock interview should touch on all the key signal areas. Provide your peer with questions that span different areas rather than clustering around one type. Check out the scripts we provide below and our question bank.

Create a feedback framework: Give your peer a simple rubric to evaluate each response. If you have the evaluation framework for the company you're interviewing with, use that. Otherwise, something like a 1 to 5 scale across dimensions works:

Structure: Were the stories easy to follow? Did you use CARL effectively?
Story choice: Did your examples demonstrate the right level of complexity for your target role?
Story depth: Did you provide enough specific, repeatable actions and quantifiable results?
Delivery: How was your energy, pacing, and overall presence?

Have them ask follow-ups: Train your peer interviewer to ask follow-up questions. "Why did you make that decision?" "What would you do differently?" "How did you measure that?" These follow-ups are where real interviews get interesting, and you need practice handling them.

Request honest feedback: Tell them you want honest feedback, not encouragement. "That was great" doesn't help you improve. "I got lost when you were explaining the architecture" does. Give them explicit permission to be critical.

Record your peer mock sessions (with permission). Watching yourself answer questions can reveal nervous habits, verbal pauses, or areas where you tend to ramble or lose focus that neither you nor your peer noticed in the moment.

Professional Mock Interviews

While peers are valuable, a professional mock interviewer offers calibration you can't get anywhere else. A professional interviewer is someone who works as a hiring manager in tech or interviews for your target company. They've seen enough candidates to know what "good" looks like and they can add some benefits to your preparation process:

Calibration: A professional mock interviewer will help ensure you've picked the best stories that represent your strengths relative to the company's values. They know what a strong Senior story looks like versus a weak one. They know what will fly at Amazon versus what will fly at Google. They've seen enough candidates to pattern-match your performance against people who got hired and people who didn't.

Expert follow-ups: An experienced manager knows what other managers think when they hear stories and will probe in the right places. They'll ask the questions that other managers will ask when they hear your story. They'll probe the spots where you're weakest, and you'll be glad they did before it's the real thing.

Pattern recognition: After conducting tens or hundreds of mock sessions, a professional coach has seen every common mistake and every effective technique. They can spot issues you can't see yourself and offer fixes that actually work.

Confidence: As hard as you prepare with peers, you might have doubts about your readiness. Having someone who's made real hiring decisions tell you "you're ready" does something for your nerves on interview day.

Getting the Most from Professional Mocks

While professional mocks represent an investment of time and money, the returns are substantial if you approach them strategically. Here's how to sequence your preparation:

Set clear goals: Discuss your objectives with the interviewer before you begin. Maybe you want to work on connecting stories to company values. Maybe you want feedback on whether the scope is right for the target level. Tell your mock interviewer what you're working on so they can focus their feedback.

Plan for at least two sessions: Everyone's situation is different, but for the average candidate, two mocks is a good place to start.

Session 1: Cover the Big Three and get feedback on your overall storytelling structure and technique. These are the stories you'll tell most frequently, so get them right first.

Between sessions: Apply that feedback to your other stories. Restructure your CARL format, adjust your pacing, fix whatever issues they identified. Schedule your mocks with enough time between them, at least a couple of days, so you can focus on implementing the feedback.

Session 2: Practice questions related to company values and other signal areas. The goal is not to prepare for specific questions but rather to ensure you can pair any question with the best story on the fly. This is the closest simulation to a real interview.

Record and review: Ask your interviewer if you can record the session and get written feedback from them. You'll want to reference these notes later as you continue to refine your stories.

Hello Interview offers behavioral mock interviews with experienced hiring managers from top tech companies. Every session is recorded so you can review it afterward, and includes detailed written feedback and actionable next steps. Premium members get $20 off their first mock.

Exercise: Build Your Practice Plan

Based on everything above, here's a progression that works for most candidates:

Week 1: Solo Foundation

Record your 3 to 5 core stories and Big Three
Review recordings and do 2 to 3 takes of each
Practice Decode, Select, Deliver with 10 to 15 random questions

Week 2: AI Extension

Use AI to generate company-specific questions
Practice responding to unexpected follow-ups
Identify and fill any gaps in your story catalog

Week 3: Human Practice

Schedule at least one peer mock interview
Apply feedback and refine stories
Schedule a second peer mock if needed

Week 4: Final Polish

Book two professional mock sessions (if budget allows)
Apply feedback between sessions
Final review and confidence building

This timeline assumes you have a month before your interview. If you have less time, compress the stages but don't skip them. Even a single day of solo practice is better than jumping straight to mocks. Even a 30-minute peer mock is better than going in cold.

Scripts to Use with Mock Interviews

Practice Script #1

Tell me about yourself.
Tell me about the largest scoped project you've ever built.
Tell me about a time when you had to solve a complex technical problem.
Tell me about a time you did something impactful that was not assigned to you.
Share an example of when you had to adapt to a requirement that changed quickly.
Tell me a time when you disagreed with your manager or another leader.
Tell me about a time when you failed.
Tell me about when you went above and beyond the requirements.
What questions do you have for me?

Practice Script #2

Tell me about yourself.
Why are you interested in this role?
Tell me about the project you're most proud of.
Share an example of when you saw an opportunity that others missed and took action on it.
Tell me about a time when you had to get something from someone who didn't want to give it to you.
Tell me about a time when you were faced with a problem with many possible solutions. How did you approach it?
Tell me about a time when you were misunderstood.
Tell me about a time when a project was behind and how you responded.
Tell me about a time when you learned something.
What questions do you have for me?

Practice Script #3

Tell me about yourself.
Tell me about the project where you've had the largest business impact.
Tell me about when you've demonstrated leadership.
Tell me about a time when you were involved in a conflict at work.
Tell me about how you handled a project that was very ambiguous.
Can you describe an instance where you proactively prepared for a potential issue before it became a problem?
Tell me about a time when you balanced planning with rapid execution.
How did you communicate something technical to someone non-technical?
Tell me about recent constructive feedback you've been given by your manager.
What questions do you have for me?

What's Next

Even with solid preparation and practice, there are specific mistakes that trip up candidates over and over. Things like burying your signal in too much context, picking stories that are too small for your target level, and ending every story with a fairy tale ending that makes the interviewer skeptical.

The next article covers the most common pitfalls and how to fix them. These are quick wins. Awareness alone fixes most of them.

Mark as read

Next: Common Pitfalls