How to Introduce Yourself in an Interview: The First 90 Seconds, Scripted

To introduce yourself in an interview, give your name and a warm one-line greeting, then answer "tell me about yourself" in 60 to 90 seconds: what you do now and at what scale, the two or three moves that got you there, and why this specific role is the logical next step. Everything else is mechanics.

What the research actually says about the first few minutes

Career advice is full of confident numbers about the first few seconds. Most of them have no study behind them. The research that does exist is narrower than the headlines suggest, and it points at something more useful than a countdown clock: early impressions bias what follows, but they rarely settle it.

Three findings are worth knowing, and all three come with caveats you should hear before you act on them.

• Early impressions correlate with final ratings. In a 2010 Journal of Applied Psychology study, Barrick, Swider and Stewart had interviewers rate candidates during the rapport-building stage — before the structured questions began. Those early ratings correlated .42 with end-of-interview scores and .22 with actual internship offers. Worth noting: these were students interviewing for internships through a campus career centre, not directors in a final round.
• But the decision usually isn't made yet. Frieder, Van Iddekinge and Raymark tracked 166 interviewers across 691 real applicants at a university career centre and asked when they had reached a decision. Only 4.9% had decided inside the first minute. A quarter had decided by five minutes. Around 60% had decided by the fifteen-minute mark — which is to say the bulk of the judgment happens during the substantive questions, not the handshake.
• Some of that early signal is noise. Swider, Barrick and Harris, in 163 mock structured interviews, found that first impressions do track something real — they correlated with expert ratings of interview performance, and with extraversion and verbal skill. But they also carried content unrelated to job qualifications, and that content leaked into the scores that followed. The useful detail for you: the distortion was strongest on the early questions and had largely faded by the end of the interview.

There is also a much-quoted handshake study. Stewart, Dustin, Barrick and Darnold (2008) had raters score the handshakes of 98 undergraduates in mock interviews and found handshake quality predicted hiring recommendations even after controlling for dress and appearance — mostly as the channel through which extraversion registered. Take it seriously and lightly at once: mock interviews with students are not a final-round panel, and one of the study's own findings was that women were rated lower on handshake quality without being rated lower on suitability, which tells you the measure is picking up more than firmness.

Notice what none of this says. Nobody has shown that a hiring decision locks in seven seconds; that figure circulates through career blogs without a hiring study attached to it, and the one dataset that actually timed real interviewers contradicts it. The honest read is that a good opening buys you a friendlier hearing for the next twenty minutes, and a bad one is recoverable — which is exactly why it's worth rehearsing and not worth panicking about.

The greeting: the thirty seconds before anyone asks a question

Nothing in the first thirty seconds is scored, which is exactly why people get it wrong — they either over-rehearse it into something stiff or they don't rehearse it at all and start the interview flustered. The greeting has one job: make the next ten minutes feel like a conversation between two competent adults.

The whole thing is four moves, and they take about eight seconds.

1. 1Name and greeting. "Hi, I'm Dana Reyes — good to meet you." Your full name once, then your first name for the rest of the hour. If they gave their name, use it back immediately: it's the cheapest way to remember it.
2. 2Hands. Offer if they offer. If they don't extend a hand, don't chase it — a nod and "good to meet you" does the same work. If you do shake: dry hand, full palm contact, one or two pumps, match their pressure rather than setting it.
3. 3One line of ordinary human content. "Thanks for making time on a Friday" or "Your building's easier to find than the last one I visited." Not a joke you've written in advance. Just proof that you can talk.
4. 4Hand the floor back. Sit when invited, put your phone away where they can see you do it, and stop talking. Let them open.

One thing to skip: do not deliver your elevator pitch in the hallway. If you front-load your positioning during the walk to the room, you will have to say it again five minutes later and it will sound rehearsed the second time. Hold it.

The structure that fits in 60 to 90 seconds

"Tell me about yourself" is not an icebreaker and it is not a request for your life story. It is an open question that most interviewers use to see whether you can organize information under mild pressure. Three beats, sixty to ninety seconds, and a clear reason you are in the room.

The three beats, in this order:

1. 1Present role and scope. What you do now, and the number that makes it concrete — team size, budget, account count, revenue, users, caseload. "I'm a project manager" tells them nothing. "I run implementations for our mid-market accounts — about fourteen live at a time, average deal size $80k" tells them what you're used to carrying.
2. 2The two or three moves that led there. Not every job. The two or three transitions that explain your shape: why you moved, what you picked up, what got bigger each time. This is the beat where people lose control and start reciting the résumé in reverse chronological order. Pick the moves that make the next sentence inevitable.
3. 3Why this job is the logical next one. One or two sentences connecting what you've been doing to what this role needs. Specific to the posting, not to the industry.

Why longer answers cost you

Sixty to ninety seconds is roughly 150 to 220 spoken words at a normal conversational pace. Three things go wrong past that. Attention: the interviewer is taking notes and has a question list to get through, and an answer that runs four minutes eats a slot they needed. Signal: an over-long answer is itself evidence about how you'll run a client call. And risk: the longer you talk unprompted, the more likely you are to hand over a detail you'd have handled better as an answer to a real question.

Most people badly misjudge their own length. An answer that feels like a minute is very often two and a half. The only fix is a timer, which we'll get to.

What to leave out

The three beats are a filter as much as a structure, and most bad versions of this answer fail by inclusion rather than omission. Four things people put in that almost never earn their seconds:

• The full chronology. Every job, in order, with dates. They have the résumé open in front of them. Reading it aloud is the single most common way to burn ninety seconds saying nothing they didn't already know.
• Where you grew up and what you studied, unless it's load-bearing. "I'm originally from Ohio" is only worth saying if the job is in Ohio and they're worried about relocation. Otherwise it's a sentence you can't get back.
• Why you're leaving. That's a separate question with its own answer, and volunteering it early makes the introduction about your last employer instead of about you. The exception is a layoff, which is cleaner named once and moved past — the third worked answer below shows the shape.
• Hobbies, in most cases. One clause at the end can humanize an otherwise dry answer if it genuinely connects to the work. A list of them reads as filler, and it competes for space with the sentence that explains why you want the job.

Five worked answers, written the way people actually speak

Structure is easy to agree with and hard to apply, so here are five complete answers written the way a person would actually say them — contractions, half-sentences, the occasional aside. Read them out loud with a timer. Each one runs between about sixty and ninety seconds at a normal speaking pace.

1. Going for an internal promotion

I'm a senior support engineer here — I've been on the enterprise queue for three years and I handle escalations for our top forty accounts. I came in as a tier-one agent in 2023, moved to enterprise after about a year mostly because I'd built the internal runbook everyone ended up using, and last spring I picked up the on-call rotation, which is really a scheduling and coaching job more than a technical one. That's the part I want more of. The team lead role is the version of what I've already been doing informally, except with the authority to actually fix the handoff between support and product instead of routing around it every week. I know the accounts, I know exactly where the process breaks, and I'd rather fix it here than learn a new product somewhere else to get the same title.

The internal candidate's trap is assuming everyone knows their history. They don't — the hiring panel often includes someone from another org. State the scope anyway, and name the thing you've been doing without the title, because that's the whole argument.

2. Changing careers

For the last six years I've taught high school biology — five sections, about a hundred and fifty students a year — and most of that job is designing instruction that has to work for people who did not choose to be in the room. Two years ago I took over curriculum mapping for our department, so I was building assessments and rewriting units based on what the data said wasn't landing. That's when I realized the part I actually liked was the design, not the classroom management. So I finished the instructional design certificate at State, and I've built three courses in Articulate since — one of them a volunteer onboarding program for a nonprofit that's still running. This role is the corporate version of what I already do: work out what people need to be able to do, then build the shortest path to it. The subject matter changes. The method doesn't.

Career changers over-explain the leaving and under-explain the transferable machinery. Flip it: one clause on why you moved, and the rest on the method that carries over. End on a sentence that reframes the change as continuity.

3. After a layoff

I was a product marketing manager at Northbeam for four years, most recently leading go-to-market for the payments product — two-hundred-person company, and I owned launch messaging, sales enablement and the competitive program. My role was cut in March when they consolidated marketing into a single team of six; about a third of the department went the same week. Before that I was at an agency doing positioning for B2B clients, which is where I learned to get a product's story straight quickly with a room full of people who don't yet agree on it. What drew me here is that you're roughly where Northbeam was when I joined — one product working, two more coming, and nobody owning the through-line between them. That's the work I'm best at, and I've had a few months to be sure it's the work I want next.

