Research Expectations for Ophthalmology Applicants
"Tell me about your research" comes up in nearly every ophthalmology interview, and most applicants mishandle it — either by summarizing a paper nobody wants summarized, or by inflating a small role into something it wasn't. What interviewers are really asking is simpler than you think: do you understand the work you did, and are you honest about your part in it?
The framework: Question → Role → Finding → Limitation
Question — what were you actually trying to answer?
Start with the scientific question in one sentence, in plain language. This immediately shows you understood the project, not just the tasks you were assigned.
Role — what did you specifically do?
Name your real contribution honestly: designing the protocol, chart review, data cleaning, the analysis, drafting the manuscript. Specific tasks, not vague "I contributed to."
Finding — what did the study find?
One sentence. The headline result. This is not a journal club presentation — they want the takeaway.
Limitation — what was weak about it?
This is the power move. Volunteering a limitation — "retrospective design, single center, we couldn't control for X" — shows critical thinking and honesty. The applicant who names the limitation before being asked it wins credibility.
First author vs. middle author
If you're a first author, you should be able to defend the whole project — the question, the methods, the statistics, the limitations. If you're a middle author, own the supporting role without apology and extract genuine learning: "I was a middle author on a glaucoma outcomes project — primarily chart review and data cleaning. Unglamorous, but it taught me how retrospective research actually works: what clean data looks like, how much judgment goes into defining variables." Then be honest about what you can't speak to: "I wasn't involved in the analysis, so I can't speak to the statistics in depth." That honesty beats bluffing — and you can pivot to ambition: a middle-author paper becomes evidence of trajectory when you say you want a first-author project as a resident, where you own the question from the start.
Never inflate a case report into a "research program." Programs have read the CV. The applicant who accurately describes a modest role looks more trustworthy than the one who stretches a small project into something grand — and trustworthiness is the entire point of this question.
The "no research" applicant
Don't apologize and don't hide. If your school has no ophthalmology department and you lacked research access, say so plainly: "My school has no ophthalmology department, so I lacked the research access some applicants had — I spent that time in deep clinical electives, and I'm excited to start producing as a resident." Programs would rather rank a future-productive resident than punish a student for their school's limitations. What matters is the forward-looking attitude, not an apology.
Connecting research to the program
When a program asks about research, they're also reading for something else: whether you'd be productive there. If your research interest aligns with a faculty member's work, saying so — genuinely, with a paper of theirs you've actually read — turns the research question into a "why our program" answer. Just make sure the interest is real and the evidence supports it.
Mistakes to avoid
- Summarizing the paper like journal club. They don't need the methods section. Question, role, finding, limitation — then stop.
- Bluffing beyond your role. If you weren't involved in the statistics, say so. Getting caught guessing is worse than admitting limits.
- Inflating small roles. A middle-authorship owned honestly beats a "research program" built on a case report.
- Apologizing for no research. State the circumstance, show the clinical depth you built instead, and point forward.
The guide's research chapter includes both full sample answers — the first-author project and the supporting role owned honestly. Get the complete guide on Fiverr — or pick up the extended edition on Amazon.