Good Questions to Ask in an Internship Interview
Questions about the project rather than the company. Use these in the interview with the team you would join, when you want to know exactly what you would build or handle, who reviews it, what you hand over at the end, and what becomes of it if priorities move halfway through. Pay, dates and process questions are better asked earlier, on the screening call.
The questions
Open any question for the note
What would I be working on in the first week?
Why ask it
A team that has thought about interns can name a first task, usually something small and real. Vagueness in week one tends to mean two weeks of reading documentation while someone works out what to give you.
Is the project already scoped, or would I help shape it?
Why ask it
Both answers are workable, but they demand different things from you. A scoped project means you can start fast; an open one means you will need someone senior available in the first fortnight or you will drift.
How was this project chosen, and how long has it been waiting?
Why ask it
Work that has been on the list for a year is real but rarely urgent, which usually means gentle supervision. Work chosen last week may not be scoped at all.
Who would I ask when I get stuck at four on a Friday afternoon?
Why ask it
Deliberately specific, because the honest answer reveals whether help is a named person or a hope. If the only answer is your manager, ask what happens when that manager is travelling.
How long is the programme, and how much of it is onboarding?
Why ask it
Subtract onboarding from the total and you have the time you actually get to do something. A twelve-week programme with three weeks of setup is a nine-week project, and it should be scoped that way.
What does an intern's week look like: how much of it is meetings?
Why ask it
Interns are often either excluded from everything or invited to everything, and both cause problems. Ask which meetings you would be in and which you would be expected to skip.
How would you tell, halfway through, that I was doing well?
Why ask it
Forces the midpoint bar into words while you can still act on it. If the answer is entirely about attitude, ask what the work itself should look like by then.
What would I hand over at the end, and who uses it afterwards?
Why ask it
Work that gets used has a name and an owner after you leave. Work that does not is usually a prototype nobody asked for, which is still a learning experience but a weaker thing to describe later.
Do interns present their work, and who is in the room?
Why ask it
The audience tells you how seriously the programme is taken. A demo to your immediate team is normal; a session with people two levels up means the company treats interns as a hiring pipeline.
How much of my work would be reviewed before it goes anywhere?
Why ask it
Careful review is a feature, not a lack of trust: it is how you learn quickly. No review at all often means nobody has time for you, and your mistakes will surface publicly.
What kind of feedback do interns get, and how often?
Why ask it
Weekly and scheduled beats occasional and informal, because informal feedback in practice means feedback only when something goes wrong. Ask whether anything is written down, since that is what you can act on.
What would make you say at the end that the project succeeded?
Why ask it
Getting the bar stated out loud stops you guessing all summer. It also shows whether the target is realistic for the number of weeks you have.
What do interns most often get wrong in the first two weeks?
Why ask it
Easier for an interviewer to answer than a question about your own weaknesses, and the answer is directly usable. The most common ones are staying quiet too long and trying to look busy instead of asking.
Is there anything I could read or set up before I start?
Why ask it
Shows initiative without overpromising, and it gives you a real prep list. It also tells you which technologies in the job description are genuinely used day to day.
What is the riskiest part of this project, and what happens if it does not work?
Why ask it
Every real project has one. A team that can name it has thought the placement through, and you learn where you will need help early.
How does the team handle it when someone new breaks something?
Why ask it
This is a question about safety, and it matters more for an intern than anyone else. Listen for whether they describe a process, such as a rollback and a review, or a person being blamed.
Are the hours fixed, and how do they work around exams?
Why ask it
Worth asking plainly if the internship overlaps a term. Their tone when answering is a preview of how the team treats boundaries in general, which is useful information either way.
If the team's priorities move halfway through, what happens to my project?
Why ask it
Shifting roadmaps are the most common way internships get derailed. A considered answer means somebody has thought about protecting your work; a surprised one means they have not.
Would the project carry on after I leave, and who would take it?
Why ask it
Work with a named owner afterwards tends to get reviewed properly while you are there. Work with nobody waiting for it is often quietly dropped.
What should I have asked that I did not?
Why ask it
Works because interviewers know the thing candidates consistently fail to check, often about hours, location or the state of the project. Most people never ask, so the answer tends to be candid.
Using these in the interview
Practical guidance for the conversation itself
Choosing which to ask
Four questions, one from each area
You will get five to ten minutes at most. Take one about the work, one about who supports you, one about how you would be judged, and one about what happens afterwards. That covers the whole programme without sounding like a checklist.
Ask them where they fit, not all at the end
When the interviewer describes the team's current work, that is the moment to ask what an intern would pick up from it. A question that follows on from their own sentence gets a longer and more honest answer.
Prepare one follow-up for each
If they say interns present at the end, the follow-up is who is in the room. If they say you would have a mentor, the follow-up is how much time that person has each week. One layer down is where the real answer lives.
Write the answers down
If you end up choosing between offers, the notes on scope, review and conversion are what you will compare. Nobody remembers this accurately two weeks later.
Signs the internship has been planned properly
- They can name a first task, not just a first project area.
- There is a named mentor, and the interviewer knows roughly how much time that person has.
- Feedback is scheduled, with at least one midpoint conversation.
- They can describe what a past intern built and who uses it now.
- They have an answer for what happens if the roadmap changes.
- Warning sign: your project would be decided after you arrive, by someone not in this interview.
- Warning sign: nobody can describe how interns are evaluated, or evaluation happens only in the final week.
Questions to leave out
- Anything answered on the careers page or in the job posting. It reads as though you did not read either.
- Whether the internship is paid, if the posting already says so. If it does not, ask the recruiter rather than the hiring manager.
- Asking how much overtime is expected in a complaining tone. Ask instead how the team handles busy periods.
- Asking whether they have concerns about you, which puts the interviewer on the spot. Ask whether they would like you to expand on anything in your application.
- Asking how you did. Ask what the next steps are and when to expect to hear, then send a short note the same day.