Behavioural Interviews Module 6 – Motivation, self-assessment and hypotheticals
Tell me about yourself: your career narrative
Answer "Tell me about yourself" with a career narrative: where you are now, two or three highlights with evidence, and why this role, timed at your pace.
What you will learn
- Build a career narrative that links where you are now, two or three highlights and this role
- Choose the highlights a role needs and back each one with evidence
- Rewrite one narrative for a recruiter, a hiring manager and a panel without changing its facts
- Explain a gap, a career switch or a layoff in one or two honest sentences
Before you start
What you’ll learn · Before you start
What you will learn
- Build a career narrative that links where you are now, two or three highlights and this role
- Choose the highlights a role needs and back each one with evidence
- Rewrite one narrative for a recruiter, a hiring manager and a panel without changing its facts
- Explain a gap, a career switch or a layoff in one or two honest sentences
Before you start
On this page
Asked “Tell me about yourself”, Gaurav, an invented backend engineer, starts with his school in Kanpur and ends with cricket: 78 words, half a minute, and not one thing he has done at work. The question opens many interviews, and it asks for a story about your work that leads to this job, not a reading of your resume.
Below, that story is built as a career narrative in three parts: where you are now, two or three highlights with evidence, and why this role fits. You will time it at your own speaking rate, tell the same facts to a recruiter, a hiring manager and a panel, and fit a gap or a career switch into a sentence or two. A program checks every narrative on this page, and it will check yours.
Three parts: where you are, what you have shown, why this role
Employers that publish their interview guidance say what this opening is for. Meta’s interview guide says its behavioural interviewer will ask about your background, “what you’re passionate about in tech, and what kind of impact you want to make”. Atlassian’s early-careers guide describes an elevator pitch: A spoken introduction of under two minutes that says who you are, what you have done and what you are looking for, used with recruiters and at career events. of under two minutes, covering who you are, your professional background and what you want next, and says it sets the stage for a “Tell me about yourself” question.
Not affiliated
The employers whose advice appears in this lesson have no tie to MySmartCoPilot. Each piece of advice is quoted from a public careers page or interview guide, linked in References, and its owner may have revised it since.
MySmartCoPilot’s structure for the answer, the career narrative: A short spoken account of your working life, the usual answer to 'Tell me about yourself': where you are now, two or three highlights with evidence, and why this role is your next step., has three parts: where you are now, in two or three sentences; two or three highlights, each with evidence; and what you are looking for, with why this role fits. Step through Gaurav’s narrative for a hiring manager:
The drawing shows the whole scene; its 6 steps are listed below.
Every step as text
- Where he is now. Two sentences: a backend engineer with three years at an online insurer, working on the claims service from the customer's upload to the payout. The interviewer now knows his work and his level.
- How he got here. One sentence on the year before, at a services company. It explains the path without walking through it; his schooling and college do not appear at all.
- The first highlight. He led the rewrite of the document checks: routine checks became rules, people kept the unusual cases, and the median time to settle a simple claim fell from 9 days to 2.
- The second highlight. He rewrote the on-call runbook with the two senior engineers paged most, and the pages that needed one of them fell from about 12 a month to 3. Two highlights, two numbers.
- Why this role. The close links his evidence to the job: the payouts platform asks for a slow money flow made fast and safe to run, the two things he has done most, at ten times his volume.
- The whole answer. Three parts in five stages: where he is now and how he got here, two highlights, and why this role. 196 words, about 1 minute 18 seconds at his rate of 150 words a minute, and every stage gives the interviewer something to ask about next.
The order does the work. The present comes first because it is what the interviewer is hiring. The past appears only as highlights that explain the present, and the close ties both to this job, so the next question is likely to be about something you chose to say. Prepare the facts of each part, not a speech: Amazon’s interview page says it does not expect perfect answers or rehearsed scripts.
A life story, or the resume read aloud
Gaurav’s first draft runs from his schooling in Kanpur to his hobbies. The interviewer already has the resume, and nothing in the draft says what he can do for this team. Start where you are now, then go straight to a highlight: “I’m a backend engineer with three years on an insurer’s claims service. Last year I led…”
Checkpoint
Check: The three parts of a career narrative
Two or three highlights the role needs, each with evidence
A highlight earns its place when the role needs what it shows. Google’s interview tips suggest cross-referencing your resume with the job description and, where the two overlap, building a library of examples. Gaurav did that for a payouts role. The job asked for four things, and he had evidence for three of them:
| What the job asks for | Gaurav’s evidence | In his narrative |
|---|---|---|
| Moving money quickly and correctly | Simple claims settled in 2 days instead of 9 | First highlight |
| Running a service on call | Night pages for senior engineers down from about 12 a month to 3 | Second highlight |
| Working with other teams | Rules the fraud team can now write for itself | Kept for a follow-up, or for a panel |
| A card-payments gateway | None yet | Not claimed |
Two highlights fill one to two minutes, and the third waits for a follow-up question. The empty row stays empty: a narrative that claims something the resume cannot back loses the interviewer’s trust at the first probe. Mirror the job’s priorities with your evidence, not with its wording. “I’m detail-oriented and customer-focused” repeats an advertisement; “simple claims now settle in 2 days instead of 9” shows both.
The checker below reads four narratives in labelled parts, times each at its speaker’s own rate and flags what an interviewer would notice. Press Edit, put your own three parts in place of one of them, set its rate and run it again:
// A narrative checker for "Tell me about yourself": each answer is written in three labelled parts (where you are
// now, two or three highlights, and why this role) and timed at the speaker's own measured rate. To check your own,
// replace one of the narratives below with yours, set its rate, and run it again.
//
// Gaurav, Jaya, Lakshmi, their employers, colleges and numbers are invented.
const NARRATIVES = [
{
name: 'Gaurav, first draft',
rate: 150, // words a minute, measured by reading a passage of known length aloud
now: "I'm from Kanpur. I did my schooling there and then my B.Tech in electronics from a college in Bhopal, where I scored 8.1. After that I joined a services company as a trainee, and then I moved to my current company, an online insurer in Bengaluru, where I work on Java, Spring Boot, Kafka, PostgreSQL, Redis, Docker and Kubernetes. I'm a passionate, hard-working team player and a quick learner. In my free time I like cricket and reading.",
highlights: [],
next: '',
},
{
name: 'Gaurav',
rate: 150,
now: "I'm a backend engineer with three years at an online insurance company in Bengaluru. I work on the claims service, the part that takes a claim from the customer's upload to the payout. Before that I spent a year at a services company, where I learned to ship to someone else's release calendar.",
highlights: [
'Last year I led the rewrite of our document checks. Simple claims used to wait for a person to read every upload; I moved the routine checks into rules, kept people for the unusual cases, and the median time to settle a simple claim fell from 9 days to 2.',
'I also own our on-call runbook. After a month of noisy alerts I rewrote it with the two senior engineers who were being paged most, and the pages that needed one of them fell from about 12 a month to 3.',
],
next: "Now I'm looking for a team where reliability is part of the product. This role, on your payouts platform, asks for the two things I've done most, making a slow money flow fast and making it safe to run, and I want to learn how that works at ten times our volume.",
},
{
name: 'Jaya, final-year student',
rate: 130,
now: "I'm in the final year of a computer science degree in Nagpur, and most of my time outside classes goes into backend work: APIs, databases and making slow things fast.",
highlights: [
'In my internship at a logistics start-up I rewrote the query behind the delivery-status page. It went from about 4 seconds to under 300 milliseconds, and the change is still running in production.',
'For my final-year project, three of us built an attendance app for our department. I wrote the backend and the tests, and 240 students used it for the whole semester without it going down once.',
],
next: 'Next I want a backend role where I can keep working on performance alongside people who know far more than I do, and this role, on a team that owns its own APIs and their speed, is that kind of work.',
},
{
name: 'Lakshmi, moving into data engineering',
rate: 120,
now: "I'm a mechanical engineer, and for five years I've worked in quality at a two-wheeler plant near Pune. For the last two of them, most of my work has been data work.",
highlights: [
'Our weekly defect report was built by hand in spreadsheets, which took a whole Monday. I taught myself SQL and Python and replaced it with a pipeline that loads the line data every night; the report now takes 10 minutes.',
'Last year I finished a data engineering course, and for its project I built a pipeline that loads about 2 million rows of public rail punctuality data every night, with tests that stop a bad load.',
],
next: "I'm moving into data engineering because building that pipeline was the part of my job I looked forward to most, and this role, on a manufacturer's data platform, needs the pipelines and an understanding of the shop floor.",
},
];
// What makes a highlight evidence: a number with what it counts, or a change from one value to another.
const EVIDENCE = /\b\d[\d,.]*\s*(?:(?:thousand|million|billion)\s+)?(?:%|per cent|seconds?|milliseconds?|minutes?|hours?|days?|weeks?|months?|years?|students?|users?|claims?|orders?|pages?|requests?|rows?|people)\b|\bfrom(?:\s+\S+){1,4}\s+to\s+\S*\d/i;
// The closing part names this role (or team) and gives a reason.
const THIS_ROLE = /\b(?:this|the) (?:role|team|job|position)\b/i;
const REASON = /\b(?:because|asks for|needs|is that kind of|is exactly|where I can|which is why)\b/i;
// What turns a narrative into a recital of the resume, and labels that stand in for evidence (MySmartCoPilot lists).
const RECITAL = ['did my schooling', 'my native', 'I was born', 'I scored', 'CGPA', 'my father', 'my hobbies', 'in my free time'];
const LABELS = ['passionate,', 'hard-working', 'hardworking', 'team player', 'quick learner', 'go-getter', 'self-motivated', 'results-driven'];
const TOOLS = ['Java', 'Spring Boot', 'Kafka', 'PostgreSQL', 'MySQL', 'Redis', 'Docker', 'Kubernetes', 'React', 'Node.js', 'Python', 'SQL', 'Spark', 'Airflow'];
const words = (text) => text.split(/\s+/).filter(Boolean).length;
const sentences = (text) => (text.match(/[.!?](?=\s+[A-Z]|\s*$)/g) || []).length;
const clock = (s) => (s >= 60 ? `${Math.floor(s / 60)} min ${String(s % 60).padStart(2, '0')} s` : `${s} s`);
const line = (ok, text) => ` ${(ok ? 'ok' : 'missing').padEnd(8)} ${text}`;
const found = (text, list) => list.filter((phrase) => text.toLowerCase().includes(phrase.toLowerCase()));
const tools = (text) => TOOLS.filter((t) => new RegExp(`(?<![\\w.])${t.replace('.', '\\.')}(?!\\w)`).test(text));
console.log('Narrative checks, each at the speaker\'s own rate');
for (const n of NARRATIVES) {
const all = [n.now, ...n.highlights, n.next].join(' ');
const total = words(all);
const secs = Math.round((total / n.rate) * 60);
const evidenced = n.highlights.filter((h) => EVIDENCE.test(h)).length;
console.log('');
console.log(`${n.name}: ${total} words at ${n.rate} a minute, about ${clock(secs)}`);
console.log(line(n.now.trim() !== '' && sentences(n.now) <= 3, `where you are now, in at most three sentences (${sentences(n.now)})`));
console.log(line(evidenced >= 2 && n.highlights.length <= 3, `two or three highlights, each with evidence (${evidenced} of ${n.highlights.length})`));
console.log(line(THIS_ROLE.test(n.next) && REASON.test(n.next), 'why this role, in the closing part'));
console.log(line(secs >= 60 && secs <= 120, 'one to two minutes when spoken'));
const flags = [
['the resume read aloud', found(all, RECITAL)],
['labels instead of evidence', found(all, LABELS).map((x) => x.replace(/,$/, ''))],
];
for (const [what, hits] of flags) if (hits.length) console.log(` flag ${what}: ${hits.join(', ')}`);
const named = tools(all);
if (named.length > 4) console.log(` flag a list of tools: ${named.length} named; keep them for the follow-up questions`);
}Output
Narrative checks, each at the speaker's own rate Gaurav, first draft: 78 words at 150 a minute, about 31 s missing where you are now, in at most three sentences (5) missing two or three highlights, each with evidence (0 of 0) missing why this role, in the closing part missing one to two minutes when spoken flag the resume read aloud: did my schooling, I scored, in my free time flag labels instead of evidence: passionate, hard-working, team player, quick learner flag a list of tools: 7 named; keep them for the follow-up questions Gaurav: 196 words at 150 a minute, about 1 min 18 s ok where you are now, in at most three sentences (3) ok two or three highlights, each with evidence (2 of 2) ok why this role, in the closing part ok one to two minutes when spoken Jaya, final-year student: 139 words at 130 a minute, about 1 min 04 s ok where you are now, in at most three sentences (1) ok two or three highlights, each with evidence (2 of 2) ok why this role, in the closing part ok one to two minutes when spoken Lakshmi, moving into data engineering: 146 words at 120 a minute, about 1 min 13 s ok where you are now, in at most three sentences (2) ok two or three highlights, each with evidence (2 of 2) ok why this role, in the closing part ok one to two minutes when spoken
Recorded with Node.js 24.21.0 on macOS 26 arm64. To run it yourself: mise exec node@24.21.0 -- node narrative_check.mjs
Runs on this device, in your browser. The first run downloads JavaScript (about 0.6 MB), which is kept for the next runs.
Your run, in this browser
Gaurav’s first draft is the shortest, 31 seconds, and fails every check: it recites his schooling and marks, names seven tools and calls him a “team player” and a “quick learner” without a single result. His narrative passes, and so do those of Jaya, a final-year student in Nagpur, and Lakshmi, a mechanical engineer moving into data engineering. Jaya’s highlights come from an internship and a college project, which is where a student’s evidence is. Atlassian’s guide asks students to go over each project’s highlights, how they and their team contributed, and its impact.
Key idea
Choose the two or three highlights this role needs, and give each one evidence an interviewer could check: a number, a change from one value to another, or something that is still in use.
One to two minutes, timed at your own rate
With a hiring manager, aim for one to two minutes: long enough for two highlights with their evidence, short enough to leave time for questions about them. Atlassian’s guide keeps its elevator pitch under two minutes. A recruiter call usually wants a shorter version, and the interview-prep track times one at 60 to 90 seconds in the recruiter call and your introduction.
Time your narrative at your own speaking rate: How many words you say in a minute: the words of a recorded answer divided by its length in minutes. With it, the word count of a story tells you how long the story will take to tell. More in “Rehearsing and delivering stories out loud” rather than a typical figure found online: read aloud a passage whose words you have counted, at your interview pace, and divide those words by the minutes it took. The length of any draft then follows: its words divided by your rate is its time in minutes. Jaya speaks at 130 words a minute, so her 139 words take 139 ÷ 130 ≈ 1.07 minutes, about 1 minute 4 seconds, which is what the checker printed. Gaurav’s 196 words at 150 a minute take 1 minute 18 seconds.
Slow down and time it again
In the checker, change Jaya’s rate from 130 to 110 and run it again. The same 139 words now take 1 minute 16 seconds, still inside the range. Then put in your own rate and your own narrative.
A narrative that runs past two minutes usually carries a third highlight or a walk through every job. Cut the highlight that the role needs least, and keep it ready for the follow-ups.
Checkpoint
Check: Highlights the role needs, each with evidence · One to two minutes at your own rate
The same facts for a recruiter, a hiring manager and a panel
Atlassian’s guide advises tailoring your pitch to the person you are speaking to. Amazon’s interview page sets the limit: treat each interviewer the same, as it is not necessary to tailor your answers to their role. Both hold when you change how much you say and in which words, and never what happened. The program below tells Gaurav’s narrative to a recruiter, to the hiring manager and to a panel with a staff engineer on it, and marks every sentence against the hiring manager’s version:
// One career narrative told to three listeners: a recruiter, the hiring manager and a panel that includes a staff
// engineer. The hiring manager's version is the base; the other two keep its facts and change the length, the depth
// and the words. Each version is timed at the speaker's own rate, and every sentence is marked against the base. To try
// your own, write your sentences into SENTENCES and list them in each version.
//
// Gaurav, his employers and every number are invented.
const RATE = 150; // Gaurav's measured speaking rate, in words a minute
// `from` names the sentences of the base whose facts a sentence retells in other words.
const SENTENCES = {
now: { text: "I'm a backend engineer with three years at an online insurance company in Bengaluru." },
service: { text: "I work on the claims service, the part that takes a claim from the customer's upload to the payout." },
before: { text: "Before that I spent a year at a services company, where I learned to ship to someone else's release calendar." },
led: { text: 'Last year I led the rewrite of our document checks.' },
rules: { text: 'Simple claims used to wait for a person to read every upload; I moved the routine checks into rules, kept people for the unusual cases, and the median time to settle a simple claim fell from 9 days to 2.' },
runbook: { text: 'I also own our on-call runbook.' },
pages: { text: 'After a month of noisy alerts I rewrote it with the two senior engineers who were being paged most, and the pages that needed one of them fell from about 12 a month to 3.' },
looking: { text: "Now I'm looking for a team where reliability is part of the product." },
fit: { text: "This role, on your payouts platform, asks for the two things I've done most, making a slow money flow fast and making it safe to run, and I want to learn how that works at ten times our volume." },
// For the recruiter: the same two results in plain words, and why this role and why now.
plainWin: { from: ['led', 'rules'], text: 'Last year I led a change to how we check claim documents, and the time to settle a simple claim fell from 9 days to 2.' },
plainRunbook: { from: ['runbook', 'pages'], text: 'I also rewrote our on-call guide, and the night calls to our senior engineers fell from about 12 a month to 3.' },
plainWhy: { from: ['looking', 'fit'], text: "I'm applying for this role because your payouts platform is the same kind of money flow at a much larger scale, and keeping money moving reliably is the work I want to keep doing." },
whyNow: { text: 'The rewrite has run smoothly for six months, so this is a good time for me to take on a bigger version of the same problem.' },
// For a panel with a staff engineer on it: the decision behind the result, and the reach beyond his own team.
decision: { text: 'The hard part was deciding what a rule could approve on its own: I limited the rules to checks whose mistakes could be caught and reversed before any money left, which still settled 7 claims in 10 without a person, and I designed them so that the fraud team could add rules of their own.' },
reach: { text: 'The runbook became the template for the four other services in our group, and new engineers now shadow on call for one week instead of three.' },
scope: { from: ['fit'], text: 'Your payouts platform serves several product teams, and that is the scope I want next: decisions that other teams build on, at ten times our volume.' },
};
const VERSIONS = {
'Hiring manager': ['now', 'service', 'before', 'led', 'rules', 'runbook', 'pages', 'looking', 'fit'],
Recruiter: ['now', 'service', 'before', 'plainWin', 'plainRunbook', 'plainWhy', 'whyNow'],
'Panel with a staff engineer': ['now', 'service', 'led', 'rules', 'decision', 'runbook', 'pages', 'reach', 'looking', 'scope'],
};
const BASE = VERSIONS['Hiring manager'];
const words = (text) => text.split(/\s+/).filter(Boolean).length;
const clock = (s) => (s >= 60 ? `${Math.floor(s / 60)} min ${String(s % 60).padStart(2, '0')} s` : `${s} s`);
// Wraps a sentence to lines of at most 68 characters, so the output reads on a phone.
const wrap = (text, width = 68) => {
const lines = [];
let current = '';
for (const w of text.split(' ')) {
if (current && (current + ' ' + w).length > width) {
lines.push(current);
current = w;
} else current = current ? `${current} ${w}` : w;
}
if (current) lines.push(current);
return lines;
};
const show = (mark, text) => wrap(text).forEach((l, i) => console.log(` ${i === 0 ? mark : ' '} ${l}`));
// The numbers a version states: facts that must stay the same from one listener to the next.
const numbers = (text) => [...new Set(text.match(/\b\d+\b/g) || [])].join(', ');
console.log(`Gaurav's narrative for three listeners, at ${RATE} words a minute`);
console.log('Marks: = as told to the hiring manager, ~ the same facts in other words,');
console.log(' + added for this listener, - left out');
for (const [listener, ids] of Object.entries(VERSIONS)) {
const text = ids.map((id) => SENTENCES[id].text).join(' ');
const total = words(text);
console.log('');
console.log(`${listener}: ${total} words, about ${clock(Math.round((total / RATE) * 60))}`);
const covered = new Set(ids.flatMap((id) => [id, ...(SENTENCES[id].from || [])]));
for (const id of ids) show(BASE.includes(id) ? '=' : SENTENCES[id].from ? '~' : '+', SENTENCES[id].text);
for (const id of BASE.filter((b) => !covered.has(b))) show('-', SENTENCES[id].text);
console.log(` numbers stated: ${numbers(text)}`);
}Output
Gaurav's narrative for three listeners, at 150 words a minute
Marks: = as told to the hiring manager, ~ the same facts in other words,
+ added for this listener, - left out
Hiring manager: 196 words, about 1 min 18 s
= I'm a backend engineer with three years at an online insurance
company in Bengaluru.
= I work on the claims service, the part that takes a claim from the
customer's upload to the payout.
= Before that I spent a year at a services company, where I learned to
ship to someone else's release calendar.
= Last year I led the rewrite of our document checks.
= Simple claims used to wait for a person to read every upload; I
moved the routine checks into rules, kept people for the unusual
cases, and the median time to settle a simple claim fell from 9 days
to 2.
= I also own our on-call runbook.
= After a month of noisy alerts I rewrote it with the two senior
engineers who were being paged most, and the pages that needed one
of them fell from about 12 a month to 3.
= Now I'm looking for a team where reliability is part of the product.
= This role, on your payouts platform, asks for the two things I've
done most, making a slow money flow fast and making it safe to run,
and I want to learn how that works at ten times our volume.
numbers stated: 9, 2, 12, 3
Recruiter: 161 words, about 1 min 04 s
= I'm a backend engineer with three years at an online insurance
company in Bengaluru.
= I work on the claims service, the part that takes a claim from the
customer's upload to the payout.
= Before that I spent a year at a services company, where I learned to
ship to someone else's release calendar.
~ Last year I led a change to how we check claim documents, and the
time to settle a simple claim fell from 9 days to 2.
~ I also rewrote our on-call guide, and the night calls to our senior
engineers fell from about 12 a month to 3.
~ I'm applying for this role because your payouts platform is the same
kind of money flow at a much larger scale, and keeping money moving
reliably is the work I want to keep doing.
+ The rewrite has run smoothly for six months, so this is a good time
for me to take on a bigger version of the same problem.
numbers stated: 9, 2, 12, 3
Panel with a staff engineer: 244 words, about 1 min 38 s
= I'm a backend engineer with three years at an online insurance
company in Bengaluru.
= I work on the claims service, the part that takes a claim from the
customer's upload to the payout.
= Last year I led the rewrite of our document checks.
= Simple claims used to wait for a person to read every upload; I
moved the routine checks into rules, kept people for the unusual
cases, and the median time to settle a simple claim fell from 9 days
to 2.
+ The hard part was deciding what a rule could approve on its own: I
limited the rules to checks whose mistakes could be caught and
reversed before any money left, which still settled 7 claims in 10
without a person, and I designed them so that the fraud team could
add rules of their own.
= I also own our on-call runbook.
= After a month of noisy alerts I rewrote it with the two senior
engineers who were being paged most, and the pages that needed one
of them fell from about 12 a month to 3.
+ The runbook became the template for the four other services in our
group, and new engineers now shadow on call for one week instead of
three.
= Now I'm looking for a team where reliability is part of the product.
~ Your payouts platform serves several product teams, and that is the
scope I want next: decisions that other teams build on, at ten times
our volume.
- Before that I spent a year at a services company, where I learned to
ship to someone else's release calendar.
numbers stated: 9, 2, 7, 10, 12, 3
Recorded with Node.js 24.21.0 on macOS 26 arm64. To run it yourself: mise exec node@24.21.0 -- node three_listeners.mjs
Runs on this device, in your browser. The first run downloads JavaScript (about 0.6 MB), which is kept for the next runs.
Your run, in this browser
Read the numbers stated under each version: 9 days to 2 and 12 pages a month to 3 are in all three. The recruiter hears them in plain words, “our on-call guide” for “the runbook”, in about a minute. The panel hears the most, 244 words in 1 minute 38 seconds, because a staff engineer weighs decisions and reach: what a rule was allowed to approve on its own and why, and the four other services that now use his runbook.
| Listener | Length | What it gets more of | Words |
|---|---|---|---|
| Recruiter | About a minute | The results | Plain words |
| Hiring manager | One to two minutes | Your part in each result | The team’s terms |
| Panel with a staff engineer | Up to two minutes | The decisions and their reach | Exact technical terms |
Key idea
Change the length, the depth and the words for each listener, and never the facts: the same numbers belong in every version of your narrative.
Checkpoint
Check: The same facts for different listeners
Gaps, switches and layoffs in one or two honest sentences
Some narratives have a part that needs explaining: a year away, a move between fields, a layoff. Give it one or two honest sentences at the point where it happened, then say what you did and what you are ready for. Lakshmi tells her switch as a path, phase by phase:
- Years 1 to 3
Quality engineer on the line
She checks parts and investigates defects at a two-wheeler plant near Pune. Her narrative gives this phase half a sentence: it is where she comes from, not what she is applying with.
- Years 4 and 5
The defect report becomes data work first evidence
The weekly defect report took a whole Monday in spreadsheets. She teaches herself SQL and Python and replaces it with a pipeline that loads the line data every night; the report now takes 10 minutes.
- Evenings
A course, and a project that runs second evidence
She finishes a data engineering course, and for its project builds a pipeline that loads about 2 million rows of public rail punctuality data every night, with tests that stop a bad load.
- Now
The switch, in one sentence why this role
She names the move and its reason at the end: building the pipeline was the part of her job she looked forward to most, and this role needs the pipelines and an understanding of the shop floor.
The timeline has 4 events, from Years 1 to 3 to Now.
Her move into data engineering needs no defence, because the evidence arrives before she names the new field. The same shape works for the other two cases:
| Situation | One or two honest sentences | Then |
|---|---|---|
| A year away | “I took a year away from work for a family reason that is now settled, and I’m ready to work full time.” | What you did to stay current, in one sentence |
| A layoff | “My role was one of 40 cut when the company closed its Pune office.” | The work you are proud of from that job |
| A switch | “I moved from quality engineering into data work because building our first pipeline was the part I enjoyed most.” | The evidence that you can do the new work |
Say it once and briefly: an explanation that runs longer than your highlights makes the gap the story, and a personal reason needs no detail. A layoff is a decision the company made, so state it as a fact about the company, without blame or apology. The interview-prep track’s lesson on career switches, gaps and layoffs has more scripts and a checker for longer explanations.
A year of exam preparation
A year spent preparing for a postgraduate entrance exam in India, such as GATE, is a gap like any other: one sentence on what you studied and what came of it, then the evidence that you are ready for this role.
Checkpoint
Check: Gaps, switches and layoffs in a sentence or two
Practise: write and time your own narrative
Write your narrative in the three labelled parts, measure your rate, and run the narrative checker above with your parts and your rate; fix each line it marks as missing. Then tell it aloud against a clock, and check yourself:
Reading Time Calculator Paste your narrative and set your own words a minute to see how long it takes to say. Stopwatch Time yourself reading a passage of known length aloud, then divide its words by the minutes for your rate.Practice that adapts to you
Practise this lesson
10 questions about 5 ideas of this lesson. Each answer is explained at once, and what you get right is kept in this browser.
Interview questions
What should an answer to “Tell me about yourself” include, and what should it leave out? A warm-up for freshers and 2–5 years.
It should include three things: where you are now, in two or three sentences; two or three highlights that this role needs, each with evidence such as a number or a result still in use; and why this role is your next step. With a hiring manager that takes one to two minutes at your own speaking rate. It should leave out what the interviewer already has or does not need: your schooling and marks, every job in order, a list of tools and labels such as “team player”. Keep the facts the same for every interviewer and change only the length and the depth. A gap, a switch or a layoff gets one or two honest sentences where it happened, and no more.
The two below need your own career. Say each answer aloud before you open its first step and follow-ups:
Model answers open with any pass: ₹79 for 1 week ($2.99), one payment that never renews.
-
Mid to senior
Your resume shows three jobs in four years. Walk me through them, and tell me why you moved each time.
-
Fresher to mid
Tell me something about yourself that is not on your resume, and why it matters for this role.
Key takeaways
- A career narrative has three parts: where you are now, two or three highlights with evidence, and why this role fits.
- Choose the highlights this role needs, back each with evidence, and leave out what you cannot back.
- Aim for one to two minutes with a hiring manager, timed at your own measured speaking rate.
- Tell the same facts to every listener, changing only the length, the depth and the words.
- Explain a gap, a switch or a layoff in one or two honest sentences, then move on to what you are ready for.
Terms in this lesson
- career narrative
- A short spoken account of your working life, the usual answer to 'Tell me about yourself': where you are now, two or three highlights with evidence, and why this role is your next step.
- elevator pitch
- A spoken introduction of under two minutes that says who you are, what you have done and what you are looking for, used with recruiters and at career events.
References
- Software Engineer Full Loop Interview Guide (linked from the onsite preparation page) (Meta Careers)
- Interviewing at Google: interview tips (Google Careers)
- Interview loop (Amazon Jobs)
- Early careers interview guide (Atlassian)
Related tools
Report a problem with this lesson
Kept only in this browser. Your Learn progress