You spent months on your project. You read the papers, cleaned the data, and rewrote your discussion section three times. Then an interviewer leans in and asks, "So what exactly did you do?" and suddenly the words won't come, because you have never had to say it out loud in plain English.
That moment matters more than it used to. Colleges are paying closer attention to student research, and some now ask applicants to walk through their work in conversation. If you did the work, you already have what you need. You just have to practice explaining it in about three minutes to someone outside your field who wants to know which parts were yours.
Below are the 12 questions worth practicing and how to answer them with confidence.
Key takeaways:
Colleges are asking students to talk through their research, and at least one highly selective school uses video interviews to check research claims.
Prepare two versions of your story: a short one that takes about two minutes, and a deeper one for when the interviewer starts asking how and why.
Be precise about your role and your mentor's. Clear credit makes your story more believable.
Why are colleges asking students to talk through their research?
Research now shows up on a lot of competitive applications, and admissions offices have noticed. In August 2026, the Wall Street Journal reported that Caltech runs a four person review team that checks the file of every admitted student. Among other steps, the team uses a video interview program to probe applicants' research claims. Caltech admitted fewer than 4% of its 11,400 applicants for the incoming class, so it has every reason to look closely.
Science competitions are moving in the same direction. Under this season's ISEF rules, every project needs a Student Support Disclosure Form (Form 2A). You list each adult who helped, describe what each person contributed, and sign a statement that you have not left out pertinent information.
None of this should worry you. It simply means the people reading your file want to hear you explain the work in your own words. If the work is yours, that conversation can become the strongest part of your interview. (If you're using one project for both competitions and applications, read How One Research Project Can Help You Win Both Competitions and College Admissions.)
How do you explain your project in two minutes?
Build a short version you can say without notes. It should contain five parts in this order:
The question. What were you trying to find out?
Why it matters. Who would care about the answer, and why?
What you did. Your method in plain terms.
What you found. Your main result.
What's next. The question your result opened up, or what you plan next.
Here's what the core of that sounds like:
"I wanted to know why some neighborhoods in my city flood more than others when they get the same rain. That matters because the city is deciding where to spend its drainage budget. I mapped ten years of flood reports against pavement and soil data, and found that the share of paved ground predicted flooding better than elevation did. Next, I'd like to test whether small rain gardens change that pattern."
That takes about 30 seconds. Add a detail or two to each part and you're at two minutes, which is plenty for a first answer.
Keep a deeper version ready too. Once the interviewer is curious, they'll ask how, why, and what you'd change. Here’s a quick test: explain your project to someone outside your field, then ask them to repeat your research question back to you. If they can, your short version works.
Which questions should you practice?
These 12 questions cover what interviewers ask most when a student brings up research. Each one is testing something specific, so knowing the purpose helps you aim your answer.
| # | Question | What it tests |
|---|---|---|
| 1 | Can you describe your project in a few sentences? | Whether you see the big picture |
| 2 | How did you come up with this question? | Curiosity and ownership of the idea |
| 3 | What did you personally do, start to finish? | Your role, stated plainly |
| 4 | Why did you choose this method? | Whether you understand the tradeoffs |
| 5 | What other approaches did you consider? | Depth of thinking |
| 6 | What was the hardest part? | Real, firsthand experience with the work |
| 7 | What went wrong, and how did you handle it? | Problem solving under pressure |
| 8 | What did your mentor contribute? | Honesty about the support you had |
| 9 | What do your results show, and what can't they show? | Whether you know the limits of your data |
| 10 | What would you change if you did it again? | Reflection and growth |
| 11 | How does your work connect to what others have found? | Familiarity with your field |
| 12 | What would you want to study next, and could you do it here? | Direction and fit with the college |
Don't memorize scripts. Know your answers well enough that you could say them a little differently each time. Interviewers can hear a recited answer, and it makes them dig harder.
How do you talk about what went wrong?
Talk about it openly, because setbacks are some of the best evidence that you did the work. Use a simple shape like this: what happened, what you tried, and what you learned. For example,
"My first model fit the training data perfectly and fell apart on new data, so I cut the number of variables from 40 to 8 and tested it on a set it had never seen."
If your project didn't produce the result you hoped for, say so plainly. A surprising result explained well shows more maturity than an inflated claim, and it gives the interviewer something real to ask about.
How do you describe your mentor's role honestly?
Most strong student projects have a mentor, and admissions officers expect that. What they want to understand is where the mentor's help ended and your work began. A vague answer like "we worked on it together" raises more questions than it settles.
Before your interview, jot down three short lists:
What your mentor suggested. A reading list, a dataset to look at, a method worth learning.
What you decided. Your research question, which variables to keep, how to read the results.
What you did with their feedback. The analysis you redid, the section you rewrote, the test you added.
Then answer in that order. For example:
"My mentor pointed me to a public weather dataset. I chose which years and variables to use, wrote the code, and ran the analysis. When I showed her my first results, she asked whether I'd accounted for seasonal patterns. I hadn't, so I went back and rebuilt the model."
That answer gives your mentor real credit and still makes it obvious which decisions were yours. If you entered a science fair, your Form 2A already describes each adult's contribution, so make sure your interview answer matches it.
How can you practice?
Start a few weeks before your first interview so the answers feel natural by the time it counts.
Do a mock interview with your mentor. They know your project better than anyone and can spot where your explanation gets thin. Ask them to push on your methods and play the skeptic.
Explain it to a family member. A parent, grandparent, or younger sibling is a great stand in for an alumni interviewer from another field. Notice the exact sentence where they lose the thread, and fix that sentence.
Record yourself. Answer three questions from the table on your phone and play them back. Listen for filler words, jargon, and places where you trail off.
Watch the clock. Keep your short version under two minutes, and most other answers between 30 seconds and a minute.
If you want a faculty member's view on what good student research looks like, read A University of Michigan Professor Answers Your Questions About Research. For the written side of your application, see How to Write About Research in College Applications, since your essay and your interview should tell the same story.
FAQ
Will my interviewer understand my research topic?
Probably not in detail. Many alumni interviewers work in unrelated fields, and admissions officers read applications across every subject. Plan for a smart listener with no background in your area. If your interviewer turns out to be an expert, they'll ask for more, and your deeper version will be ready.
What if I can't remember a detail about my methods?
Say so honestly, then share what you do remember. Guessing a precise number is riskier than admitting you'd need to check. Reread your paper the week before your interview so the details are fresh.
Should I bring my paper or poster to an alumni interview?
Usually no. Alumni interviews are conversations, and handing over a document can pull the focus away from you. If the interviewer asks to see your work, offer to send a link afterward. Check each college's interview instructions, since a few have their own guidance.
How do I explain a project that didn't get the result I expected?
Walk through what you expected, what you found instead, and why you think the gap exists. Unexpected results happen in real research all the time. Explaining yours clearly shows you understand the science behind your project.
How long should my answer be?
About two minutes for your project overview. For most other questions, aim for 30 seconds to a minute, then let the interviewer steer. If they want more, they'll ask.
Ready to own the conversation?
Scholar Launch students practice explaining their work with their Faculty Advisor before they ever face an interviewer. Want to learn how that works? Talk with our team.
