The way to answer "tell me about yourself" is to give a short, structured pitch in three parts: what you do now, how you got here, and what you want next, with each part pointed at the job you are interviewing for. Keep it to about 60 to 90 seconds, which is roughly 170 to 260 spoken words. It is usually the first question of a recruiter screen, and that round decides a lot: Ashby's 2026 Talent Trends report, built on over 54 million applications, puts the pass rate at the recruiter screen at about 35%, against 95% after the onsite. Below are the formula, the timing math, ten sample answers and a written version for application forms.
The formula: present, past, future
The structure most career advice converges on has three parts. The Muse credits it to career coach Lily Zhang and describes it in its guide (updated March 2025): talk about your current role and "perhaps a big recent accomplishment", then tell the interviewer how you got there, then explain what you want to do next and why this role fits.
| Part | What to say | Share of the answer | Test |
|---|---|---|---|
| Present | Your current role, degree or situation, plus one specific result | About 40% | Would the interviewer remember one detail? |
| Past | The two or three steps that explain how you got here | About 30% | Does each step connect to this job? |
| Future | What you want next and why this role, at this company, fits | About 30% | Could you say it only to this employer? |
The shares are our suggestion, not a rule. The order can change too: The Muse notes you can open with a strong story from your past and then come forward, which suits career changers whose reason for switching is the interesting part.
The formula is not your life story, and it is not your resume read aloud in order. The interviewer has the resume. They want the version of it that explains why you are applying for this job and gives them something to ask about next.
How long to talk
There is no measured ideal length. The Muse looked at the range of advice and found it all over the place: "keep it to 30 seconds or less", aim for "a minute", or "no more than two minutes". It quotes career coach Al Dea, who sees people "start losing steam after 1.5 to 2.5 minutes of uninterrupted talking". The "45 to 90 seconds" figure that search summaries repeat is a reasonable rule of thumb, but we found no study behind it either.
We use 60 to 90 seconds, and the useful part is turning that into words you can draft. In a 2005 analysis of 11,700 conversation sides in the Fisher English corpus of recorded phone calls, linguist Mark Liberman at the University of Pennsylvania measured a mean speaking rate of 172.7 words per minute. Native American English speakers came out at about 173 to 174 words a minute, men and women alike.
| Target length | Words at about 173 per minute | What fits |
|---|---|---|
| 30 seconds | about 86 | One line per part. Use when a recruiter says "briefly" |
| 60 seconds | about 170 | One result in present, two steps in past, one fit reason |
| 90 seconds | about 260 | Room for a second result or a short story |
| 2 minutes | about 345 | The upper edge; expect to lose the listener's attention |
Nerves speed some people up and slow others down, so time yourself out loud rather than trusting the arithmetic.
Ten sample answers
These are samples written for this post. The names of schools, companies and products are left generic and every number is illustrative, so replace them with your own. The first nine run between about 110 and 150 words, under a minute at the pace above, which leaves room for pauses and one detail of your own. The tenth is the short version for a phone screen.
1. Computer science new grad, applying for a software engineer role
"I just finished my computer science degree, and the work I am proudest of is a scheduling tool I built with two classmates for our campus tutoring center. It replaced a shared spreadsheet, and about 40 tutors used it every week of the spring term. I wrote the backend in Python and owned the database design, which is where I learned the most, mostly from getting it wrong once. Before that I did a summer internship on a small team that maintained an internal billing service, where I fixed bugs and wrote my first production tests. What I want next is a team that ships to real users often, with code review I can learn from. Your posting talks about owning features end to end on the payments side, and that is the closest thing I have seen to what I enjoyed in both of those projects."
What to cut: the list of languages you know, your GPA, and any class project the interviewer would need context to understand. One project told well beats four named.
2. Data analyst new grad
"I graduated in May with a degree in economics and a minor in statistics, and for the last year I have worked part time as a research assistant cleaning and analyzing survey data for a public policy lab. The project I would point to is a dashboard I built in Tableau that let the lab's director compare response rates by county without asking me to rerun queries. That taught me that the analysis is only half the job and the other half is making it usable. I got into data through an intro econometrics class where I realized I liked the question of whether a number could be trusted more than the number itself. I am looking for an analyst role where I would work close to the people making decisions, which is why the operations analytics team here stood out."
What to cut: the full tool list (SQL, Python, R, Excel, Tableau). Name the one tool that produced the result and let the interviewer ask about the rest.
3. International student on F-1 OPT, applying for a machine learning role
"I am finishing my master's in data science, and my capstone was a model that flags likely late shipments for a regional distributor we partnered with. The interesting part was not the model but the data: half the delivery records had missing timestamps, and I spent most of the project building a way to fill them that the operations team agreed with. Before my master's I worked for two years as a data engineer, mostly building pipelines, so I am comfortable on the unglamorous side of machine learning. I want a role where I build models that get used in production and not just in notebooks. Your team's posting mentions forecasting for supply planning, which is close to my capstone and to the pipeline work I did before."
What to cut: the visa explanation. It does not belong in this answer unless the interviewer asks, for the reasons in the visa section below. Also cut the story of why you chose to study in the United States, unless the role is about something that story proves.
4. Career changer, teacher to instructional designer
"For six years I taught high school chemistry, and the part of the job I kept getting pulled into was building materials, not delivering them. Two years ago I redesigned our department's lab safety course as a short online module, and it became the version every new student took. That project is why I am here. Since then I have finished a certificate in instructional design, built a portfolio of three e-learning modules, and spent this summer doing contract work for a nonprofit's volunteer training. What I bring that most designers do not is years of watching what happens when the learners are actually in the room. I want to do that work full time, and your team's focus on onboarding training for field staff is close to what I did with the safety course."
What to cut: any apology for leaving teaching, and the reasons you are unhappy in your current field. Frame the move as a direction, not an escape.
5. After a layoff, product manager
"I have been a product manager for five years, most recently at a logistics software company, where I owned the carrier onboarding product. The result I would point to is cutting the time it took a new carrier to go live from about three weeks to one, mostly by removing steps we had assumed were required. In June my whole team was cut in a restructuring, which gave me the chance to be deliberate about what comes next. Before that role I started as a support engineer, which is why I still read support tickets every week. I am looking for a B2B product with a messy operational side, where the job is as much about process as features. Your posting for the integrations team reads like that."
What to cut: the details of the layoff, how you feel about it, and anything negative about your former employer. One plain sentence, then move on. Our guide to reason for leaving answers covers how to word it on a form.
6. Sophomore, applying for a summer internship
"I am a second-year computer engineering student, and outside of classes most of my time goes to our robotics team, where I write the code for the drive system. Last season I rewrote our motor control so the robot stopped drifting during matches, which was the first time something I wrote had a visible effect on a result. I got into engineering by fixing old laptops for friends in high school, which turned into a small side business. This summer I want to work on a real codebase with people who are better than me, and your internship's focus on embedded firmware is exactly the part of the robotics work I like most."
What to cut: high school achievements beyond one line of origin story. If it happened before college, it needs to explain something about now.
7. Bootcamp graduate, applying for a front-end role
"I finished a full-stack bootcamp in the spring after four years working in retail management. Since then I have built and shipped two projects that people use: a booking page for a local yoga studio and an accessibility audit tool I wrote after realizing how many small business sites fail basic screen reader checks. The audit tool taught me more about HTML than the bootcamp did. Retail management sounds unrelated, but it is where I learned to take a complaint, find what actually broke and fix it fast, which is most of front-end work. I am looking for a team that cares about accessibility, and your posting's line about WCAG compliance is the reason I applied."
What to cut: the bootcamp's curriculum. The interviewer wants what you built after it, not what it taught.
8. Mid-career backend engineer
"I am a backend engineer with six years of experience, the last three on a team that runs the order service for an online retailer. The project I am proudest of was splitting a single overloaded database into two, which we did without downtime during the busiest month of the year. I led the migration plan and wrote most of the tooling for the cutover. Before that I spent three years at an agency building APIs for different clients, which is where I learned to work in codebases I did not design. Next I want to work on systems with more scale and fewer people, where one engineer's decisions carry further. Your platform team seems to be that kind of group."
What to cut: the full chronology. Two jobs explained well are better than five jobs listed. Save the technical depth for the follow-up questions.
9. Returning after a gap, operations coordinator
"I am an operations coordinator, and I am returning to work after two years caring for a family member full time. Before that I spent five years coordinating vendor schedules for a property management company with about 60 buildings, and I built the shared calendar system the team still uses. During the two years away I kept a hand in by managing the books and schedules for a small community clinic as a volunteer. I am ready to be back full time, and I want a role with a lot of moving parts and people who rely on things running on time, which is how your facilities coordinator posting reads."
What to cut: the medical or family details of the gap. One sentence is enough, and you choose how much to say.
10. The 30-second version for a recruiter phone screen
"I am a data analyst finishing my first year at a regional bank, where I build the weekly reporting on loan applications. The thing I have done that I like most is automating a report that used to take a full day by hand. Before that I studied mathematics. I want to move into product analytics, closer to customer behavior, which is why this role caught my eye."
What to cut: everything else. On a short screen with a list of questions, the short version is a courtesy, and the recruiter will ask for more.
What to cut from each
The same five things come out of almost every first draft.
| Cut this | Why | Keep instead |
|---|---|---|
| A list of skills or tools | Nobody remembers a list | The one tool that produced your result |
| Personal history before your field | It spends the opening on context | One sentence of origin, only if it explains your direction |
| Generic adjectives ("passionate", "hard-working", "detail-oriented") | Every candidate says them | A result that shows the trait |
| Negatives about a past employer or field | It becomes the thing they remember | A plain statement of what you want next |
| Information the form already has | It wastes time and can raise questions early | What the form cannot show: how you think |
A quick test: read your draft and underline every sentence the interviewer could not have learned from your resume. If less than half is underlined, rewrite.
Should you mention your visa status
Usually not, and the reason is practical. This answer is your chance to show what you can do. Work authorization is a separate question with its own place in the process.
The US Justice Department's Immigrant and Employee Rights Section (IER), in a September 2022 technical assistance letter, lists two pre-employment screening questions it "has previously identified as appropriate":
- "Are you legally authorized to work in the United States?"
- "Will you now or in the future require sponsorship for employment visa status (e.g., H-1B visa status)?"
The same letter says IER "has repeatedly cautioned employers against using pre-screening questions (beyond the two questions IER has deemed appropriate)". In practice, those two questions often appear on the application form, and recruiters often ask them during the screen. That is the moment to answer them, truthfully and briefly. Our guide to work authorization questions covers how to answer them on forms.
There are two exceptions. If the recruiter has already asked and you know sponsorship is a known issue for the role, a one-line close such as "and I am authorized to work here on OPT, as I noted on my application" can save time. And if your story is the visa (for example, your past includes a move that explains your direction), mention the move and keep the immigration detail out of it. This is general information, not legal advice.
The written version for application forms
Many application forms include a free text box with "Tell us about yourself" or "Describe yourself in a few sentences". Same formula, written. Check the box for a character limit first; when there is none, 100 to 150 words is a good length, because the reader is skimming many applications.
A sample, written for this post:
I am a recent computer science graduate who likes building tools that other people rely on. At university I led the backend for a scheduling app used by our campus tutoring center, and during a summer internship I wrote tests and fixed bugs on an internal billing service. Both projects taught me the same thing: the work that matters most is the part users never see break. I am applying to this role because it involves owning payments features end to end on a small team, which is where I do my best work. I would welcome the chance to talk about how I could contribute.
That is 106 words. Three differences from the spoken version: open with a one-line summary rather than "I just finished", drop filler like "the thing is", and close with a sentence that points at the next step.
Mistakes that cost the first impression
- Asking what they want to hear. A one-word clarifier is fine ("Professionally?"), but "where should I start?" signals you did not prepare.
- A memorized monologue. Learn the three beats and the one result, not the exact sentences. A word-for-word script sounds read.
- No ending. Close on the future and stop. A clean stop invites the next question; trailing off with "so, yeah" does not.
- Saying something you cannot back up. Anything you mention is fair game for a follow-up. If you name a project, be ready to explain your part in it in detail, which is where the STAR method helps.
For the rest of the first round, our guide on how to prepare for an interview walks through what to research and practice.
Getting to the interview
ApplyEze, the product this blog belongs to, works on the step before the interview. It writes a resume for each posting, adds a cover letter when the form asks, and completes applications on 12 platforms, including Greenhouse, Lever and Workday (Workday and Oracle need a connected application inbox), from a desktop app on your own machine. It does not prepare you for interviews. One thing to know if you use it: ApplyEze brings the posting's named skills and tools onto your skills line, even when your own record does not list them. There is no step to remove one before a live run, so use a dry run to see what it writes. Read the version that was sent before your screen, and be ready to talk about every line on it. The interviewer will be reading that version while you answer this question.