Skip to content

Black Friday

50% off every Premium pass. Ends

Get 50% off

Mock Interview Questions With a Script and Scoring Sheet

Use a flexible 30-minute mock interview plan, question bank, follow-up prompts and a practice rubric to identify clearer, more relevant answers.

Larbi Sahli
· Founder, Roleframe
Published · 12 min read
Mock Interview Questions With a Script and Scoring Sheet
On this page

A mock interview gives you a chance to explain your experience aloud, notice missing detail and try a clearer answer. This guide supplies a flexible 30-minute plan, a question bank, follow-up prompts and a practice scoring sheet.

The timings and rubric are suggestions for rehearsal, not a validated assessment or a prediction of an employer’s process. Adapt them to the actual interview format, the role and any communication or accessibility needs.

A flexible 30-minute practice plan

Choose questions before starting and leave time for follow-ups. The plan below uses seven main prompts; alternatives in the question bank let you adapt the session. Real interviews do not follow a universal order, and a technical exercise may need a separate session.

Agree whether this is an uninterrupted rehearsal or a coached practice. In an uninterrupted run, save detailed feedback until afterward. In a coached run, it is fine to pause and try a different approach.

MinutesRoundQuestions
0:00–4:00Opening1. Tell me about yourself, focusing on experience relevant to this role.
4:00–8:00Motivation2. What interests you about this role and organization?
8:00–18:00Experience3. Tell me about a difficult problem you worked on. 4. Describe a disagreement or mistake and how you responded.
18:00–23:00Role-specific5. Ask one question based on a relevant requirement in the posting.
23:00–26:00Reflection6. What skill are you working to improve, and how?
26:00–30:00Candidate questions7. What would you want to ask the interviewer?

For the opening, the tell-me-about-yourself guide can help you select relevant experience. For the close, prepare questions about the work and expectations using questions to ask during an interview.

If earlier discussion already answered your questions, acknowledge that and ask a useful follow-up if you have one. The absence of a fresh question does not, by itself, prove a lack of interest.

How to run the mock

With a partner, one person answers while the other asks questions and notes useful observations. A third person can take notes if available. Share the posting and practice goals first, and choose a quiet setting that resembles the planned interview where practical.

For video practice, check sound, connection, captions or other tools you need, and how notes affect the conversation. Record only with everyone’s informed agreement, using a suitable device or service. Agree who can access the file and when it will be deleted; written notes are a valid alternative.

Give the candidate time to think and clarify a question. For an uninterrupted rehearsal, avoid supplying the answer mid-sentence, but do not equate a neutral expression or an artificial pressure test with how every real interviewer behaves.

Four follow-ups for experience-based answers

  • “Which part did you personally handle?” Distinguish the candidate’s work from the team’s.
  • “What happened afterward?” Explore the outcome, including unresolved or mixed results.
  • “How do you know?” Separate recorded evidence, observation and assumption.
  • “What did you learn or what would you change?” Explore reflection without requiring a perfect ending.

Choose a follow-up when it reveals something useful; do not ask all four after every question. A motivation question, technical exercise or short factual answer may need a different prompt. If an outcome is not yet known, a truthful explanation is better than inventing one to complete the story.

Interview prepFree to use. Takes a few seconds.

Turn your resume into interview answers

Upload your resume. You get the questions an interviewer is likely to ask and a STAR answer for each, built from your own experience.
Likely questions for your interviews
A STAR answer for each, from your resume
The themes they will probe
Builds every answer from what your resume says and never adds experience or figures of its own. It is not an ATS and does not simulate one.
Processed for this check, never stored.

A question bank for repeat mocks

Use the bank to vary future sessions or focus on an area that needs practice. Repeating a question can also be useful when you want to check a specific improvement. The notes suggest what to discuss, not an employer’s hidden scoring key.

For examples of story structure, see behavioral interview questions and STAR questions. Use your own facts instead of memorizing someone else’s achievements.

Warm-up questions

  • “How did you hear about the position?” Give the actual source and, if useful, what prompted your interest; this does not require a research story.
  • "Walk me through a typical day in your current job." A strong answer picks the two or three responsibilities relevant to the target role instead of listing everything.
  • "What accomplishment are you most proud of?" Listen for a specific project and the candidate's own part in it.
  • “What do you know about the organization?” Discuss accurate, relevant information from its public materials. A recent announcement is optional, not a requirement.

