Talking About Your Honours or Masters Work

Ask a graduate applicant to describe their honours project and you can usually predict the next three minutes. Background, then more background, then a methods section, then an apology that it is quite technical, then a result the listener has no framework for. The applicant finishes slightly out of breath, aware it did not land, and unsure why.

Explaining research at interview is a skill of its own, and it is one of the few interview skills that is genuinely useful for the rest of your career. The panel may include a clinician outside your field, an academic from a different discipline and a community member. If your explanation only works for people who already know your area, it does not work.

What the question is really for

Almost nobody is assessing your science. They are assessing whether you can take something complicated and make it comprehensible to someone who needs to understand it, which is roughly the entire job of a doctor talking to a patient. Your project is the test material, not the subject.

Two secondary things are being checked. Whether you can identify what actually mattered rather than describing everything you did. And whether you can talk about your own contribution honestly in a project where a supervisor probably designed the thing.

A ninety second structure

Five moves. Practise them until you can do it without notes:

• The problem in human terms. One sentence about a person, a disease, a system or a cost. Not the gap in the literature. Something a stranger would agree is worth solving.
• The question. What specific thing was unknown, phrased as a question a non specialist could repeat back.
• What you did, in one sentence, with the technique named but not explained. We compared two groups. We looked at records over five years. We built a model and tested it against real data.
• What you found, including if the answer was nothing. Negative and inconclusive results are perfectly acceptable and often make better answers.
• Why it matters, honestly scoped. Not that it will change medicine. That it is one step, and here is the next one.

Then stop. The most common failure is not being unclear, it is not stopping. If they want more, they will ask, and the questions they choose tell you what they care about.

The jargon audit

Write out your ninety seconds and circle every word you learned during the degree. Gene names, assay names, statistical terms, acronyms, and the ordinary words your field uses strangely. Then remove or translate each one. Expression becomes how much of it the cell makes. Cohort becomes the group of people we followed.

You are allowed one technical term if it is the heart of the project, provided you define it in six words the first time. Two or more and you have lost the room.

The test that never fails: explain it to someone in your family who did not study science, and ask them to tell you back what you were trying to find out. If they cannot, the problem is your explanation, not their attention.

The follow ups, and what they are checking

What was your actual contribution

Be precise and be modest. If your supervisor designed the study and you ran the samples and did the analysis, say exactly that. Overstating your role in a project is the kind of thing that unravels badly under one more question, and understating it is easily corrected by the interviewer. Never claim authorship position or credit you do not have.

What would you do differently

This is a self awareness question wearing a methods costume. Give a real limitation, ideally one you noticed yourself partway through, and explain what you did about it at the time. Sample size is the answer everyone gives. Find a better one.

How does this relate to medicine

Resist the urge to claim your project makes you a better future doctor. It probably does not, directly. What it gave you is transferable: tolerance for ambiguity, comfort with being wrong in public, the habit of asking how confident anyone actually is in a finding. That last one is a real clinical skill and it is a much stronger answer than pretending your assay has bedside relevance.

Explain it as if I were a patient

Some stations do this deliberately, sometimes with an actor. Have a thirty second version ready with no numbers and no technical words, and check the person is following you rather than delivering it as a monologue.

If the project went badly

Plenty of honours and masters projects produce very little, through funding, timing, a difficult supervisor or a technique that never worked. That is not a weak answer, it is a resilience answer with unusually good detail attached. Describe what broke, what you tried, when you decided to change course, and how you handled the months where the work stopped rewarding you. Interviewers are far more interested in that than in a clean result.

Where it fits in the wider interview

Your research is one story, not your whole case. It works well for stations about failure, integrity, teamwork and communication, and poorly for anything about advocacy or empathy. Work through a broad range of MMI question types used across Australian programs and deliberately answer some of them without mentioning the project at all. Research heavy applicants return to it by reflex, and it starts to sound like the only thing you have done.

Time it out loud, because ninety seconds is shorter than it feels and research answers expand without you noticing. MasterMed's AI interviewer runs timed stations and marks you against a rubric, which will tell you quickly whether the explanation is landing or drifting. The first speaking station is free on the trial, no card, and the trial never converts by itself.

How much your research background is discussed at all depends on the program. Some structure part of the interview around your written application, others never mention it. An overview of how GEMSAS interviews are organised and a walkthrough of a typical circuit such as the Monash medicine interview will orient you, but formats change between cycles, so check each university's current admissions page.

Get it down to ninety seconds a stranger can repeat back, keep your contribution honest, and let the project be one good story rather than your entire identity in the room.