An internship interview is a gentler thing than a full job interview, and it is worth saying that plainly because most candidates walk in braced for the wrong fight. Nobody expects you to have run a team or shipped a product to a million users. What an internship interviewer actually wants to know is narrower: can you think clearly out loud, can you point to one real thing you have done, and can you pick up a specific skill fast enough to be useful in a few weeks. Because the bar is narrower, the questions are far more predictable than most candidates assume, and predictable questions are exactly the kind you can prepare for properly instead of hoping to improvise well.
The opening question is almost always some version of tell me about yourself, and here the content of your answer matters less than most people think. What actually gets judged is whether you can open with a clear line about who you are, move to one relevant thing you have done, and stop, all inside a minute, without wandering into your school days or a list of hobbies nobody asked about. An interviewer forms an opinion about how you organise information within the first thirty seconds of this answer, well before they have heard a single fact worth remembering, so structure is doing more work here than content.
Close behind it comes some version of why this company, or why this role, and this is the question where most freshers accidentally sound identical to everyone else who applied. "I want to learn and grow" and "your company has a great culture" are true of almost every company on earth, which means they tell the interviewer nothing about you specifically. One concrete, checkable reason beats three generic ones every time: a particular product you have actually used and have an opinion about, a specific problem the team is publicly known to be working on, a person whose work you have followed. The test is not whether your reason sounds impressive. It is whether it proves you actually looked at this company rather than pasting the same paragraph into every application you sent this week.
The project question is the real differentiator
Somewhere in most internship interviews, you will be asked to walk through a project, and this is the question that separates candidates far more sharply than anything else on the list, because it is the hardest one to fake convincingly and the easiest one to prepare for properly if you actually did the work.
The instinct most candidates follow is to describe everything about the project, every feature, every tool, every line on the resume bullet. Resist it. Pick one thing. Then explain a decision you made inside it and the reasoning behind that decision, and, if you can manage it, a mistake you caught partway through and how you caught it. A decision with reasoning proves you understood what you were building rather than following a tutorial to the end. A caught mistake proves you were actually paying attention while you built it, which is a much stronger signal than a clean, mistake-free story that sounds rehearsed because it probably is.
If the interviewer can open a link and see the graded version of what you are describing, this entire exchange changes shape. They stop having to take your account of the project on faith, and they can compare what you just told them against what actually happened, which is a comparison that works entirely in your favour if your project was genuinely yours.
A basics check on whatever you claimed
If your resume states a skill, expect it to be tested lightly rather than taken on trust. Put Python on your CV and a reasonable interviewer will ask you to read ten lines of it and say what they do, or write ten lines that solve something small. This is not meant to be a hard technical round, and it usually is not one. It exists purely to confirm the gap between what your resume claims and what you can actually do in front of someone is small enough not to worry about. The candidates who struggle here are almost never the ones who know too little. They are the ones who listed a skill they used once, briefly, months ago, and never reinforced.
Availability and the practical questions
Somewhere near the end come the logistics: when can you start, how many hours a week can you commit, is this remote or in office, do you have any exams or a semester schedule that will interrupt the internship partway through. These questions feel like an afterthought, but answering them vaguely is a real way to lose an offer that everything else in the interview earned you. Know your dates before you walk in. An interviewer choosing between two similar candidates will often default to the one whose availability caused them zero extra thinking.
The asymmetry almost nobody closes
Here is the pattern worth noticing across all of the above. Most candidates spend their preparation time on answers: rehearsing what they will say for each question, smoothing the delivery, timing the pauses. Almost none of them spend any preparation time on evidence: the thing an interviewer could actually check if they wanted to, rather than just listen to and take on faith.
That asymmetry is exactly where a graded, verifiable project changes the shape of the room. An interviewer who has to take your word for everything keeps asking questions, because asking is the only tool they have. An interviewer who can click a link and see the rubric, the score, and the actual work behind your answer stops interrogating and starts recruiting, because you have just handed them the one thing every interview is actually trying to extract: proof, rather than a claim about proof.
If you have no internship yet to point to, that is not the same problem it looks like from the outside. It means you need one real, gradeable piece of work you can defend in detail, not a longer list of things you have merely heard of. Read our guide on getting your first internship with zero prior experience for the fuller path, and treat the interview questions above as the checklist to prepare against once you have something real to bring into the room.
