Internship Interview Questions to Ask Candidates: 16 Structured Questions

Ask intern candidates about how they learn, what they have owned, and how they work with other people, because coursework, projects and part-time jobs are the whole evidence base a student has. Skip the five-years-of-experience questions entirely. A strong internship screen is 20 to 30 minutes, uses the same six to eight questions for every applicant to a req, and scores each answer against anchored levels written before anyone applied.

Most internship interviews are improvised. Whoever is free that afternoon takes the call, asks about the resume, chats about a class the student mentioned, and writes "seems sharp" in a doc. Multiply that by a hundred candidates across a fall cycle and you have a hundred incomparable conversations, which is worse than useless when you have to rank a class and pick fifteen.

The fix is not to make the questions harder. It is to ask the same job-relevant questions of everyone and to know in advance what a good answer sounds like. Below are the questions worth asking, the ones to cut, and how to score answers from people whose longest professional engagement lasted a summer.

What should you ask an intern candidate?

Ask for specific past behavior in the contexts a student actually has: classes, group projects, campus organizations, part-time work, side projects, sports, caregiving. The pattern that works is a concrete prompt ("tell me about a time you...") followed by a probe for what they personally did, because group projects are where students most often describe the team's work as their own without meaning to mislead.

Cap the set at six to eight questions for a 25 minute screen. More than that and you get shorter answers to every question, which is the opposite of what you want. Pick from the groups below based on what the internship actually requires.

Learning speed and coachability

• Tell me about something you had to learn quickly, outside of a class. How did you go about it?
• Describe a time you got feedback you disagreed with. What did you do?
• What is something you were bad at six months ago and are better at now?
• Walk me through a project that did not work out. What would you do differently?

These four carry more weight than anything else in an internship screen. You are hiring someone for ten to twelve weeks, and the difference between an intern who contributes by week three and one who never quite gets going is almost entirely how fast they absorb correction. The failure question is the most informative of the set: candidates who can describe a specific mistake and what they changed are describing a skill, while candidates who reach for "I'm a perfectionist" are describing an interview they rehearsed.

Ownership and initiative

• Tell me about something you started that nobody asked you to start.
• Describe a time you were given a vague assignment. How did you decide what to do first?
• What is a project you kept working on after the grade was in, or after you were done with the job?

Ambiguity is the shock most interns hit in week one. School gives you a rubric, a deadline and a defined deliverable; a real team gives you a Slack message that says "can you look into this?" The middle question above predicts that transition better than any credential does, and it is answerable by a student who has never held a job.

Working with other people

• Tell me about a group project where the work was not divided evenly. What did you do?
• Describe a time you had to explain something technical to someone who did not have your background.
• When you are stuck and your manager is unavailable for a few hours, what do you do?

That last one is worth asking every intern candidate for every role. The single most common intern failure mode is sitting silently on a blocker for two days because asking felt like admitting they could not do it. The answer you want describes a sequence: try a couple of things, timebox it, write down what was tried, then ask. The answer that should concern you is "I would keep trying until I figured it out."

Role-specific evidence

• Walk me through something you built, wrote, analyzed or organized that you are proud of. What was the hardest decision in it?
• What did you choose not to do in that project, and why?

Two questions do most of the role-specific work at intern level. Asking for the hardest decision separates people who did the thing from people who watched it get done, because only the person who made the tradeoff can describe the option they rejected. Keep the artifact broad: a research paper, a club budget, a data analysis for a class, a mod for a game, all of these are scorable.

Logistics, asked identically of everyone

• What is your expected graduation date?
• Are you legally authorized to work in the United States, and will you require sponsorship now or in the future?
• What are your dates of availability for the internship period?

These are ordinary business questions when every candidate for a req is asked them the same way, in the same position in the interview, with the answer recorded. They become a legal problem when they are asked selectively, which is exactly what happens in improvised interviews where an interviewer asks the question only of candidates whose name or accent prompted the thought.

What should you not ask an intern candidate?

Age, or anything that backs into it. This is the trap specific to campus hiring: interviewers who would never ask a career hire their age will cheerfully ask a student what year they were born, when they finished high school, or how old they were when they started coding. Ask for the expected graduation date, which is a legitimate business need, and stop there.

Also off the list, for the same reasons they are off the list for any candidate:

• Family, marital or pregnancy status, including friendly-sounding versions like whether they plan to stay local after graduation because of a partner.
• Where they are from or what their first language is. If the job needs a language, ask about proficiency in that specific language.
• Financial circumstances, including whether they have a car, whether they are on financial aid, or how they are paying for school. If reliable transport is a genuine requirement, ask whether they can meet the schedule.
• Disability or health, including indirect routes like asking about a gap in their studies. Ask instead whether they can perform the essential functions with or without reasonable accommodation.
• School prestige as a scored criterion. Not illegal, but it is a proxy for family income far more than for capability, and it is the fastest way to make a campus program look homogeneous.

