How to Answer “Tell Me About Yourself”
It is the first question in almost every interview, it sets the tone for the next forty minutes, and it is the one people prepare least. Most candidates either recite their CV chronologically or freeze and say “well, what would you like to know?”. Both waste the only moment in the interview where you get to decide what the conversation is about.
The short answer
Answer in three parts, in this order: who you are professionally right now, one or two pieces of evidence that match this job, and why you are in this room. Sixty to ninety seconds. Present, past, future — in that order, not the other way around.
The reason present comes first is simple: the interviewer is deciding whether to keep listening. Starting with “I graduated in 2014…” spends your best seconds on your least relevant fact.
Part 1: who you are now (10–15 seconds)
One sentence. Your current role, your domain, and roughly how long you have been doing it. No adjectives about yourself — “passionate”, “results-driven” and “hard-working” are invisible to an experienced interviewer because everyone says them.
“I'm a commercial lawyer — seven years, mostly M&A and contract work in fintech.”
Part 2: the evidence (30–45 seconds)
Two examples, chosen because they match this job description, not because they are your favourites. Each one needs a number or a concrete outcome. This is the part that decides whether the rest of the interview is easy or hard: whatever you mention here is what they will ask about next, so you are effectively choosing the topics.
“Last year I led the legal side of an acquisition — €40 million, six weeks from term sheet to signing. Before that I rebuilt our contract templates, which cut the average review time from nine days to two.”
Part 3: why you are here (10–15 seconds)
Connect your direction to their role. Not flattery about the company — a reason that would still make sense if they were a competitor.
“I want to move from supporting deals to owning the legal function end to end, which is what this role is.”
Four example answers
Software engineer: “I'm a backend engineer, six years, mostly distributed systems in Go. Right now I own the payments service at my company — about 400 requests a second, and I led the migration that took p99 latency from 900ms to 120ms. Before that I built our event pipeline. I'm looking for a place where I can work on systems at a larger scale, which is why this role interested me.”
Product manager: “I'm a PM in B2B SaaS, five years. I own onboarding at my current company — we took activation from 31% to 52% over three quarters by rebuilding the first-run experience. Before that I ran the integrations roadmap. I'm looking for a product where I own a full P&L rather than one funnel.”
Sales: “I've sold enterprise software for eight years, currently mid-market in Germany. Last year I closed €2.1M against a €1.6M target, and I built the outbound motion our team still uses. I'm interested in this role because it's a move into a longer, more technical sale, which is the direction I want.”
HR / People: “I'm an HR business partner, six years, mostly in fast-growing tech. I currently support two engineering orgs, about 200 people — I rebuilt our performance cycle last year and cut voluntary attrition from 18% to 11%. I want to move into a role with more say in how the org is designed, not just how it's run.”
Four mistakes that waste the question
- Starting with your education. Unless you graduated this year, it is the least relevant thing about you and it burns your best seconds.
- Telling your whole career chronologically. Three minutes of history, and the interviewer has stopped listening by the second job.
- Answering personally. “I'm from Lisbon, I have two cats and I love hiking” is charming and tells them nothing about whether to hire you. Save it for the small talk at the end.
- Listing adjectives. “Motivated, detail-oriented team player” is what someone says when they have no evidence. One number beats ten adjectives.
Preparing without memorising
Do not write a script and learn it — it sounds like a script, and the moment the interviewer interrupts you lose your place. Write down six bullet points instead: one for who you are, four candidate pieces of evidence, one for why this role. Then say it out loud three times, differently each time. You want the content memorised, not the sentences.
Pick which two pieces of evidence to use only after you have read the job description. The same person should give a different answer to a startup and to a bank.
If you freeze anyway
Interviews are stressful and prepared answers evaporate. Interview Copilot listens to the interviewer and shows you an answer in your own voice, in real time — built from your CV, so the examples are yours rather than invented. It works for any profession, and it stays invisible during screen share on Zoom, Meet and Teams.