Why Consulting? Answers That Don't Sound Like Everyone Else's

An informed decision, not enthusiasm. Enthusiasm is free; every candidate has it by definition. The interviewer is checking three harder things. First, is your picture of the job accurate? Consulting as experienced, workstreams, rework, client politics, travel, differs from consulting as imagined, and people who bought the imagined version leave expensively. Second, does your reason connect to your history? A motivation with no footprint in your past choices is a motivation invented for the interview. Third, did you choose consulting over alternatives, or default into applying because the recruiting pipeline was there?

Underneath all three is churn risk. Firms invest heavily in year-one consultants and lose the investment when reality surprises them. Your answer is being read as a prediction of your month-nine self: the candidate who knows about the Thursday-night rework and wants the job anyway is a different bet than the candidate who knows about the airport lounge.

This reframing should change what you say. Facts about the job's difficulty are not risks to your answer; they are its strongest material. Naming the costs and choosing anyway is precisely the signal that cannot be faked by someone who has not done the homework.

Run the swap test: if your sentence works in another candidate's mouth without editing, it carries no information about you. "I want to work with smart people on varied problems with a steep learning curve" passes the swap test perfectly, which is exactly the problem. It also fails the firm test, since it describes Google, a hedge fund, and a good startup equally well, and the interviewer will say so out loud.

Specificity is not detail for its own sake. It is evidence, and evidence lives in three places. Your history: moments where you did consulting-shaped work, scoped an ambiguous problem, advised someone senior who could ignore you, got pulled toward diagnosis over execution, and wanted more. Your verification: conversations with people in the job, what they told you that surprised you, what you checked and confirmed. Your comparison: the alternatives you weighed and the specific reason each one lost.

One structural trick makes any answer more specific: replace category words with instances. Not "varied problems" but the two unrelated problems you want to work on. Not "smart colleagues" but the thing a consultant said in a coffee chat that changed how you saw the job. Not "learning curve" but the specific skill you watched a consultant deploy and could not yet match. Instances survive follow-ups; categories dissolve on the first "such as?"

Three beats, sixty to ninety seconds. Beat one: the pattern in your work that points here, told as a moment rather than a trait. Beat two: what you did to verify that consulting is that pattern at full strength, and what the verification taught you, including the costs. Beat three: what you want next that your current path does not offer, stated as a choice.

A compressed example, from a senior engineer: "Over eight years of building payment systems, the work I kept volunteering for was the two weeks before anything got built, when nobody agreed on the problem yet. I got pulled into three of those scoping fights outside my own team, and they were the best work I did. I spent this spring testing whether consulting is that job: I did a dozen conversations with consultants, two of them blunt about the rework and the travel. What I want is the version of that work I cannot get internally: a new problem every few months, in industries I have not seen, with people who teach structuring as a craft. Staying means one problem a year and a promotion into managing the building, not the diagnosing. So this is the deliberate move."

Notice what the structure buys. Every claim has an instance attached. The costs are named, which pre-empts the lifestyle probe. And the last line frames consulting as a comparison won, which pre-loads your defense for the follow-up that is coming next.

This follow-up, in some phrasing, arrives in most interviews, and it is the best gift in the fit portion: an invitation to show your comparison set. The candidates it destroys are the ones whose answer was attraction with no alternatives behind it.

Answer by naming what consulting beat. Three alternatives cover most candidates: staying and getting promoted, moving to a startup or operating role, and internal strategy or chief-of-staff jobs. Pick the two you genuinely considered and say why each lost. "Staying wins on depth and loses on repetition; I would spend three years perfecting a system I already understand. A startup wins on ownership and loses on range; it is one bet, one industry, for years. Internal strategy came closest, but the work answers to one executive team's appetite, and I watched two strategy groups spend a year on decks nobody was obligated to act on. Consulting is the only one where the problem changes quarterly and the client has paid enough to take the answer seriously."

The content matters less than the fact of the comparison. An answer that knows what it rejected is structurally impossible to reuse across candidates, which is the entire test. If you have not done this thinking, do it before the interview, because this follow-up is where invented motivation goes to die.

The lifestyle probe, and for candidates past thirty it is nearly guaranteed. The interviewer is not moralizing about work-life balance; they are testing whether your decision included the costs, because a senior hire who quits in month ten over travel is an expensive mistake someone approved.

