How to answer "tell me about yourself" without rambling

The 90-second answer framework

Use this order when you prepare:

1. Current frame: what you do now, in one sentence.
2. Proof: one concrete example that matches the role.
3. Pattern: the kind of work you keep getting trusted with.
4. Bridge: why this company or role is the logical next conversation.

The proof comes before the biography. That is the Koru angle: your answer should be built from evidence you can defend, not a summary of every job you have had.

Why people ramble

It's not nerves, though nerves don't help. It's that you're doing two things simultaneously: deciding what's relevant and articulating it clearly. That's too much cognitive load for a high-pressure moment. Your brain picks the safest structure it knows, chronological order, and off you go.

The chronological approach feels safe because it's complete. But completeness is the enemy of clarity. The interviewer doesn't need your whole career. They need the version of your career that explains why you're sitting in this specific chair.

The sorting framework

Before the interview, answer three questions about this specific role. On paper, not in your head.

1. Sort: what problem are they hiring someone to solve?

   Read the job description past the buzzwords. What's the actual gap? A team that's growing too fast? A product that needs a technical overhaul? A customer segment that's being underserved? Every role exists because something isn't working yet.

2. Match: which 2-3 parts of my experience prove fit?

   Out of your full career, which roles, projects, or skills are relevant to the problem you identified? Everything else gets cut. Your first job in a different industry? Cut. That management role that taught you a lot but has nothing to do with this position? Cut.

3. Anchor: what should they remember after the call?

   If the interviewer forgets everything else, what should stick? "She scaled a platform from 10K to 500K users." "He turned around a team that was missing every deadline." One sentence that anchors you in their memory.

Those three answers are your "tell me about yourself" structure. Everything else is noise.

Examples by seniority and function

Early-career marketer: "I am a lifecycle marketer focused on turning user behavior into clearer onboarding messages. In my last role I rebuilt the first-week email flow after support tickets showed users were missing one setup step. Activation improved, and the sales team reused the same language in demos. I am looking for a role where I can keep working close to product usage, not just campaign calendars."

Senior engineer: "I am a backend engineer who tends to get pulled into reliability problems. Most recently I led the retry and idempotency work after payment webhooks created repeated support escalations. The fix reduced manual cleanup and gave support a clearer runbook. This role is interesting because the infrastructure has real customer consequences, not just internal elegance."

People manager: "I manage teams through ambiguous delivery work. This year I changed planning so risks were written before the meeting instead of discovered during it. The team caught dependency issues earlier and quieter engineers had more influence on technical decisions. I am looking for a manager role where coaching and operating cadence matter as much as roadmap ownership."

The structure that works

Forget "present-past-future." It's overused and tends to produce generic answers. Instead:

Total: about 90 seconds when spoken aloud. Specific enough to be memorable. Relevant enough to prompt good follow-ups.

Same person, different role

The important thing about this structure: it changes for every application. The same career produces different answers depending on the role.

Same career, same person. Different selections because the problem each company is trying to solve is different.

What to cut

This matters as much as what you include. Cutting is hard because everything feels relevant when it's your own career. It's not.

The sorting gets easier with a record

The three-question framework is easy if you have a record of your career achievements tagged by skill and theme. You search for what matches the role, pick 2-3 highlights, done. It's hard if you're trying to remember your entire career in real time while someone watches you think.

But even without a system, the three questions work. They just take longer to answer because you're working from memory instead of records.