"Tell Me About Yourself": The Resume-Anchored Answer That Works

It opens almost every interview, and it's not small talk. "Tell me about yourself" is two tests wearing a friendly face: can you communicate under mild pressure, and — less obviously — does what you say match the resume in front of me?

That second test is why the answer should be built from your resume, not improvised alongside it. The interviewer is holding your document, half-reading it while you talk. Alignment reads as credibility; drift reads as embellishment — of the answer, or of the resume.

The 90-second structure

Three movements, in this order:

1. Present, framed for them (~20 seconds)

One sentence about who you are professionally — using the same framing as your resume summary, aimed at their role:

"I'm a frontend engineer, six years in, mostly building B2B SaaS dashboards — the last two focused on accessibility, which is a big part of why this role caught my eye."

If you followed our resume summary formula, this sentence already exists. Say it, don't recite it.

2. Two proof points from your resume (~50 seconds)

Pick the two bullets from your resume most relevant to this job — the same ones you moved to the top when tailoring it — and give each three sentences: situation, what you did, the number.

"At Acme I led our WCAG compliance effort — we went from failing audits to AA across twelve apps in about nine months, and I got to build the design-system side of that. Before that, at WebStudio, I shipped fifteen client storefronts, which is where I learned to work fast without breaking accessibility."

Why these two and not your whole history: the interviewer will probe what you mention. You're choosing the terrain for the next ten minutes. Choose bullets you can go three questions deep on — which, if your resume is honest, is all of them. (This is also the interview's revenge on keyword-stuffed resumes: every invented line is a trap you set for yourself.)

3. Why here, why now (~20 seconds)

Close by pointing forward, specifically:

"I'm looking for a place where accessibility is a product priority rather than a checkbox — and the fact that this role reports into product, not compliance, is exactly that."

That specificity comes from the job description — the same document you mined for keywords. Generic closers ("I'm excited about new challenges") waste the slot.

Tailor it per company (ten minutes, not an hour)

The structure is stable; slots change per application:

• Movement 1's "why this caught my eye" → from the job's top requirement.
• Movement 2's two proof points → whichever resume bullets best match this job description.
• Movement 3's specifics → one true detail about the role, team, or product.

If you tracked which resume version you sent (your pipeline has it), building the answer takes minutes: open that version, take its top two bullets, done.

Practice out loud — three times, not thirty

Once silently to structure it, twice out loud to find the phrases that don't fit your mouth. Stop before it sounds memorized; the goal is knowing your three beats, not your three paragraphs. Time yourself once — under 90 seconds, always. If you want pressure-testing with follow-up questions, Job SuitUp's mock interviewer asks them based on your actual resume and the actual job description — including the uncomfortable ones about your gaps.

What not to do

• The chronological life story — "I was born in…" or even "I started my career in 2014…" walks through everything and emphasizes nothing.
• Two minutes plus — past 90 seconds, you're answering questions nobody asked.
• Hobbies as filler — unless directly relevant, they dilute the six seconds of attention this answer gets, same as on the resume.
• Contradicting your resume — different titles, different numbers, different emphasis. The document and the answer are one story told twice.

FAQ

Should the answer be different for a recruiter screen vs. the hiring manager? Same structure, different depth. Recruiters get the 60-second version with clear keyword alignment; hiring managers get the full 90 with more technical meat in the proof points.

What if my resume has a gap or a short stint they'll ask about? Don't hide from it in the opener — but don't lead with it either. Have a one-sentence honest answer ready for the follow-up; the prep kit generates the uncomfortable questions on purpose.

Can I use the same answer for every company? The skeleton, yes. Sending the identical answer everywhere fails the same way identical resumes do — movement 3 in particular has to be true of this company, or it's audibly filler.