50 Common Interview Questions and How to Answer Them

Most interviews draw from the same pool of common interview questions. The wording shifts from company to company, but the interviewer is nearly always testing one of six things: whether you can explain your background, why you want this job, how well you know yourself, how you acted in real situations, how you would handle new ones, and whether the practical details line up.

That makes your prep far more manageable. You don't need 50 memorized scripts. You need five answer frameworks and eight to ten true stories you can adapt on the spot.

Below are 50 questions grouped by what they really test, each with a strategy and, where it helps, a short example. After the list you'll find a story bank template and a seven-day practice plan that turns reading into answers you can deliver out loud.

Why the same questions show up in almost every interview#

Interviews look improvised from the candidate's chair, but many employers run them from a script. The U.S. Office of Personnel Management describes structured interviews as using set rules for asking and scoring questions, with highly structured versions giving every applicant the same questions and rating answers against benchmarks. OPM names two main question types: behavioral (what you did) and situational (what you would do).

The competencies behind those questions are predictable too. Employers screen for a short list of skills, and the questions are built to collect evidence of each one.

NACE's own write-up of its earlier Job Outlook 2025 survey found nearly 90% of employers looking for evidence of problem-solving and close to 80% wanting strong teamwork skills. The exact ranks move a little each year, but the same attributes stay at the top.

Read the chart as a prep guide. If teamwork and problem-solving lead the list, expect at least one question on each, and make sure your strongest stories prove them.

Five frameworks that answer almost any interview question#

Each question family has a structure that fits it. Learn these five and you'll rarely freeze, because you'll always know what the first sentence of your answer should be.

Present–Past–Future#

Start with what you do now, add the one or two past experiences that explain how you got here, and finish with why this role is the logical next step. It keeps self-introductions short and points them at the job.

STAR#

Situation, Task, Action, Result. Use it whenever a question asks for a specific time or example. Our STAR method guide breaks down each step with longer examples.

Claim–Proof–Link#

Make one clear claim ("I'm good at turning messy data into decisions"), prove it with a specific example, then link it to something the employer needs. This works for strengths, "why should we hire you," and most fit questions.

Approach–Example–Check#

For hypotheticals, explain the steps you'd take, anchor them in a time you did something similar, and say how you'd confirm it worked. This shows judgment instead of guesswork.

Honest–Fix–Proof#

Name a real limitation, describe the specific system you use to manage it, and give evidence that the fix works. It's built for weakness, mistake, and feedback questions.

Adapt the frameworks to your experience level#

The same question lands differently depending on where you are in your career. Adjust your examples, not your frameworks.

• Students and new grads: Draw from class projects, part-time jobs, clubs, and volunteering. Interviewers expect it. Focus on learning speed and initiative.
• Career changers: Lead with transferable results and explain the pivot early, ideally in your answer to question 1.
• Mid-career candidates: Show scope growth. Each story should involve more people, budget, or complexity than the last.
• Managers and senior leaders: Expect questions 42 and 43 in every round. Your results should include team outcomes, not just your own output.

The questions don't change much between levels. What changes is the size of the problems in your stories and how much of the result came from other people you led.

Opening and background questions (1–8)#

These come early and set the tone. Interviewers use them to see whether you can summarize yourself clearly and whether your story makes sense for this role.

1. Tell me about yourself#

Use Present–Past–Future and keep it under 90 seconds. Lead with your current role and one result, add the experience that matters most for this job, then say why you're interested. Our guide to answering "tell me about yourself" covers variations for career changers and new grads, and the free tell me about yourself generator can draft a first version from your resume.

2. Walk me through your resume#

This is a longer cousin of question 1. Move chronologically but spend 80% of your time on the last two roles. For each move, give a one-line reason ("I left to take on budget ownership"). The interviewer wants to see a logic to your choices, not a list of every task.

3. How would you describe yourself in three words?#

Pick three words that match the job posting and that you can back up. Say each word, then add one short proof. "Organized: I run our team's sprint board. Curious: I taught myself SQL to answer my own reporting questions. Steady: I'm the person people call during an outage."

4. What do you know about our company?#

Show research beyond the About page. Mention a recent product launch, a market the company is entering, or a line from the job posting about team priorities. Then connect one detail to your experience. Two specific facts beat five vague compliments.

5. How did you hear about this position?#

