Behavioral · Stories with evidence

Tell me about yourself.

Easyintroductioncareer narrativecommunicationUpdated Oct 2026
Quiz this track

Short answer

Give a 90-second arc: current scope and role, two or three accomplishments with outcomes, then why this role is the logical next step. Anchor the story to what the job needs.

This is not an invitation to narrate your resume. The interviewer is testing whether you can summarise your professional identity and connect it to the role in front of you. Aim for roughly 90 seconds and leave obvious threads for them to pull.

A structure that holds up

  • Present: your current role, team size and the surface you own
  • Evidence: two or three accomplishments stated as problem, action and measurable result
  • Transition: the specific gap or opportunity that makes this role the right next step
  • Close with a hook, such as a problem you want to work on, rather than a summary

Pick evidence that matches the job description. If the role is platform-heavy, lead with reliability or developer-experience work. If it is product-heavy, lead with user impact and shipping cadence. Cut anything that does not support that thesis, even if you are proud of it.

Avoid a chronological life story, personal trivia and vague adjectives like passionate. Every sentence should either establish scope or prove impact.

Follow-ups you should expect

Interviewers use these to check whether the first answer was understanding or memorisation.

  1. 1Which of those accomplishments are you most proud of, and why?
  2. 2What is the through-line across these roles?
  3. 3What would your last manager say is your biggest gap?
  4. 4Why is this the right next step rather than a lateral move?

Say it in the interview

I am a product engineer with about six years of experience, currently owning the checkout surface for a mid-sized marketplace. Last year I led the migration of our payment flow to a new provider, which cut failed transactions by roughly a fifth and reduced support tickets. Before that I built the internal tooling that let our support team resolve refunds without engineering help. I am looking for a role where I can pair that product sense with deeper platform ownership, which is exactly the scope here.

Use this as a model, not a script. Saying it in your own words is what makes it survive follow-up pressure.

Related questions

Reading is step one

Now say it out loud.

Understanding an answer and delivering it under pressure are different skills. Rehearse this topic in a live Behavioral mock interview and get scored feedback on depth, clarity and confidence.