"Tell Us About Yourself" on an Application: What They Want
The short version: answer with a present-past-future structure — what you do now, the experience that got you here, and what you want next that this role offers. Keep it professional, specific to the job, and tight. On a written application this is your highlight reel, not your life story.
"Tell us about yourself" feels open-ended, which is exactly why it stalls people. But reviewers aren't asking for your biography. They're asking for a quick, relevant snapshot: who you are professionally, why your background fits, and where you're headed. Give them that in a few clean sentences and you've nailed it.
What they actually want
When this appears as a text box on a written application — common in Workday, Greenhouse, and Lever summary fields — the reviewer is skimming for a fast answer to one question: does this person fit the role?
So they're looking for:
- Relevance. The parts of your background that connect to this job, not everything you've ever done.
- A clear professional identity. Who you are at work, in a sentence or two.
- Direction. A sense that this role makes sense as your next step.
What they're not looking for: your hometown, your hobbies, your full career history in order, or anything that reads like a diary entry. The mistake people make is treating it as "tell us your story" instead of "tell us why you fit."
The present-past-future formula
This is the cleanest structure for the written version. Three short moves:
- Present — what you do now and a relevant strength.
- Past — the experience that shaped you, focused on what's relevant.
- Future — what you want next, and why this role fits.
Here's the formula filled in:
"I'm a [current role] focused on [relevant area], where I've [key strength or result]. Before that, I spent [time] in [relevant experience] that built my [skill]. I'm now looking to [goal], which is exactly what drew me to this role."
Notice it moves in one clean arc and lands on this job. That last line is what makes it feel intentional rather than generic.
A worked example
Say you're a customer support specialist applying for an account manager role:
"I'm a customer support specialist who's spent the last three years turning frustrated users into loyal ones — my retention numbers led the team last quarter. Before support, I worked in retail, which taught me how to read people and solve problems on the spot. I'm ready to move into account management, where I can own relationships start to finish, and that's exactly what this role offers."
Three sentences, present-past-future, every line relevant to the job. No fluff, no life story, and a clear reason this role is the next step.
What to leave out
This field is a highlight reel. Cut anything that doesn't earn its place:
- Your full life story. Where you grew up, your family, your hobbies — unless one genuinely connects to the role.
- Weaknesses. There's a separate question for that. Don't volunteer them here.
- Salary needs or why you left past jobs. Off-topic and risky in an opening summary.
- A chronological dump. You're not reciting your resume in order; you're curating.
- Vague filler. "I'm a hard-working team player" says nothing. Show it with a specific.
If a line doesn't help the reviewer see your fit, it's taking up space.
Written vs. spoken: what changes
The same structure works for the interview, but the written version has different rules. Here's the difference at a glance:
| Written application | Interview | |
|---|---|---|
| Length | Short paragraph, 3-5 sentences | 60-90 seconds spoken |
| Reading style | Skimmed quickly | Heard in full |
| Best wording | Concise, specific, scannable | Conversational, a little more story |
| First line | Must hook fast — reviewers skim | Can warm up slightly |
| Editing | Revise until tight | Practice out loud |
The written version rewards brevity and specificity because reviewers move fast. If anything, err shorter than you think.
Tailor it, then keep it tight
The structure stays the same across applications, but the specifics should shift to match each posting. Pull the strength and goal that line up with what the role emphasizes.
A few practical notes for the written box:
- Lead with your most relevant strength. Don't make them dig for it.
- Match the length to the field. A small box wants 3-4 sentences; a larger one can take a short paragraph.
- Read it back as a stranger. Does it answer "why does this person fit?" in five seconds? If not, trim.
This is one of the open-ended fields worth real effort, which is why it helps to not burn your energy on the repetitive ones. JobRizzer autofills the standard fields — name, contact info, work history, authorization — across the major ATS platforms from your saved profile, so the time you'd spend retyping basics goes into tailoring answers like this one instead. You review and submit every application yourself.
The bottom line
"Tell us about yourself" on an application is a relevance test, not a biography prompt. Use present-past-future, keep it to a few specific sentences, and land on why this role is your next step. Leave out the life story, the weaknesses, and the filler — your job here is to make the reviewer see, fast, that you fit.
For the questions that pair with this one, see our hub of common application questions, or go straight to the spoken "tell me about yourself" answer, how to answer "what makes you a good fit", and where do you see yourself in 5 years, which picks up the "future" part of your story.
FAQ
What should I write for "tell us about yourself" on an application?
Use a present-past-future structure: what you do now, the relevant experience that got you here, and what you want next that this role offers. Keep it professional and tied to the job. Three to five sentences is usually plenty for a written box.
Should I include personal details?
Keep it work-relevant. A brief personal note is fine if it genuinely connects to the role, but skip your full life story, hobbies, and family details. Reviewers want a quick read on whether you fit the job, not a biography.
How is the written version different from the interview answer?
The interview answer is spoken and can be 60-90 seconds; the written version should be tighter and skimmable, usually a short paragraph. The structure is the same, but written answers reward concise, specific wording because reviewers skim quickly.
What should I leave out?
Skip your weaknesses, salary needs, why you left past jobs, and anything off-topic. This field is your highlight reel, not your full history. Lead with what's most relevant to the role you're applying for.