Internship interview questions come in three kinds: questions about you, questions about times you worked with other people, and questions about the skills in the job posting. The second kind matters more than students expect. When we read 121 internship postings for software, data and finance roles, 109 of them asked for teamwork or collaboration, more than asked for any single technical skill. So prepare the stories first. The technical part is easier to cram.
Number of 121 software, data and finance intern postings naming each trait
| Teamwork or collaboration | 109 |
| Communication | 79 |
| Learning quickly | 66 |
| Problem solving | 36 |
| Ownership or initiative | 32 |
Source: Intern postings on employer career sites (Greenhouse, Ashby, Lever, Workday, Oracle, amazon.jobs), read by Internhood on Nov 7, 2026
A posting is not an interview script, but it is the clearest statement of what a team wants. Walk in with at least two true stories about working with other people: one where it went well, and one where it did not.
Seven questions to prepare, and how to answer them
1. "Tell me about yourself"
Nobody wants your life story here. Give them about 60 seconds: what you study now, one thing you did that fits the job, and why this internship.
I'm a third-year computer science student at [university], and lately I've been most interested in backend work. Last spring I built a room-booking tool for our robotics club. About 60 people use it every week, and keeping it running taught me more about databases than any class has. I applied here because the posting says interns own a service from start to finish, and that's the part I want to get better at this summer.
A made-up student, to show the shape: now, one proof, why here. About 60 to 90 seconds out loud. Practice it until it sounds like you, not a script.
2. "Why do you want this internship?"
Interviewers are checking whether you read the posting. Name something real from it, then connect it to something you have done.
Two reasons. First, the posting says interns [work on X / rotate through Y / own a project end to end], and that's exactly what I want after [related class or project]. Second, I [use the product / followed your work on Z / talked to someone on the team], and I liked that [specific detail]. I think I can be useful quickly because I've already [relevant skill with proof].
3. "Tell me about a time you worked on a team"
The most likely behavioral question, given how often postings ask for teamwork. Use the STAR shape, and spend most of your time on what you did.
Situation: In my [course] project, four of us had five weeks to build [what], and halfway through one teammate stopped replying. Task: I was responsible for [your part], but the [missing part] was blocking all of us. Action: I messaged them directly first, then suggested to the group that we split their work. I took [specific piece], set up a short check-in twice a week, and kept a shared list of who owned what. Result: We submitted on time and got [grade or outcome]. The teammate came back and finished the write-up. Next time I would set up the check-ins in week one, not week three.
Say "I" in the Action part. "We" makes it impossible to tell what you did.
4. "Tell me about a time you had to learn something quickly"
66 of the 121 postings asked for people who learn fast. Pick a story with a deadline in it, name exactly what you learned and how, and finish with what you shipped.
Last semester I had ten days to learn enough SQL to pull survey data for a marketing class project. I worked through the first few chapters of an online tutorial, then took a query a classmate had working and changed it one line at a time until I understood every part. By the deadline I had six queries feeding our analysis, and I still use SQL in my part-time job at the campus bookstore.
5. "Tell me about a time something went wrong"
They want to see you own a mistake without falling apart. Choose a real one with a fix, not a disguised boast like "I work too hard". Spend one sentence on the mistake and the rest on what you changed.
In [context] I [the mistake, stated plainly], which meant [consequence]. I told [person] the same day, fixed it by [action], and checked [what else could be affected]. Since then I [the habit you changed, e.g. test with real data before sharing / confirm deadlines in writing].
6. "What is your biggest weakness?"
Give a real, work-relevant weakness that is not central to the role, then show what you are doing about it. For a software internship, waiting too long to ask for help is a fair answer. "I am bad at coding" is not.
I sit on problems too long before asking for help. On my first group project I lost most of a weekend to a setup error that a teammate fixed in ten minutes. Now I give myself 30 minutes, write down what I've tried, and then ask. I get unstuck faster, and my questions are better because I've already ruled things out.
7. "Walk me through a project on your resume"
Expect follow-ups on every line you wrote, so only list what you can explain. Cover the problem, your design choices and why, one thing that broke, and the result. If someone else built part of it, say so before they ask.
Technical questions by internship type
Technical rounds follow the posting. These are the skills that came up most in the postings we read for each field, and the kind of question that tests them. The marketing sample is small, so treat that row as a pointer rather than a count to rely on.
| Internship | What postings named, and what to practice |
|---|---|
| Software engineering | Named: Python (27 of 47), JavaScript or TypeScript (24), C++ (21), data structures (18). Try: reverse a linked list, find duplicates in an array, explain the hardest bug in your project. |
| Data analyst | Named: SQL (14 of 18), Excel (11), statistics (10). Try: a query with a JOIN and GROUP BY, and when you would use a window function. |
| Data science | Named: Python (29 of 30), machine learning (29), statistics (23), A/B tests (13). Try: how you would test whether a new feature raised sign-ups, and what overfitting is. |
| Finance | Named: accounting (19 of 26), Excel (14), modeling or valuation (13). Try: walk through the three statements, and how depreciation affects each. |
| Marketing | Named: communication (11 of 12), analysis or metrics (11), writing (10). Try: how you would measure a campaign, and rewriting a product description for a new audience. |
Counts are postings that named each skill. Software 47, data 48, finance 26 and marketing 12 postings, read on employers' career sites, November 7, 2026.
What is different at Amazon and at banks
Amazon. After the online assessment, the interviews are mostly about past situations, judged against its Leadership Principles. Every behavioral answer should be a STAR story you can tie to one of them. Our Amazon internship guide covers each step and which student stories fit which principle.
Investment banks. Postings for summer analyst roles describe financial analysis, modeling, valuation and research on live deals, so expect technical questions on accounting and valuation, alongside "why banking" and "why this bank". See finance internships for when banks post and what they ask for.
Software internships. Many start with an online coding assessment before any interview. Our software engineering internships page lists the languages and skills 47 postings asked for.
Questions to ask the interviewer
Have three ready and ask two. Good questions are about the work, the team and how you will be judged, which also tells you if the internship is worth taking.
Questions worth asking
- What would a successful intern have finished by the end of the summer?
- What did last year's interns work on, and did any of it ship?
- Who would I go to day to day with questions, and how often do interns meet their manager?
- How is the end of the internship evaluated, and how do return offers work here?
- What does the first week look like?
- What do you enjoy about working on this team?
Skip anything the posting or careers page already answers, and leave pay, hours and remote work for the recruiter or HR round unless the interviewer brings them up.
After the interview: thank-you and follow-up emails
Send a short thank-you the same day. It rarely decides an offer on its own, but it is easy and it gives you a thread to reply to later. If you have heard nothing after the date they gave you, a polite follow-up is fine.
Subject: Thank you, [internship title] interview Hi [Name], Thank you for taking the time to talk with me today about the [internship title] role. I especially enjoyed hearing about [specific thing they said about the team or project]. Our conversation made me more excited about the chance to [what you would work on], and I think my experience with [relevant skill or project] would help me contribute quickly. Thanks again, and I look forward to hearing from you. [Your name] [Phone] | [LinkedIn or portfolio link]
Subject: Following up, [internship title] Hi [Name], I interviewed for the [internship title] role on [date] and wanted to check in on the timeline. I'm still very interested in the position and happy to send anything else that would help. Thank you, [Your name]
Send it a few working days after the date they gave you, or about a week after the interview if they gave none. Once is enough.
Cold email for an internship
Some internships at small companies never get posted at all. A short, specific email to the person who runs the team works better than a generic note to a careers inbox.
Subject: [Your degree] student interested in a summer internship on [team] Hi [Name], I'm a [year] [degree] student at [university]. I've been following [company]'s work on [specific thing], and I recently [built / wrote / analyzed something related], which you can see here: [link]. Are you taking on an intern for summer [year]? I'd be glad to send my resume or do a short call at a time that suits you. Thanks for reading, [Your name]
Under 120 words, one link, one clear question. Follow up once after a week, then let it go.
Questions people ask
What behavioral questions are asked in internship interviews?
Mostly "tell me about a time" questions on teamwork, learning something new, handling a mistake and taking initiative. They match what postings ask for: teamwork appeared in 109 of the 121 intern postings we read and fast learning in 66. Prepare four or five true stories and adapt them.
What questions does HR ask in an internship interview?
The HR or recruiter round is usually practical: your graduation date, which dates and locations you can work, whether you need visa sponsorship, and sometimes pay expectations. Answer plainly and check the posting first, since many list the pay and the graduation window.
How do I answer interview questions with no work experience?
Use class projects, group assignments, part-time jobs, clubs and volunteering. Interviewers for interns expect that. What matters is a specific situation, what you did and a result, not where it happened.
How long should an interview answer be?
About one to two minutes for a behavioral answer and under 90 seconds for "tell me about yourself". Longer answers tend to bury the result, which is the part they need.
How can I prepare for an internship interview in one day?
Reread the posting and list its top five skills. Write one story for each, plus your 60-second introduction, and say them out loud twice. Prepare two questions to ask, and for a technical role do three practice problems in the main language the posting names.
Is it OK to look at notes in a video interview?
A few keywords next to your screen are fine. Reading full answers is easy to spot and sounds flat, so keep notes to prompts like "group project, deadline, check-ins".