Answer honestly and use it as a bridge. If someone referred you, name them and say what they told you that made you apply. If you found it on a job board, say what in the posting caught your attention.

6. Why are you looking for a new job?#

Frame the move as moving toward something, not away. Mention growth you want, scope you've outgrown, or a direction this company offers. Never criticize your current employer. See how to answer "why are you leaving your job" for scripts covering layoffs, toxic teams, and relocation.

7. Why did you leave your last job?#

If you were laid off, say so plainly, give the business reason in one sentence, and move to what you've done since. If you were fired, own it briefly, share what you learned, and point to evidence that the lesson stuck. Keep this answer under 45 seconds.

8. Can you explain this gap in your resume?#

State the reason in one sentence (caregiving, health, study, a layoff, travel), mention anything you did to stay sharp, and close by confirming you're ready now. You don't owe medical details. Our guide to employment gaps has wording for each situation.

Motivation and fit questions (9–15)#

Fit questions check whether you've done your homework and whether your reasons for wanting the job will hold up after six months. Use Claim–Proof–Link for most of them.

9. Why do you want to work here?#

Give two reasons tied to this specific company: something about the work, the mission, the team, or the way they operate. Then connect each reason to your experience. Our guide on answering "why do you want to work here" shows how to research the answer in 20 minutes.

10. Why are you interested in this role?#

This differs from question 9. Focus on the work itself: the problems you'd solve, the skills you'd use, and the part of the job you'd enjoy most. Quote a phrase from the posting so it's clear you read it closely.

11. Why should we hire you?#

Summarize your fit in three points that mirror the job's top requirements, and prove each with a result. Close with what you'd bring that other candidates might not. Our full guide to answering "why should we hire you" has templates for different experience levels.

12. What makes you different from other candidates?#

You don't know the other candidates, so don't guess about them. Describe the combination that makes you useful: a technical skill plus an unusual background, or deep industry knowledge plus a track record of shipping fast. Combinations are more memorable than single traits.

13. What are you looking for in your next role?#

Name two or three things this role actually offers. If you say "more leadership" and the role has no reports, you've created doubt. Match your wish list to the posting and you'll sound like you've already chosen them.

14. What type of work environment do you prefer?#

Describe conditions where you do your best work, then show you can adapt. "I do my best work with clear goals and room to decide how to hit them. I've also worked in tightly structured teams, and I like having checklists when the stakes are high."

15. What motivates you?#

Pick a motivator that this job will feed: solving puzzles, helping customers, building something that lasts, seeing measurable progress. Give an example of a time that motivator pushed you to do better work.

Strengths, weaknesses, and self-awareness questions (16–22)#

These questions test whether you see yourself accurately. Overconfidence and false modesty both hurt you here. Be specific and back every claim with evidence.

16. What is your greatest strength?#

Choose a strength that's central to the role, not a generic trait like "hardworking." Make the claim, give one example with a result, and link it to the job. If the posting stresses stakeholder management, your strength should be about stakeholders.

17. What is your greatest weakness?#

Use Honest–Fix–Proof. Pick a real weakness that isn't a core requirement of the job, explain the system you use to manage it, and show it working. Skip disguised strengths like "I care too much." Our guide to answering "what is your greatest weakness" has examples by role.

18. How would your manager describe you?#

Give two or three traits and attach a real piece of evidence to each: a line from a performance review, a project you were trusted with, or a recurring responsibility. Evidence makes the answer credible; adjectives alone don't.

19. What would your coworkers say you could improve?#

This is the weakness question from a peer angle. Pick something collaborative and fixable, such as being slow to delegate or too brief in written updates. Then describe what you changed.

20. What's your proudest professional accomplishment?#

Pick an accomplishment that resembles the job you want. Use a compressed STAR: one sentence of context, two or three of actions, one of result. Explain why you're proud of it, since that reveals what you value.

21. Tell me about a mistake you made at work#

Choose a real mistake with moderate stakes, not a catastrophe and not a trivial typo. Own it without blaming others, explain how you fixed it, and describe the process change that prevents it from happening again.

22. Tell me about feedback that changed how you work#

Share specific feedback, how you reacted, and what you changed. The best answers show you sought follow-up feedback to confirm the change worked. This proves you're coachable, which matters more than being right.

Behavioral interview questions (23–32)#