Motivation questions

  • “Why are you leaving?” Give an accurate, relevant explanation. You can discuss a mismatch without inventing a positive reason or making unsupported allegations.
  • "Where do you see yourself in five years?" Listen for a direction connected to this role, delivered without a rehearsed ladder speech.
  • “What are your salary expectations?” Practice clarifying the role, compensation components and available range; prepare a researched range if you choose to give one.
  • "Why should we hire you?" Listen for a match between two or three of the posting's requirements and specific evidence for each.

Behavioral questions

  • "Tell me about a time you disagreed with your manager." Strong answers show respectful pushback and a resolution, whichever way it went.
  • "Tell me about a time you had to learn something fast." Listen for the method they used, plus proof it worked.
  • "Describe a time you missed a deadline." Strong answers own the miss and name what changed afterward.
  • "Tell me about a time you dealt with a difficult customer or stakeholder." Listen for de-escalation and the outcome for that person.
  • "Give me an example of leading without formal authority." Strong answers show influence: who moved, and why they moved.
  • "Tell me about a time you received tough feedback." Listen for what they actually did differently, with a concrete before and after.

Situational questions: what would you do if

  • “What would you do if a deadline was at risk?” Explain how you would assess urgency, communicate and agree on priorities; the order depends on the situation.
  • “What would you do if you found a serious mistake?” Assess immediate risk and follow the appropriate escalation process. Do not assume a private conversation must precede urgent safety or compliance action.
  • "What would you do if two managers gave you conflicting priorities?" Listen for making the conflict visible to both instead of quietly picking one.
  • “What would you do in your first 30 days?” Explain what you would learn, clarify and address, while allowing for urgent responsibilities.
  • “What if a customer asks for something the product cannot do?” Explain the limitation honestly and explore an authorized alternative or follow-up without promising unsupported capability.

Role-specific: customer-facing jobs

  • “A customer is already angry. What do you do?” Explain how you would listen, clarify the issue and follow safety and escalation procedures if needed.
  • "Tell me about a time you turned an unhappy customer around." Strong answers include what the customer said or did afterward as evidence.
  • “How do you handle a request you must refuse?” Explain the limit respectfully and offer an authorized alternative when one exists.
  • "Tell me about balancing speed against thoroughness with a queue behind you." Strong answers name the tradeoff they made and why it fit that case.

Role-specific: technical roles

  • "Walk me through a recent project from problem to result." Listen for the why behind the technical choices, at a level a non-specialist could follow.
  • "Tell me about a bug or failure that took days to resolve." Strong answers show a search that narrowed methodically rather than guess-and-check.
  • "How do you decide something is good enough to ship?" Listen for named criteria, plus who else weighs in.
  • “Explain a technical concept to someone outside the field.” Check whether the listener can follow the explanation and ask useful questions.

Role-specific: office and administrative roles

  • “How do you track tasks from several people?” Describe the method you actually use, how you prioritize and how you confirm completion. A brand-name tool is optional.
  • “Tell me about an error you caught.” Explain what you checked and what happened; do not invent the cost of a hypothetical failure.
  • “You receive a confidential document by mistake. What do you do?” Avoid further disclosure, use the approved reporting process and follow instructions for handling the file.
  • "Tell me about managing a calendar conflict between two executives." Strong answers show judgment about priority plus how each party heard the decision.

Questions that may need more preparation

  • "What is your greatest weakness?" A strong answer names a real weakness and the specific fix in progress, never a strength in disguise.
  • “How do you explain a gap in work history?” Give the relevant context you choose to share accurately. You do not need to invent productive activity or disclose unnecessary private details.
  • "Tell me about a time you failed." Strong answers pick a real failure with stakes, plus what changed in how they work.
  • “Why did your last job end?” Describe the relevant facts without assuming motives or misrepresenting a dismissal as a resignation.
  • "Tell me something about yourself that is not on your resume." Listen for something with a work-relevant thread, delivered without a rehearsed feel.

The scoring sheet: five criteria, scored 1 to 3

This is an editorial practice rubric, not a psychometric test, hiring cutoff or measure of job competence. Use 1–3 only for criteria relevant to the question, and mark others “not applicable.” An introductory question does not need a project outcome; a situational question should explain a proposed approach rather than pretend the event already happened.

The US Office of Personnel Management describes structured interviews as using predetermined questions and common rating standards. This practice sheet borrows the idea of explicit criteria, but it does not reproduce a particular employer’s assessment.