One sentence for the layoff, in neutral language, with the scale of it — "a third of the department" does more for you than any amount of reassurance. Then move. No apology, no bitterness, no long explanation of the restructure. Interviewers in 2026 have seen a lot of these.

4. First job out of school

I graduated in May with a statistics degree from State, and honestly the two things I'd point to are both outside the coursework. I spent three semesters in the campus data lab building dashboards for the athletics department — mostly cleaning ticketing and attendance data that showed up in four different formats every week. And last summer I interned on the analytics team at Halden, where I automated a weekly report that had been taking someone six hours in a spreadsheet. That's where I found out I like the plumbing part of this work more than the modeling part, which is why this role stood out — the posting is unusually honest that it's a lot of pipeline work early on. I'd rather start where the data comes in than where the charts come out.

With no career to summarize, the present-role beat becomes "what I've actually done with my hands." Two concrete artifacts beat a list of coursework and a GPA. And a line showing you read the job description carefully is worth more at this level than anything else you can say.

5. Returning after a career break

I'm a controller by background. My last role was at Ridgeline, a sixty-million-revenue manufacturer, where I ran month-end close, managed two staff accountants and led our ERP migration in 2023. I stepped out for about two years to care for my father through his illness, and he passed last fall. The past six months I've been rebuilding deliberately — kept my CPA current, finished the NetSuite administrator coursework, and taken contract close work for two small companies to get my reps back. So I'm not coming back cold. What I'm looking for is the scope I left: a close I own end to end, at a company big enough to have real complexity and small enough that I'm not a cog in it. Which is how this role reads to me.

Lead with the professional identity, not the gap. Name the break plainly in one sentence — vagueness reads worse than the truth — and then spend your words on what you've done to re-enter. "I'm not coming back cold" answers the question they're not allowed to ask directly.

What changes by format

The words barely change between formats. What changes is the mechanics around them: who speaks first, what you do with your hands, how long the silence lasts before someone unmutes, and how many people you have to acknowledge without doing it five separate times.

In person

You have a walk, a threshold and a seat, and each is a place to do something with your hands. Wipe your palm on your trouser leg on the walk over — cold, damp hands are the single most common physical complaint and the fix is that simple. Carry one thing, not three. If you're offered water, take it: it gives you a legitimate two-second pause later when you need one. Sit back in the chair rather than perching, and let your notebook rest closed until the questions start. What you're wearing does part of the greeting for you before you speak, and it should match the company rather than a generic idea of "interview clothes" — our guide to interview outfits decided by the company you're interviewing at is built around exactly that calibration.

Phone screen

With no visual channel, pace and energy carry everything, and both drop when you're slumped. Stand up, or at least sit forward. Smile — it really is audible: in a classic 1980 Perception & Psychophysics experiment, Tartter found listeners could pick the smiled version of an utterance well above chance, because smiling raises the fundamental and formant frequencies. Two practical notes: recruiters usually want a shorter version, closer to 45–60 seconds, and they will follow it with logistics, so have your notice period, location constraint and salary range decided before you pick up. Keep the job description on screen and a single index card with your three beats. Don't pace: you will find the dead spot in your apartment mid-sentence.

Video call

Most first rounds now happen on video, and they're increasingly instrumented — ZipRecruiter's Q2 2026 New Hire Survey found 35% of new hires met AI somewhere in their interview process, up from 22% two quarters earlier, including 15% who sat through an AI-analyzed video interview. Join two to three minutes early, and expect the awkward window where you're both on and nobody has spoken. Break it yourself: "Hi, can you hear me okay? Great — I'm Dana, good to meet you." Deliver the first sentence of your answer to the lens, then relax back to the face on screen; nobody can hold lens contact for ninety seconds without looking strange. Notes go directly under the camera, never off to the side. For framing, lighting and the rest of the on-camera mechanics, see our guide to looking confident on Zoom and Teams, and the separate piece on what to wear to a video interview — the wardrobe rules genuinely change when a webcam is the only witness.

One-way video (recorded, no interviewer)

The asynchronous screen — you get a prompt, a countdown and a record button — has become common enough at the first stage that it's worth its own preparation. There's no one to read, so the temptation is to perform. Don't. Deliver the same 60-second version you'd give a recruiter, to the lens, at your normal pace. Check three things before you start: how many retakes you're allowed (some platforms give one, some none), how long the prep timer runs, and whether your first answer is a throwaway practice question. And accept the first decent take. On a recorded answer, the fourth attempt reliably sounds more rehearsed and less human than the second.

