Mock Interview Questions: 20 to Practice With Sample Answers

Last updated: August 2026

Quick Answer

A mock interview is a rehearsal under real conditions: same questions, same format, same clock, followed by feedback. The 20 questions below are the ones worth rehearsing first, because they appear in nearly every loop and they are the ones candidates answer worst out loud. Run them as a timed session, not a reading exercise. Record yourself or use OphyAI Interview Practice for voice or text mocks with follow-up questions, a transcript and per-answer feedback, then use OphyAI Interview Copilot to keep your structure visible during the live round.

#	Question	What a mock reveals
1	Tell me about yourself	Whether you can be interesting for 90 seconds without rambling
2	Why do you want this job	Whether you read the job description or the homepage
3	Why are you leaving your current role	Whether you can be honest without being bitter
4	What is your greatest strength	Whether you have evidence or an adjective
5	What is your greatest weakness	Whether you sound self-aware or rehearsed
6	Tell me about a time you failed	Whether you own it or distribute the blame
7	Tell me about a time you disagreed with your manager	Whether you can hold a position and still ship
8	Tell me about a project you led end to end	Whether you know what you actually decided
9	How do you prioritise when everything is urgent	Whether you have a method or a mood
10	What questions do you have for me	Whether you prepared or improvised

How to Run a Mock Interview That Actually Helps

University career centres run mock interviews in a consistent shape, and it is worth copying: roughly 20-25 minutes of interviewing followed by 10-15 minutes of feedback, using a real job description and your actual resume. The feedback half is the part most people skip, and it is the part that changes anything.

Four rules make the difference between practice and theatre.

Use a real job description. Print the posting you are actually applying to. Generic practice produces generic answers.

Answer out loud, on the clock. Reading an answer you wrote is not practice. The failure mode you are trying to find is the one that only appears when you speak: the 90-second answer that becomes four minutes, the story that arrives at the point too late.

Take the follow-up. A single question is not a mock interview. Real interviewers ask “what would you do differently” and “what did the other person think”. Practice with something that pushes back, whether that is a friend with a list or OphyAI Interview Practice, which asks follow-ups and returns per-answer feedback with your transcript.

Review the transcript, not your memory. Your memory of the answer is better than the answer. Read it back and cut the first two sentences of every story; they are almost always throat-clearing.

The Questions, With Sample Answers

1. “Tell me about yourself.”

Why they ask: It sets the frame for the next 45 minutes, and interviewers use your answer to choose what to dig into.

Sample answer: “I am a data analyst with four years in retail e-commerce, mostly on pricing and promotions. At my current company I own the weekly pricing model, which covers about 3,000 SKUs, and last year I rebuilt it to use elasticity estimates instead of flat margin rules, which lifted promotional revenue by roughly 8% without hurting margin. Before that I was in supply chain analytics, which is where I learned SQL properly. I am looking to move to a company where pricing is a product rather than a spreadsheet, which is why this role interested me: the posting mentions building the pricing service itself, and that is the part I want to do next.”

Weak answers start at university, run chronologically, and end with “and then I saw your posting”. Present, past, future, in 90 seconds.

2. “Why do you want this job?”

Why they ask: To separate candidates who applied to this role from candidates who applied to 200 roles.

Sample answer: “Two things. The posting says the team is moving from monthly batch reporting to an event-driven pipeline, and that migration is exactly the work I did at my last company, so I would be useful in month one rather than month six. The second is the scope: this role owns the metric definitions as well as the pipeline, and in my experience the definitions are where the arguments actually happen. I have been the person adjudicating those arguments informally, and I would rather own it formally.”

Weak answers describe the company’s reputation or products in a way any candidate could say. Name something specific to the role.

3. “Why are you leaving your current role?”

Why they ask: To predict whether you will leave theirs, and to check whether you speak badly about employers.

Sample answer: “I have been in the same role for three years and I have learned what it can teach me. The team is small, so the ceiling is real: there is no senior track above me without someone leaving. I would like to work somewhere with a bigger data problem and people more senior than me to learn from. I am not leaving because of anything that went wrong, and I gave my manager six months of notice about wanting to grow, which is part of why I am looking now rather than quietly.”

Weak answers either badmouth a manager or claim everything is perfect, which raises the obvious question.

4. “What is your greatest strength?”

Why they ask: To see whether you can support a claim with evidence rather than an adjective.