A man fills out a scoring sheet with five criteria after running a mock interview with a friend in a living room.
CriterionA 1 sounds likeA 2 sounds likeA 3 sounds like
Addresses the questionThe main question remains unanswered.Part of the question is answered, with a point to clarify.The answer addresses the question clearly; clarification is used when needed.
Relevant detailThe answer lacks detail needed to understand it.There is an example or approach, but scope or contribution is unclear.There is enough relevant detail to understand the example or proposed approach.
Evidence or reasoning, where relevantA result is asserted without a basis, or the proposed action is unexplained.Some evidence or reasoning is present, with an important gap.Evidence, limitations and reasoning are explained accurately; unknowns remain identified.
Connection to the roleThe relevance to the question or role is unclear.A relevant connection is present but needs explanation.The answer makes the relevant capability understandable without forcing a keyword match.
Clarity and pacingThe structure makes the answer difficult to follow.The answer can be followed, with a useful edit to structure or detail.The structure and level of detail suit the question and agreed practice format.

Turn observations into a small practice plan

Review the notes before the numbers. A useful observation is specific: “I could not tell which part you owned,” or “You explained the result but not how it was measured.” A score alone gives the candidate little to change.

Choose one or two priorities for the next attempt. For example, clarify individual contribution in a team story, or explain the trade-off behind a technical choice. Do not add a result to every answer when it does not belong, and do not treat an accent, eye contact pattern or natural speaking style as proof of ability.

If you compare scores across sessions, use comparable questions and criteria. A higher practice score may reflect familiarity with the prompt; it is not evidence that an offer is more likely.

Build a mock interview from a real job posting

A posting gives you material for more relevant practice. It does not reveal the actual interview questions or the employer’s internal weighting. Use stated duties and required qualifications to choose areas to explore, then confirm the interview format with the recruiter when possible.

  1. Identify several responsibilities or qualifications important to the role, distinguishing required criteria from preferences. Position or repetition in an advert does not prove interview weighting.
  2. Draft one experience question and one hypothetical question for each selected area. Keep the hypothetical within the responsibilities of the role.
  3. Find an honest example from work, study, volunteering or another relevant setting. If experience is missing, prepare to explain the limitation and what you would need to learn.
  4. Select a manageable subset for the available time, including an introduction and candidate questions. Keep the remaining prompts for another session.

Here is the method worked end to end for a fictional posting: a customer success associate at a mid-size software company. The five requirements pulled from the description are owning onboarding for new accounts, driving renewals and reducing churn, handling escalations, working in Salesforce daily, and turning customer feedback into product requests.

Fictional posting requirementExperience promptSituational promptPossible evidence, if true
Own onboarding for new accountsTell me about a time you taught someone a process or product from zero.A new customer has not logged in two weeks after kickoff. What do you do?A training bullet from any prior job: onboarded new hires, wrote the guide they used
Drive renewals and reduce churnTell me about a time you kept a customer who was about to leave.A customer says they are evaluating a competitor at renewal. Walk me through your next call.Any retention or repeat-business bullet, even from a non-software job
Handle escalationsTell me about the angriest customer you have dealt with and how it ended.A customer emails your CEO directly about a bug you already knew about. What happens next?The de-escalation story behind a support metric on the resume
Work in Salesforce dailyTell me about a tool you learned on the job and how you got fluent.You notice stale account data in the CRM is skewing reports. What do you do?Actual CRM use or a clearly identified example of learning another system; do not imply Salesforce experience if you lack it.
Turn feedback into product requestsTell me about a time you carried a customer's problem to another team and pushed it through.Three customers report the same friction this week. What do you do with that?A cross-team bullet showing information moved across a boundary and something changed

The final column suggests evidence to explore, not a requirement that every answer already appears on the resume. Interviews can cover relevant experience, reasoning and interests beyond that document. Distinguish transferable experience from direct experience with the exact task or tool.

Mock interview formats, and where to find a partner

Use the expected format where you know it, and adjust the practice to the task. Ask the recruiter about timing, exercises, permitted materials and any accommodations you need rather than relying on a universal interview script.

