How to answer "Tell me about yourself"

What the interviewer is actually asking

Almost every interview opens with some version of this: “tell me about yourself”, “tell us about yourself”, or “walk me through your resume”. It sounds like small talk. It is not.

MIT’s career office suggests hearing the prompt as “tell me about yourself as it is of interest to me (the interviewer)”. That single reframe fixes most weak answers. Nobody is asking where you grew up or what you do at weekends. They want a short professional map: what you do, what you have done, and why you are sitting in front of them.

Three things get judged in those first two minutes. Can you be concise under mild pressure? Do you understand what this role needs? Can you talk about your own work in your own words, without reciting a page? There is a practical bonus too: interviewers tend to follow up on whatever you mentioned, so a clear opening answer quietly sets the agenda for the next half hour.

A structure that works: present, past, future

The simplest reliable shape moves forward in time, with the present first.

Present

Open with one or two sentences on what you do now and the part of it that is relevant here. A job title on its own is thin, so add scope: the kind of work, who you do it for, how much of it there is. “I am a support engineer on a team of six, handling escalations for enterprise customers” tells the interviewer far more than “I work in support”.

Past

Then give the short version of how you got here, picking only the steps that build toward this job. Two or three sentences is usually enough. Name one concrete achievement with a result attached, because it gives the interviewer something to ask about and it proves you can be specific. Skip the full chronology; your first summer job is not needed unless it genuinely is.

Future

Close on why this role, at this company, now. Most candidates drop this part, and it is the part that makes an answer feel aimed rather than recycled. Tie something specific from the job description to the work you want more of, then stop talking.

If the invitation is “walk me through your resume” instead, the same three beats work in the same order. You simply allow yourself one extra sentence per role.

How long should the answer be?

One to two minutes spoken, which is roughly 150 to 250 words. Under thirty seconds reads as unprepared or guarded. Past three minutes you are spending the interviewer’s questions for them, and their attention with it.

The only useful test is to say it out loud against a timer rather than counting words on a page. Most people find their first attempt runs close to four minutes, and almost all of the excess sits in the middle section. Cut there first.

Length also depends on who is asking. A recruiter on a twenty-minute screening call wants the forty-five-second version. A hiring manager with a full hour can take the whole two minutes and will probably interrupt with a follow-up, which is a good sign rather than a bad one.

Sample answers for three profiles

These samples are written to be adapted, not copied. Each one follows present, past, future, and each runs about a minute spoken.

Graduate or entry level

I finished a BSc in economics in June, and for the last two years most of my energy went into data work: I ran the analysis for our student consulting group and taught myself SQL and Tableau so I could do it properly.

The project I am proudest of was for a local bakery chain. They had three years of sales sitting in spreadsheets and no idea which locations were losing money. I cleaned the data, built a simple dashboard, and the owner used it to change opening hours at two sites.

I am looking for a first analyst role where I can keep doing that with better data and people to learn from. Your junior analyst opening mentions reporting for operations teams, and that is exactly the kind of question I like working on.

Notice what is absent: no grades recited, no hobbies, no apology for being new. One real piece of work carries the whole answer.

Experienced professional

I am a project manager at a logistics software company, where I run implementations for mid-market clients. Usually three or four live at once, each about four months end to end.

I moved into project management from the support side six years ago, which turned out to be useful, because I had already watched these rollouts fail from the other end. Since then I have taken the hardest accounts, and last year I reworked our kickoff process after two projects slipped. Our average go-live delay went from about three weeks to under one.

I have gone about as far as implementations go at my current size of company. Your posting is for someone who will build the delivery playbook while the team grows from five to fifteen, and that is the problem I want next.

The pattern here is scope, then one result, then a reason for moving that is about the work rather than about escaping a manager.

Career changer

For the last eight years I have been a secondary school science teacher, and for the last three of those I was the person who automated things: timetable conflicts, report generation, a Python script that took a day a week out of our marking admin.

That turned into a deliberate switch. I finished a nine-month software development course in the spring, built two small web applications, and I have been contributing to an open-source lesson planning tool since February.

I am applying for junior developer roles where communication is part of the job. Your team works directly with non-technical users on an education product, and explaining complicated things to people who did not ask for them is the skill I already have.

Career changers often treat their past as a liability. Told this way it becomes the reason to hire them: name the transferable skill, show proof that the change is real and already underway, then connect it to the role.

What to leave out

Personal details that have nothing to do with the job: age, marital status, children, health, religion, where you were born. Interviewers in the US and UK are generally not supposed to ask about most of these, so volunteering them puts you both in an awkward position.

Your life story in order. Starting at school and working forward is the single most common way this answer goes wrong, because the interesting part arrives after the interviewer has stopped listening.

Anything negative about your current employer or manager. Even a fair criticism lands as a warning sign in the first two minutes. Say what you are moving toward, not what you are running from.

Salary expectations, notice periods and logistics. There is a later point in the process for all three, and raising them now suggests you are solving a different problem.

Hobbies, unless one genuinely supports your case. Running a 400-member online community is relevant for a community manager role. Otherwise it is filler that pushes out something that would have helped.

And finally, the recited paragraph. If it sounds like a cover letter being read aloud, the interviewer switches off and waits for the end. Know your three beats, then speak like a person.

Written versions and the recruiter screen

The same question turns up in places other than the room. Application forms often ask you to tell us about yourself in a text box, and the written version follows the same present, past, future order in roughly 100 to 150 words. Cut the warm-up sentence entirely and lead with your current role, because nobody reads a text box patiently.

On a recruiter screening call you usually get an abbreviated version: “introduce yourself” or “give me the quick overview”. Deliver present and future with one line of past. The recruiter is checking you against a brief before passing you on, so make the match obvious and make it fast.

Recorded video interviews are a third case. There you often get a fixed time limit and no follow-up question, so the closing part has to do more work. Name the role by title and say plainly why it fits, since there is no interviewer to pull that out of you.

How to tailor it and rehearse

Start from the job description, not from your resume. Mark the three things the employer puts first or repeats in different words, then check that your answer touches at least two of them. If it touches none, you have prepared an answer for a different job.

Write it out once in full, so you know what you think. Then throw the sentences away and keep three anchors: your current scope, your one proof point, your reason for this role. Anchors survive nerves. Memorised sentences fall apart the moment you lose your place.

Say it out loud at least five times, to a person or a recording rather than a mirror. Listen for two faults in particular: filler at the start, and a final sentence that trails off instead of ending. Fix the first ten seconds and the last ten seconds, and the middle usually takes care of itself.

Rewrite the closing part for every application. Your present and past barely change from one interview to the next. The reason you want this specific job always should.