Intern interview questions for students with no work history

On 7 August 2026 we switched on an option that lets our AI interview ask each candidate three questions built from their own resume, such as how they actually implemented a project they listed, scored on a rubric written for those questions. The obvious use is experienced hires with long work histories. I think it matters even more for students. An intern’s resume is almost entirely projects, coursework and college activities, and asking “how did you build the thing you put on page one?” is the fastest way to find out whether the student did it.

That is the core of a good set of intern interview questions. Interns have no work history to probe, so most interviewers fall back on “tell me about yourself” and “what are your strengths”, which every placement cell trains students to answer. This guide is for the recruiter or team lead who has to pick 20 interns from 400 applications. It covers the project deep-dive that does most of the work, questions on learning, feedback and reliability, role-specific additions and a scoring guide that does not depend on the college name. If you are also converting interns to full-time roles, we wrote about screening interns for conversion separately.

What should an intern interview find out?

An intern interview should find out three things: whether the student really did the work on their resume, how quickly they learn something new, and whether they will show up and finish what they start. Subject knowledge matters less than people think, because a good internship teaches the subject. Ownership, learning speed and reliability are hard to teach in ten weeks.

The order matters. Start with the project, because it is the only evidence you have and it tells you how deep the rest of the interview needs to go. Learning and feedback come next. Practical checks (dates, location, stipend) come last, so a student who is nervous at the start has time to settle before you judge how they talk.

Why the usual intern questions fail

“Tell me about yourself”, “why do you want to intern here” and “where do you see yourself in five years” are fine as warm-ups, but they do not separate candidates. Placement cells coach every student on them, many students now draft answers with AI tools, and the answers converge on the same three sentences. Grades do not separate candidates much either: a 7.8 and an 8.4 CGPA from different universities measure different things.

What does separate students is depth on something specific. Two students can list the same final-year project. One can tell you why they chose that database, what broke two weeks before submission and what they would change. The other can tell you what the project does. That difference shows up within three follow-up questions.

Ask about a project they built, then go three levels down

Pick one item from the resume, the one the student seems proudest of, and stay on it for ten minutes.

1. “Tell me about this project in two minutes, as if I had never heard of it.” You learn whether they can explain clearly before you test depth.
2. “Which part of it did you personally do? What did your teammates do?” Group projects are normal. A student who says “we” for everything and cannot name their own part is a flag.
3. “What was the hardest problem you hit, and how did you solve it?” Listen for a specific problem and a specific fix, not “we faced many challenges.”
4. “If you started again tomorrow, what would you do differently?” Students who really built something always have an answer.
5. “How did you know it worked?” Testing, a demo to a professor, real users, a result. This one catches projects that were copied from a tutorial.

Follow-ups are where the interview happens. When an answer is smooth and general, ask “can you give me an example of that?” or “what did you try first that did not work?” Real memories have rough edges. Rehearsed summaries do not.

For a non-technical student, the same structure works on a college fest, a club, a family business or a part-time job: what was your part, what went wrong, what would you change.

Questions on learning and feedback

Interns are hired to learn, so test learning directly.

• “Tell me about something you taught yourself in the last six months that was not in your syllabus. How did you go about it?” A specific skill and a specific method (a course, a project, a person they asked) beats “I am a quick learner.”
• “Tell me about a time a professor, manager or senior told you your work was not good enough. What did you do next?” You want a student who changed something, not one who argued or went quiet.
• “You are given a task on day two and you do not understand it. Your manager is in meetings all day. What do you do?” Good answers try first, write down specific questions and ask a teammate. Weak answers either wait silently or guess and submit.

The last one is a situational question, and it works well for students because it needs no experience to answer. More on writing these well is in our guide to situational interview questions.

Questions on reliability and working with others

An intern who is brilliant and unreliable costs the host team more time than they save.

• “Tell me about a deadline you nearly missed. What happened?” Honest students have one. “I have never missed a deadline” is the weakest answer.
• “In a group project, what did you do when a teammate was not contributing?” Listen for a conversation and a fair split of work, not a complaint about the teammate.
• “What else will you be doing during the internship: exams, another internship, a course?” Ask plainly. It is not a disqualifier; it tells you which weeks will be thin.

Questions for specific intern roles

Add two or three questions for the function the intern will join.

Keep the role question short. Its job is to show how the student thinks, not to test knowledge they have not been taught yet.

How to score interns with no work history

Score each area 0 to 3 right after the interview and write one line of what the student said next to each score. Agree the anchors with the host team before the first interview. Google’s guide to its own hiring describes the same habit: every candidate is graded on an identical scale, with documented examples of answers at each level.

Do not score the college or the grades here. A student from a lesser-known college who scores 3 on ownership has shown you more than a 9.0 CGPA with a 1. Reading a fresher’s resume fairly before the interview is its own problem, and we covered it in how resume matching handles freshers.

Why bother this much for an internship? Because a good intern programme is a hiring pipeline. NACE’s 2026 internship survey found that 63.1 percent of 2024-25 interns were converted to full-time hires, and 88.3 percent of those offered accepted. Those are US employers, but the logic carries over: the intern you pick in this interview is often the graduate you hire next year.

When 400 students apply for 20 internship seats

The method above takes 20 minutes a student with a team lead in the room. For 400 applications that is more than 130 hours of interviewing, during the same weeks the team is running its own projects. So most teams shortlist by college and CGPA instead, and the project deep-dive happens only for the few who were already favoured.

The first round can run the same method at that scale. In HireQwik, a job can be set so the voice interview asks each student questions built from their own resume, which is the project deep-dive above, and scores the answers against level descriptions the host team writes. The student takes the 10 to 20 minute interview from their phone at a time they choose. That matters for students: in our hiring data from India, 9 PM was the most popular interview hour when candidates booked their own slot, and students interview after class. The team lead receives a short list with a verdict, the reasons and the recording, and spends their 20 minutes on the role-specific round with students who have already shown they did their own work. HR still makes every decision.

The questions stay the same either way. The difference is whether every one of the 400 students gets asked them, or only the ones from colleges you already know. If you run campus drives at this volume, our campus hiring page shows how the first round fits around them.