Build a short evidence bank
Prepare four or five examples you can use flexibly rather than memorizing an answer per question. Useful ones: solving a problem where the first approach failed, learning something unfamiliar under time pressure, working with someone you disagreed with, and handling a mistake you made. For each, know the situation in a sentence, what you personally did, what happened, and what you would do differently. The same example can answer several different questions if you know it well, which is why depth beats breadth here. This is general editorial preparation advice; the employer's own instructions determine the actual format.
Explain one project from end to end
Expect to talk through something you have built, analyzed, or researched. Be ready with the purpose, the constraints, the approach you chose and what you rejected, and how you knew it worked. Separate your contribution from your teammates' clearly and without diminishing either. Practice the explanation on someone outside your field first, then add technical depth when asked — being able to adjust the level is itself a signal. Name a limitation honestly; a candidate who says what their project does not handle is more credible than one who claims everything worked.
Study the actual team's work
Read the posting and the official team or program pages, and arrive with a specific reason this work interests you. 'I admire the company' is not a reason; 'the role involves X and I spent last semester on Y' is. Prepare for the format the employer described: for a technical or case assessment, use the preparation material they supply and any practice resources they permit. Do not seek leaked questions or unauthorized help — it usually breaches the terms you agree to and can end your candidacy.
Ask questions that help you decide
You are also evaluating them. Useful questions: what an intern actually worked on last cycle, who provides supervision and how often, how feedback is given, what the team is trying to accomplish this year, and what the working schedule really looks like. Save compensation, location, travel, and enrollment conditions for the recruiter rather than the technical interviewer, and resolve them before accepting anything. Do not assume an internship carries a return offer; if that matters to you, ask directly how often it happens.
Check the practical details beforehand
Confirm the time and time zone, the meeting link or the address, who you are meeting, and anything you were asked to bring or prepare. For a remote interview, test the platform, camera, microphone, and connection on the actual device you will use, and have a fallback — a phone number or a second network — in case something fails. Ask in advance if you need an accommodation. Arrive a few minutes early and treat everyone you meet as part of the process, because they are.
Close it out and learn from it
Write down what you were asked and anything you learned about the role while it is fresh; it is the best preparation for the next round and for other interviews. A brief thank-you note is optional unless the employer says otherwise, and it should be short and specific rather than a second pitch. Then carry on with your other applications while you wait. If you are turned down, you can ask politely whether feedback is available — many employers cannot give it at internship volume, and that is not a reflection on your application.
Check eligibility and the selected role's document instructions before submitting. FirstInternships does not accept applications or store your resume.
Find a program