A job seeker in her fifties uses an online platform to find a mock interview partner.
  • Phone: practice explaining an example without visual cues, checking sound and allowing clarification. Choose a duration that fits the expected screen.
  • Video: test the platform and equipment you will use where possible. Check captions, audio delay and note placement. If an asynchronous recording is required, practice within its actual time and retry rules.
  • Panel: ask partners to alternate questions and follow-ups. Practice tracking the questions and addressing the group in a way that works for you.
  • Technical or case: use an authorized practice exercise relevant to the role. Allocate enough time to explain assumptions, work through the task and discuss trade-offs; do not squeeze a full assessment into a short behavioral slot.

Ask a trusted colleague, mentor or friend who can listen carefully and give specific feedback. A subject specialist can help assess technical reasoning; someone unfamiliar with the field can help identify unclear explanations. Neither relationship guarantees better feedback on every topic.

A university career service or local public employment service may offer practice or coaching. Check eligibility, availability and cost directly before planning around it. Keep confidential workplace examples out of shared materials.

Solo interview practice when there is no partner

Solo practice can help you hear an answer aloud and identify missing detail. It cannot fully reproduce an unfamiliar person’s follow-up questions, so use it for specific goals such as structure, clarity or checking the accuracy of an example.

  1. Pick a small set of relevant prompts, including one you have not recently rehearsed.
  2. Answer aloud. Record yourself only if useful and store the file appropriately, or use short written notes instead.
  3. Review applicable rubric criteria and identify one concrete change. Do not force a score for a criterion that does not fit.
  4. Try the answer again using a few factual reminders rather than a memorized script.
  5. Adapt length to the question and actual time limit. One or two minutes can be a practice target for some experience answers, not a universal minimum or maximum.

You can use your resume in Roleframe as a reference while choosing experience to discuss. Check dates, responsibilities and results before rehearsing them. A document review or AI suggestion cannot verify the underlying event or tell you what a real interviewer will ask.

If you use an AI tool to generate practice prompts, review them for relevance and accuracy, and avoid uploading confidential information. Treat its feedback as a suggestion to examine, not an employer’s assessment.

The feedback talk after the mock

Reserve time after the practice for useful feedback. Ten minutes is a planning option, not a validated minimum. Start with what the candidate wanted to improve and use observations from the answers.

  1. Identify something that worked and explain why it helped the listener understand the answer.
  2. Choose one answer to revisit. Point to the missing detail or unclear reasoning, then let the candidate decide how to revise it.
  3. Agree on one or two practice goals rather than rewriting every response at once.
  4. Repeat when useful and feasible. There is no universal number of sessions or spacing that guarantees measurable improvement.

Treat the mock as one piece of wider preparation rather than the whole plan. The full week-out sequence, from company research to logistics, is in how to prepare for an interview.

Frequently asked questions

Which questions belong in a mock interview?

Choose prompts that suit the role and expected format: an introduction, motivation, relevant experience, a role-specific question and your own questions can form a useful starting set. The seven-prompt plan on this page is one rehearsal option.

How long should a mock interview last?

Use the expected interview format and your practice goals. This page suggests thirty minutes plus feedback, but a short phone rehearsal or a longer technical exercise may need a different plan.

What are the five P’s of interviewing?

Different guides use different mnemonics. One familiar version is “proper preparation prevents poor performance,” but it is a reminder rather than a validated method or guarantee. Focus on understanding the role, selecting accurate examples and practicing aloud.

What are ten useful questions to practice?

Consider an introduction, current responsibilities, interest in the role, interest in the organization, a relevant strength, a development area, a difficult problem, a disagreement, a mistake and your questions for the interviewer. Adapt the list to the actual role.

Which interview questions are hardest?

That depends on your experience and the role. Gaps, mistakes, salary or unfamiliar technical scenarios may need more preparation. Identify what makes a question difficult for you and practice an accurate answer or a clear explanation of what you do not know.

Should practice be recorded?

Only if it helps and everyone involved agrees in advance. Confirm access, storage and deletion arrangements. Notes are an alternative, and a recording is not necessary for useful practice.

How many mock interviews should I do?

There is no universal minimum. Repeat enough to address specific gaps without replacing research, rest or other preparation. Use feedback to decide what another session should test rather than repeating solely to raise a score.

Was this helpful?
Want more guides like this in your Google results?

Ready to start your new resume?

Writing a resume takes time, and even a polished one can miss what a hiring manager is looking for. Roleframe helps you build a clear, ATS-safe resume in minutes and tailor it to the job you want.

Build my resume nowFree forever · no credit card