Intern Interview Questions (2026) and How to Answer
By FindAJobAI team Updated How we wrote this page
Internship interviews rarely expect deep work experience. Instead, interviewers probe why you chose this field, how you learn new things, how you handle group projects or coursework under pressure, and whether you'll be reliable and curious on the job. Many include a simple technical or problem-solving question suited to your level.
Interviewers want genuine interest, evidence you can learn quickly, and signs you'll show up, ask questions and follow through.
Below: 30 questions with what each one really asks and an answer outline, full sample answers to the 10 most asked, red flags to avoid and a 7-day plan.
Answering with STAR
Tell each story in four steps: the situation in a sentence, your task, the actions you took (most of the answer) and the result, with a number if you have one. Aim for about two minutes; the outlines show what to include, the details must be yours.
Behavioural questions (1–10)
How you've handled real situations. Answer each with one true story, in STAR order.
1.Tell me about a group project where not everyone contributed equally.
What they're really asking: Can you handle an unequal team without just complaining or doing everyone's work?
Answer outline (STAR)
- SituationA class project or club activity where one or two people did little.
- TaskGet the work done without resentment building up.
- ActionRaised it directly but calmly with the group, split tasks with clear deadlines, and followed up midway.
- ResultThe project was finished on time, and you learned to assign specific, visible tasks earlier next time.
Full sample answer (fictional example)
In a senior capstone project, two of five group members barely showed up to meetings or submitted their parts late. Rather than just absorbing the extra work quietly, I called a short meeting and laid out exactly what was left and who was doing what, with specific deadlines two days before the real one. I also offered to help if someone was stuck rather than just assuming they didn't care. One person stepped up once given a clear, small task; the other still lagged, so I reassigned their piece early enough to cover it. We submitted on time with a solid grade, and I learned to assign specific tasks earlier instead of leaving work open-ended.
2.Tell me about a time you had to learn something completely new in a short amount of time.
What they're really asking: Will you pick things up quickly on the job without much hand-holding?
Answer outline (STAR)
- SituationA new software tool, concept or assignment with little lead time.
- TaskGet competent enough to contribute, fast.
- ActionFound a tutorial or documentation, practiced on a small example, and asked a classmate or professor one specific question.
- ResultYou submitted the assignment on time, and kept the resource for later.
Full sample answer (fictional example)
For a marketing class project, I had to build a basic dashboard in a tool I'd never used, with about four days before the presentation. I found the tool's own tutorial videos first and rebuilt a sample dashboard just to get familiar with the interface. When I got stuck on connecting a data source, I asked a classmate who'd used it before, with one specific question rather than asking them to explain the whole tool. I finished a working dashboard the night before, practiced the walkthrough twice, and the presentation went smoothly. I still have my notes from that week saved for the next time I need a new tool fast.
3.Tell me about a time you made a mistake on an assignment or project.
What they're really asking: Can you own an error instead of hiding it or blaming something else?
Answer outline (STAR)
- SituationA wrong assumption, missed requirement or late submission.
- TaskFix what you could, and learn from it.
- ActionTold the professor or team lead as soon as you noticed, explained what happened, and proposed a fix.
- ResultYou recovered some credit or trust, and changed your process to catch it earlier next time.
Full sample answer (fictional example)
I misread a requirement on a statistics project and analyzed the wrong variable for most of the assignment, only noticing two days before it was due. I told my professor as soon as I realized, explained exactly what I'd misunderstood, and asked if a short extension was possible given how late I'd caught it. She gave me one extra day. I redid the analysis correctly, double-checked it against the assignment sheet line by line this time, and submitted it a day late for a small penalty instead of submitting wrong work on time. Since then I reread requirements a second time before starting, specifically looking for anything I might have skimmed.
4.Tell me about a time you balanced schoolwork, a job or activities with a tight deadline.
What they're really asking: Do you manage your time, or do things slip through the cracks?
Answer outline (STAR)
- SituationOverlapping deadlines across classes, a part-time job or a club.
- TaskMeet the important deadlines without burning out.
- ActionListed everything out, ranked by deadline and weight, and said no to one lower-priority thing.
- ResultEverything important got done, and you noticed which habit caused the crunch.
5.Tell me about a time you asked for help or feedback.
What they're really asking: Will you ask questions instead of guessing and getting it wrong?
Answer outline (STAR)
- SituationStuck on an assignment or unsure if your approach was right.
- TaskGet unstuck without wasting a lot of time.
- ActionTried on your own first, then asked a specific question rather than 'I don't get it'.
- ResultYou got unstuck quickly, and used the same approach again later.
Full sample answer (fictional example)
I was stuck on a coding assignment where my program kept crashing and I couldn't figure out why after about 40 minutes of trying things somewhat randomly. Instead of continuing to guess, I wrote down exactly what I expected to happen, what actually happened, and the specific line I suspected, then brought that to office hours. The TA pointed out I was comparing a string to a number, something I'd have kept missing on my own. It took five minutes to fix once someone looked at it the right way. Now when I get stuck, I write down the specific problem first, which usually helps me either solve it myself or ask a much better question.
6.Tell me about a time you had to speak up in a class or group setting even though it was uncomfortable.
What they're really asking: Will you contribute ideas even when it feels risky?
Answer outline (STAR)
- SituationA group discussion or meeting where you disagreed with the direction.
- TaskSay something useful without derailing the group.
- ActionWaited for a natural pause, raised your point calmly with a reason, and stayed open to being wrong.
- ResultThe group considered your point, and either changed course or explained why not.
7.Tell me about a time you had to teach or explain something to someone else.
What they're really asking: Can you communicate clearly, a core skill for any workplace?
Answer outline (STAR)
- SituationA classmate, teammate or family member who didn't understand something you knew.
- TaskHelp them actually understand, not just repeat the information.
- ActionFound out what part confused them, used a simple example, and checked they could explain it back.
- ResultThey understood it, and you noticed what explanation worked best.
8.Tell me about a time you had to manage a disagreement with a teammate.
What they're really asking: Can you resolve conflict without it becoming personal?
Answer outline (STAR)
- SituationA disagreement over approach, workload or credit on a shared project.
- TaskResolve it so the work and the relationship both survived.
- ActionTalked to them directly and privately, focused on the specific issue, and proposed a compromise.
- ResultYou reached an agreement, and the project or friendship continued without lingering tension.
9.Tell me about a time you had to be resourceful with limited information or support.
What they're really asking: Will you figure things out instead of waiting to be told everything?
Answer outline (STAR)
- SituationAn assignment or task with vague instructions and no one immediately available to ask.
- TaskMake reasonable progress on your own.
- ActionSearched for similar examples, made a reasonable interpretation, and documented your assumptions.
- ResultYour work was mostly on track, and you adjusted quickly once you got clarification.
10.Tell me about a time you received critical feedback that was hard to hear.
What they're really asking: Can you take criticism without getting defensive?
Answer outline (STAR)
- SituationA grade, review or comment that was more negative than you expected.
- TaskImprove rather than just feel bad about it.
- ActionTook a moment before responding, asked clarifying questions, and made a specific change afterward.
- ResultYour next attempt or assignment reflected the feedback clearly.
Technical and role-skill questions (11–22)
Can you do the work itself? Think out loud and name the trade-offs.
11.Why are you interested in this field or this company specifically?
What they're really asking: Is your interest genuine and informed, or generic?
Answer outline
- Connect a specific class, project or experience to why this field appeals to you.
- Mention something concrete about the company: a product, a value, a team you looked into.
Full sample answer (fictional example)
I got interested in this field through an intro course where we built a small project applying what we'd learned to a real problem, and I realized I liked the process more than I expected, not just the grade. Looking into your company, I read through a few case studies on your site and liked that the work seemed to directly involve customers, not just internal reports nobody reads. I also looked at a recent post from your team about a project they shipped, and the way they described the process matched how I like to work: concrete problems, clear outcomes, and room to learn along the way.
12.Walk me through a class project or personal project you're proud of.
What they're really asking: Can you explain your own work clearly to someone unfamiliar with it?
Answer outline
- Describe the goal, your specific role, and the tools or method you used.
- Mention one real challenge you hit and how you solved it.
Full sample answer (fictional example)
For my database class final, I built a small app that tracked volunteer hours for a campus club I'm part of, since they were using a messy spreadsheet before. I designed the database structure, built a simple form for logging hours, and added a report view so officers could see totals by person and by event. The hardest part was handling duplicate entries when someone logged the same event twice; I added a basic check comparing date and event name before saving. The club actually started using it instead of the spreadsheet, which felt like a real result beyond just a grade. With more time, I'd add login accounts instead of one shared form.
13.How do you approach a problem you've never seen before?
What they're really asking: Do you have any method, or do you freeze without a clear answer?
Answer outline
- Break it into smaller, familiar pieces first.
- Look for similar problems you've solved before, or search documentation.
Full sample answer (fictional example)
I try to break it into smaller pieces I do recognize, since most new problems have at least one familiar part hiding inside them. I'll look for a similar problem I've solved before or check documentation or examples for the specific part I'm stuck on. Then I try something small and concrete rather than overthinking it in the abstract, check whether it moved me closer to the answer, and adjust from there. If I'm genuinely stuck after a real attempt, I ask a specific question rather than a vague one, which I've found gets much more useful help.
14.What tools, software or skills from your coursework are most relevant to this role?
What they're really asking: Can you connect classroom learning to real job tasks?
Answer outline
- Name specific courses, tools or projects, not just a list of class titles.
- Explain briefly what you actually did with each, not just that you 'learned' it.
- Be honest about what you know well versus what you've only touched briefly.
15.How do you stay organized when you have multiple assignments or tasks at once?
What they're really asking: Will you need constant reminders, or can you manage your own workload?
Answer outline
- Describe a concrete system: a planner, a task app, or a weekly review.
- Explain how you decide what to prioritize when things conflict.
- Mention a time the system actually prevented something from being missed.
16.What do you do when you don't understand something in class or at work?
What they're really asking: Will you speak up, or quietly fall behind?
Answer outline
- Try to work it out yourself first, using notes or documentation.
- Ask a specific, well-formed question rather than a vague one.
- Follow up to confirm you actually understood, not just nodded along.
17.What are you hoping to learn or get out of this internship?
What they're really asking: Are your expectations realistic and does it show real engagement?
Answer outline
- Mention specific skills or exposure you want, tied to the role's actual work.
- Show you understand interns do real but supervised work, not just make coffee or shadow silently.
Full sample answer (fictional example)
I'm hoping to get real exposure to how a team actually ships work, not just the theory from my classes, things like how priorities get decided and how feedback actually flows between people. I'd also like to build one or two concrete things I can point to afterward and explain clearly, rather than a vague list of tasks. Beyond the specific skills, I want honest feedback along the way, even if it's critical, since that's how I'll actually improve faster than just completing tasks quietly on my own.
18.What's a tool, language or method you taught yourself outside of class?
What they're really asking: Does your curiosity extend beyond what's assigned?
Answer outline
- Name something specific, with a real reason you learned it.
- Describe what you built or did with it, even if small.
- Be honest about your current level rather than overstating it.
19.How would you check your own work for mistakes before submitting it?
What they're really asking: Do you have any quality-check habit at all?
Answer outline
- Reread or retest against the original requirements, not just for typos.
- Compare your result against a rough expectation of what it should look like.
- Ask a classmate or peer to glance at it if time allows.
20.Describe how you'd approach a task you're given with no clear deadline.
What they're really asking: Will you self-manage, or let it drift indefinitely?
Answer outline
- Ask for a rough deadline or priority level if one isn't given.
- Set your own target date and check in partway through.
- Flag early if it's taking longer than expected rather than going silent.
21.How comfortable are you with spreadsheets or basic data tools?
What they're really asking: A baseline check for almost any internship, regardless of major.
Answer outline
- Describe actual experience with formulas, sorting, filtering or basic charts.
- Mention any exposure to more advanced tools if relevant to the role.
- Be honest about gaps, and mention willingness to pick them up quickly.
22.What would you do if you were given a task clearly outside your current skill level?
What they're really asking: Will you ask for help or quietly struggle and produce weak work?
Answer outline
- Try a first attempt to understand what's actually required.
- Ask for guidance or a resource rather than guessing blindly the whole way.
- Be upfront about where you need support, while showing willingness to stretch.
Take-home or live exercise: tips
Internship interviews sometimes include a short technical question, a simple coding or case exercise, or a request to walk through a school project in detail.
- Pick one or two projects you know inside and out, even if simple, rather than many you can only describe vaguely.
- Narrate your thinking out loud during any live exercise; interviewers weigh process as much as the final answer.
- If stuck, say what you're thinking and what you'd try next rather than going silent.
- Ask clarifying questions before diving in, since that's itself a skill being assessed.
Situational questions (23–30)
Scenarios that test judgement: say what you'd do first, and why.
23.Your supervisor gives you a task with instructions you don't fully understand. What do you do?
What they're really asking: Will you ask for clarification instead of guessing and wasting time?
Answer outline
- Reread the instructions and attempt to identify specifically what's unclear.
- Ask a clear, specific question rather than saying you're confused in general.
Full sample answer (fictional example)
I'd reread the instructions once more and try to pin down exactly what's unclear, rather than feeling generally confused. Then I'd ask a specific question, like which format they want the output in, rather than saying 'I don't really get this.' If my supervisor was unavailable and the task wasn't urgent, I'd make a reasonable attempt based on my best interpretation and clearly flag the assumptions I made when I handed it in, so they could redirect me quickly if I'd guessed wrong. I'd rather show progress with a flagged assumption than sit idle waiting for a perfect answer.
24.You finish your assigned work early with time left in the day. What do you do?
What they're really asking: Will you look for more to do, or just wait around?
Answer outline
- Check in with your supervisor rather than assuming you're done for the day.
- Offer to help a teammate, or ask if there's something you could start on.
Full sample answer (fictional example)
I wouldn't just wait quietly. I'd check in with my supervisor to let them know I'd finished and ask if there was anything else they needed, since they might have more context on priorities than I do. If they weren't available, I'd ask a teammate if they needed a hand with anything. If genuinely nothing was available, I'd use the time to review feedback I'd gotten earlier or read documentation relevant to upcoming work, rather than just scrolling my phone until the day ended.
25.You're asked to present your work to a team that includes people more senior than you. How do you prepare?
What they're really asking: Can you communicate confidently without overstating your experience?
Answer outline
- Focus on what you actually did and learned, not trying to sound more senior than you are.
- Practice explaining it simply, since not everyone will know the details you do.
- Prepare for a few likely questions so you're not caught off guard.
26.You realize you misunderstood a task and have been doing it wrong for two days. What do you do?
What they're really asking: Will you flag it immediately, or hope no one notices?
Answer outline
- Tell your supervisor as soon as you realize, rather than waiting to be found out.
- Explain clearly what you misunderstood and ask how to correct course.
- Use it as a lesson to confirm your understanding earlier on future tasks.
27.Your manager seems too busy to answer your questions. What do you do?
What they're really asking: Can you keep moving without constant hand-holding?
Answer outline
- Save up smaller questions and ask them together instead of interrupting repeatedly.
- Try documentation, teammates or your own research first.
- Still flag anything urgent or blocking right away, rather than waiting.
28.You're given conflicting instructions by two different people. What do you do?
What they're really asking: Can you navigate organizational confusion without freezing?
Answer outline
- Point out the conflict to both, politely, rather than guessing which to follow.
- Ask who has final say on this particular task if it's unclear.
- Document the agreed direction so it doesn't come up again.
29.You notice a small error in a senior colleague's work. What do you do?
What they're really asking: Will you raise it respectfully, or stay silent out of nervousness?
Answer outline
- Mention it privately and tentatively, since you might be missing context.
- Frame it as a question rather than a correction, such as asking whether X was intentional.
- Accept gracefully if there's a reason you didn't know about.
30.You're not enjoying the actual work of the internship as much as you expected. What do you do?
What they're really asking: Will you be honest with yourself and others, or just quietly disengage?
Answer outline
- Keep doing the work well regardless, since professionalism matters either way.
- Talk to your supervisor about adjusting your tasks if it's genuinely a poor fit.
- Use the experience to learn what you do and don't want next time.
Red flags to avoid in your answers
Each one is quick to fix before the day.
Giving vague, generic reasons for wanting the internship.
Connect a specific class, project or company detail to your actual interest.
Overstating skills or experience you don't really have.
Be honest about your current level; enthusiasm to learn matters more than false confidence.
Describing group work only in terms of what went wrong with others.
Focus on what you personally did to move the project forward.
Having no questions prepared for the interviewer.
Prepare a few genuine questions about the role, team or feedback process.
How to prepare for an intern interview in 7 days
An hour or two a day is enough; the order matters more than the length.
Day 1: Pick your stories
Choose two or three school or personal projects you can explain clearly, including one mistake you learned from.
Day 2: Learn the team and product
Read the company's actual products, recent posts or case studies, not just the mission statement.
Day 3: Practice explaining your coursework
Rehearse describing your major projects in plain language, as if to someone outside your field.
Day 4: Brush up relevant basics
Review any tools, spreadsheets or coursework concepts the posting mentions, even briefly.
Day 5: Write your STAR stories
Draft four STAR stories: a group project, learning something fast, a mistake, and receiving feedback.
Day 6: Prepare your questions
Write five genuine questions about the role, team structure and how feedback works.
Day 7: Dry-run interview
Do a practice run with a friend or career center covering behavioral and simple technical questions, then rest.
Questions to ask the interviewer
Pick two or three; the answers tell you whether you want the job.
- What would a typical week look like for an intern in this role?
- What kind of projects do interns usually work on, and how closely are they supervised?
- What separates an intern who gets a return offer or strong reference from one who doesn't?
- How does the team give feedback during the internship?
- What skills or experience have past interns found most useful afterward?
Preparation tips
- Prepare two or three school or personal projects you can explain clearly, even if small.
- Research the company's actual products or work, not just its mission statement.
- Practice explaining your coursework in plain language, since interviewers may not know your field's jargon.
- Prepare honest answers about limited experience; enthusiasm and a learning plan matter more than polish.
Prepare the general questions too: tell me about yourself, why do you want to work here? and why are you leaving? Afterwards, send a thank-you email; when the offer comes, negotiate the salary.
How we wrote this page
The FindAJobAI team wrote the questions, outlines and sample answers for intern interviews. The people, employers and numbers in the samples are invented: copy the structure, and use details from your own work.
Once we track enough live intern job ads, this page also shows the skills they ask for most, counted the same way as our in-demand skills report.
Last reviewed on November 1, 2026.