Contents

Mock Interview Questions: 50 Practice Questions and How to Run a Mock Interview | OfferBull

Mock Interview Questions: 50 Practice Questions and How to Run a Mock Interview

Nice mocks fail you later. You want a prompt that forces a number, a decision, or a trade-off. And a partner who asks the next annoying follow-up instead of nodding.

This list is fuel. Say the answers. Don’t memorize the sheet. For speak / record / timer habits, use how to practice for an interview. Tech loop habits: how to get the most out of mock interviews for tech roles.

Sample shapes are fictional. Borrow the order.

How I’d run it

Alone. Sticky. Timer. Phone recording. Replay once. Score with the rubric. Same prompt again with one fix.

Friend. Surprise questions beat a shared answer sheet. Interrupt fog. Five questions plus follow-ups. Swap roles so nobody softballs for an hour.

AI. Paste the JD. Speak. Let follow-ups land. Catch yourself reading a paragraph into the mic? Stop. OfferBull is that voice loop on iOS and Android, before the real interview only.

/images/posts/mock-interview-questions/notepad-phone-practice.jpg One prompt. Timer. Speak. The page is not the answer.

Rubric (be mean)

Mark 1–5 after each answer. Polite scores teach nothing.

Axis135
ClarityForgot the askMostly on topicClear arc; answered it
SpecificityVague “we” talkOne concrete detailNamed action + result
StructureSoupRough beginning/middleTight open + close
CalmRushed or frozeRecoveredSteady pace

Raise one axis per retry. Not all four.

/images/posts/mock-interview-questions/mock-session-stages.svg Warm-up → core Qs → follow-ups → score → one retry. Then stop.

Behavioral / STAR (15)

Stories ballooning? STAR method interview questions and examples. Bigger bank: behavioral interview questions and answers.

  1. Tell me about a time you disagreed with your manager.
  2. Describe a project that failed. What changed after?
  3. Walk me through a tight deadline you hit without trash quality.
  4. Tell me about influencing without authority.
  5. Describe a team conflict and how it ended.
  6. Feedback that stung. What shifted?
  7. Incomplete requirements, and you still shipped. How?
  8. A mistake that hit customers or users. Own it.
  9. When you said no, and why that was right.
  10. Mentoring someone junior through a hard task.
  11. You simplified a process everyone had accepted.
  12. Everything was “P0.” How did you prioritize?
  13. Difficult stakeholder. What worked?
  14. You changed your mind after new data.
  15. A decision you’d remake with what you know now.

Skip Hollywood. Small real weeks beat invented drama.

Tell-me-about-yourself variants (8)

Shapes: tell me about yourself sample answers.

  1. Walk me through your background for this role.
  2. How did you get into this field?
  3. What’s the thread across your last two jobs?
  4. Why are you looking now?
  5. Summarize your last role in 60 seconds for a non-expert.
  6. What part of your experience maps least obviously to this JD, and how do you bridge it?
  7. If I only remember one project, which?
  8. Where should the next role stretch you?

Time these. Untimed intros become TED talks.

Role-general judgment (12)

  1. Why this company?
  2. Why this role instead of the nearby title?
  3. First 90 days. Sketch them.
  4. How do you decide “good enough” on a ship date?
  5. Two leads want different things. What do you do?
  6. A metric you watch at work, and why that one.
  7. You pushed back on a timeline. Tell me.
  8. Bad news upward. How do you send it?
  9. What kind of manager helps you do your best work?
  10. Under-leveled or over-leveled before. How did you notice?
  11. Something you’re still actively getting better at.
  12. How do you keep learning without turning every week into a course pile?

“Why us?” with zero research is a free reject. Open the careers page. Name one real product or problem.

Soft tech / collaboration (10)

Even when there’s no coding pad.

  1. Explain a technical trade-off to a non-technical partner.
  2. Debug with thin logs and an intermittent bug.
  3. You disagreed in a peer’s review. How’d that go?
  4. You documented something so the next person didn’t page you.
  5. Estimate when you’ve never built this exact thing.
  6. A production incident you helped close.
  7. New features vs debt. How do you balance?
  8. Onboarding onto a messy codebase or process.
  9. Requirement vs a constraint you can’t move.
  10. When is a design “done enough” to build?

Tools are secondary. They want judgment.

/images/posts/mock-interview-questions/self-score-after-mock.jpg Score while the answer is fresh. Kind scores teach nothing.

Closing questions (5)

  1. What does success look like here at six months?
  2. Hardest open problem on the team right now?
  3. How does the team handle technical disagreements?
  4. What does the loop still need from me?
  5. Anything in my background that gives you pause?

Ask two, not seven. Write them down so you don’t blank.

Spoken shapes (made up on purpose)

Q: What’s a decision you’d remake?

I’d say: “Launch date on Project North. We shipped a partial API because sales had a Friday. Support spiked two weeks. Next time I’d cut admin UI scope first and keep the API contract stable, even if the deck looked thinner.”

Q: Why this company?

I’d say: “I’ve used your billing alerts when I ran a small tools budget. The JD’s false-positive focus matches my last year on-call. I want that problem with a team that already owns the surface.”

Q: Tell me about a disagreement with your manager.

Weak: “We didn’t always agree, but we talked it out and it was fine.”

That’s a shrug. Add the disagreement, the options you brought, and what changed.

Steal the order. Swap your facts. If it sounds like a LinkedIn essay, cut adjectives until a coworker recognizes the week.

FAQ

How many mock interview questions should I prep? Depth on 8–12 stories beats shallow answers for all 50. Use the rest as surprise prompts.

Different answers per company? Same core stories. Swap “why us” and which project you lead with.

How long is a good mock? 30–45 minutes. Five questions with follow-ups beats fifteen rapid-fire.

Should my friend give the “right” answer? No. They tell you what was unclear. You own the content.

Is AI alone enough? Strong for reps and timing. Still get one human who interrupts before a final round if you can.

Practicing with OfferBull

A list on a screen won’t interrupt you when you dodge the result.

OfferBull is an AI mock interview app for iOS and Android. Voice interviewer. You speak. Paste a JD or upload a resume. Follow-ups on what you said. Suggestions and STAR while you practice. English and Chinese.

Before the interview. Not during.

Start an AI mock interview


Practice This Out Loud

Tonight: pick five from the bank you usually skip. Timer on. Record. Score with the rubric. Retry the weakest one. Then a short voice mock with follow-ups. → Practice Now