Sample answer: “Turning ambiguous requests into a scoped piece of work. When our head of marketing asked for a dashboard showing why churn was up, the actual question underneath it was which segment to spend retention budget on. I spent an hour on that before writing any code, then built a much smaller thing that answered it: three segments, a cost per saved customer for each. It took two days instead of two weeks, and it changed how the budget was allocated that quarter. I do that reflexively now, and it is the reason I get pulled into vague projects.”

Weak answers name a virtue and stop: “communication”, “hard-working”, “attention to detail”.

5. “What is your greatest weakness?”

Why they ask: To see whether you are self-aware and whether you are actively working on something.

Sample answer: “I over-invest in the first version. My instinct is to make something complete before showing it, which means feedback arrives late and I have sometimes built the wrong thing carefully. What I have changed is deliberate: I now show a rough version at the 25% mark, even when it is embarrassing. On the pricing rebuild I shared a spreadsheet mock-up in week one, and the feedback killed an approach I would otherwise have spent a month on. I still have to make myself do it, so it is a habit rather than a fix.”

Weak answers are disguised strengths (“I care too much”) or an unfixed disqualifier for the job you applied to.

6. “Tell me about a time you failed.”

Why they ask: Ownership. Interviewers are listening for who the subject of the sentences is.

Sample answer: “I shipped a reporting change that silently double-counted refunds for eleven days. I had tested the new logic against a sample where refunds were rare, so the bug did not show up. Finance caught it, not me, which is the part I am least happy about. I fixed it that day, then wrote a reconciliation check that compares the report total against the ledger nightly and alerts on a variance over 0.5%. That check has caught two unrelated problems since. What I changed permanently is that I now pick test data by the edge case rather than by convenience.”

Weak answers choose a failure that was really someone else’s, or a trivial one with no consequence.

7. “Tell me about a time you disagreed with your manager.”

Why they ask: To see whether you can hold a position, and whether you can lose gracefully.

Sample answer: “My manager wanted to launch a pricing test across all regions at once to get results faster. I thought the variance between regions would make the result unreadable, and said so with a rough power calculation showing we would need three times the traffic to detect the effect we cared about. He pushed back on timeline grounds, which was fair. We compromised on two regions chosen for similar traffic profiles, ran it for three weeks, and got a clean result. If he had overruled me I would have run it his way and instrumented it so we could still separate the regions afterwards.”

Weak answers either always win the disagreement or never had one.

8. “Tell me about a project you led from start to finish.”

Why they ask: To find out what you actually decided rather than what your team delivered.

Sample answer: “I led the migration of our reporting stack off a nightly batch job onto an event-driven pipeline. Three engineers, ten weeks. The decision I owned was the scope cut: the original plan migrated all 40 reports, and I proposed doing the 12 that were business-critical and freezing the rest, because the long tail was mostly unused. That halved the timeline. The hard part was the freeze, which meant telling four teams their report would not change for a quarter. I did those conversations myself rather than delegating them. We shipped a week early, and the unused reports were deleted rather than migrated.”

Weak answers use “we” throughout and never name a decision with a cost.

9. “How do you prioritise when everything is urgent?”

Why they ask: To hear a method, because everyone claims to be good at this.

Sample answer: “I separate deadline from importance, because urgent usually means someone is standing over it rather than that it matters most. My working rule is: anything that is losing money or blocking another person goes first, anything with a hard external date goes second, and everything else is negotiable and I say so out loud. The part that makes it work is telling people what I am not doing. When three teams asked for the same week, I sent one message listing what each would get and when, and two of them moved their own deadlines once they could see the queue.”

Weak answers describe a tool (“I use a Kanban board”) rather than a decision rule.

10. “Tell me about a time you had to learn something quickly.”

Why they ask: To predict your first three months, when you will know nothing.

Sample answer: “I inherited a forecasting model written in R when I had only used Python. I gave myself a week: two days reading the code with the previous owner’s notes, two days rewriting one module I understood well as a way to learn the idioms, and one day producing the forecast under supervision. I got it out on time and broke nothing, but I was slow for a month afterwards and said so in standups rather than pretending. I also wrote down every idiom that confused me, and that file became the onboarding doc for the next person.”

Weak answers claim to learn everything fast without naming the method or the cost.

11. “Describe a time you used data to change someone’s mind.”

Why they ask: To test whether you can make an argument, not just an analysis.

Sample answer: “Our support lead wanted to hire two more agents because the queue was growing. I pulled six months of ticket data and found 38% of tickets were password resets on one legacy flow. I brought one chart, not a deck: tickets by category over time, with that category highlighted. The recommendation was a self-service reset, not headcount. He disagreed initially because the queue was real today, so we did both: one temporary contractor for six weeks while engineering shipped the reset. Volume dropped 31% and the contractor was not extended.”

