Home / Tools / Tell me about yourself

Tell me about yourself

A spoken answer in present, past, future order. You get a 60-second version, a 30-second cut, and a 90-second version, with the time it takes to say each one.

What the question is actually asking

“Tell me about yourself” sounds open. It is not. The interviewer is handing you the frame for the rest of the conversation, and they are timing it whether or not a clock is visible. They want to know what job you are here to do, whether you have done adjacent work, and why this role is the one you want. They do not want your childhood, your full employment history, or a list of tools.

A useful answer is short enough to interrupt. If you talk for three minutes, you have spent the time they were going to use on a real question, and you have signaled that you cannot tell the difference between a frame and a memoir. Candidates who do this are often prepared. They prepared the wrong artifact. They wrote a speech. The interviewer wanted a handle.

This page builds that handle in the browser. You enter the role, your years in this kind of work, your current role or background, two or three wins with numbers, one strength, and why you want the job. You get a 60-second version in present-past-future order, a 30-second cut, and a 90-second version. The time next to each box is an estimate at about 150 words a minute, which is a conversational pace, not a commercial. Edit the words. Copy them. Nothing you type is uploaded, and you do not need an account.

Present, past, future

Present is two jobs of work, done in a sentence or two. Name the role you are interviewing for, and name the work you do now. If you have years in this kind of work, say the number once. If you do not, say that you are early and name the background you are coming from. Do not apologize for the background. An apology makes the interviewer manage your confidence instead of listening to the proof.

Be careful with the years. They attach to the kind of work, not to your age and not to an old career you are leaving. A teacher with eight years in the classroom who wants a product role should not open with “I’m a product manager with eight years of experience.” That sentence is false, and the resume will contradict it. Put the classroom in the background. Put zero or one in the years field if the product work is new. The builder follows that rule. It will not award you a title you did not claim.

Past is evidence. One result for a 30-second answer, two for a minute, three only if you have the longer version and each result is still one sentence. Every result needs a number or a concrete before-and-after. “Improved collaboration” is a claim. “Cut status meetings from 5 hours a week to 90 minutes” is a result. You should be able to say what you owned and what the team owned. If the honest version of a win is “I found the bug in the query and finance changed the definition,” say that. The follow-up will be kinder than the follow-up to a number you inflated.

Future is why you are in this room. The product, the unit, the buyer, the students, the stack, the city’s schools. Then the strength you will use, stated as a habit rather than a pile of adjectives. “Making tradeoffs explicit when a system is under load” gives them a hook for the next question. “Hard-working team player” gives them nothing to hold. After the future, stop. The silence is theirs.

People miss this structure in two predictable ways. They start in the past, which usually means they start in college, and the present arrives only if the interviewer is patient. Or they start with praise for the company and never offer proof. Praise without proof sounds like you read the careers page out loud. Proof without a reason sounds like you would take any job with the same title. You want both, in that order: where you are, what you have done, why this.

How long it should be

Match the length to the room, not to how much life you have lived. A new executive and a new grad both need a minute. The executive’s minute is denser. It is not longer.

Thirty seconds gets one result. You say the role, the proof, and the reason, and you sit still. Recruiters use this cut when they still have compensation, visa, and timeline questions. If you give them the 90-second version, they will interrupt you, and you will feel rushed even though you caused it.

Sixty seconds is the version to practice until it is boring. Two results, the strength, the reason. If a friend times you and you pass 75 seconds, cut a result rather than talking faster. Fast talking hides the numbers. The interviewer writes down what they can hear.

Ninety seconds is for a round where the opener is the interview, not the preamble. You can add a third result and one sentence on how you would start. You still do not add a fourth job. Past 90 seconds, you are borrowing time from “tell me about a time,” and that is the question that actually differentiates people.

The estimates on this page assume 150 words a minute. Nervous candidates often talk faster and finish a 150-word answer in 45 seconds, then fill the quiet with a new story they did not plan. Practice once at a pace where you could repeat a sentence if someone asked. If the box says the draft is long for the slot, it is long. Cut a clause. Do not plan to “just talk faster” in the room.

How to fill in the builder

