How to answer "tell me about yourself" in an interview
A practical way to answer "tell me about yourself" in an interview: a present-past-future structure, the right length, and a skeleton you can fill in.
A practical way to answer "tell me about yourself" in an interview: a present-past-future structure, the right length, and a skeleton you can fill in.
The first question is almost always the same, and most people fumble it. "So, tell me about yourself." A good answer here does not win the interview, but a bad one digs a hole you spend the next half hour climbing out of. The good news: this is the one question you can fully prepare, because you already know it is coming.
What the interviewer wants is not your autobiography. They want a sixty to ninety second pitch for why you, specifically, fit this role. Give them that, and you set the tone. Here is the structure I use, the length to aim for, and a skeleton you can fill in tonight.
"Tell me about yourself" is not a memory test or an icebreaker to fill silence. It is a soft open that does real work: it lets the interviewer hear how you talk when nobody handed you a script, and it lets you point the conversation where your strongest material lives.
So treat it as an invitation, not a trap. You are not reporting facts they can read on your resume. You are answering a question they did not say out loud: why are you the right person for this job? Everything you choose to mention should serve that question. If a detail does not, it belongs somewhere else or nowhere.
The cleanest way to keep your answer on track is three beats, in this order.
The order matters. Leading with the present puts your most relevant self first, while a chronological answer makes the listener wait through years of context before they learn whether you can do the job. Past goes in the middle because it is supporting evidence, not the headline. Future goes last because it hands the conversation forward, often straight into "why this company," which is frequently the next question anyway.
Aim for sixty to ninety seconds. Under thirty and you sound underprepared or nervous. Over two minutes and you lose the room, because the interviewer stops listening and starts wondering when you will stop.
Sixty to ninety seconds is roughly three or four sentences per beat, no more. That constraint is a feature: it forces you to cut everything that is not load-bearing. Time yourself out loud once or twice. Not to memorize a script, which sounds robotic the moment a nerve hits, but to feel how long ninety seconds actually is, so you can land it without watching the clock.
The same answer should not work for two different jobs. If it does, you have written a generic one, and a generic answer is forgettable.
Before the interview, read the posting again and find the two or three things it clearly cares about most. Then make sure each of those shows up in your present or future beat. Applying to a role heavy on cross-team work? Your "present" mentions the projects where you coordinated across teams. Applying somewhere that ships fast? Mention the time you owned something end to end and got it out the door. You are not lying or inventing. You are choosing, from everything true about you, the parts this specific room needs to hear.
Two failures account for most weak answers, and both come from misreading the question.
A smaller third trap: rambling because you never decided where to stop. That is what the structure and the time limit fix.
Here is a frame to make your own. Swap in your specifics and cut anything that does not serve "why me for this role."
Present: "I am a [role] at [company], where I [own / focus on] [area]. The part I am strongest at is [skill the job needs]."
Past: "I got into this through [one or two steps]. Along the way I [built / learned the thing that matters here]."
Future: "Now I am looking to [what you want next], which is why this role caught my eye: [specific thing about the company or job that fits]."
Three sentences each, said like a person, not recited. Read it aloud, trim the filler, and you have a confident open you can give without notes.
Preparing this answer is mostly about knowing what a specific role wants and matching your real experience to it. JobScalr is a mobile app that reads a job posting against your background, gives you an honest match score from 0 to 100 with the reasoning behind it, and includes interview prep: a short study deck built from the posting, plus space to practice your own answers out loud. It does not write your story for you or invent experience you do not have. It just helps you see which parts of your background this particular interview will care about, so your sixty seconds land on the right things.
Ready to sharpen your next application?
See JobScalr →