Problem and scope
“Tell me about yourself” tests whether a candidate can select role-relevant information, explain contribution clearly, and open useful follow-up. It is not a résumé recitation or a childhood biography. Microsoft’s career toolkit recommends preparing an elevator pitch, and its interview guidance emphasizes concrete examples; this question is categorized as general.
What the interviewer is testing
The interviewer is listening for clear positioning, credible examples, measurable outcomes, fit for the target role, and a natural path to deeper questions. A strong answer states current capability, evidence built in the past, and the problem the candidate wants to solve next, usually in about 60–90 seconds.
Clarifying questions
- Is this a recruiter screen, technical interview, or hiring-manager opening?
- Which two or three capabilities matter most for the role?
- Which experience proves those capabilities rather than merely listing duties?
- Has the interviewer already read the résumé, and what can be skipped?
- Which project or outcome do you want them to ask about next?
- Is there a career change, gap, or industry move that needs one sentence of context?
A 30-second answer framework
“I currently do X as a Y, with a focus on turning A into B. In project C, I used D to move E from metric one to metric two while handling constraint F. I now want to solve G in this role because it combines my H strengths; I can go deeper on that project if useful.”
Step-by-step answer
Step 1: State your professional positioning
Use one sentence for current role, domain, and core capability. For example: “I’m a product manager for B2B data products, focused on turning complex compliance workflows into measurable customer outcomes.” Keep the positioning adjacent to the role and avoid empty adjectives.
Step 2: Choose one or two proofs
Pick projects that demonstrate the requirements, then explain context, your actions, and outcomes. Use real numbers, scope, or change; if the result belonged to a team, state your contribution instead of claiming the entire outcome.
Step 3: Explain a trade-off
Add one important judgment or constraint, such as balancing speed, quality, cost, or compliance. This shows how you think rather than only naming a project and its result.
Step 4: Connect to the target role
Explain why the experience matters for this role and which problem you want to solve. Base the connection on the job description and public facts, not memorized slogans or unverified motivation claims.
Step 5: Close and invite a follow-up
Finish within 60–90 seconds and offer one concrete project to explore. If the interviewer asks for more detail, answer with facts, actions, and results; if they ask for less, retain positioning, proof, and role connection.
Model answer
“I currently own data-export and compliance experiences for a B2B SaaS product, turning high-risk workflows into measurable customer outcomes. In my last role I led a tenant-migration project: after interviewing administrators, we reduced export failures from 18% to 6% while retaining approval and audit records. My contribution was the failure taxonomy and recovery flow, delivered with engineering and support through a staged rollout. I now want to solve complex workflow usability problems in your platform products, which matches my experience in process design, metrics, and cross-functional delivery. I can walk through the migration trade-offs next.”
Common mistakes
- Starting with the first job on the résumé → the timeline buries the point → lead with current positioning and relevant proof.
- Stacking adjectives → no evidence is verifiable → replace “excellent” and “responsible” with actions and results.
- Claiming a team result as personal work → follow-up exposes the mismatch → state boundaries and collaborators.
- Telling a full life story → the answer runs long and cannot be explored → keep one or two proofs.
- Repeating company slogans → motivation sounds generic → connect to role problems and public facts.
- Never closing → the interviewer lacks a next question → leave a concrete project as an entry point.
Follow-up questions
Follow-up 1: How long should it be?
Prepare a 60–90 second version and a 30-second compressed version. Adjust to the interviewer’s time and role level, then let them choose what to explore.
Follow-up 2: How should you mention a career change or gap?
After positioning, use one or two sentences for the change, actions taken, and current goal. Do not litigate every detail; return quickly to evidence of role-relevant capability.
Follow-up 3: What if outcomes were not measurable?
Describe scope, users, duration, decision impact, or quality change, and separate known outcomes from estimates. Never invent numbers to make the story sound larger.
Follow-up 4: How do you avoid sounding scripted?
Keep the structure, not fixed sentences. Memorize three or four keywords, adapt proof to the role, and practice resuming from any point if interrupted.