Tell me about yourself for an internship interview

Internship interviews expect a student. Say so, then show one piece of work you finished and why this internship is the one you want.

Build your answer

Target role The job you are interviewing for. Years of experience Years in this kind of work. Use 0 for a first role or a career change. Current role or background A field, a path, or a short phrase.

Win 1 Include a number. Win 2 Optional. Win 3 Used in the long version.

Key strength One habit, not five adjectives. Why this company or role A reason that would be wrong for a different employer.

Runs in your browser. Nothing you type is uploaded.

30-second version

About 30 seconds · 76 words

A short cut for a recruiter screen.

Stop after one result. A short screen does not need the second story.

60-second version

About 52 seconds · 131 words

The default. Present, then past, then future.

If they lean in, drop the second result and spend the time on how the first one happened. Leave duties from the job description out.

90-second version

About 84 seconds · 210 words

A longer cut when they ask you to walk through it.

I'm looking for a software engineering internship role. I've worked in a junior studying computer science. Before that, this is the work that got me here. I built a course scheduler that 80 classmates used during registration. I also fixed a lab partner's flaky test by isolating one shared fixture. A later result was tutored 10 students through the intro programming course. None of that is a title. It is the work I can walk through. The through-line is making a small version work before I add scope. The future I'm aiming at is a software engineering internship role, because this internship ships intern projects to real users, and I want that constraint. The first thing I'd measure is the constraint the team already feels. The numbers in those results are ones I can defend, including what I owned. The software engineering internship role is the move, and the results are how I know I can do the work. I can say any of those results more slowly, with the owner and the number intact. I would use the same judgment on the next software engineering internship problem. The work I want next is still software engineering internship work: a clear owner, a number, and a decision I can explain.

They can interrupt. Go present, then proof, then why this role. When they ask, go from the headline number to the decision you made.

When you can say the minute without the page, practice it live with Luna. It hears the question and helps you keep a line. 24 hours free.

How to answer it for this role

You have about a minute, sometimes less, before a project question. The opener is not your chance to cover every class. Name your year, your major or focus, and the internship you want. Then one project or job with a result.

A campus job counts. So does research, a student org you actually operated, or a class project with a user. Say which it was. Interns who blur a homework assignment into a startup get a painful follow-up.

Why this company should be specific enough that it would be wrong for the company next door. A product you use, a paper you read, a tool you already tried. "You are a leader in the space" works for the whole list.

What to emphasize

Year in school and the internship title.
One finished project or job.
A reason that would not fit every employer.

What to leave out

Your life story before college.
Every club you joined.

Sample 60-second answer

This is the sample loaded into the builder above. About 52 seconds, 131 words. Replace every fact with yours before you practice it.

I'm looking for a software engineering internship role. I've worked in a junior studying computer science. Before that, this is the work that got me here. I built a course scheduler that 80 classmates used during registration. I also fixed a lab partner's flaky test by isolating one shared fixture. The through-line is making a small version work before I add scope. The future I'm aiming at is a software engineering internship role, because this internship ships intern projects to real users, and I want that constraint. In the job I'd bring that strength to the team's current goal, and I'd report what moved. I have the detail under each number, including what I would measure again. That is the minute: the software engineering internship work, the proof, and the reason.

The 30-second cut is about 30 seconds. The longer cut is about 84 seconds. Both use the same facts in the same order. Read the longer structure guide if you want the timing rules in full: how long the answer should be.

Tips before you say it

Say the 60-second version out loud before you edit it. A sentence that looks fine on the page often runs long or sounds like a memo.
One number per win. “Improved the process” is a claim. “Cut hold time from 6 minutes to 2” is a result you can be questioned on.
Stay in order: present, past, future. If you start with where you grew up, the interviewer is waiting for you to arrive.
Leave a door open and then stop talking. The extra story you add in the silence is usually the one you did not prepare.
Keep your part separate from the team’s. “We launched” collapses the first follow-up. “I cut the scope, engineering shipped it” survives.

Other roles

Questions people ask

What if this is my first interview?

Say the beats slowly: present, one result, why this internship. You do not need a polished career narrative. You need to be specific and stop.

Should I mention other interviews?

No. This answer is about this role. Recruiting status is a different conversation, and only if they ask.

Can I use the 30-second version?

Yes for career fairs and recruiter screens. Use the 60-second version for a scheduled interview. The 90-second version is usually too long for an intern screen.