Two failure modes bracket the good answer. Bravado, "I thrive under pressure, hours don't scare me", reads as untested confidence and invites harder probing. Minimizing, "I hear it's gotten better", reads as bargaining with reality. The pass is informed consent with mechanics: show you know the actual shape of the load, and show the arrangement that absorbs it. "I asked three consultants to walk me through their worst month, so I am not pricing this off the brochure. We made the decision as a household: my partner's schedule carries Tuesdays and Thursdays, and I am trading my current four hours of weekly commuting for hotel nights. The version of this I could not sign up for is unpredictability plus a team that hides it; the version I am signing up for is heavy, scheduled, and honest about itself."

If you have specific constraints, name the accommodation you have already verified exists, staffing preferences, regional models, rather than asking the interviewer to reassure you. Arriving with the solution is the senior move.

One checkable reason beats three impressive ones. The generic prestige answers, global platform, brand, impact, fail the swap test across firms exactly the way generic why-consulting answers fail it across candidates. What passes is anything the interviewer could verify or recognize: a practice you have a real connection to, work of the firm's you have read and can discuss, people you have spoken with, named, and what they told you.

The strongest firm layer has the same shape everywhere: a thread connecting your background to something this firm demonstrably does. An engineer who spent years in payments citing the firm's payments practice, a specific published piece from it, and a conversation with someone in it has built an answer no other candidate in the room can give. Note the compounding: each element alone is thin, the combination is unfakeable.

Two hygiene rules. First, no cross-contamination: praising the wrong firm's positioning is rare, but importing the wrong vocabulary is common, and interviewers notice their competitor's language. Keep one page of notes per firm and review the right page that morning. Second, calibrate claims to your actual exposure. "I spoke with two people in the practice and both described the same thing I saw in my own work" is credible. "Your culture is unique" from someone who has never been inside the building is not.

Answer it straight. Parallel processes are the norm, interviewers ran them too, and evasion burns credibility on a question that was not dangerous. The test hiding inside it is consistency: your stated preference must follow from the criteria you have been using all interview, because a ranking that contradicts your own logic marks everything before it as performance.

So: name the processes plainly, then rank on your criteria. "I'm in process with the other two of the big three and one boutique. If everything converted, I would choose here, and for the reason I gave earlier: the payments practice is where my background compounds fastest, and nobody else I am talking to has the equivalent." No firm is insulted by the existence of alternatives; the answer they are listening for is whether your preference is reasoned or flattery.

If this firm is genuinely not your first choice, do not claim it is. Rank honestly on dimensions this firm wins, fit with a practice, office, the people you have met, without declaring a loser out loud. "The honest answer is it would come down to practice fit, and this is the strongest match I have seen" is true, consistent, and diplomatically complete. Interviewers respect a reasoned second choice far more than a detected lie about first place.

A logistics question wearing a fit costume. Offices staff locally more than candidates assume, so the interviewer is checking whether you will still be here in year three or engineering a transfer by month six.

The strong answer has roots and reasons: ties to the city, family, partner's work, community, plus a reason the office itself makes sense for your interests, its client base, its anchor industries, a practice concentration. "My partner's practice is here, we own our place, and the office's client mix is heavy in the industrials work I come from" ends the inquiry. If you are relocating, the bar is slightly higher: show the move is planned and durable, not speculative. Naming a concrete tie, signed lease, partner's transfer, family nearby, does more than enthusiasm about the city's energy.

Do not fake roots, and do not wing local knowledge. An interviewer who lives there will outlast you on neighborhood talk in one exchange. If the honest answer is that the office is your second choice of location, anchor on what is true: the practice fit, the people you met, the client base, and a stated commitment to the location for the tenure that matters.

The interviewer's real question is why now, because the default read on a senior switcher is escape: a plateau, a reorg, a boss. Escape answers are disqualifying even when partly true, so the answer must be extension: the through-line from your operating years to this job, and the thing consulting adds that the current path cannot.

Build it in three moves. First, claim the through-line: the part of your job that was already consulting, scoping ambiguous problems, advising executives who could ignore you, parachuting into broken projects, and evidence you were pulled toward it repeatedly. Second, name the ceiling without bitterness: "staying means one domain and a management track; the diagnostic work I want more of is five percent of the next role, not fifty." Third, state what the firm gets, because a senior switcher is a two-sided trade: operating credibility with clients who have sat where you sat, delivery realism about what implementation costs, and pattern recognition juniors cannot fake.

Then let the years discipline the delivery: your answer should sound like a decision made with an eight-year base rate behind it, calm, costed, specific, not like a conversion experience. Interviewers extend senior candidates less benefit of the doubt on romance and more on evidence. Spend accordingly.

For experienced candidates this follow-up is sharper than the generic version, because the alternatives are real jobs you could plausibly get this quarter, and the interviewer knows it. The comparison has to be won on mechanics, not mood.

