Residency interview questions: prepare the story behind your answer.

Build your answer

1. Choose one meaningful influence or experience.
2. Connect it to what you focus on now.
3. Close with what you hope to learn or contribute in residency.

Pitfalls to avoid

• Retelling your full CV.
• Using a memorized biography that leaves no room for conversation.
• Adding achievements or responsibilities you cannot substantiate.

Build your answer

1. Name a specific feature from a source you checked.
2. Explain why that feature matters to your learning or practical needs.
3. Connect it to a real experience or goal.

Pitfalls to avoid

• Generic praise.
• Calling a program your only choice without meaning it.
• Treating website language as proof of day-to-day culture.

Build your answer

1. State the direction you are considering now.
2. Name the experience or value behind that interest.
3. Explain what you hope residency will help you explore or build.

Pitfalls to avoid

• Presenting an early interest as an unchangeable promise.
• Claiming that a specific career path is guaranteed.
• Giving an answer disconnected from any real experience.

Build your answer

1. Choose one contribution.
2. Give a brief example that shows it.
3. Describe how it could support peers or shared work.

Pitfalls to avoid

• Listing adjectives without evidence.
• Comparing yourself favorably against other applicants.
• Claiming a team result as solely your own.

Build your answer

1. Give only the context needed.
2. Describe your responsibility and one action you took.
3. Share the result and what you learned about working with others.

Pitfalls to avoid

• Speaking only about what the group did.
• Taking credit for others’ work.
• Blaming teammates instead of reflecting on your own choices.

Build your answer

1. Choose a specific, non-confidential example.
2. Explain how you prioritized and communicated.
3. Reflect on what helped and what you would adjust.

Pitfalls to avoid

• Suggesting that needing support is a weakness.
• Describing unhealthy coping as a model to follow.
• Making broad claims about how you will handle every future situation.

Build your answer

1. Choose one or two experiences that shaped your thinking.
2. Explain what you learned about the work.
3. Connect that learning to your current motivation.

Pitfalls to avoid

• Claiming a single experience proves what medicine is always like.
• Using a dramatic story that is not yours to share.
• Relying on clichés without personal meaning.

Build your answer

1. Name one relevant strength.
2. Give a concise example.
3. Explain how you keep developing it.

Pitfalls to avoid

• Offering a list with no evidence.
• Choosing a strength only because it sounds impressive.
• Describing a strength as flawless or universal.

Build your answer

1. Name a real but manageable growth area.
2. Explain how you recognized it.
3. Describe a specific step you have taken and what you are learning.

Pitfalls to avoid

• Giving a disguised compliment.
• Sharing a concern without describing any response.
• Making a claim about improvement that you cannot support.

Build your answer

1. Summarize the feedback without identifying others.
2. Explain your response and any clarifying conversation.
3. Describe a change you tried and what you learned.

Pitfalls to avoid

• Dismissing the feedback or attacking its source.
• Claiming every criticism was correct.
• Saying you changed without giving a concrete example.

Build your answer

1. Give concise context and your role.
2. Describe the response you chose and any support you used.
3. Explain what you learned and what you would carry forward.

Pitfalls to avoid

• Blaming other people.
• Claiming a setback made you stronger without explaining how.
• Sharing confidential details or overstating the outcome.

Build your answer

1. Offer a concise introduction.
2. Name one or two verified program features.
3. Explain the genuine connection while leaving room for questions.

Pitfalls to avoid

• Turning the answer into a sales pitch.
• Repeating claims that are not verified.
• Using the same program-specific paragraph everywhere.