Behavioral questions ask about real past events, usually starting with "tell me about a time" or "give me an example." They're built on the idea that past behavior predicts future behavior, which OPM calls the behavioral consistency principle. Our full list of behavioral interview questions goes deeper by competency.

Use STAR for every one of them, and weight your time toward the action. Many candidates spend half their answer on background, which leaves no room for the part interviewers score.

23. Tell me about a time you solved a difficult problem#

Pick a problem with a clear cause you had to find. Spend your action section on how you diagnosed it: the data you checked, the people you asked, the options you ruled out. End with the fix and the measurable outcome.

24. Describe a time you worked on a team that struggled#

Name the specific problem (unclear roles, a missed handoff, a conflict). Focus on what you did to help the team recover, not on who caused the trouble. Results can include the project outcome and how the team worked afterward.

25. Tell me about a time you disagreed with your manager#

Show that you disagreed with data, in private, and respectfully. Then show you committed to the final decision, even if it wasn't yours. Interviewers want to see that you can push back without creating friction.

26. Give an example of leading without formal authority#

Describe a time you rallied peers, set a direction, or ran a project you weren't assigned to lead. Explain how you got buy-in: a shared goal, a clear plan, credit given to others.

27. Describe a time you missed a deadline or nearly did#

Show early warning and recovery. Explain when you saw the risk, who you told, what tradeoff you proposed, and how you delivered. Close with what you now do differently to spot slippage sooner.

28. Tell me about a time you had to learn something quickly#

Name the skill, the deadline, and your learning method: documentation, a mentor, a small test project. End with what you delivered using the new skill.

29. Describe a time you handled a difficult customer or stakeholder#

Describe the person's concern fairly, without mocking them. Show that you listened, found the real need, and offered options. The best results include the relationship improving, not just the issue closing.

30. Tell me about a time you failed#

Choose a real failure with a lesson you've applied since. Spend less time on the failure and more on the analysis and change. A second, smaller example showing the lesson in action makes this answer strong.

31. Tell me about a time you used data to make a decision#

Explain the question you were trying to answer, the data you gathered, any limits it had, and the decision it led to. Show that you didn't just collect numbers; you acted on them.

32. Tell me about a time you went beyond your job description#

Pick an example where the extra effort solved a real problem, not just one where you worked late. Explain why you stepped in and what changed because you did.

Situational and problem-solving questions (33–38)#

Situational questions present a hypothetical and ask what you would do. Interviewers score your process, not whether you guess their preferred answer. Use Approach–Example–Check.

33. What would you do in your first 90 days?#

Outline three phases: learn (meet people, review data, understand priorities), contribute (take on a defined project), and improve (propose one change based on what you learned). If you want to bring a written plan, our 30-60-90 day plan guide shows the format.

34. How would you handle two urgent requests from different managers?#

Clarify deadlines and business impact with both requesters, make a proposal, and escalate only if they still conflict. Show that you'd communicate the tradeoff openly instead of quietly dropping one task.

35. What would you do if you saw a coworker cutting corners?#

Separate low-stakes shortcuts from safety, legal, or ethical issues. For minor issues, talk to the coworker first. For serious ones, follow company policy and report it. Interviewers listen for judgment and integrity in equal measure.

36. How would you approach a task you've never done before?#

Describe your learning loop: find existing documentation, ask someone who's done it, try a small version, check results, and then scale. Anchor it with a time you did exactly that.

37. What would you do if you disagreed with a decision after it was made?#

Explain that you'd raise new information if you had it, through the right channel, and otherwise commit fully. Teams need people who don't relitigate every decision.

38. How do you prioritize when everything feels urgent?#

Name your method: impact versus effort, deadlines, dependencies, and who's blocked. Then show it in action with a real week where you used it.

Teamwork, conflict, and management questions (39–44)#

Because teamwork tops employer wish lists, expect at least one of these. Managers should expect several.

39. How do you handle conflict with a coworker?#

Explain your steps: talk privately and early, ask questions to understand their view, focus on the shared goal, and agree on next steps. Then give a short real example. Avoid saying you never have conflict; it sounds unlikely.

40. How do you handle stress and pressure?#

Describe specific habits, such as breaking work into checkpoints, flagging risks early, or protecting focus time. Give one example of a high-pressure week and what you delivered.

41. How do you give and receive feedback?#