Panel

The rule that solves most of it: introduce yourself once to the room, not once per person. On the way in, greet each panelist individually with "good to meet you" and their name if you catch it — but say your own name once, to the room, when you sit. If nobody offers names and roles, ask: "Could I get everyone's names and what you each do here?" Then write them down in seating order. When "tell me about yourself" comes, start with the person who asked, then let your eyes travel across the panel in a normal conversational rhythm, and finish back on the asker. Don't systematically rotate — it looks like a sprinkler. The quiet one who asks nothing is often the decision-maker; include them.

How to recover when you ramble

Everyone rambles at some point, usually in the second half of an answer they thought was going well. The damage comes less from the rambling than from what people do next — apologizing twice, starting over, or speeding up. There are cleaner ways to land a plane you've already overflown.

• Land it, don't circle. Cut to a summary sentence: "The short version is I've spent six years doing X and this is the same job at bigger scale." One sentence, then stop talking. The stop is the important half.
• Hand it back deliberately. "I can go deeper on any of that — which part is most useful?" You've converted a monologue into a conversation and given the interviewer control, which they wanted anyway.
• Apologize once, at most. "Sorry, that ran long" is fine. Repeating it makes the length the topic for the rest of the hour.
• If you blank on the opening, buy time honestly. "Let me start with what I'm doing now." That's a complete sentence, it's true, and it puts you back on beat one.
• If a second interviewer asks the same question later in the loop, answer it again. Shorter, and weighted to whatever that person's function cares about. Never say "I already covered that with Sam" — they compare notes, and they're allowed to.

One structural fix beats all the recovery tactics: know your own landing sentence in advance. If you've decided how the answer ends, you can jump to it from anywhere. And if the opening genuinely went badly, the Swider finding above is the one to hold onto — in that data the drag of a poor first impression was concentrated on the early questions and had mostly washed out by the end of the interview. The recovery window is real; it's just made of good answers, not of apologies.

What the interviewer sees before you speak

Before most interviews now, someone opens your LinkedIn profile. That photo is not scored and no reasonable interviewer treats it as evidence of anything, but it is the visual you they carry into the call — and on video, the gap between the photo and the person on screen is the only thing it can really cost you.

So the standard is lower than the internet suggests and more specific: current, recognizable, and lit well enough to survive a 400-pixel circle. A photo from a decade ago, or one processed so heavily it doesn't match the face on the call, creates a small unnecessary dissonance in the first ten seconds. Our guides to LinkedIn profile photos and getting a real smile in a headshot cover the craft side; the second one is worth reading before a job search specifically, because a tight, forced smile photographs as tension. If the only question you have is whether yours is too old to leave up, our piece on how often to update your LinkedIn photo answers just that one.

A fair caveat, since we make one of these tools: an AI headshot is a good profile photo and a bad disguise. Generate from recent selfies, pick a result that looks like you on an ordinary Tuesday, and skip anything that smooths you into someone else. A photographer still has the edge when you want direction in the room, an unusual crop, or images of you in your actual workplace — the trade is time and money against that control. Either way, on a video call the interviewer is comparing the photo and the face whether they mean to or not, and only accuracy protects you there.

A practice routine for the week before

Preparation for this fails in a predictable way: people write the answer, read it four times in their head, and then hear it out loud for the first time in the interview. Rehearsal has to happen in the same channel you'll perform in — mouth, not eyes.

1. 1Write the three beats as bullets, not sentences. Scope line, two or three moves, why this job. Memorizing prose produces recitation; memorizing beats produces speech.
2. 2Record yourself on your phone and time it. Once. Then listen back and note only where you drifted. Most people cut thirty seconds on the second attempt without trying.
3. 3Build a short version and a long version. Roughly 45 seconds for a recruiter screen, 90 for a hiring manager. Same beats, different depth on beat two.
4. 4Rehearse the greeting too. Say your own name out loud a few times. It's the one line people fumble, because it's the one line they never practice.
5. 5Do one full run in the actual format. If it's a video call, open the meeting software, look at your own framing, and deliver it to the lens. If it's in person, do it standing, out loud, in shoes.

Then stop. Past about six run-throughs the answer starts to calcify, and a calcified answer is audibly worse than a slightly rough one. You are aiming for a person who knows their own story well, not a person performing a script — which, conveniently, is also what the interviewer is aiming to meet.