The Interview Questions Worth Preparing for—and How to Answer Them

Common job interview questions ask about your background, motivation, strengths, weaknesses, and examples of past work. Begin with the 10 priority questions below, then use the additional 20-question bank to broaden your preparation. Build three to five adaptable stories for behavioral prompts, and use direct, question-specific structures for motivation, career history, self-assessment, technical, case, and logistical questions. MIT Career Advising recommends preparing three to five flexible stories rather than scripting every response.

Start here: the 10 questions to prepare first

These 10 questions recur across the career-preparation guides cited here, but they are preparation priorities rather than a statistically ranked “top 10.” CareerOneStop recommends reviewing common questions, writing experience-based responses, and practicing them aloud; other career guides cover the same core themes of background, motivation, strengths, goals, achievements, and employer fit. CareerOneStop provides a practical question bank and preparation guidance.

Question	What it likely assesses	Answer outline	Customize—and avoid
Tell me about yourself.	Relevant background, communication, focus	Relevant background → present strengths → connection to this role	Customize: Which two experiences best match the job? Avoid: Reciting your full resume or personal history.
Why do you want this role?	Motivation and understanding of the work	Appealing responsibilities → evidence you can contribute → career direction	Customize: Which listed responsibility genuinely interests you? Avoid: Discussing only pay, prestige, or the need for any job.
Why this organization?	Research, judgment, alignment	Specific employer need or priority → connection to your experience or interests	Customize: What did you learn from the employer’s public materials? Avoid: Praise that could describe any organization.
What are your strengths?	Self-awareness and relevant capability	Two or three role-relevant strengths → brief evidence for each	Customize: Which requirements matter most in the posting? Avoid: Unsupported adjectives such as “excellent” or “hardworking.”
What is your greatest weakness?	Self-awareness and development	Real, manageable limitation → work impact → improvement effort	Customize: Which genuine limitation does not undermine an essential duty? Avoid: A disguised strength such as “I care too much.”
What accomplishment are you proud of?	Performance, ownership, values	Challenge → personal contribution → outcome → significance	Customize: Which achievement demonstrates a required competency? Avoid: Describing only what the team did.
Why should we hire you?	Overall fit and likely contribution	Key job requirements → matching evidence → contribution you could make	Customize: What evidence distinguishes your fit for this role? Avoid: Claiming superiority over candidates you do not know.
Where do you want to be in five years?	Direction, expectations, alignment	Skills to develop → responsibilities to earn → connection to the opportunity	Customize: What realistic growth could this role support? Avoid: An inflexible title prediction or an unrelated ambition.
Why are you leaving, or why did you leave?	Career judgment and transition context	Brief truthful reason → what you seek next → connection to this role	Customize: Which forward-looking factor matters most? Avoid: Unnecessary criticism of a former employer or colleague.
Do you have questions for us?	Preparation, judgment, mutual fit	Ask about priorities, success measures, challenges, team, or next steps	Customize: What important issue remains unanswered? Avoid: Asking something already covered or easily found online.

For “Tell me about yourself,” build a concise professional arc: the relevant background that brought you here, the strengths that define your current work, and why those points lead naturally to this opportunity. It is not a request for your complete biography.

Keep “Why this role?” separate from “Why this organization?” The first concerns the responsibilities and problems you would handle. The second concerns the employer’s mission, customers, products, priorities, culture, or operating context. In both cases, connect what you researched with your evidence and career direction.

For strengths and hiring fit, make a compact case by pairing important job requirements with proof: a project, qualification, responsibility, result, or informed example. For a weakness, acknowledge a real limitation and explain the practical steps you are taking to manage it.

Know the question type before choosing an answer structure

Not every interview question needs a story. First identify the kind of response the prompt requires.

• General questions concern your background, motivation, qualifications, goals, preferences, and work style.
• Behavioral questions request a specific example from your past, often beginning with “Tell me about a time…”

• Situational questions present a hypothetical future problem and ask what you would do.

• Logistical questions address availability, location, travel, schedule, relocation, or compensation.

Some employers use structured interviews, in which candidates receive predetermined questions and responses are judged against common standards. The U.S. Office of Personnel Management describes structured interviews as a method for assessing job-related competencies more consistently; structure does not mean that every interview will feel rigid or that bias disappears. See OPM’s overview of structured interviews.

