CoachNed
Two empty chairs across a long interview table

Fundamentals

Tell Me About Yourself Consulting: A 90-Second Map

Learn how consulting interviewers use tell me about yourself to pick follow-ups, with three original spoken answers, the hooks each plants, and what a partner notes.

UpdatedReviewed by Ned

I stop writing after the first ninety seconds of "tell me about yourself" when I already know which two stories I want next. That is the real job of the question. It is not a warm-up autobiography, and it is not a polished present-past-future script. It is a map. You hand me two deliberate hooks. I choose which thread to pull.

After this piece you should be able to deliver a 60–90 second answer that plants exactly those hooks, hear what a partner is likely writing down, and reuse the same spine for undergrad, MBA, and experienced-hire rooms without sounding like a template.

What the interviewer is doing while you talk

Firms publish the shape of the conversation more clearly than candidates admit. McKinsey's interviewing page says most client-facing roles include a personal experience interview followed by a problem-solving interview, and asks you to prepare important experiences in detail with focus on your role and actions. BCG's interview process puts a skills interview first for consulting: experience, skills, and motivation, then the case. Bain's interviewing page says consulting roles typically combine behavioral questions with case work, and that they want people who can explain why they want to join Bain specifically.

So when I open with "tell me about yourself," I am not killing time before the case. I am building a shortlist of threads I can deepen in the next ten minutes: leadership under constraint, influence without authority, analytical ownership, or a clean motive for advisory work. Your resume is already on the table. Your job is to make the next question easy for me.

Yale's career office puts a useful ceiling on length: keep the story under two minutes and highlight strengths that invite follow-ups rather than a full personal history (Yale Office of Career Strategy). In a consulting room I prefer the bottom of that range. Ninety seconds is generous. Sixty is often better.

Consulting still absorbs a large share of top MBA talent, which is why this opener gets so much folklore. As of the Class of 2025, Harvard Business School reports that 21% of graduates who actively sought and accepted full-time roles entered consulting. High volume does not mean the answer should be longer. It means interviewers have heard hundreds of chronologies and are hunting for a usable thread.

The map, not the timeline

Build the answer as three moves, not three eras of your life.

  1. One-line positioning. Who you are in professional terms right now, in one sentence.
  2. Two hooks. Two short, concrete experiences a partner can probe. Each hook needs a verb, a constraint, and a result you owned.
  3. Landing. One sentence that makes consulting the logical next problem type, not a brand wish.

That is the whole spine. Chronology is optional. If your strongest proof is a campus project from last spring and a summer internship from the year before, lead with those. Do not tour every line of the resume so I can "get the full picture." I already have the full picture. I need the selectable picture.

Ned's rule. Plant two hooks you can defend for eight minutes each. If I cannot ask a follow-up without you inventing detail, the hook was decoration, not evidence.

Timing math you can rehearse

At conversational pace, most people speak about 140–160 words per minute. Aim for 100–140 spoken words for "tell me about yourself." That is roughly 45–60 seconds if you speak deliberately, or about 70–90 seconds if you add one clarifying clause per hook.

Target lengthSpoken words (approx.)What fitsWhat breaks
45–60 sec100–120Positioning + 2 hooks + landingThree hooks, firm flattery, childhood
60–90 sec120–140Same, with one number per hookResume tour, "and then… and then…"
2+ min280+Almost neverEverything; I stop listening

Worked rehearsal: write the answer as a paragraph, count the words, cut until you are under 140, then speak it into your phone once. If the recording runs past 90 seconds, you are adding throat-clearing, not evidence.

What a partner writes down

I am not scoring charisma. I am marking whether the map gives me usable PEI or skills threads before the case starts. In a typical first round of eight candidates, Ned's estimate is that two or three give a map I can follow immediately; most give a chronology with one soft claim about "problem solving."

What I hearWhat I writeNext question I ask
Clear role + constraint + owned result"Hook A: led X under Y; probe decisions""Walk me through the trade-off you made."
Motive tied to a problem type"Why consulting: advisory / ambiguity / clients""Why this firm, not industry or PE?"
Chronology with no probeable claim"Resume read-aloud; no thread"Generic "tell me about a time…" (you lost control)
Two hooks that contradict"Story risk; dig for ownership""What was your contribution versus the team's?"

The win condition is simple: after ninety seconds I should already know which two experiences will carry the behavioral half. You chose them. I did not have to dig them out of a fog.

Three spoken answers (use the structure, not the facts)

These are fully invented. Do not mimic the companies or numbers. Steal the architecture: positioning, hook one, hook two, landing. After each answer I show the hooks and the partner note.

Undergrad: campus project + internship

"I'm a junior in industrial engineering at Northwestern, focused on operations and process improvement. Last fall I led a four-person student consulting team for a 12-location regional coffee chain that was losing 4 points of margin on drinks. We ran two weeks of store observations, rebuilt the labor schedule against peak hours, and cut average ticket time by about 18 seconds in the pilot stores. The summer before that, I interned in a hospital throughput group where I owned the evening boarding dashboard and helped the charge nurse cut hallway wait from 41 to 29 minutes over six weeks. Those were the first times I saw a messy operations problem turn into a recommendation someone actually used, which is why I'm pursuing consulting rather than a pure engineering track."

