How to Prepare for a Technical Internship Interview

What technology internship interviews actually assess, how to prepare for each part, and how to answer when you do not know something.

Book a Consultation
Min read
2
Category
Career Guide
In short: Technology internship interviews assess three things: whether you can reason out loud through an unfamiliar problem, whether your claimed skills are real, and whether you communicate clearly. Prepare by rehearsing your projects in detail, practicing thinking aloud, and preparing an honest way to say you do not know.

Internship interviews are not scaled-down senior interviews. Interviewers know you have little experience, so they are testing your reasoning process and your honesty rather than your recall.

The three things being assessed

  1. Reasoning: can you work through an unfamiliar problem out loud without freezing?
  2. Verification: is the skill on your resume actually yours?
  3. Communication: can you explain something technical to someone who was not there?

Prepare your projects properly

Every project on your resume should have a three-minute version and a fifteen-minute version. Expect to be asked why you made a specific decision, and what you would do differently.

  • What problem the project solved and who for
  • One decision you made and the alternative you rejected
  • One thing that went wrong and how you diagnosed it
  • What you would change if you rebuilt it now

Practice thinking out loud

Silence is the most common failure in a technical interview. The interviewer cannot assess reasoning they cannot hear. Narrate your assumptions, state what you would check first, and say when you are guessing.

How to say you do not know

Not knowing is expected. Bluffing is disqualifying, because it tells the interviewer you might bluff during an incident too.

I have not worked with that. Based on what I know about how the surrounding pieces behave, I would expect it to work roughly like this, and the first thing I would check is whether that assumption holds.

Questions worth asking them

  • What does a typical week look like for an intern on this team?
  • How is my work reviewed, and how often?
  • What does a successful internship look like at week twelve?
  • What is the most common reason interns struggle here?

The week before

  1. Reread your own project code or configuration, you have forgotten more than you think
  2. Do one timed practice problem out loud, recorded, and watch it back
  3. Write your three-minute project summaries down and say them to another person
  4. Test your camera, microphone and internet connection on the actual platform

Where to go next

Turn the reading into something you can show

Courses end in graded projects and internships end in documented deliverables, both give you something concrete to talk about.