What is "tell me about yourself" actually asking?

It is asking why you are sitting there, in about ninety seconds. The mistake is treating it as a biography and starting at university; the useful answer is a short arc from what you do now, through what you have done that is relevant, to why this role. It is the only question you can fully prepare, which is why a weak answer to it is so costly.

How do I answer the weakness question without a fake weakness?

Name a real one that is not fatal for this job, and say what you do about it. Interviewers have heard "perfectionism" enough that it now reads as evasion. A genuine limitation plus a concrete mitigation answers the question they are actually asking, which is whether you can see yourself clearly.

What makes a failure story work?

Owning the decision and naming what you changed afterwards. The trap is choosing a failure that was somebody else's fault, which answers a different question, or one so small it reads as evasion. Pick something that genuinely went wrong, say what you would do differently, and show that you did it differently later.

How do I answer "where do you want to be in five years"?

Answer honestly at the level of direction rather than title. Naming a specific job you want in five years invites a comparison with the one on offer; naming the kind of problems you want to be working on says the same thing without the trap. If the honest answer is that you do not know, saying what you want to be better at is a real answer.

Should I have different answers for different companies?

Same stories, different emphasis. Rewriting your material per company is unsustainable and produces thin answers everywhere; re-cutting a story to lead with the part that matches this role takes minutes and works. The stories are the asset — the framing is the per-company work.

What do I say when I genuinely have no example?

Say so, then answer the nearest real thing. "I have not led a team, but I have owned this piece end to end and here is how I handled the coordination" is a good answer. Inventing an example is the worst option available, because follow-up questions are what interviews are made of.

content:contentPage.section.resource

Common interview questions

The questions that come up in most interviews, what each one is really asking, and how to answer without a script.

Last reviewed: 19 August 2026
Length: About 6 minutes
Scope: Maintained, not published. Corrections welcome.

A small number of questions carry most interviews, and they are the same ones nearly everywhere: tell me about yourself, why this role, describe a conflict or a failure, what are your strengths and weaknesses, where do you want to be, and do you have any questions for us. Preparing those specifically is worth more than trying to anticipate everything, because the alternative is composing an answer live to a question you could have seen coming. What follows is what each one is actually asking — which is rarely what it appears to ask — and how to answer it without sounding like something you memorised.

Who this is for

Where it applies.

Drilling the universal openers

"Tell me about yourself" opens most interviews and is the answer people prepare least, because it sounds like small talk. It is not: it is where you decide what the rest of the conversation is about. Sixty to ninety seconds, structured — where you are now, two things worth knowing, why you are in this room.

Building a failure or conflict story you can actually tell

Use a real one and a small one. An invented failure is audible, and a catastrophic one spends the interview on damage rather than on judgement. The part being assessed is what you changed afterwards, which is why a story with no lesson attached lands worse than the failure it describes.

Adapting per role without rewriting everything

The stories stay the same; the emphasis moves. One example can answer a question about ownership at one company and about collaboration at another, depending on which beat you spend the time on. Preparing four flexible stories beats preparing twelve rigid ones.

Drilling the six questions that carry most interviews

A small set of questions appears nearly everywhere, and each has a real underlying ask. Preparing these six well covers more ground than preparing thirty superficially, because most other questions are one of the six in different clothes.

In order

How it works.

List the 10 most common questions for your role type
Tell-me-about-yourself, why-this-role, why-this-company, conflict, failure, leadership, strengths, weaknesses, 5-year-plan, plus 1–2 role-specific. Pin them.
Draft 60–90 second answers using STAR or similar structure
For behavioral: STAR format. For "tell me about yourself": current role + 2 highlights + what you want next. For weaknesses: real weakness, not central to the job, with active mitigation.
Practice each out loud and time-boxed
Answering in your head is faster and clearer than answering aloud, so the version you rehearse silently is not the version that arrives in the room. That gap is where interviews come apart, and the only way to find it is to hear yourself.
Tailor each per role
Same core structure; different specifics per role. Tell-me-about-yourself for a fintech PM role emphasizes payments work; for a consumer PM role emphasizes consumer experience. Reuse structure; tailor substance.
Practice transitions between questions
Real interviews chain questions ("you mentioned conflict — tell me about a time you disagreed with leadership"). Practice the chain, not just isolated answers. Smooth transitions signal preparation; awkward jumps signal scripted answers.

Worked

Worked illustrations.

Constructed to show the shape of the decision, not reported cases. The figures are illustrative.

A candidate drilling tell-me-about-yourself for a fintech PM role

Drafts a 75-second answer leading with current PM role + two payments-related highlights + what they want next. Practices 5 times on video. Real interview: nails the opener; sets tone for a strong full conversation. Offer follows.

A candidate using a real small failure for the failure question

"I underestimated the timeline on a project last year by 3 weeks. Here is what I learned..." Honest reflection lands better than a manufactured "I am too much of a perfectionist" answer that interviewers see through immediately.

A candidate who prepared the opener last

They had six polished stories and no answer to "tell me about yourself", and spent the first three minutes of every interview recovering from a rambling start. Writing ninety seconds and timing it fixed the problem in one evening — and it was the question they had assumed needed no preparation.

Asked often

Questions people bring here.

What is "tell me about yourself" actually asking?: It is asking why you are sitting there, in about ninety seconds. The mistake is treating it as a biography and starting at university; the useful answer is a short arc from what you do now, through what you have done that is relevant, to why this role. It is the only question you can fully prepare, which is why a weak answer to it is so costly.
How do I answer the weakness question without a fake weakness?: Name a real one that is not fatal for this job, and say what you do about it. Interviewers have heard "perfectionism" enough that it now reads as evasion. A genuine limitation plus a concrete mitigation answers the question they are actually asking, which is whether you can see yourself clearly.
What makes a failure story work?: Owning the decision and naming what you changed afterwards. The trap is choosing a failure that was somebody else's fault, which answers a different question, or one so small it reads as evasion. Pick something that genuinely went wrong, say what you would do differently, and show that you did it differently later.
How do I answer "where do you want to be in five years"?: Answer honestly at the level of direction rather than title. Naming a specific job you want in five years invites a comparison with the one on offer; naming the kind of problems you want to be working on says the same thing without the trap. If the honest answer is that you do not know, saying what you want to be better at is a real answer.
Should I have different answers for different companies?: Same stories, different emphasis. Rewriting your material per company is unsustainable and produces thin answers everywhere; re-cutting a story to lead with the part that matches this role takes minutes and works. The stories are the asset — the framing is the per-company work.
What do I say when I genuinely have no example?: Say so, then answer the nearest real thing. "I have not led a team, but I have owned this piece end to end and here is how I handled the coordination" is a good answer. Inventing an example is the worst option available, because follow-up questions are what interviews are made of.

Worth knowing

Small things that help.

A small number of questions cover most behavioural interviews. Drill those rather than trying to anticipate everything.
Memorise the structure, not the words. A rehearsed sentence is audible and a rehearsed shape is not.
Sixty to ninety seconds is the target for an opener. Longer stops being an answer and becomes a monologue.
Use one real, small failure. Inventing one is the thing an interviewer is best at detecting.
Practise out loud and timed. The version in your head is faster and clearer than the one that arrives.
Have questions of your own that you actually want answered. The ones asked to look interested are recognisable as such.

ClearHire Editorial

Written to be corrected. If something here is wrong, say so and it changes.