Questions to Ask Interviewer for Internship
The day-to-day set. These are for working out what you would be doing between arriving and leaving each day: what the project is, how much of it is real work rather than shadowing, what you would be allowed to touch, and who checks it before it goes anywhere. Pay, return offers and timelines are deliberately left to Questions to Ask an Interviewer for an Internship.
The questions
Open any question for the note
What would I be working on in the first couple of weeks?
Why ask it
The honest answers range from a scoped project to shadowing until someone finds you something. Both exist; you only get to choose if you ask before accepting.
Is the internship built around one project, or would I be supporting ongoing work?
Why ask it
A defined project gives you something to talk about in future interviews. Support work often teaches more about how the place runs but leaves you with nothing to show, so it is worth knowing which you are signing up for.
Who would I report to day to day, and have they supervised interns before?
Why ask it
An internship is mostly determined by one person's attention. A first-time supervisor with a full workload is the most common reason an internship drifts.
Which parts of the job would I be doing without supervision by the end?
Why ask it
Sets the trajectory rather than the starting point. An internship where nothing is ever handed over completely tends to produce a summer of small tasks and no story to tell afterwards.
How much of the day goes on meetings, and how much on the work itself?
Why ask it
The ratio decides whether the project gets finished. If interns sit in every meeting the team holds, ask when they are expected to do the thing they were hired for.
How many interns would be on the team, and would we work together or separately?
Why ask it
A cohort gives you people to ask basic questions without embarrassment. Being the only intern means more access to real work and fewer places to hide when you are stuck.
Will I have access to the real systems and data, or is there a lot I cannot touch?
Why ask it
Access restrictions quietly define the internship. Interns without production or client access often end up on documentation and slide decks regardless of the original plan.
How much of the work is independent, and how much is shadowing?
Why ask it
Shadowing is useful for a week and dull for ten. The ratio, and when it shifts, tells you whether you will be producing anything by the end.
How often would I get feedback, and who from?
Why ask it
Interns are frequently left to guess how they are doing until a final review that is too late to act on. A scheduled weekly check-in is the single best predictor of a useful internship.
What does a strong intern do differently here from an average one?
Why ask it
Interviewers give practical answers to this: asking earlier when stuck, writing things down, following up. It also tells you what they have been disappointed by before.
What do interns here usually find hardest?
Why ask it
Answers about unclear instructions, waiting on other people, or the slow pace of approvals describe the real texture of the job better than any list of responsibilities.
Who should I go to when I am stuck and my supervisor is not around?
Why ask it
A named second person is a sign the team has thought about supporting you. No answer means your productive hours will depend on one person's calendar.
Is there a final presentation or deliverable at the end?
Why ask it
A closing deliverable gives your work an audience beyond your supervisor, and gives you a concrete artefact. It also tells you the internship is planned rather than improvised.
Would I be in team meetings, and how does the team communicate day to day?
Why ask it
Being in the standing meetings is what turns an internship into an apprenticeship. Interns kept out of them learn the tasks but not the reasoning.
Do interns get to see other parts of the business, and how does that get arranged?
Why ask it
Some places will set up a call with anyone you ask for; others discourage it. Knowing which tells you how much of your own learning you will have to organise.
What is the slowest part of this job, and how much of it would land on me?
Why ask it
Every role has waiting, cleaning up and chasing people. Asking directly is better than discovering in week three that the project depends on an approval nobody can hurry.
What would I be able to do at the end that I cannot do now?
Why ask it
Turns the internship into a concrete skill rather than a line on a CV. A specific answer means someone has thought about the summer; a vague one means you would be filling gaps.
What should I brush up on before day one, and what would you expect to teach me?
Why ask it
The split between the two halves is the useful part. A team that expects you to arrive already fluent in their whole stack has not budgeted any time to train you, and you will spend the first fortnight hiding gaps instead of asking.
If I were away for a day, what would stall?
Why ask it
A gentle way of finding out whether the work is real. If nothing would stall, the project is decorative, and you should ask what else you could pick up.
Which parts of my coursework would actually be useful here?
Why ask it
Tells you what to revise and, more usefully, how much of the job is nothing like a degree. Interviewers often name one tool or method that carries most of the weight.
Preparing for an internship interview
Practical guidance for the conversation itself
Before the interview
Find out what the team actually does
Read the team's product pages, recent announcements, or published work rather than the company's about page. You want one specific thing you can name, which is what separates you from candidates who researched the brand.
Decide what you want out of the summer
A named skill, a portfolio piece, a reference, or a return offer are different goals and lead to different questions. Choose two before the call so you know which answers matter.
Sort out your constraints in advance
Term dates, exam periods, notice on another job, and any credit requirements from your course. Bring these up as facts to work around, not apologies.
Reading the answers
- A supervisor who can describe your first two weeks in detail has planned for you. One who says it depends on what comes in has not.
- Ask what previous interns built. Concrete examples are the strongest evidence the programme is real work.
- If nobody can say who supports you when your supervisor is away, expect to lose days waiting.
- Watch for enthusiasm about exposure and networking with no mention of a project. That combination often means administrative work.
- Take the conversion number over the conversion policy every time.
Common pitfalls
Only asking what you will get
Balance the learning questions with one about what the team needs from you. Interviewers notice which side of that a candidate spends their questions on.
Avoiding the pay and hours question
Students often skip it out of politeness and find out the terms after accepting. Asking plainly is normal and gets a plain answer.
Assuming the posting is accurate
Internship listings are recycled year to year. Ask what changed since last summer, especially if the description reads like a full-time role.