Question cue	Type	Recommended structure	Example
“Tell me about…” or “Why…”	General	Direct answer → relevant evidence → role connection	“Why do you want this role?”
“Tell me about a time…”	Behavioral	Situation → Task → Action → Result	“Tell me about a time you handled conflict.”
“What would you do if…”	Situational	Clarify → prioritize → proposed actions → intended outcome	“What would you do if two deadlines conflicted?”
“How does X work?”	Technical	Assumptions → method → reasoning → conclusion	“How would you diagnose this failure?”
“Estimate, analyze, or recommend…”	Case	Clarify objective → structure → analyze → synthesize	“Should this company enter the market?”
“When can you start?”	Logistical	Direct factual answer → necessary condition	“Are you available to travel?”

STAR is primarily useful for behavioral questions. It can also help organize a situational answer, although a hypothetical response should emphasize your reasoning and intended actions rather than pretend the event already happened. STAR is usually unnecessary for short factual, motivational, or logistical answers.

Case interviews are especially associated with consulting, while technical interviews are particularly relevant to STEM, engineering, and computing roles. Practices still vary by occupation and employer. UC Davis distinguishes these role-dependent interview formats in its preparation guidance.

A categorized bank of 20 questions and answer plans

The following 20 questions are additional to the 10 priorities above. They are grouped by purpose, not claimed frequency. Each “likely competency” is a reasonable area of interest, not a universal hidden meaning shared by every interviewer.

Background and fit

1. “Walk me through your resume.”

• Key points: Select the transitions and responsibilities that explain your fit; finish with why you are considering this role.
• Common pitfall: Reading every line chronologically without explaining its relevance.

2. “What makes you unique?”

• Key points: Identify a credible combination of skills, perspective, and experience.
• Common pitfall: Making unverifiable comparisons with other candidates.

3. “What motivates you?”

• Key points: Name the problems, responsibilities, or working conditions that energize you and connect them to the role.
• Common pitfall: Offering a polished value statement unsupported by behavior.

4. “What do you know about this organization or industry?”

• Key points: Discuss relevant products, services, customers, mission, priorities, or industry conditions.
• Common pitfall: Repeating the employer’s homepage without explaining why the information matters.

Self-awareness

5. “How would you describe your work style?”

• Key points: Explain how you plan, communicate, and balance independent work with collaboration.
• Common pitfall: Describing only your ideal environment rather than how you adapt.

6. “What kind of manager helps you do your best work?”

• Key points: Describe useful conditions such as clear priorities, appropriate autonomy, and candid feedback.
• Common pitfall: Listing demands or criticizing previous managers.

7. “How do you handle stress?”

• Key points: Explain how you assess urgency, prioritize, communicate, and recover.
• Common pitfall: Claiming that you never experience stress.

Evidence of performance

Use a specific past event and STAR for these prompts.

8. “Tell me about a time you led.”

• Key points: Show how you set direction, aligned people, made decisions, or removed obstacles.
• Common pitfall: Treating employee supervision as the only form of leadership.

9. “Tell me about a time you worked on a team.”

• Key points: Explain the shared goal, your role, how you coordinated, and the result.
• Common pitfall: Saying “we” throughout without identifying your contribution.

10. “Tell me about a time you solved a difficult problem.”

• Key points: Define the problem, explain your diagnosis, compare options, and show the decision.
• Common pitfall: Jumping from the problem to the result without showing your reasoning.

11. “Tell me about a time you managed competing deadlines.”

• Key points: Explain your criteria, trade-offs, sequencing, and communication.
• Common pitfall: Suggesting that working longer was your only strategy.

12. “Tell me about a time you handled conflict.”

• Key points: Describe the disagreement neutrally, clarify interests, and explain the decision or lesson.
• Common pitfall: Presenting yourself as entirely right and the other person as unreasonable.

13. “Tell me about a time you made a mistake or failed.”

• Key points: State what happened, own your part, explain the corrective action, and show what changed afterward.
• Common pitfall: Choosing a trivial mistake or blaming circumstances.

14. “Tell me about a time you adapted to change.”

• Key points: Explain what changed, how you reassessed priorities, and how you helped the work continue.
• Common pitfall: Pretending the change created no difficulty.

15. “Tell me about a time you showed initiative.”

• Key points: Identify what you noticed, why action was warranted, and how you involved the right people.
• Common pitfall: Describing unauthorized action without considering stakeholders.

Career history and logistics

16. “Can you explain this employment gap or career transition?”

• Key points: Answer directly, provide only useful context, mention relevant development where truthful, and redirect to current fit.
• Common pitfall: Overexplaining or becoming defensive.

17. “How have you developed professionally?”

• Key points: Identify a skill gap, action taken, application, and next development priority.
• Common pitfall: Listing activities without showing what changed.

