How to Answer "Tell Me About Yourself" (Internship)

The interviewer opens with "tell me about yourself," and your mind goes blank, because "yourself" is too big a question to answer cold. The fix is a three-part formula you can fill in tonight: where you are now, the one thing you've done that maps to this role, and why you're in this chair. Below you get the skeleton, two full worked examples (one technical, one not), a fill-in template, and an honest list of what to cut. This is just the opener of the interview, so once it's handled, the rest of the questions get easier.

The 3-part formula: present, past, why this role

Almost every strong answer to this question runs in the same three beats, in this order.

Present. Where you are right now, in one clean sentence: your year, your major, and what you're currently focused on. "I'm a second-year computer science student at State, focused on data work." That's it. No throat-clearing, no "well, where do I start."

Past. The one or two things you've done that connect to this role. Not your whole history, and not necessarily the most impressive thing you've ever done. The thing that maps to the job. If you're interviewing for a data internship, the class project where you cleaned a messy dataset beats the prestigious-sounding club presidency that has nothing to do with data. Pick for relevance, not for shine.

Why this role. The honest bridge from what you've done to why you applied, ending on the role itself. This is where you say what you want to learn or do here. End on the role, not on a sentence that trails off into nothing.

Aim for roughly 60 to 90 seconds, which is about 150 to 200 words spoken. That figure is a rule of thumb, not a stopwatch rule: the point is long enough to be substantive, short enough that they don't lose you. And whatever you do, land the ending on the role, so the last thing they hear is why you want to be there.

Two worked examples

Here are two complete answers, in different fields, with each sentence labeled so you can see which beat it's doing. Both use made-up clubs and projects as illustration. Yours will use your real ones.

Example 1: a technical role (data or software internship)

"I'm a second-year computer science student at State, and lately I've been spending most of my time on data projects rather than pure coding. present Last semester, for a class project, I built a tool that scraped our campus events page and flagged scheduling clashes between club events. The messy part wasn't the code, it was cleaning the inconsistent date formats, and I ended up enjoying that more than I expected. past That's why I applied for this data internship: I've been figuring out the data-wrangling side on my own, and I want to learn how a real team does it with proper pipelines instead of my one-off scripts. why this role"

The present beat is one sentence and signals direction (data, not just coding). The past beat picks the project that maps to a data role and is honest about which part actually taught the student something. The why-this-role beat connects "what I did alone" to "what I want to learn here," and lands on the role.

Example 2: a non-technical role (marketing, comms, or operations)

"I'm a third-year communications major at State, focused on social and content. present This year I took over my film club's Instagram, which was basically a dead account, and turned it into how we actually fill screenings. I grew it from around 80 to 240 followers over a semester, and I learned that the captions mattered less than posting on a consistent schedule. past That's why this marketing internship caught my eye: I've been running a tiny account by feel, and I want to learn how a team plans content with real data and a calendar behind it. why this role"

Same structure, different field. The past beat comes from a club role, not a job, and the number (80 to 240) is this student's own illustrative result, not a benchmark. The why-this-role beat is honest about the gap ("by feel" versus "real data") and ends on the role.

Fill-in template: write your own in 10 minutes

Copy this skeleton and fill the three brackets:

"I'm a year major at school, focused on current interest. One sentence on the project, club, or job that maps to this role, plus what it taught you. That's why I applied here: I want to what you'll learn or do in this role."

Filling each bracket:

• Present: keep it to one sentence. Year, major, current focus. Resist the urge to add a second clause.
• Past: choose the one thing that maps to this role, then say what it taught you, not just that you did it. One or two sentences, no more.
• Why this role: name the gap between what you've done and what the role offers, and end on the role.

Then say it aloud twice. Reading it in your head doesn't count, because written sentences sound stiff when spoken. Saying it out loud is how you catch the parts that sound like an essay and smooth them into something that sounds like you talking.

What to cut (the honest list)

Most weak answers fail by adding the wrong things, not by missing good ones. Cut these:

• The childhood or high-school origin story. "Ever since I was young, I've loved technology." It eats your 90 seconds and tells the interviewer nothing about whether you can do the job now.
• The resume read-back. Reciting your resume line by line is wasted time, because they've usually already read it. Pick the one relevant thing and go deep, instead of skimming everything shallow.
• Hobbies, family, and relationship status. They didn't ask about your life, they asked a screening question. Save the personal color for the small talk, not the opener.
• The life-philosophy preamble. "I believe that in today's world, communication is more important than ever." It's filler, and it delays the part they actually care about.
• Apologizing for thin experience. "I don't really have much experience, but..." never helps. It plants doubt before you've said anything, and interviewers screening interns already expect you to be early-career. Lead with what you've done, not with what you lack.

When your "past" is thin

This is the part most guides skip, because they quietly assume you have a prior internship to drop into the past slot. You usually don't, and that's fine. Interviewers screening interns generally expect no work history at all.

When your past is genuinely thin, shift the weight. Keep the past beat to one honest line, one class project or one club role, and don't stretch it. Then spend the time you saved on the why-this-role bridge and on what you're actively learning right now. "I'm working through a SQL course on my own because I want the data side to be a real skill, not just something I've touched" does more work than padding a thin project into a fake epic.

If you sit down to write the past beat and come up empty, the real fix isn't better phrasing. It's to build a small piece of proof first: one finished project gives you a genuine past beat. And when you write the resume that goes with this interview, frame thin experience honestly so the page and your answer tell the same story.

Delivering it live vs. on a recorded video

In a live interview, you can read the room. If the interviewer is nodding along, you can trim; if they look lost, you can slow down. The formula is a safety net you can adjust on the fly.

In a one-way recorded video, you can't adjust, because nobody's reacting. You record into a webcam, and that's what gets reviewed. So the structure matters more, not less, and you rehearse against an actual timer until the three beats come out clean in one take. The mechanics of recorded screens (lighting, retakes, the short thinking window) are their own thing, covered in one-way video interviews and online assessments.

Frequently asked questions

How long should "tell me about yourself" be in an internship interview?

Roughly 60 to 90 seconds, or about 150 to 200 words spoken. That's a convention, not a hard rule, but it's a useful target: under 60 seconds tends to read as low effort, and over two minutes is where you start to lose the interviewer. Time yourself once so you know where you land.

How do I answer "tell me about yourself" with no experience?

Interviewers screening interns generally don't expect a work history, so stop translating "experience" as "jobs." Fill the past beat with a class project, a club role, or a part-time job that maps to the role, and lean more weight onto the why-this-role bridge and what you're currently learning. One honest, relevant thing beats a padded list.

Should I memorize my "tell me about yourself" answer?

Prepare the structure and rehearse it aloud until it sounds spoken, but don't memorize it word for word. A recited script sounds robotic and falls apart the moment you lose your place. Knowing your three beats cold lets you say it naturally every time, even when nerves hit.

What should I NOT say in "tell me about yourself"?

Skip the childhood or origin story, the line-by-line resume read-back, hobbies and family and relationship status, the life-philosophy preamble, and any apology for thin experience. Each one burns your 90 seconds on something the interviewer didn't ask for and doesn't help your case.

How do I start my answer to "tell me about yourself"?

Open with your present in one clean sentence: your year, your major, and your current focus. "I'm a second-year computer science student focused on data work." Skip the "well, where do I start" throat-clearing and go straight in; the confident opening sets the tone for the rest.

Tonight: write your three-part answer from the template, time it once, and say it aloud twice so it sounds spoken instead of recited. Then do the same for the questions you ask at the end, and keep applying so you get more reps at saying it for real. Browse internships to keep the interviews coming.