How to Introduce Yourself in an Interview (in Under 2 Minutes)

Introduce yourself in an interview with three beats in under 90 seconds: who you are now, the relevant path that got you here, and what you're looking for next. Skip the life story. Lead with the role-relevant version of yourself, make your point, then stop talking and let the interviewer take the conversation from there.

How do you introduce yourself in an interview?

Give a 60 to 90 second answer built on three beats: who you are now, the relevant path that got you here, and what you're looking for next. That's the whole formula. Interviewers ask this question to get oriented, not to hear your autobiography.

Most candidates over-answer because they mistake this question for permission to talk. It isn't — it's a warm-up lap, a chance to set the frame before the real questions start. The best intros end while the interviewer is still leaning in, not after they've started glancing at their notes wondering if you're done.

This question shows up under a few different names — "tell me about yourself," "walk me through your background," "introduce yourself" — and they all want the same thing: a tight, role-relevant summary, not a chronology. If you've ever frozen on 'tell me about yourself', the fix is the exact structure below.

Lead with the professional identity that matches the job in front of you, not whichever title looks most impressive on your resume. A backend engineer interviewing for a management role should open as a leader who happens to code, not a coder who occasionally leads.

The present-past-future structure

This three-part shape keeps you concise and on-point: present, past, future, in that order, and nothing else.

Present — state your current role and identity in one line. "I'm a product manager at a mid-size fintech company, focused on payments infrastructure." No qualifiers, no hedging, just where you are right now.

Past — pick one or two wins that explain how you got here and why they matter to this room. Not your whole resume; the two or three data points that draw a clear line from where you started to where you're sitting now. If an old job doesn't sit on that line, leave it out, however proud you are of it.

Future — say why this role, now. This is the beat most people skip, and it's the one that actually answers the implicit question behind "tell me about yourself": why are you here, applying for this job, today. One sentence connecting your trajectory to the opening in front of you closes the loop and hands control back to the interviewer.

Three beats, roughly 20 to 30 seconds each. Resist the urge to add a fourth.

A worked example

Here's the structure as a real 90-second intro you can adapt to your own background.

"I'm currently a senior customer success manager at a SaaS company, where I manage a portfolio of enterprise accounts worth about $4M in annual revenue. I got here by starting in support, moving into onboarding, and then building a renewals process that cut churn in my segment by double digits over two years — so I've seen the customer relationship from every angle, not just the easy parts. What I'm looking for now is a role where I own strategy for a whole book of business instead of executing someone else's playbook, which is what drew me to this opening."

Notice what that example does. It opens with a clean, specific line, not "well, so, let me think about where to start." It includes exactly one proof point with a number attached, because one credible number beats five vague claims. And it ends on a forward-looking close tied directly to the job at hand, not a shrug like "and that's basically my background."

Swap in your own titles and numbers, but keep the shape. The structure works whether you're two years into your career or twenty.

How to tailor it to the job

The same person has many possible intros — pick the one that matches this specific posting, not a one-size-fits-all script.

Mirror the posting's top priorities. If the job description leads with cross-functional leadership, your past beat should surface a leadership example, even if your best story is technical. Read the first three bullet points of the listing before you write your intro; they tell you exactly what this interviewer is primed to hear.

Cut anything irrelevant to this role, even the achievement you're proudest of. A 90-second intro has room for one or two proof points, not four. Every sentence that doesn't serve this specific job is a sentence stealing time from one that does.

Match tone to the company. A fast-moving startup rewards energy and brevity; a more formal or regulated employer — banking, government, healthcare — rewards a slightly more measured, credential-forward version of the same three beats. Same structure, different volume and word choice. That consistency should carry through everything else about how you show up, including what to wear to the interview.

If you're applying to a few different types of roles at once, keep two or three versions of this intro ready, each leading with a different past win and future rationale, so you're never reciting something that doesn't fit the room.

Mistakes that make you ramble

Most bad intros share the same three failures: starting too early, listing too much, and never landing.

Starting at birth, or close to it. "So I grew up in Ohio, and I always liked computers..." is a story, not an introduction. Interviewers don't need your origin story; they need to know if you can do this job. Start with your current or most recent role and work forward from there, not from age six.

Listing everything instead of the relevant few. If your past beat has six bullet points, none of them land. Pick the two that most directly support the case for this job and cut the rest, even the ones you're personally proudest of. A good interviewer will always ask a follow-up if they want more.

No landing point. Trailing off with "...and yeah, that's kind of it" or "...so, I don't know, that's me I guess" undoes an otherwise strong answer, because it signals the story doesn't actually have a point. Decide your last sentence in advance — a clear, forward-looking line about why you want this role — so you land the plane instead of letting it drift.

Rambling is rarely a knowledge problem; it's a planning problem. Candidates who haven't decided their three beats in advance end up narrating their thinking in real time, and that's what sounds unstructured on the other side of the table. Write your three beats down and say them out loud before the interview, even if you never use the exact words in the room.

Once you can deliver this in under two minutes without notes, you've handled the hardest 90 seconds of the interview — and set the frame for everything that follows. The rest of the conversation is just this same present-past-future logic, applied question by question. Land the Offer with AI walks through exactly that: using a tool like ChatGPT to tailor this intro, and the rest of your answers, to each specific posting, so you're never reciting a generic script in a room that deserves a specific one.

Frequently Asked Questions

How do I introduce myself in an interview?

Use a 60 to 90 second present-past-future structure: who you are now, the relevant experience that led here, and what you want next. Lead with the version of you that fits this specific role, not your full career history.

How long should my self-introduction be?

About 60 to 90 seconds. Long enough to show relevant fit, short enough to stay sharp and hand the conversation back to the interviewer.

Is 'introduce yourself' the same as 'tell me about yourself'?

Effectively yes. Both want a concise, role-relevant summary of your background and goals, not your personal life history, so the same present-past-future structure answers either one.

What should I not include?

Skip your full chronology, unrelated jobs, and personal details that don't bear on the role. End on a clear point that connects your background to this specific job, rather than trailing off.