How to answer "Tell me about yourself"
Answer "Tell me about yourself" in 60 to 90 seconds with three parts: what you do now, the one or two past experiences that make you right for this role, and why this role is the next step. It is a pitch for this job, not your life story, so every sentence should point at the job description.
By Evin JohnPublished 6 min read
Why interviewers open with it
The question looks like small talk, but it does three jobs. It shows how well you can summarize yourself under mild pressure, it gives the interviewer threads to pull for the rest of the conversation, and it reveals whether you understand what this particular role needs. Variants such as "Walk me through your resume" or "Introduce yourself" want the same thing.
Because it sets up the rest of the interview, your answer is also a chance to steer: mention the project you most want to be asked about, and you will often be asked about it.
The structure: present, past, future
| Part | What to say | Length |
|---|---|---|
| Present | Your current role or situation in one line, and the area you focus on. | About 15 seconds |
| Past | Two experiences that prove you can do this job, each with a specific result. | About 40 to 50 seconds |
| Future | Why this role and this company are the logical next step for you. | About 15 to 20 seconds |
Some people prefer past, present, future. The order matters less than the rule behind it: every part should connect to the job you are interviewing for. If a sentence would be just as true in an interview for a completely different job, cut it or make it specific.
Build your answer in four steps
- Read the job description for its top three needsUnderline the requirements that repeat or come first, for example "owns features end to end", "works directly with customers" or "scales data pipelines".
- Match a proof point to two of themGo through your resume and pick the projects that best show those needs. Write each as an action and a result: "rebuilt the onboarding flow, which cut drop-off from 40% to 25%".
- Write the future lineSay what draws you to this role specifically. A real reason (the product, the stage of the company, a problem you want to work on) beats a compliment about the company.
- Say it aloud and cutTime yourself. Most first drafts run two to three minutes. Remove dates, job titles you already listed and any story without a result until you land between 60 and 90 seconds.
Example answers
Fictional example
- I am a backend engineer at a logistics startup, where I own the services that price and schedule deliveries. Two things from the last few years are relevant here. First, I moved our pricing service from a nightly batch job to an event-driven pipeline, which let us quote in real time and cut failed bookings by about a third. Second, I led our on-call rotation through a database migration with no customer-facing downtime, which taught me a lot about rollbacks and idempotency. I am looking at payments because the same problems, correctness under retries and systems that cannot lose data, are the whole job there, and I want to work on them full time.
Fictional example
- For the past six years I have taught high-school math, and for the last two I have also run our school's adoption of a new learning platform. That second part is why I am here: I gathered feedback from forty teachers, worked with the vendor to prioritize fixes, and got weekly active use from about 30% to over 80% in one semester. I took a product management course to put structure around what I was already doing. I am applying to your team because you build for teachers, and I know their week from the inside.
Fictional example
- I just finished a degree in economics, where I focused on statistics and spent most of my final year on data projects. The one I am proudest of is an analysis of city bike-share data: I cleaned two years of trip records, built a dashboard the local transport office now uses, and found that three stations caused most of the rebalancing cost. I also interned at a retail company, writing SQL reports for the merchandising team. I want to start my career somewhere decisions actually change based on the analysis, which is what drew me to this role.
Adjust it for your situation
- Senior and leadership roles: lead with scope (team size, systems or revenue you own) and pick proof points about decisions and people, not individual tasks.
- Career gaps: mention the gap in one neutral sentence if it is recent, say what you did or learned, and move to why you are ready now. Do not apologize or over-explain.
- Recruiter screens: keep it shorter, around 45 seconds, and make sure your current role, your level and what you are looking for are crystal clear.
- Technical interviews: one sentence on the technologies you work with most helps the interviewer calibrate the questions that follow.
Mistakes that cost the most
- Reciting your resume in date order. The interviewer has it; they want the relevant highlights.
- Personal history (where you grew up, hobbies) unless it genuinely connects to the role.
- Vague claims with no result: "I am a hard worker and a team player" proves nothing.
- Running past two minutes. If you do, the interviewer stops listening before you reach the part that matters.
- Ending without a handover. A closing line like "Happy to go deeper into either of those projects" invites the next question.
Practicing it with Natively
With Pro (or during the free trial), Natively can work from your resume and the job description you add. In a practice session it transcribes what you say and can suggest an answer outline that draws on your own projects, which is a quick way to find the two proof points that fit a given role. Afterwards, the transcript shows you exactly how long you spoke and which parts drifted. See the behavioral interview assistant for how it works on a call.
Questions people ask
How long should my answer to "Tell me about yourself" be?
Aim for 60 to 90 seconds, which is roughly 150 to 220 spoken words. In a recruiter screen 45 seconds is often enough. If you go past two minutes, you are probably reciting your resume instead of pitching for the role.
Should I mention personal details or hobbies?
Only when they connect to the job, for example a side project in the same field. The interviewer is asking why you fit this role, so personal history that does not support that answer takes time away from the parts that do.
Is "Walk me through your resume" the same question?
Mostly. Use the same structure, but expect to name each recent role briefly before focusing on the two experiences that matter most for this job. Keep the emphasis on results, not on dates and titles.
Where to go next
Practice with the same assistant you would use on a call: it listens, transcribes and suggests answers from your own resume and the job description.
Facts on this page were last checked on . Product details come from the Natively app itself; if something here is out of date, tell us at hello@heynatively.com.
