Residency interview answer guide
A research project setback: a residency interview answer guide
A research-setback answer should explain the project question, your role and how the team responded when the work did not go as planned. Keep methods and findings accurate, and do not confuse a disappointing result with a failed study.
How to approach it
- 1
Define what actually went wrong
Distinguish an unexpected finding from a process problem, such as recruitment delays, missing data or an unsuitable analysis plan. State your role. Do not imply you were the principal investigator if you were assisting.
- 2
Explain the response with supervision
Describe what you brought to the mentor or team, what options were considered and what changed. If a protocol or approved plan needed review, explain the real process without claiming that you independently changed it.
- 3
Separate the result from the learning
Say whether the project continued, changed scope or stopped. Use findings you can support and protect unpublished or confidential material. Explain one improvement in how you plan or check research now.
A fill-in outline, not a script
Our project asked [question]. My role was [contribution]. We encountered [specific setback]. I [action] and discussed [options] with [mentor]. The team decided [next step]. The result was [known outcome]. I learned [planning or research habit].
This is an illustrative outline. Replace every bracket with something true from your own experience. The AAMC advises applicants to prepare rather than rehearse, so you can answer the question you are actually asked.
What advisers and program directors say
The AMA's research interview guidance asks applicants to know the project design, results and next steps, and to tailor detail to the interviewer's interest. That is especially important when explaining a setback.
AAMC recommends reflecting on failure and learning, but a research answer still needs accurate definitions of what failed and what was simply unexpected.
Mistakes to avoid
- Calling a negative finding a failure without explanation.
- Taking credit for the whole team's decision.
- Inventing significance or publication status.
- Sharing private data or an unapproved protocol change.
Check your answer
- Can you explain design and findings accurately?
- Is your contribution separate from the mentor's?
- Are unpublished details safe to discuss?
Follow-up questions to expect
- What other options did the team consider?
- How did the setback affect the question?
- What would you change in the next project?
Common questions
What if the project was never published?
Explain its actual status and what you contributed. Publication is not a reason to invent a better outcome or conceal a useful learning experience.
Should I discuss statistics in detail?
Know them, but match the detail to the question. Start with the main issue and your response, then expand when asked.
What if the result contradicted our hypothesis?
Describe it as a finding unless there was a specific quality problem. Explain what the team learned and how it affected the next question.
Related guides
Sources
- AMA, How to highlight your research work in residency interviews (Dec 2024)
- AAMC, Preparing for Your Interview(s)
This page is general editorial guidance based on the sources above. It is not a prediction of any program's questions or a statement of its current policies.