Mock Interview Practice

About the mock interview practice

Knowing what you'd say and actually saying it in two minutes are different skills. This free interview practice tool gives you one common interview question at a time, starts a timer when you begin typing, and reviews your answer as soon as you finish. You'll see roughly how long the answer would take to say, whether it has a clear situation, action, and result, whether it includes a concrete number, and which filler words crept in.

The feedback runs in your browser on transparent rules, so you can see exactly why an answer was flagged, and your answers aren't saved or sent anywhere. Below you'll find what each check means, how to turn a weak answer into a strong one, how to make typed practice feel like a spoken interview, and a simple routine for the week before.

How to use it

1. 1

   Read the question and start the timer

   Each question appears on its own. The timer starts when you begin typing, or you can start it yourself and think first, which is what you'll do in a real interview.

2. 2

   Type the answer you'd say out loud

   Write in spoken sentences, not notes. Set the scene briefly, explain what you did, and finish with what happened. Aim for one to two minutes of speaking time.

3. 3

   Get feedback and revise

   Read the feedback on length, structure, specifics, and filler words. Rewrite the weakest part once, then say the improved version out loud before you move on.

4. 4

   Go to the next question or shuffle

   Work through the set in order or shuffle for a less predictable session. Come back to the questions you struggled with on a different day and see whether they get easier.

What the feedback checks and why

Every check targets something interviewers notice, even if they wouldn't describe it this way. The rules are simple on purpose, so you always know what to change.

Rules can't judge whether you picked the right example or whether your tone was convincing. Use the feedback to fix structure and detail, then test content and delivery by practicing with a person.

• Length: your word count converted to speaking time at about 140 words per minute. Under roughly 90 words usually means you skipped the context or the result. Over about 330 words usually means too much background.
• STAR structure: whether the answer sets a scene, says what you did in the first person, and ends with an outcome. Missing parts are named so you know what to add.
• Specifics: whether you included at least one concrete number, such as time saved, people affected, money, or a before-and-after.
• "We" versus "I": a flag when "we" clearly outnumbers "I," because interviewers need to know what you personally did.
• Filler words: words such as "basically," "literally," and "kind of" that weaken an answer, especially when they repeat.

How to turn a weak answer into a strong one

Most first attempts share the same problems: too little context, "we" instead of "I," and an ending that trails off. Take the question "Tell me about a time you had to meet a tight deadline."

First attempt: "We had a big client report due early and everyone was really busy. We basically just worked late and got it done on time, and the client was happy." That's about 12 seconds of speaking, with no personal action, no number, and no clear result.

The fix: keep the same story but answer three questions. What exactly changed? (The deadline moved up a week.) What did you do? (Set up daily check-ins, built a script for the slowest tables, proposed cutting a redundant chart.) What happened because of it? (Delivered two days early, the client renewed, and the script now saves six hours a quarter.) The full revised answer and its feedback are in the examples below.

Make typed practice feel like the real thing

Typing an answer helps you organize it, but interviews are spoken. A few habits close the gap between what you write and what you'll say under pressure.

• Say it first, then type it. Answer out loud with the timer running, then type what you actually said, not what you wish you'd said.
• Write in one pass. Don't edit while you type. Finish the answer, get feedback, then revise.
• Record one answer per session on your phone and listen for pace, filler words, and endings that fade out.
• Rehearse your first sentence. A clear opener such as "At my last job, I led the move to a new scheduling system" gets you started without rambling.
• End on the result. Say the outcome, then stop talking. A clean finish beats a nervous summary.

A practice routine for the week before

Short, frequent sessions work better than one long cram. Fifteen to twenty minutes a day for the week before an interview is a manageable routine for most people.

Save your best versions in a document as you go. They become your story bank, the set of examples you'll adapt when an interviewer asks something you didn't predict.

• Day one: answer five questions cold, without preparing, so you know where you stand.
• Days two to four: focus on the questions that got the most flags, and fix one issue per attempt.
• Day five: shuffle and answer ten questions back to back, the way a real interview runs.
• The day before: reread your best answers and practice each opening line out loud.

Examples

Frequently asked questions