Target role is the job in the posting, not your whole identity. “ICU nurse,” “account executive,” and “4th grade teacher” are better than “healthcare professional,” “seller,” or “educator.” If the posting says senior, and you are interviewing for senior, use their word. If you are stretching for it, do not promote yourself in sentence one. The level conversation can happen after they have heard a result.

Current role or background is a noun phrase. “Backend engineer on a payments team.” “Medical-surgical nurse at a community hospital.” “A student who covers a campus service desk.” You do not need a company name unless the name helps a stranger place the work. You do need enough that the next sentence can be a result rather than an explanation of what your job was.

Wins should start with a verb when you can manage it: led, cut, closed, taught, kept, shipped, caught. Put the number in the same line. Two wins is the right count for a minute. The third is for the long version. If you only have one number you trust, use one. A thin true answer beats a full false one. The builder will not invent a metric for you. It will only arrange what you typed, which is the point. You are the person who has to defend it.

Strength is one habit. Write it the way you would say it to a coworker, not the way a review form demands. “Listening for the real objection before I answer the polite one” is a habit. “Strategic, collaborative, and data-driven” is three posters. Why this company is a specific reason. If you cannot name one, you are not ready to say this answer for that employer. You can still practice the present and the past.

Examples at different levels

These are samples so you can hear the shape. They are not yours. If a number is not from your work, do not borrow it. Interviewers ask how you measured the thing, and a borrowed number collapses in that question. Use the samples to see what “specific” sounds like, then replace every fact.

New grad

I'm looking for a new grad software engineer role. I've worked in computer science senior with one internship. Before that, the results are specific. I shipped an internship dashboard that 30 support agents used daily. I also cut a class project's test runtime from 11 minutes to 4. The way I work, when it counts, is asking the constraint before I start building. What I want next is this new grad software engineer seat, because this team pairs new grads with a real on-call, and I want that kind of first year. In the job I'd bring that strength to the team's current goal, and I'd report what moved. Those results are the kind of work I want to keep doing as a new grad software engineer. I can explain the constraint behind the first result and the number I was willing to defend.

That sample is about 58 seconds at 150 words a minute. Edit the new grad version if the facts are not yours. They should not be. The builder is there so you can swap in numbers you can defend.

Career changer

I'm looking for a product manager role. For the past 1 year I've worked as an elementary teacher who spent the last year on curriculum software. Before that, this is the work that got me here. I raised class reading growth 1.4 grade levels with a weekly plan. I also shipped a lesson-planning pilot that 18 teachers kept using. The through-line is turning a fuzzy goal into a weekly plan people actually follow. The future I'm aiming at is a product manager role, because this product team writes for teachers, and I want the planning habit on a product they use. In the job I'd bring that strength to the team's current goal, and I'd report what moved. I have the detail under each number, including what I would measure again. That is the minute: the product manager work, the proof, and the reason.

That sample is about 58 seconds at 150 words a minute. Edit the career changer version if the facts are not yours. They should not be. The builder is there so you can swap in numbers you can defend.

Nurse

I'm looking for an ICU nurse role. For the past 5 years I've worked as a medical-surgical nurse at a community hospital. Before that, the results are specific. I precepted 9 new nurses who all passed orientation on time. I also cut medication-scan misses on my shift from 14 a month to 3. The way I work, when it counts, is staying calm and specific when a patient's status changes. What I want next is this ICU nurse seat, because this ICU's patient mix matches the acute work I know, and I want to learn the rest with a preceptor. In the job I'd bring that strength to the team's current goal, and I'd report what moved. Those results are the kind of work I want to keep doing as an ICU nurse. I can explain the constraint behind the first result and the number I was willing to defend.

That sample is about 60 seconds at 150 words a minute. Edit the nurse version if the facts are not yours. They should not be. The builder is there so you can swap in numbers you can defend.

No experience

I'm looking for a customer service representative role. I've worked as a student who covers a campus service desk. Before that, this is the work that got me here. I kept a Saturday desk moving when two coworkers called out. I also turned 14 angry returns into exchanges in one quarter. The through-line is staying patient without losing the next step. The future I'm aiming at is a customer service representative role, because I want a support role where that calm is the job, and I can learn the product on purpose. In the job I'd bring that strength to the team's current goal, and I'd report what moved. I have the detail under each number, including what I would measure again. That is the minute: the customer service representative work, the proof, and the reason.

