Questions to Ask About an Internship
Questions for a recruiter, hiring manager, or former intern when you are deciding whether to take an internship: what you would actually work on, who would supervise you, how you would be judged, and what happens at the end of the term.
The questions
Open any question for the note
What would I be working on in my first two weeks?
Why ask it
A concrete answer means someone planned for your arrival. "We will find something for you" usually means an intern showing up before anyone decided what the work is, and a fortnight of shadowing while they figure it out.
Would I own a specific project, or help out across whatever the team needs?
Why ask it
Owning a defined piece of work gives you something to describe in your next interview. Answers built around helping wherever needed often produce a term of small errands that are hard to point at afterwards.
Who would I report to, and how often would we meet?
Why ask it
A manager who meets an intern weekly can unblock you before a week is lost; monthly check-ins mean a stalled project goes unnoticed for three weeks. Ask who covers for them during holidays, because summer internships collide with holiday season.
Is the internship paid, and are the hours fixed or flexible?
Why ask it
How an organization pays interns tells you how it values the work they do. Hedging on hours often means an expectation of unpaid overtime near a launch, which is worth knowing before you plan a summer course or a second job.
Are there other interns, and would we work together or separately?
Why ask it
A cohort gives you people to ask basic questions without embarrassment and a sense of what normal progress looks like. Being the only intern can mean unusual access to senior people, or it can mean nobody notices you are stuck.
Is the work in person, remote, or a mix, and can that change during the term?
Why ask it
Arrangements described loosely in interviews have a way of firming up after you have signed a lease. Ask what the expectation is in writing, especially if you would be relocating for the role.
What have past interns built that the team still uses?
Why ask it
This is the clearest evidence that internships here produce real output rather than practice work. If nobody can name a single thing, expect to spend the term on a report that gets read once.
What happened to last year's interns?
Why ask it
They know the answer, so watch how readily it comes. Naming people, where they went, and who returned suggests a program that stays in touch. Generalities usually mean few offers were made.
How do you decide who gets a return offer, and when is that decision made?
Why ask it
The timing matters as much as the criteria. If the decision depends on next year's headcount being approved, a strong internship may still end with nothing, and you will want to keep applying elsewhere in parallel.
What would a successful internship look like to you by the last week?
Why ask it
If they cannot describe an end state, there is nothing to evaluate you against and the final review comes down to impressions. A clear answer also gives you something to steer toward from week one.
How would I get feedback, and would I hear anything before the final review?
Why ask it
Feedback that arrives only at the end removes any chance to correct course while it still counts. Ask specifically whether there is a midpoint conversation, because that is where a struggling internship gets saved.
What tools and systems would I need to learn, and how long does access usually take?
Why ask it
Setup time eats short internships. If accounts, permissions, and a laptop routinely take two weeks, a ten-week term is really eight, and the answer tells you whether anyone has thought about that.
What do interns here usually struggle with in the first month?
Why ask it
An honest answer names something real: an unfamiliar codebase, a slow approval process, or the difficulty of asking for help. "Nothing, they all do great" means nobody has been paying close attention.
Who would I go to when I am stuck and my manager is unavailable?
Why ask it
You want a second name, ideally someone who sits nearby. A single point of contact who is often in meetings turns a small blocker into two lost days, which is a large fraction of a short term.
How much of the work would be independent, and how much alongside someone more experienced?
Why ask it
Both extremes go badly. Left entirely alone, interns produce work nobody wanted; supervised every minute, they learn nothing. Good answers describe pairing early and loosening once you have shipped something.
Would I get to see what other teams are doing, and how does that happen?
Why ask it
Exposure only occurs if someone schedules it. Look for named mechanisms, a rotation, a shadow day, an open demo, rather than an assurance that people here are friendly and happy to chat.
Is there a presentation or final deliverable expected at the end?
Why ask it
Where a final presentation exists, it is often what the wider team judges you on, and it is the only thing most of them will ever see. Knowing in week one lets you collect material as you go instead of reconstructing it in a panic.
What is the team working on right now, and where would my project fit into it?
Why ask it
Work connected to a current priority gets attention, reviews, and users. A side project that touches nothing anyone else cares about tends to be quietly abandoned the week after you leave.
What would you want me to have read or practiced before I start?
Why ask it
The reply doubles as a description of the real work. It also separates managers who have prepared for an intern from those who will be assembling a plan on your first morning.
What are the remaining steps in your process, and when should I expect to hear back?
Why ask it
A named date lets you manage other offers and gives you a legitimate reason to follow up. Pressure to commit combined with vagueness about their own timeline is worth noticing.
Choosing Between Internships
Practical guidance for the conversation itself
Match the question to the person
Recruiters know logistics
Pay, dates, hours, visa and housing support, and the steps left in the process are all things a recruiter can answer precisely. Asking them what your project would be usually produces a description copied from the job posting.
The hiring manager knows the work
Save the questions about the project, the supervision, the first two weeks, and the definition of success for whoever would actually manage you. Their fluency in answering is itself information about how much thought went into the role.
Former interns know the truth
One message to someone who did the internship last year is worth several interviews. Ask what surprised them, how long setup took, and whether they would do it again. People who have left the company answer most freely.
When to ask what
- Early interviews: what the work is, who you would work with, how the team is doing.
- Later interviews: supervision, feedback, what success looks like, return offers.
- After an offer: pay, hours, start date, equipment, and anything you want in writing.
- Any stage: what past interns built, which is the single most revealing question available to you.
- Never leave the last conversation without knowing the decision date.
Common pitfalls
Choosing on brand name alone
A recognizable employer with no plan for you is worse for your next application than a small team where you shipped something real. What you can describe having done matters more than the logo on the badge.
Accepting perks as an answer
Free lunch, social events, and merchandise are cheap to provide and tell you nothing about the work. When these dominate the pitch, ask again what you would be building.
Not asking about the return offer
Candidates avoid this question because it feels presumptuous. Programs designed as hiring pipelines expect it, and the answer changes how you plan the rest of your recruiting season.