Weak answers describe the analysis in detail and skip how the decision actually changed.

12. “Tell me about a time you received difficult feedback.”

Why they ask: To see whether feedback lands or bounces.

Sample answer: “In a review my manager told me my written updates were unreadable: too long, no conclusion at the top. My first reaction was defensive, because the detail was there deliberately. I asked for an example, and reading my own update back with that framing it was obviously true. I changed the format to a two-line summary followed by detail, and asked her to tell me for a month whether each one was better. Three of the first four were, and the fourth was too long again. It is now the format I use for everything.”

Weak answers pick feedback they disagreed with and then explain why they were right.

13. “Walk me through your resume.”

Why they ask: To hear the logic connecting your moves, and to probe any gaps.

Sample answer: “I will do it in three moves rather than job by job. I started in supply chain analytics because I wanted to work where the numbers had physical consequences, and that is where I learned SQL and forecasting. I moved to e-commerce pricing because the feedback loop is faster: you change a price and you know within a week. The gap in 2024 was six months of caring for a family member, and I did contract analytics work part-time through it. The move I want next is toward owning the system rather than the analysis, which is this role.”

Weak answers narrate every job at equal length. Group your career into two or three moves and explain each one.

14. “Where do you see yourself in five years?”

Why they ask: To check that your ambition and this job point in the same direction.

Sample answer: “Owning a data platform and the team that runs it, which means about two more years of doing the engineering myself before I would be any good at leading it. That is why this role fits: it is hands-on, but it also owns the definitions and the stakeholder relationships, which is the part of the leadership job I have the least practice at. I am not trying to move into management within a year, and I would rather be the person who still writes the migration than the one who assigns it.”

Weak answers promise loyalty in the abstract or describe a job at a different company.

15. “What are your salary expectations?”

Why they ask: To check budget alignment before either side spends more time.

Sample answer: “Based on the range on the posting and what I have seen for similar scope in this market, I am looking at 95 to 110 thousand for base, and I care more about where the role sits in your band than the exact number, because that determines the next two years. If the level is flexible I am happy to discuss it after the technical rounds when we both know more. Is there a band attached to this role that you can share?”

Weak answers name a single number with no reasoning, or refuse to answer at all.

16. “Tell me about a time you missed a deadline.”

Why they ask: To see how early you raise a problem.

Sample answer: “I missed a quarter-end reporting deadline by two days. The cause was a dependency: a schema change upstream landed a week late and I had planned as if it would land on time. What I did wrong was not raising the risk when the upstream team first slipped, because I thought I could absorb it. When it became obvious I could not, I told the stakeholder immediately with a revised date and what they would get on the original date, which was a partial report. Now I flag dependency slips the day they happen, even when I still think I can absorb them.”

Weak answers blame the dependency and stop, without the earlier decision they own.

17. “How do you handle competing stakeholders?”

Why they ask: Most senior work is this, and it is hard to fake.

Sample answer: “I make the trade-off visible instead of arbitrating privately. Finance and marketing both wanted the attribution model to be the source of truth, and they wanted different definitions of a conversion. Rather than picking one, I wrote both definitions down with the numbers each produced for the same month, and put them in front of both leads together. Seeing a 22% gap made the conversation about which decision the number was for, which is answerable, rather than which one was right, which is not. We ended with one model and two labelled views.”

Weak answers describe escalating to a manager as the first move.

18. “What would your last manager say is your biggest area for growth?”

Why they ask: It is the weakness question with a witness, and it is harder to dodge.

Sample answer: “She would say I take on other people’s work. When someone is struggling my instinct is to do the thing rather than help them do it, which is faster once and worse over time. She named it in a review after I rewrote a junior analyst’s model overnight instead of sitting with him. I have been deliberate since: I ask whether the person wants help or wants it done, and I set aside time to pair rather than fix. It is better, but under deadline pressure the old instinct still shows up.”

Weak answers claim the manager would say nothing, which is not believable.

19. “Why should we hire you?”

Why they ask: To hear you make the case in the terms of the job.

Sample answer: “Three reasons, matched to the posting. You need someone who can run the batch-to-streaming migration: I have done that once already, including the part where the old reports have to keep working. You need someone who owns metric definitions: that is the work I have been doing informally for two years and want formally. And you are a small team, so you need someone who will talk to stakeholders directly rather than through a manager, which I prefer anyway. The thing I would need help with is the infrastructure side, and the posting says there is a platform team, so that is fine.”