18. “What are your salary expectations?”

• Key points: Give a role- and location-relevant range, state important assumptions, and consider total compensation.
• Common pitfall: Using an arbitrary number or a supposedly universal formula.

Research comparable work rather than borrowing a figure from a sample answer. Account for responsibilities, seniority, location, variable pay, benefits, and other material terms. Indeed likewise recommends researching a market range rather than relying on an unspecified universal number.

19. “When can you start?”

• Key points: State an honest date or notice requirement and any necessary condition.
• Common pitfall: Promising availability you cannot honor.

20. “Are you willing to travel, relocate, or work the required schedule?”

• Key points: Answer each requirement directly and clarify scope where needed.
• Common pitfall: Agreeing under pressure and attempting to reverse the answer later.

Build three to five reusable STAR stories

STAR stands for:

• Situation: The context needed to understand the event.
• Task: Your responsibility, objective, or challenge.
• Action: The specific steps you personally took.
• Result: What happened, what changed, or what you learned.

After identifying the important competencies in the job description, prepare three to five truthful stories that collectively cover themes such as leadership, teamwork, conflict, failure, pressure, deadlines, initiative, change, and problem-solving. Your examples can come from paid work, education, volunteering, military service, extracurricular activities, caregiving, or personal projects.

Use this vertical worksheet for each story:

• Competency: Which job requirement does the story demonstrate?
• Situation: What was happening, and what constraints mattered?
• Task: What were you personally responsible for?
• Individual actions: What specific steps did you take?
• Result: What happened?
• Metric or concrete evidence: What genuine number, date, milestone, decision, or observable indicator supports the result?
• Lesson: What did you learn or change afterward?
• Possible follow-ups: What did you own? What alternatives did you consider? What went wrong? How did you measure the result? What would you do differently?

The Action portion should make your contribution unmistakable. Use specific verbs such as analyzed, proposed, tested, negotiated, scheduled, escalated, simplified, coached, or documented. Explain the team context, but do not hide your work inside repeated “we” statements.

Finish with an outcome when one exists. A genuine number, completion milestone, stakeholder decision, quality indicator, or observable change can add precision. If no useful metric exists, state the concrete outcome or lesson. Never invent a number to make an answer sound stronger.

One story may support several competencies. A delayed project might demonstrate leadership, conflict management, prioritization, or communication, depending on which facts and actions you emphasize. Keep the event consistent, answer the exact prompt, and memorize facts and story beats rather than complete wording.

Worked example: adapt one story to three questions

The following is a fictional structure, not a claimed result. Replace every bracketed item with truthful details from your own experience.

Constant event: A cross-functional project was approaching a deadline. Responsibilities were unclear, two contributors disagreed about priorities, and a required dependency was late.

Version one: leadership

• Situation: The project was due in [time period], but ownership was unclear and a dependency threatened delivery.
• Task: I was responsible for [actual responsibility] and needed to help the group regain direction.
• Action: I clarified the deliverable, proposed owners for each workstream, confirmed deadlines, and worked with [person or team] to remove the dependency blocker.
• Result: We delivered [truthful outcome], supported by [real metric or concrete evidence]. I learned [lesson].

The leadership version emphasizes setting direction, assigning responsibility, and removing blockers.

Adapt the emphasis without changing the event: a teamwork answer can focus on listening and agreement; a prioritization answer can focus on sequencing and trade-offs.

A weak answer would say:

“We communicated well, worked hard, and finished the project successfully.”

A stronger structure would be:

“I identified that [specific dependency] would delay [deliverable], proposed [specific change], confirmed ownership with [stakeholders], and tracked [real indicator] until [truthful result].”

Be prepared for follow-ups: What did you personally own? What alternatives did you consider? What went wrong? How did you measure the result? What would you do differently?

Handle difficult questions without evasion or spin

A difficult answer does not need to make you look flawless. It needs to be direct, relevant, and credible.

For a weakness, identify a genuine but manageable limitation. Explain when it affects your work and what you are doing about it, such as using a planning system, escalating earlier, seeking feedback, practicing a skill, or completing training. Do not rename a strength as a weakness.

For a mistake or failure, state what happened, acknowledge your responsibility, and explain any corrective action. Then identify what changed in your later behavior. The original result does not have to become a success story; a credible lesson may be the appropriate conclusion.

For conflict, separate the person from the issue. Describe the disagreement neutrally, show how you listened or negotiated, and explain how a decision was reached. If the matter remained unresolved, discuss what you learned rather than inventing harmony.