One more that is specific to interns: do not ask whether they would be willing to work unpaid, or treat willingness to do so as a positive signal. Under the Department of Labor's primary beneficiary test, whether an intern is an employee entitled to minimum wage turns on who benefits most from the arrangement, and a candidate volunteering to work for free does not change that analysis. If the work you need done is really a defined short-term project with a deliverable rather than a learning role, that is a signal you want a paid contractor, and a vetted freelancer on a fixed scope is usually both cheaper and more legally straightforward than an internship built around production work.

How do you score intern answers when nobody has work experience?

By scoring the structure of the answer rather than the impressiveness of the setting. A student describing how they rescued a failing group project for a 300 level history seminar can demonstrate exactly the same competencies as someone describing a product launch, and if your rubric only recognizes the second one you are scoring access to opportunity.

Write three anchored levels per criterion before the cycle opens. For a criterion like "handles ambiguity":

• Level 1: Describes waiting for instructions, or gives a general answer with no specific instance.
• Level 2: Gives a specific instance, describes asking a clarifying question or picking a starting point.
• Level 3: Specific instance, describes how they narrowed the problem, what they decided to do first and why, and what they checked before going further.

None of those levels mention confidence, polish or enthusiasm, which is deliberate. Those three are where interviewer bias concentrates in student interviews, because a 20 year old's poise mostly measures how many adults they grew up talking to. Score what the answer says. Our interview scorecard template has a fuller structure you can copy, and candidate interview scoring explains how anchored levels stay comparable across a large pool.

How long should an internship interview be?

Twenty to thirty minutes for the first round, and one round before the hiring manager conversation. Students are interviewing with eight employers in the same three weeks, and a 60 minute screen for a twelve week internship reads as a company that does not value their time. Drop-off climbs sharply past the half hour mark.

Keep the structure tight: two minutes of context on the role, six to eight questions with follow-ups, five minutes for their questions, and a clear statement of what happens next and by when. That last part costs nothing and is the single biggest driver of whether strong candidates stay engaged while you finish screening the rest of the pool.

How do you screen hundreds of intern applicants in a few weeks?

This is the real constraint in campus hiring, and it is why so many programs end up back at GPA cutoffs despite knowing better. A fall cycle can bring two thousand applications against a campus team of three, and at 25 minutes each a full structured screen is roughly 830 recruiter hours. Nobody has that, so the screen gets cut instead of the questions getting better.

There are three honest ways out. Narrow the pipeline with a genuine job requirement rather than a proxy, which helps but rarely enough. Add temporary interviewer capacity from the wider team, which works if you train them on the same rubric and accept the consistency cost. Or remove the per-candidate hour entirely by having an AI interview agent conduct the structured first round, so every applicant answers the same questions on their own schedule and your recruiters open a ranked shortlist with transcripts instead of a queue of resumes. That last approach is what our campus recruiting software page covers in detail, including how it fits alongside the sourcing and career fair tools you already run.

Whichever route you take, the compliance duties travel with the decision, not the tool. If the role sits in New York City, which a large share of analyst and engineering intern classes do, Local Law 144 requires an independent bias audit within the prior 12 months, a published summary and 10 business days of candidate notice before an automated tool is used. Illinois requires notice, explanation and consent for AI-analyzed video interviews. Our guide to AI hiring compliance sets out what each US rule asks of the employer.

What questions will intern candidates ask you?

Expect these, and have real answers ready, because students compare notes and vague answers travel fast on campus:

• What will I actually work on? Name a project. "Shadowing" is a red flag to good candidates.
• Is there a path to a full-time offer, and what percentage convert? If you track it, share the number. If you do not, say so rather than implying one.
• Who will I report to, and how often will we meet?
• Is the internship paid, and what is the rate? In a growing number of states and cities, the posted range is legally required on the job posting anyway.
• Is it in person, hybrid or remote, and for which weeks?

The conversion rate question is the one candidates weigh most heavily and the one employers most often fumble. A specific, honest number, even a modest one, does more for your offer acceptance rate than any amount of enthusiasm about company culture.

Putting it together

Pick six to eight questions from the groups above, weighted toward learning speed and ownership. Write three anchored levels for each before applications open. Ask every candidate for the req the same set in the same order, including the logistics questions. Record the answers, score against the levels, and rank on the scores rather than on who you remember liking.

None of that is complicated. The reason it does not happen in most campus programs is arithmetic: structured screening costs an hour of human time per candidate, and campus volume arrives in a three week spike. Solve the arithmetic and the quality problem mostly solves itself. If you are building the question set now, our pre-screening interview questions guide covers the general first-round version, and first round interview screening explains how the round fits into the rest of the process.