Weak answers list qualities without mapping them to the job’s actual requirements.

20. “What questions do you have for me?”

Why they ask: It is the last scored moment, and preparation is visible.

Sample answer: “Three. First, what does the first successful 90 days look like for whoever takes this role? Second, the posting mentions the migration: is the scope already agreed, or is defining it part of the job? Third, when this role has been hard to fill or someone has left it, what was the reason? I would rather know the honest failure mode than the pitch.”

Weak answers ask about things the careers page already answers, or say “no, you covered everything”. Our guide to questions to ask the interviewer has more, sorted by who you are talking to.

How to Practice These

Reading these answers will not move your interview performance; saying yours out loud, badly, and then again, will. Run the 20 questions across three sessions rather than one, and re-record the five that went worst.

OphyAI Interview Practice gives you voice or text mock interviews with follow-up questions, a transcript and per-answer feedback, in behavioural, technical, system design and case formats, so you can practise the follow-up rather than just the opener. OphyAI Interview Copilot gives real-time answer suggestions and a live transcript during interviews on Zoom, Microsoft Teams and Google Meet, in 35 languages, for the live round where the employer allows it. For coding loops, OphyAI Coding Interview walks a problem with a streamed approach and code so you can re-solve it unassisted, and OphyAI Resume Builder keeps the resume you are being asked about consistent with the stories you rehearsed.

Start practicing →

Frequently Asked Questions

How long should a mock interview be?

Copy the shape career centres use: about 20-25 minutes of questions followed by 10-15 minutes of feedback, so roughly 35-45 minutes in total. Longer sessions produce fatigue rather than insight, and the feedback half is what actually changes your answers. If you only have 20 minutes, do five questions with feedback rather than twelve without, because an unreviewed rehearsal mostly reinforces whatever you already do.

How many mock interviews should I do before a real one?

Three is a reasonable floor for an important interview: one to find out how bad the answers are out loud, one to fix the worst three, and one close to the real thing under time pressure. Spread them across several days rather than stacking them, because the improvement comes from the review in between. For a loop with several formats, do at least one mock per format rather than three of the same behavioural session.

What questions should I ask in a mock interview?

Start with the 20 above, then add the ones specific to your target: the company’s known round names, the role’s technical content, and anything on your resume you would rather not be asked about. That last category matters most. The point of a mock is to find the answer that collapses under a follow-up, so deliberately include the employment gap, the short tenure, or the project that failed.

Are AI mock interviews as good as practising with a person?

They are better at some things and worse at others. An AI mock is available at 11pm, never gets bored of your fourth attempt, and gives you a transcript you can read back, which is where most of the value is. A human who knows your industry is better at judging whether a story is credible and at reading the room. The practical answer is to use both: AI for volume and transcripts, a person for a final credibility check.

Should I memorise my answers?

No. Memorise the structure and the evidence, not the sentences. A memorised answer sounds memorised, and it breaks the moment an interviewer interrupts with a follow-up, which they will. What you want committed to memory is the list of stories you own and the number at the end of each one, so you can assemble the right one on demand. Rehearse the same story three different ways rather than one way three times.

What should I do with the recording or transcript afterwards?

Read it rather than replay it, because reading removes the sympathy you have for your own voice. Look for three things: how long the first sentence takes to reach the point, how many stories end without a result, and where you said “sort of” or “kind of”. Fix the openings first; the first fifteen seconds of an answer determine whether the interviewer is still listening at forty.

How do I run a mock interview alone?

Print the job description, set a timer, and answer out loud to a camera as if a person were there. The two things solo practice loses are follow-up questions and the pressure of being watched, so add them back deliberately: write three follow-ups per question before you start and force yourself to answer them, or use a tool that generates them. Never practise by typing answers, because your written voice is not your spoken one.

Sources and verification notes

Sources checked August 2026. The session structure described above (a timed interview segment followed by a dedicated feedback segment, using a real job description and resume) is drawn from published university career centre mock interview programmes; the sample answers are illustrative compositions rather than transcripts of real interviews.

University of Illinois Career Center, Mock Interviews: published mock interview format, including the interview-plus-critique structure. Checked August 2026.
UMBC Career Center, Practice Interviews: session length and the preparation materials candidates are asked to bring. Checked August 2026.
Berkeley Career Engagement, Interview Preparation: published preparation guidance on researching the employer and rehearsing with the job description. Checked August 2026.
University of Iowa Pomerantz Career Center, Mock Interviews: mock interview scheduling and the feedback component. Checked August 2026.