"Tell me about yourself" is usually the first question in an interview, and it is the one people most often answer badly. Some candidates recite their resume from the oldest job forward. Others say "well, when I'm not working..." and talk for four minutes. If you are searching for how to answer "tell me about yourself", the short version is this: give a 60 to 90 second pitch that says who you are now, backs it with one or two things you have done, and ends on why this job. This guide shows how to build that answer for a specific posting, with a worked example and a way to rehearse it.
What the interviewer is really asking
The interviewer has your resume. They are not asking you to read it back. In the first two minutes they want to learn three things:
- Can you summarize yourself clearly? It is a quick test of how you communicate.
- What do you think matters about your background? What you pick tells them how you see your own strengths.
- Why are you in this room? They want to hear a link between your past and this job.
That is why a chronological recap falls flat: it answers none of the three. It is also why a long personal story falls flat: it tells them about you, but not about you in this role.
How to answer "tell me about yourself": a three-part structure
Use present, proof, and why this role. Each part is a sentence or two.
1. Present: who you are at work right now
One sentence with your current role or focus, framed the way the job ad would frame it. "I'm a frontend developer" is fine. "I'm a frontend developer who mostly builds accessible React interfaces" is better, if that is what the posting cares about.
If you are between jobs, studying, or changing careers, say what you do now in the direction you are heading: "I'm a former teacher moving into instructional design, and for the last six months I've been building e-learning modules for a nonprofit."
2. Proof: one or two things you did that this job needs
This is the part people skip. Pick one or two concrete examples, not a list of adjectives. Each one should be:
- Relevant: it matches a requirement in the posting.
- Specific: a project, a problem, a result, a tool.
- Short: one or two sentences. You are opening a door, not telling the whole story. If they ask a follow-up, that is when you go into detail (a full STAR story works well there).
A useful way to think about it, borrowed from candidates who found it worked: frame your proof as two problems you are good at solving, each with one example.
3. Why this role: the bridge to the job
End by connecting the first two parts to this employer. "That's why this role caught my eye: you're rebuilding your player portal in Next.js, which is the kind of work I want more of." This hands the conversation back to the interviewer and gives them an easy next question.
How long should it be?
Aim for 60 to 90 seconds, which is roughly 150 to 220 words spoken. If you time yourself and you are past two minutes, cut examples, not the "why this role" ending.
Pick your proof from the job posting, not from your resume
Most generic answers come from starting with your resume. Start with the posting instead:
- List the must-have requirements in the job ad.
- Mark the ones you can back with something real: a job, a project, a course with a real deliverable.
- Pick the one or two strongest matches as your proof.
- Note the requirements you clearly lack. Do not cover them in this answer, but expect a question about them later and prepare a short, honest reply.
If you have a profile and saved jobs in Curri, the job's How you match panel in Jobs For You does this sorting for you. For each requirement it shows whether your profile covers it and, when it does, the evidence it found. In the demo profile below, the matched items are Next.js and React ("Built her portfolio site with Next.js; uses React at work"), TypeScript, and "a portfolio of shipped side projects". Those are the obvious candidates for the proof part of the answer. The requirements marked "Not found in your profile" (Node.js, PostgreSQL, two years of experience) are the questions to prepare for next.
A worked example
Here is how the three parts come together for the demo profile above (a junior frontend developer with about a year and a half of experience) applying to that Full Stack Developer role at a game studio. The profile and job are demo data, used only to show the method.
First, the version that recites the resume:
"I did a bootcamp, then I got my first job as a junior frontend developer, where I work on React and TypeScript. Before that I studied graphic design. I also have some side projects. I'm passionate about accessible interfaces and I'm a quick learner."
Every sentence is true, and none of it lands. It is in date order, it lists traits instead of evidence, and it never says why this job.
Now the three-part version:
"I'm a frontend developer, and most of my day is building accessible React and TypeScript interfaces. (present)
Outside work I build and ship my own projects. My portfolio site is built in Next.js and gets over a thousand visitors a month, and I helped build ArtConnect, a React platform that connects local artists with galleries and buyers. (proof)
That's what drew me to this role: you're building a player portal and store in Next.js and TypeScript, which is what I already do every day, and I want to grow into the backend side with Node and PostgreSQL on a team that ships often. (why this role)"
It runs about 45 seconds. Notice what it does with the gaps: it does not hide them or claim them. It names the backend as the direction of growth, which is honest and sets up the follow-up question on the candidate's terms.
Common mistakes and quick fixes
| Mistake | Fix |
|---|---|
| Starting with "I was born in..." or your first job | Start with what you do now. |
| Listing traits ("hard-working, passionate, quick learner") | Replace each trait with one thing you did that shows it. |
| Covering every job | Pick the one or two examples that match this posting. |
| No ending, so you trail off | Always end on "that's why this role...". |
| Memorizing it word for word | Memorize the three beats and the examples; say the words fresh each time. |
| One answer for every interview | Keep the present line, swap the proof and the ending per job. |
What about personal details and hobbies?
A short personal line is fine if it adds something, such as a hobby that relates to the work or shows how you think. Keep it to one sentence and put it after the proof, not in place of it. If you have an employment gap, you do not need to raise it here; if it comes up, have a short answer ready (how to explain an employment gap covers that).
If you are changing careers
Your present line does the heavy lifting. Describe yourself in terms of the new field, then use proof that transfers: a project, a course deliverable, or work from your old job that looks like the new one. The same idea applies to your resume; see how to write a resume for a career change.
Rehearse it out loud, against the real job
You do not know your answer until you have said it out loud a few times. Record yourself on your phone, listen back, and cut anything that sounds like a cover letter. Then practise a second version that is 30 seconds long, for interviewers who cut in early.
In Curri you can practise against the specific job. Open the job in Jobs For You, use the chat button in its toolbar to add it to the chat, and the job becomes the chat's context. Then ask something like "Help me write a 60-second answer to 'tell me about yourself' for this job, using my profile" or "Ask me 'tell me about yourself' and give me feedback on my answer."
The coaching chat reads your profile before it answers, so its suggestions start from your real work rather than a template, and it can suggest which achievements to bring up. Your profile's own professional summary is also a useful starting point for the present line, but rewrite it in spoken language: a summary written for a page usually sounds stiff when said aloud.
Chat messages are paid from your credit by usage, at the price of the model you choose, and new accounts start with $5.00 of free credit. See pricing for the current details, or career coaching for what else the chat can help with.
The short version
- Answer in 60 to 90 seconds: who you are now, one or two pieces of proof, why this role.
- Choose the proof from the job posting's requirements, not from the top of your resume.
- Replace traits with examples, and always end on the bridge to this job.
- Memorize the beats, not the words, and say it out loud before the interview.