Internship interviews are not designed to be impossible — they are designed to find potential. Knowing what is actually being tested removes most of the fear.
What internships really test
Three things: baseline technical competence, communication, and learnability. Nobody expects a finished professional. They expect someone who can think, explain, and grow.
Technical prep that works
Review fundamentals of whatever the role needs — for software roles, that means basic data structures, one language deeply, and your own projects. Be ready to walk through your own code line by line; "tell me about this project" is the most common technical question of all.
Behavioral questions
"Tell me about a challenge you faced" and "why do you want this role" come up constantly. Prepare two or three real stories from coursework or projects using a simple shape: situation, what you did, what resulted. Real beats rehearsed.
Questions YOU should ask
"What would I work on in the first month?" "How is feedback given here?" "What do successful interns go on to do?" Good questions signal seriousness and give you real information — interviews go both ways.
The day before
Sleep properly, lay out what you need, re-read the role description and your own CV, and prepare your setup if virtual. Cramming new topics the night before helps nothing.
After the interview
Send a short thank-you note within a day. Then keep applying elsewhere — never pause your search waiting on one outcome. If rejected, ask politely for feedback; some interviewers give genuinely useful answers.
Every interview makes the next one easier, including the ones that go badly. The students who get internships are usually just the ones who kept showing up.