Hooks planted: (1) student consulting leadership with a measurable ops result; (2) hospital internship with owned dashboard and wait-time change.

Partner note: "Ops + client-ish delivery; probe leadership of peer team and how she handled pushback from store managers. Motive = applied problem solving, not prestige."

MBA: operator moving to advisory breadth

"I'm a second-year MBA at Booth after five years in supply chain at a mid-market medical-device manufacturer. In my last role I ran the SKU rationalization workstream for a plant that carried 1,800 active SKUs with 22% of volume driving most of the overtime. I cut the active set by 180 SKUs and freed about $1.1 million in annual carrying cost without missing a major customer SLA. At Booth I've been on a pro-bono team advising a Chicago nonprofit on whether to centralize purchasing across eight sites; I owned the cost baseline and the go/no-go recommendation. Consulting is the next step because the work I liked most was diagnosing a messy operating system and aligning people who did not report to me, not managing the same P&L forever."

Hooks planted: (1) SKU rationalization with hard dollars and SLA constraint; (2) pro-bono purchase centralization with owned recommendation.

Partner note: "Operator with influence without authority; probe stakeholder conflict on SKU cuts. Motive = breadth + advisory, not escape from ops."

Experienced hire: specialist who can talk to a CEO

"I'm a senior product analyst at a B2B payments company, where I own pricing experiments for mid-market merchants. Last year I led a six-month test on interchange-sensitive fee tiers across 4,200 merchants; we lifted contribution margin 70 basis points while keeping churn flat in the treatment cohort. Before that I spent three years in corporate strategy at a regional bank, where I built the branch-closure model the CFO used to shut 19 underperforming sites and reallocate $28 million of opex. I'm looking at consulting because the problems that stick with me are the ones where analysis has to survive a room of skeptics, and I want that across industries rather than one product roadmap."

Hooks planted: (1) pricing experiment with margin and churn trade-off; (2) branch-closure model used by a CFO with dollar impact.

Partner note: "Senior IC with exec exposure; probe how he handled merchants who hated the fee change, and why firm over in-house strategy. Risk: check client empathy vs pure analytics."

Notice what none of these do. They do not open with childhood, hometown, or "I've always loved puzzles." They do not recite GPA, club titles, or every internship. They do not end with "your firm culture really resonates." The landing names a problem type. The firm conversation can come later, when I ask.

Mistakes that kill the map

The resume tour. If every bullet gets a sentence, you have given me zero selection. Cut until two experiences carry the weight.

The trait salad. "I'm analytical, collaborative, and passionate about impact" is not a hook. A hook is a situation I can ask about for eight minutes.

The fake firm landing. Naming a firm's value statement you read last night does not plant a thread. It plants doubt. Prefer "why consulting as a problem type," then answer firm fit when asked.

The third hook. Two is the budget. A third usually means you do not trust the first two.

The case preview. Do not solve a mini-case inside the opener. Save structure for the problem-solving half.

Practice this today

Write your answer as one paragraph under 140 words. Label the two hooks in the margin. Then rehearse aloud once without notes and once with a partner who is allowed to ask only one follow-up: "Walk me through the decision you made in hook one."

If you want a fuller behavioral drill with follow-ups, use CoachNed's behavioral interview practice. Everything is open for seven days, no card; then $120 for a recruiting season or $49 a month.

Free live AI interview

Rehearse with a live AI interviewer

A live behavioral interview with follow-up questions. First question is free.

Start free

Live voice · Question 1 of 6

For the case half that usually follows, run one live voice case on /interview so the opener and the problem-solving muscle stay in the same session.

Frequently asked questions

How long should tell me about yourself be in a consulting interview?

Aim for 60–90 seconds, roughly 100–140 spoken words. Yale's career guidance caps the networking version under two minutes; consulting rooms reward the shorter end because the case still has to fit.

Should I use present-past-future for consulting?

You can, but it is a weak spine if it forces a chronology instead of two probeable hooks. Lead with positioning, plant two experiences, land on motive. Time order is optional.

What if the interviewer interrupts halfway through?

Stop. Answer the interruption. That usually means your first hook was useful and they are already pulling the thread. Do not insist on finishing the script.

Do experienced hires need a different structure than students?

Same map, denser hooks. Experienced hires should replace campus leadership with owned P&L, client, or executive exposure. Students should not invent senior judgment they do not have.

Is tell me about yourself scored separately from the case?

Firms describe fit or personal-experience assessment alongside problem solving; they do not publish a universal weight for the opener alone. Treat it as the doorway into the scored behavioral stories, not as free talk.

Sources

CoachNed is not affiliated with McKinsey, BCG, Bain, Deloitte, or any firm named above.