That sample is about 54 seconds at 150 words a minute. Edit the no experience version if the facts are not yours. They should not be. The builder is there so you can swap in numbers you can defend.

A few patterns show up across those levels. The new grad does not pretend to have a career. The career changer names the move and translates one result, instead of apologizing or pretending the old job was the new job. The nurse names a unit and a safety result, not a calling. The candidate with no formal experience says so, then uses a real desk shift. None of them start with “ever since I was young.”

More role-specific samples, each with the builder already filled in:

• Software engineer
• Senior software engineer
• New grad
• Career changer
• Product manager
• Data analyst
• Data scientist
• Nurse
• Teacher
• Sales
• Customer service
• No experience
• Manager
• Internship
• Marketing
• UX designer
• Project manager
• Accountant
• Consultant
• Bootcamp grad
• Engineering manager
• Human resources

Mistakes that make a true story sound weak

The life story. You start with where you were born or why you chose the major. By the time you reach the job, the interviewer has picked the next question and is waiting for an opening. The fix is ruthless. The first sentence contains the role you want.

The resume in order. You mention every company because leaving one out feels dishonest. It is not dishonest. It is editing. The jobs you leave out can appear when they ask you to walk through the resume. In this answer they compete with the result you needed them to hear.

The tool pile. Languages, certifications, methodologies, software brands. One clause is plenty if the posting requires the tool and you have used it. A sentence made only of proper nouns is not proof. Proof is a change in the world: a faster close, a quieter on-call, a class that learned the skill, a quota, a queue.

The apology. Career changers and people with gaps do this most. “I know I don’t have the typical background, but…” spends the opening on the objection. State the direction and the proof. You can answer the objection later if they raise it. Many of them will not, once the proof is specific.

The missing future. You end on the past, and the interviewer has to ask why you want the job. That question is fine, but you have used your free chance to answer it. The last two sentences are the only part you must rewrite for every company. Candidates who reuse them sound like they applied in bulk, because they did.

The fake precision. You upgrade “helped with retention” into “owned a 12-point lift” because the sentence sounds better. It does sound better, for about forty seconds. Then they ask what you changed in week two, and the sentence dies. Use the smaller true number.

The memorized block. You can recite it and you cannot leave it. They ask a clarifying question in the middle and you restart from the top, or you freeze because the next sentence was glued to the previous one. Practice from the three beats. Look away from the page. If you get lost, start the beat again, not the whole speech.

How to practice it

Read the 60-second version once, out loud, with a timer. Note where you add words that are not on the page. Those extra words are the real answer, and they are usually where you run long. Cut there. Then close the laptop and give the answer from memory of the beats: present, two results, why. Record it on your phone if you can stand to listen. You are listening for the number, not for a performance.

Do a second pass where a friend interrupts after the first result and asks “what did you personally do?” If you cannot answer without the rest of the script, the win is too bundled. Split it before the interview, not during it.

On the day, use the 30-second version if the recruiter sounds like they are moving fast. Use the 60-second version otherwise. Keep the 90-second version for when they say “take your time” or “walk me through your background.” Starting with the long one “just in case” is how people talk over a recruiter screen.

When you can say it without the page, practice it as a live question instead of a monologue. Luna sits on a practice call, hears the question, and helps you keep a spoken line if you blank. The facts still have to be yours. A coach, a friend, or a tool can help you deliver a story. None of them can supply a result you did not earn.

Tips before you say it

• Say the 60-second version out loud before you edit it. A sentence that looks fine on the page often runs long or sounds like a memo.
• One number per win. “Improved the process” is a claim. “Cut hold time from 6 minutes to 2” is a result you can be questioned on.
• Stay in order: present, past, future. If you start with where you grew up, the interviewer is waiting for you to arrive.
• Leave a door open and then stop talking. The extra story you add in the silence is usually the one you did not prepare.
• Keep your part separate from the team’s. “We launched” collapses the first follow-up. “I cut the scope, engineering shipped it” survives.

Questions people ask