For a difficult departure, provide a concise and truthful account without unnecessary negativity. Then connect the transition to what you are seeking now when appropriate. Layoffs, terminations, and lengthy gaps involve different circumstances, so there is no responsible universal script beyond direct, constructive framing.

If you lack a close workplace example, choose a relevant event from education, volunteering, extracurricular activities, military service, caregiving, or a personal project. It still needs a defined responsibility, specific personal actions, and an outcome or lesson.

Prepare questions for the employer and close the interview

Candidate questions should help you assess the opportunity as well as demonstrate preparation. Choose two or three questions that address information you genuinely need and that the interviewer has not already covered. CareerOneStop’s guidance similarly recommends preparing questions about responsibilities, challenges, success criteria, culture, stakeholders, and next steps.

Useful options include:

• “What are the role’s top priorities in the first 90 days?”
• “How will success be measured?”
• “What challenge should the new hire address first?”
• “Which skills are most important for someone entering this role?”
• “How does the team divide responsibilities?”
• “What are the team’s most important current challenges?”
• “How would you describe the working culture?”
• “What opportunities are available for learning or growth?”
• “Who are the role’s main stakeholders?”
• “What is the next step in the process?”

No individual question guarantees a favorable impression. Select questions that help you judge the responsibilities, expectations, working environment, and potential fit.

At the end, thank the interviewer, briefly reiterate your interest if it is genuine, and clarify the next step. Career-center guidance also recommends sending a short follow-up thank-you email, but it should be treated as professional communication—not as a tactic guaranteed to change the decision.

Adjust the practice—not the truth—for interview format

Interview format changes delivery and preparation, not the facts of your experience.

• Phone: Keep the job description and concise notes nearby. Choose a quiet setting, listen carefully, and leave room for follow-up questions.
• Live video: Test the platform, camera, microphone, connection, and lighting. Keep notes brief enough that you do not read from them.
• Panel: Begin by addressing the person who asked the question, then include the group naturally. Make each example easy to follow against the competency being discussed.
• Recorded video: Test your equipment, learn the platform’s process, practice within any stated response limit, look toward the camera, and preserve a conversational delivery.
• Technical: Add practice with the knowledge, tools, calculations, or work samples expected for the occupation.
• Case: Practice clarifying the objective, structuring ambiguous problems, testing assumptions, and synthesizing a recommendation.

Some video-interview publishers suggest fixed timing ranges, but those figures are publisher guidance rather than universal standards. A factual answer may take only a sentence or two. A behavioral answer needs enough detail to explain the context, your responsibility, your actions, and the result. Stop when you have answered the question instead of stretching every response to the same duration.

A general question bank is not sufficient preparation for technical or case interviews. Review the employer’s stated process and add role-specific problem practice.

If an interview question becomes personal

In the United States, the Equal Employment Opportunity Commission recommends that employers avoid questions about protected personal characteristics such as race, color, religion, sex, national origin, and age, along with questions about pregnancy or plans to start a family. An age-related question may be relevant when used to verify a lawful age requirement for the job. The guidance does not say that every sensitive question is automatically unlawful; wording, purpose, jurisdiction, and current law matter. Read the EEOC’s guidance on personal interview questions.

If a question feels personal, you can:

• Ask how the information relates to the job’s requirements.
• Address the underlying job-related concern, such as schedule or travel availability, if comfortable.
• Decline briefly and redirect to your qualifications.

This is general information, not legal advice. HRaizon also describes its content as informational rather than legal, HR, or employment advice. For legal questions, confirm current requirements through authoritative guidance or qualified counsel.

One-page practice checklist

• [ ] Mark the job description’s most important responsibilities and competencies.
• [ ] Draft concise, role-specific answers to the 10 priority questions.
• [ ] Review the additional 20 questions most relevant to the role.
• [ ] Research the organization, role, industry, and relevant compensation market.
• [ ] Build three to five truthful STAR stories.
• [ ] Map each story to multiple competencies without changing its facts.
• [ ] Record your personal actions, genuine outcomes, and lessons.
• [ ] Remove invented metrics, generic praise, and unsupported claims.
• [ ] Rehearse follow-ups about ownership, alternatives, trade-offs, setbacks, and measurement.
• [ ] Prepare two or three unanswered questions for the employer.
• [ ] Confirm the time, format, location, platform, equipment, and contact details.
• [ ] Practice natural delivery rather than memorizing scripts.

Effective interview preparation means organizing real evidence around the role—not predicting every question or performing a polished version of someone else’s answer.