Take them one at a time, on the dimension where each genuinely competes. Internal strategy offers the analytical work, so beat it on consequence and cadence: internal teams answer to one executive's appetite, projects can outlive their relevance, and you get one company's problems on one company's clock. Chief of staff offers the executive exposure, so beat it on craft: it is a proximity job, learning by osmosis with no methodology and no bench of people whose job is teaching you. A startup offers intensity and ownership, so beat it on range and reversibility: it is a single five-year bet on one product in one market, and the skill it builds is deep but narrow.

Then close with the honest common denominator: consulting is the only option where problem variety, a client obligated to engage, and an institution that teaches structuring as a discipline arrive together. Concede what the alternatives win, ownership, depth, equity, because a comparison with no concessions reads as rehearsed. You are demonstrating judgment about careers, which is, not incidentally, the product consultants sell.

The question behind the question: will your ego survive week three, when someone five years younger restructures your analysis and is right? Firms have watched senior hires clear every intellectual bar and then fail on exactly this, so reassurance is worthless. Evidence is the currency.

First, show you know the actual terms: the level you would enter at, what that level owns, and who you would report to. Naming it plainly, "I would come in at the post-MBA level, running workstreams, not studies, with a project leader above me", proves the decision was made with the org chart in view, not discovered on day one. Second, produce the evidence: a recent, concrete instance of operating under someone else's structure and being better for it. A senior engineer who spent last quarter executing a framework they initially disagreed with, and can say what changed their mind, has answered the question. A candidate who says "I'm humble, it won't be a problem" has not.

Third, reframe the seniority as an asset priced into the choice: "I am not buying a title, I already had one. I am buying three years of compressed skill acquisition, and the tuition is taking direction again. I did the math on that trade before applying." That sentence only works if the rest of your interview backs it, which is the point.

A pure information check, and devastating to candidates who prepared motivation but not reality. The interviewer wants your picture of an ordinary Tuesday, because the gap between your picture and the real one is exactly the gap they expect you to fall into by month nine.

The real Tuesday, worth knowing cold: you own a workstream, a slice of the problem, and most of the day is gathering evidence for it, client data that arrives late and wrong, interviews with client managers who have their own agendas, analysis that gets rebuilt when the data changes. Output is mostly pages: analysis turned into slides, versioned more times than seems sane, because the document is how the team thinks. There are check-ins with your manager, working sessions with client counterparts, and a steady undertone of making numbers reconcile. Travel varies by firm and region from weekly flights to mostly-remote with anchor days. The glamorous version, boardrooms and strategy, is real and rare: minutes per week, earned by the hours around it.

Deliver it with specifics and a little affection for the unglamorous parts. "Most of the job is building the evidence, and the version that finally reconciles at 9pm is weirdly satisfying" tells the interviewer you met the actual job and liked it, which is the entire screen.

Both sides know the attrition math: most people who start in consulting are gone before partner. The question is not testing whether you will pretend otherwise; it is testing whether your plan makes you a good investment for the years you are there, and whether you lie under mild pressure.

The declared tourist fails: "two years for the toolkit, then back to industry" prices your departure into the hiring decision. The fake lifer also fails: "partner, definitely" from a candidate with no evidence pointing that way reads as the flattery it is. The credible answer commits to the near term and stays honest about the far term: "In five years I want to be the person who gets staffed on the messiest version of a diagnostic and trusted to run it, which here means senior project leader territory. Whether the answer after that is the partner track is a decision I want to earn the right to make with real information. What I am not doing is treating this as a toolkit stop; I priced that path and it is a bad trade at my stage."

Senior switchers get one extra beat: connect the five-year picture to the switch itself. You left a known trajectory for this one; saying what the new trajectory is for shows the move had a destination, not just an exit.

The last five minutes are still scored, informally but durably, because your questions reveal what you are optimizing for. Every question is a disclosure. "What is the staffing model between offices?" discloses someone planning logistics of a real life here. "How soon can I specialize?" discloses someone negotiating the job before holding it. "What do most people do after two years?" discloses the exit thinking you spent the whole interview not mentioning.

Ask what a person who meant their why-consulting answer would ask. About the work: what separates the consultants the interviewer fights to staff from the merely good ones at the two-year mark. About development: how feedback flows in practice on a team mid-study, not the official cadence. About them: what has kept the interviewer here past the point most of their start class left, asked plainly, senior people answer that question with surprising candor, and the answer teaches you something real while the conversation stops feeling like an audit.

Two mechanical notes. Have three questions ready and expect two to get answered en route; asking something already covered signals autopilot. And skip questions whose answers are on the website, hours, industries, "culture", because research you did not do is also a disclosure.