Self-presentation
How to answer: “Tell me about yourself”
The opener that sets the frame for the whole interview. Deliver a 60-90 second present-past-future arc, not a resume read-out.
Why it is asked
What this question is really testing
This is almost always the first question, and it is the single highest-leverage answer you give all day. It is not a memory test of your resume; the interviewer already has that. They are checking whether you can take an open prompt and shape it into a clear, relevant narrative under mild pressure, which is exactly what you will do every day on the job when someone asks what you are working on.
The biggest mistake is treating it as autobiography. Strong candidates use a present-past-future structure: start with who you are professionally right now, give one or two pieces of past evidence that earned you that present, then pivot to why this specific role is the logical next step. That last pivot is what separates a forgettable answer from one that makes the interviewer lean in.
Aim for 60 to 90 seconds. Longer and you lose the room; shorter and you look unprepared. Practice it out loud until the shape is automatic but the words still sound like you, not a script.
The signal
What interviewers listen for
- A clear professional identity in the first sentence, not a slow build-up.
- Relevance: every detail connects to the role you are interviewing for.
- Evidence of impact, with at least one concrete outcome rather than responsibilities.
- A deliberate close that hands the interviewer a reason to keep going.
Worked example
A STAR answer you can adapt
Scenario: Mid-level backend engineer changing companies. Read it for the shape, then swap in your own story.
Situation
I am a backend engineer with five years of experience, currently at a fintech where I own the payments service that handles about two million transactions a day.
Task
When I joined, that service was the team's biggest source of on-call pages, so I was asked to make it boring.
Action
I led a rewrite of the reconciliation pipeline, added idempotency keys end to end, and built the dashboards the team had been missing, all while keeping the migration zero-downtime.
Result
On-call pages for payments dropped by roughly seventy percent and we have not had a customer-visible incident in eight months. I am looking to move because I want to work on systems at a larger scale, which is why this role stood out to me.
Answer skeleton
Fill-in-the-blank template
I am a [identity] with [N years] in [domain], currently [present role + scope]. Earlier I [one past proof point with a result]. Now I am looking to [future], which is exactly why [this role] caught my attention.
Avoid these
Common mistakes
- Reciting your resume in chronological order from your first job onward.
- Going over two minutes and watching the interviewer's attention drift.
- Including personal life details that add no professional signal.
- Ending flatly instead of pivoting to why you want this role.
By role
How the answer shifts by role
Engineering
Lead with the systems you own and one quantified reliability or scale outcome. Avoid a tour of every language you know.
Product management
Frame your identity around the outcomes you drove and the bets you made, not the features you shipped. Mention the metric you moved.
Engineering management
Anchor on team and org impact: the size of team you grew, the delivery you unblocked, and how you think about people, not just systems.
Be ready for
Likely follow-up questions
- What made you decide to leave your current role?
- Tell me more about that project you mentioned.
- Why this company specifically, out of everywhere you could go?
Last reviewed by the site editor: June 2026
Nearby topics
Questions that often follow this one
Interviewers rarely stop at one story. These prompts sit close to this one and reward the same preparation.
Turn prep into an offer
Behavioral rounds are only half the loop. See the technical and behavioral questions for your exact role, and when an offer lands, check it is competitive with the salary comparison tool.