Tell Me About Yourself — the Thread, Not the CV

P61.career-narrative.01 · Audience: guest, it-ml, language-pro

Shaping a Story — Stakes, Action, Change Why This Role, Why This Company

LLM grading (this page):Real gradingOff — no LLM calls

"Tell me about yourself." Four words, and most candidates reach for the CV: born here, studied that, first job, second job, third job — a chronology delivered in the order it happened, ending wherever the clock runs out. The interviewer already has the CV. What they do not have, and what the question is actually probing for, is whether you can say what it all adds up to. A list of jobs is data; a career is a claim. This module teaches the difference: finding the one thread that runs through your working life, building it into a present–past–future answer, and bending the same thread toward whichever role is across the table.

🗺️ So far you have built: nothing yet — this is where the Motivation & Fit pillar opens. The raw material is not a textbook: it is your own working life, whatever field it happens to be in. If you have met the Answer Structure pillar (P60), you know how to shape a single story; this track is about the story that contains all the others — the account of your career itself.

In this module you will: the through-line technique: your career as one coherent thread rather than a chronology; the present–past–future architecture that turns the thread into a 90-second answer; tailoring the thread to the role in the room; and 'where do you see yourself in a few years' answered as the same thread extended forward. It closes on a two-rung ladder where you write your own through-line, then your own full answer — mentor-graded, your real career as the material.

Step 1 / 6 — The question behind the question

No interviewer asks "tell me about yourself" to learn your dates of employment — those are printed on the page in front of them. The question is a test of selection and self-knowledge: out of everything that has happened to you, what do you consider the point? A chronology answers a question nobody asked and fails the one they did, because it makes the listener do the summarising you were supposed to have done.

ⓘ Concept: They have the facts; they are asking for the meaning

'tell me about yourself' = 'what does your career add up to, and why does it lead here?'

Why it matters — Whoever tells the story of your career frames it. If you recite the CV, the interviewer builds their own story from it — and they may build the wrong one, or none at all. Answering well means arriving with the interpretation already made: what connects these jobs, what you were reaching for, why the next step is this room. That act of selection is itself the evidence the interviewer wants — it shows you can find the signal in a pile of facts, starting with your own. The same failure has a name in every craft: a report that is all data and no finding, a lesson that is all material and no point. The CV is the data. You are being asked for the finding.

✅ Key takeaways

'Tell me about yourself' asks for the meaning, not the facts — the interviewer has your CV; what they want is your own one-sentence account of what it adds up to. Reciting the chronology hands them the summarising work you were supposed to arrive with.
A through-line is the one pursuit you kept getting better at across job titles — specific enough to be almost surprising, and strong enough to explain your last two or three moves without strain. It compresses six jobs into one claim plus evidence, and turns pivots from apologies into chapters.
The architecture is present–past–future, about 90 seconds: open with who you are now (the thread), back it with two or three past proof points, end on why the thread leads to this role — so the last thing they hear is the bridge to the job.
Tailor the evidence and the ending, never the thread: choose which proof points to surface and phrase the future for the room, but keep the pursuit itself fixed. One thread with several tellings is preparation; several threads is fiction that follow-up questions will snap.
'Where do you see yourself in a few years?' is the same thread extended forward — growth in the direction you are already moving, with this role placed explicitly on the line. Specific about direction, unspecific about titles.
The thread named here is load-bearing for the whole track: the interviewer's inevitable follow-up is 'so why us?', and the next module answers it as your thread meeting their specific problem — an answer built from research, not flattery.

Next: P61.career-narrative.02 — Why This Role, Why This Company

The thread you name here is load-bearing for the whole track: the why-this-company answer of the next module is the thread meeting their problem, and the strengths of the module after that are the thread's sharpest edges. Step back any time to the P61 pillar overview to see where this track is heading.

Ask the mentor about this module

Ask a question about this content. The mentor explains and grounds its answer in what you are studying; asking is recorded as a learning signal, not a grade.

Images, PDF or text. Kept on this device only.

Keeping your files on this device

Keep a copy of the files I attach, in this browser

Off by default. The mentor always gets your file; this only decides whether your own copy stays here. Copies live in this browser only - they do not follow you to another device, and clearing site data removes them.

Ctrl/Cmd + Enter to send

🎓 Practice ladder

2 graded rungs · ~20 min

Now write it about yourself. Both rungs are mentor-graded craft exercises on your own material: rung 1 distils your career into a two-sentence through-line; rung 2 builds the full 90-second answer on the present–past–future architecture. The mentor grades the telling, never the career — and you may substitute a low-stakes or invented example anywhere you prefer.

Rung 1 — Your through-line in two sentences (explorer)

Loading exercise…

Rung 2 — The 90-second answer (practitioner)

Loading exercise…

Try it yourself

A scratch console for this page's ideas — ungraded, nothing you run here is recorded.

Scratch console

A scratch console with the scientific stack (pandas, numpy, scikit-learn). Runs on the server — no network, resource-limited and measured.

Output appears here.

My notes on this module

Loading your notes...

Where next?

Continue

Why This Role, Why This Company →

Career Narrative · P61

Later in Career Narrative

This module unlocks

Strengths & Weaknesses Without Clichés

Go up a level