Mock interview questions are practice interview questions that mirror what a real interviewer will ask, so you can rehearse your answers out loud before it counts. They cover the same ground as an actual interview: your background, past behavior, role-specific skills, and how you handle hypothetical situations.
Quick answer: A good bank of mock interview questions spans five categories: opening/general, behavioral, role and skills, situational, and closing questions you ask them. Aim to practice 40-50 questions total, but say your answers out loud rather than just reading them. The list below gives you specific questions to work through today, plus one worked sample answer using the STAR method.
What are the main categories of mock interview questions?
Most interviews pull from a few predictable buckets. If you practice a handful from each, you will be ready for the majority of what any interviewer throws at you.
| Question type | What it tests | Example question |
|---|---|---|
| Opening / general | Your pitch, focus, and fit | Tell me about yourself. |
| Behavioral | How you actually acted in the past | Tell me about a time you handled conflict on a team. |
| Role & skills | Whether you can do the job | Walk me through a project you are proud of. |
| Situational | Your judgment on hypotheticals | What would you do if a deadline slipped? |
| Closing / questions to ask | Your curiosity and interest | What does success look like in this role? |
For the full picture on how to run practice sessions, see our complete guide to mock interviews.
Opening and general questions
These usually come first and set the tone. Get them tight and you buy goodwill for the rest of the conversation.
- Tell me about yourself.
- Why do you want this job?
- Why do you want to work here?
- Why are you leaving your current role?
- What are your greatest strengths?
- What is your biggest weakness?
- Where do you see yourself in five years?
- What are you looking for in your next role?
- Walk me through your resume.
- What do you know about our company?
The first one trips up most people. See how to nail tell me about yourself before you practice the rest.
Behavioral questions
Behavioral questions start with "Tell me about a time" or "Give me an example." They test what you have actually done, not what you claim you would do.
- Tell me about a time you handled conflict with a coworker.
- Describe a time you failed and what you learned.
- Tell me about a time you led a project or team.
- Give an example of a goal you set and how you reached it.
- Tell me about a time you disagreed with your manager.
- Describe a time you had to work under a tight deadline.
- Tell me about a time you went above and beyond.
- Give an example of a mistake you made and how you fixed it.
- Tell me about a time you had to persuade someone.
- Describe a time you juggled competing priorities.
- Tell me about a time you received hard feedback.
- Give an example of a time you dealt with an unhappy customer or stakeholder.
For deeper coaching on this category, read our breakdown of common behavioral interview questions.
Role and skills questions
These probe whether you can actually do the work. They vary by field, so swap in the specifics of your target role.
- Walk me through a project you are proud of.
- What tools and technologies do you use day to day?
- How do you measure success in your work?
- Describe your process for starting a new project.
- How do you stay current in your field?
- What is a hard problem you solved recently?
- How do you prioritize when everything feels urgent?
- What would you focus on in your first 90 days here?
- How do you handle a project outside your comfort zone?
- What part of this role are you most and least excited about?
Situational questions
Situational questions are hypotheticals: "What would you do if..." They test judgment, not memory, so think out loud and explain your reasoning.
- What would you do if you were assigned a task with unclear instructions?
- How would you handle a teammate who is not pulling their weight?
- What would you do if you disagreed with a decision from leadership?
- How would you respond if a project deadline suddenly moved up?
- What would you do if you made a mistake that no one noticed?
- How would you handle two managers giving you conflicting priorities?
- What would you do in your first week if you felt lost?
- How would you approach a problem you have never seen before?
Closing questions and questions to ask them
The interview usually ends with a chance for you to ask questions. Skipping this signals low interest, so have a few ready.
- Do you have any questions for me?
- Is there anything about my background that concerns you?
- What does success look like in this role after six months?
- What are the biggest challenges the team is facing right now?
- How would you describe the team culture?
- What does the path to growth look like from this role?
- What are the next steps in the process?
- How is performance measured and reviewed here?
What does a strong sample answer look like?
The STAR method keeps behavioral answers clear: Situation, Task, Action, Result. Here is a worked example for "Tell me about a time you handled conflict on a team."
- Situation: On my last team, a designer and I disagreed about whether to ship a feature on schedule or delay it a week to fix a usability issue.
- Task: As the engineer closest to the code, I needed to break the stalemate without steamrolling the designer or missing our launch commitment.
- Action: I set up a 20-minute call, pulled the actual support tickets tied to the issue, and proposed a middle path: ship on time behind a feature flag, then roll out fully once the fix landed.
- Result: We launched on schedule, the fix shipped four days later, and support tickets for that flow dropped by about 30 percent the next month. The designer and I used the flag approach on two projects after that.
Notice the answer is specific, names a real tradeoff, and ends with a measurable result. That is the difference between a generic answer and one an interviewer remembers.
How do you actually practice these out loud?
Reading the questions is not practicing. You learn the answers by saying them, hearing yourself ramble, and tightening them up.
- Pick 8-10 questions across categories rather than trying all 50 at once.
- Say each answer out loud, start to finish, without notes.
- Record yourself or use a timer to catch answers that run long.
- Repeat the ones that felt shaky until they come out clean.
The fastest way to get real feedback is to practice these questions in a mock interview that grades you. You paste the job description, an AI calls your phone and runs the session for that exact role, then scores you with concrete tips on what to fix.
How many questions should you practice before an interview?
You do not need to memorize all 50. Cover the categories, prioritize behavioral and opening questions, and prepare three or four strong stories you can adapt to different prompts.
A single real interview typically runs 8-15 questions, so practicing 15-20 gives you comfortable coverage. Depth beats breadth here.
Bottom line: Use this bank to practice mock interview questions across all five categories, build a few STAR stories you can reuse, and rehearse them out loud instead of in your head. The questions above are close to what you will actually be asked, so time spent here transfers directly to the real thing.