For giving feedback, describe a clear, private, specific approach tied to behavior and impact. For receiving it, show you ask questions, act on it, and follow up. One example for each side is enough.

42. Describe your management style#

Name your style in a sentence, then prove it with two behaviors your team would recognize, like weekly one-on-ones or clear decision rights. Add how you adjust for new hires versus experienced staff.

43. How do you handle an underperforming team member?#

Outline a fair process: diagnose the cause, set clear expectations, provide support, track progress, and escalate only if nothing improves. A real example where performance turned around is ideal.

44. Do you prefer working alone or on a team?#

Say you can do both and explain when each works best for you. Then lean slightly toward whatever the role needs. A remote analyst role and a client-facing team role call for different emphasis.

Career goals, salary, and logistics questions (45–50)#

These closing questions are short but carry real stakes. A clumsy salary answer or vague goal can undo a strong interview. Here's how to handle each one.

For deeper scripts, see our guides on where you see yourself in five years, salary expectations, and the best questions to ask in an interview.

Questions an interviewer shouldn't ask, and how to respond#

Some questions create legal risk for the employer. The U.S. Equal Employment Opportunity Commission says questions about marital status, number of children, and child care are often used to discriminate against women and may be treated as evidence of intent to discriminate. It advises employers to avoid them unless needed after an offer is accepted, for purposes like insurance.

Most interviewers who ask these questions are making small talk, not screening you out. You can still steer the conversation back to job-related ground.

Mistakes that sink otherwise good answers#

Strong candidates lose offers on delivery, not content. Watch for these patterns when you practice.

• Starting with background instead of the answer. Lead with the point, then support it.
• Saying "we" for everything. Interviewers can't hire your team. Use "I" for your actions.
• No result. Every story needs an ending, even if it's "the client renewed."
• Rambling past two minutes. Stop when you've given the result. Let them ask for more.
• Negative comments about past employers. Even fair criticism sounds risky to a new employer.
• Inventing examples. Follow-up questions expose made-up stories fast.

Build a story bank that covers the most common interview questions#

A story bank is a short list of real experiences, each mapped to the competencies it proves. With eight to ten stories, you can answer nearly every behavioral and self-assessment question on this list. Villanova's career center makes the same point in its common interview questions guide: prepare specific examples ahead of time and connect them to the role.

Here's a sample bank for a mid-level marketing coordinator. Build yours the same way.

Use this checklist to make sure your bank is complete:

• At least one story for each of the top five competencies in the job posting
• At least one failure or mistake with a clear lesson
• At least one conflict story where the relationship improved
• A result for every story, with a number if one exists
• A mix of recent stories, mostly from the last three years
• Each story told out loud in under two minutes

To predict which competencies you'll be asked about for a specific role, paste the posting into our free interview question generator, then check your bank against the list it returns. If a story needs structure, the STAR method answer generator can turn your notes into a draft.

A seven-day practice plan#

Reading answers doesn't make you fluent. Speaking them does. This plan fits around a full-time job with about 30 to 45 minutes a day.

1. Day 1: Decode the job. Highlight the top five skills in the posting and list the questions each skill suggests.
2. Day 2: Build your story bank. Write eight to ten stories in STAR bullet form, one line per step.
3. Day 3: Draft your openers. Write and time your answers to questions 1, 9, 11, 16, and 17.
4. Day 4: Say everything out loud. Record yourself answering ten questions. Cut anything that runs past two minutes.
5. Day 5: Practice with follow-ups. Have a friend, or an AI mock interview tool, ask "why?" and "what would you do differently?" after each answer.
6. Day 6: Prepare your closers. Finalize your salary range, start date, and five questions for the interviewer.
7. Day 7: Light review only. Reread your story bank once, prepare your outfit and logistics, and rest.

If you want structured feedback on delivery, the free mock interview practice tool scores your answers for clarity and structure. For logistics, use the interview prep checklist the day before.

Your next steps#

Start with the 15 questions you're most likely to hear: 1, 6, 9, 11, 16, 17, 20, 23, 24, 30, 39, 45, 46, 48, and 50. Draft those answers, build your story bank, and practice out loud at least twice before the interview.

Then go one level deeper on the questions that worry you most. Our full interview preparation checklist covers research and logistics, and once the interview is over, send a thank-you email within 24 hours that refers back to one of your strongest answers.