Internship interview advice almost always arrives as a list of questions with model answers attached, which is the one format that cannot help you. Interviewers reuse those lists too. A memorized answer survives the first question and falls apart on the follow-up, and in an internship loop the follow-up is where the decision actually gets made.
There's a more useful thing to know, and it's measurable. Internship postings ask for something different from entry-level full-time postings, and the difference is specific enough to prep against.
Internship postings ask for something entry-level postings don't
We looked at every active internship posting in Four-Leaf's job index, 2,341 of them with full descriptions, and compared the language against a random sample of 8,000 non-internship postings. Snapshot taken August 2026.
Two things separate them, and they're not the two you'd guess.
Learning language is the first. Words like learn, curious, and curiosity appear in 78.9 percent of internship postings, against 45.9 percent of the comparison set. Stated experience requirements are the second, in the other direction. Only 1.5 percent of internship postings name a years-of-experience requirement, against 25.4 percent of everything else.
What's more interesting is what didn't move. Collaboration and teamwork language shows up in 89.8 percent of internship postings and 91.8 percent of the rest. Communication sits at 69.1 percent against 66.1 percent. Problem-solving language appears in 20.0 percent against 21.9 percent. Those three are effectively identical across both groups.
So the popular framing, that internships are a softer version of a real job interview where they mostly check whether you're pleasant to work with, is wrong on the evidence. Employers ask interns for the same collaboration and communication they ask everyone for. What they drop is the experience requirement, and what they add is an explicit demand that you learn fast.
That's the rubric. An intern loop is scoring how quickly you absorb correction and how clearly you reason when you're past the edge of what you know. Every question below is a different instrument for measuring one of those two things.
One caveat on the numbers. This measures the language employers write into postings, which is what they say they want. It's a strong signal about the rubric and it isn't the rubric itself, since no company publishes its intern scorecard. Treat it as the shape of the thing.
The behavioral questions and what each one screens for
"Tell me about yourself." Screens for whether you can select. You have four years of material and ninety seconds, and the interviewer is watching what you choose to include. A strong answer moves in one direction, usually toward the work the internship involves, and leaves out the parts that don't serve it. The tell that separates a real answer from a rehearsed one is whether it changes at all between companies. If it doesn't, you're reciting.
"Tell me about a time you worked on a team." Screens for whether you can describe other people accurately. Almost every candidate says the team went well. The ones who read as credible name what a specific teammate was better at than they were. That's a small thing that's hard to fake and it maps directly onto the 89.8 percent of postings asking for collaboration.
"Tell me about a time you got feedback you disagreed with." This is the coachability question and it's the highest-signal item in most intern loops. It's also the one where candidates most often perform the wrong virtue. The version that lands describes the disagreement honestly, then what you did with the feedback anyway, and then whether you turned out to be right. Candidates who claim they immediately saw the wisdom of the feedback usually sound like they're managing the interviewer rather than answering.
"Why this company?" Screens for whether you did fifteen minutes of work. There's no clever answer here and there doesn't need to be one. Naming something specific the team shipped, and why it interested you, clears the bar that most answers miss.
"Tell me about a project that didn't work." Screens for whether you can hold a failure without either collapsing into it or explaining it away. The strong version spends most of its time on the decision that caused the problem rather than on the recovery. Recoveries are interchangeable. Decisions are diagnostic.
The technical questions where reasoning matters more than the answer
Technical intern screens are calibrated to coursework. The interviewer usually knows the problem is solvable with what you learned in a second-year class, which frees them to watch something else entirely: what you do in the first ninety seconds.
Data structure and complexity questions. Screens for vocabulary and honesty about tradeoffs. Being able to say why you reached for a hash map instead of a list, in plain language, does more than arriving at the optimal solution silently. Our data structures interview questions guide covers the same signal mapping for full-time loops, where the bar assumes you can already narrate.
A small live coding problem. Screens for whether you talk before you type. In a full-time loop, narrating your approach is table stakes. In an intern loop it's the entire point, because the interviewer is trying to find out whether you'll be teachable on real work where nobody can see your screen.
"Walk me through how you'd debug this." Screens for method. There's a strong version that starts by reproducing the problem and a weak version that starts by guessing at causes. Interviewers can tell the difference in one sentence.
A question drawn from a language on your resume. Screens for whether your resume is accurate. If you listed Python, expect something at the level of a standard Python screen, scaled down. The failure mode is listing five languages and being shaky in four. Two you can defend beats five you listed.
The project and coursework questions that separate two identical resumes
Two intern candidates from the same program with the same GPA look identical on paper. Project questions are how interviewers break the tie, and they're the rounds students under-prepare most.
"Walk me through this project." Screens for ownership. Group coursework makes this genuinely hard, and interviewers know it. The answer that works says plainly which parts you built and which parts you didn't. Candidates who narrate the whole project in the first person get found out on the next question, every time.
"Why did you build it that way?" Screens for whether the decisions were yours. Any answer that amounts to the tutorial doing it that way is a real answer and a costly one. Better to name a constraint you were working under, even a boring one like a deadline.
"What would you do differently now?" Screens for growth since the project shipped. A candidate who can't name anything either hasn't learned since or isn't looking. This is the question where the 78.9 percent learning language in intern postings shows up most directly.
"What's something you learned outside of class?" Screens for self-direction. It doesn't need to be impressive and it definitely doesn't need to be technical. It needs to be true and specific enough that a follow-up question doesn't dead-end.
What to do when you genuinely don't know
This deserves its own section because it's the moment intern loops are built around and the moment candidates handle worst.
Say you don't know. Then say what you'd do about it. Name the first place you'd look, the person you'd ask, or the smaller version of the problem you'd try first. That answer reads as honest and trainable, which is precisely the trait the postings data says employers are screening for.
Guessing with confidence is the failure. It's not that the guess is wrong. It's that an intern who guesses confidently in a low-stakes interview will guess confidently on production work where nobody's checking, and that's the specific risk a supervisor is trying to price. The candidate who says "I don't know, here's how I'd find out" is describing exactly how their first three months would go, and it's the version a manager wants.
Questions worth asking at the end of an intern loop
Interns get a different set than full-time candidates, because the things worth knowing are different.
Ask what an intern did last summer that made the team want to keep them. It's specific, it's flattering without being obvious, and the answer tells you the actual scoring criteria for the internship itself.
Ask what the first two weeks look like. Onboarding quality varies enormously between intern programs and it's the single biggest predictor of whether you'll ship anything.
Ask who you'd be paired with day to day, and whether they've mentored an intern before. A team with no mentoring habit is a summer of sitting on your hands regardless of the brand on the door.
Skip the questions about company culture and values. They produce the same answer at every company, and our fuller guide on questions to ask at the end of an interview covers the ones that don't.
A one-week prep plan
- Pick three projects and write down what you personally did on each. Not what the team did. Your parts, in a sentence each. This one exercise fixes the ownership problem that sinks most project rounds.
- For each project, write the decision you'd change and why. That's your answer to the growth question, and it's the hardest one to improvise.
- Practice the feedback story out loud, twice. Out loud specifically. Written answers to the coachability question read fine on the page and come out defensive when spoken, and you can't hear that until you say it.
- Do one timed technical problem while narrating. Record it. The goal isn't the solution, it's checking whether you go silent when the problem gets hard. Most people do, and you can only fix what you've heard.
- Spend fifteen minutes on the company. Find one shipped thing you can name. That's the whole assignment.
- Write your three closing questions on paper. Bring the paper. Nobody has ever been marked down for it.
If you want the reps rather than the reading, voice mock interviews run the same questions with follow-ups, which is the part a question list can't simulate.
Where this leaves you
The whole intern rubric compresses into one idea. Nobody expects you to have done the job. They expect to find out how fast you'd learn it, and every question in the loop is a different way of asking that.
Which means the prep that pays is narrow. Three projects you can discuss from any angle, one honest story about being corrected, and the discipline to say you don't know before you say anything else. Candidates who can do those three things clear intern loops with a thinner resume than the person who memorized forty answers.