The Non-Negotiables

The middle of the pack is where offers get lost. Every interviewer who sits across from you is answering four questions, and the people who get out of the middle are the ones who give a clear yes on all four. Here is what each one takes.

1. Would I put you in front of a client?

This is communication, and it runs through the entire interview: the intro, the behavioral questions, the case, the wrap-up. Four things.

Structured. Answer first, then the reasons. Top down. If I have to wait for the point, I've stopped listening.

Succinct. A story is about ninety seconds. If you're still talking at three minutes, you've lost the room, and you'd lose a client the same way. Interviewers are likely doing 6-8 of these during the day and will zone out or forget your story unless it's succinct.

Conversational. Not a script. I'm listening for things to respond to, and a candidate who mentions they played college football or loves South Florida has just given me one. That's not small talk. Listening builds connection, and connection is what makes an interview feel like a conversation instead of an interrogation.

Polished. No filler words, no slang, and appropriate stories. I don't need to hear about the party. You'd be surprised how often it comes up.

The non-negotiable here is simpler than all of that: don't run on, don't read a script, and answer the question you were asked. If I ask about a weakness and you tell me about a strength, you've failed the question and told me you don't listen.

The case has a communication test too. Can you take the information I give you and turn it into something that resonates? The sharpest version of this is reading an exhibit. I hand you prior analysis or raw data, and you have to structure and interpret it quickly, in a way a client would follow. It's the most apples-to-apples moment in the interview, because that's the job.

2. Would I staff you on my team?

Two halves: the case and the person.

On the case, I'm asking whether I'd have to do the job for you. Where candidates fall flat: forgetting the question we're answering, which tells me you're going through the motions instead of listening, and not being able to take a nudge. I'm happy to partner on a case and suggest where to go next. I can't do it at every turn.

On the person: have something to say. I want someone I can sit across a table from and talk about work and about what they did over the weekend. Consultants are, for the most part, human. We care about things other than issue trees and slides. And I want a real example of a time you didn't succeed: pushback, failure, a project that went sideways. The job will put you down sometimes. The muscle to learn from it, or smile it off, is one of the things I'm hiring for.

There's a human element here when you're working 12+ hour days in the middle of nowhere on complex problems with clients that are pushing back on you. You want someone hard working, likeable, humble, and smart.

3. Do you know what you're getting into?

The short one, and the easiest to get wrong by being bland.

If this is one of your first cases, don't lead with that. Lead with what you've done to prepare. I want to know you took this seriously.

On fit, I want to hear what specifically about my office, my firm, and the industry matters to you. "I want to travel, I like hard problems, I like working in teams" is fine, and it puts you in the middle of the pack. I've heard it a hundred times, and somewhere in the second sentence I've zoned out. Specific beats polished here. Show who you've spoken to, why you think consulting is better for you than corporate strategy or banking, and why you think you'll be a great fit and the firm will benefit from having you.

4. Can you do the job?

This is the case, and it's where the weight is. Four pieces: structure, math, insight, wrap-up.

Structure. I'm asking whether you could take a question and turn it into a work plan. Don't give me a canned four Ps. Tailor the structure to what I just told you. And find the shortcut: if you have information, use it to say where you'd start and why. "I want to start with three-year revenue growth, split into price and volume. You mentioned price competition and new entrants, so my concern is we've over-cut on price." That's a clear yes on structure in two sentences.

Math. Two parts. First, structure it the way you'd build it in Excel: break the calculation into its component parts, the way you'd lay out a model. That's the entry-level job, and when you show me the components I can test them with you, the way I would with an analyst. Second, get the answer right. Sometimes rounding is fine, but it is good to check. If you forget a zero and quickly catch your mistake you can usually recover. Orders of magnitude wrong, and not noticing, is not: if the market is a billion dollars and you're projecting our startup client at two billion in year three, you've been dinged, and it's hard to recover. Incorrect math is the easiest way to get rejected and the way most candidates end up failing.

Insight. This shows up in every piece of the case: the structure, the math, the exhibit, the recommendation. Reading what's on the page isn't enough to distinguish yourself. Insight is tying what you just learned back to the problem. "We cut price in line with competitors, but volume still fell. So price probably isn't the issue. I'd look at customer reviews and product quality next, because something else is costing us share." Every time you learn something, connect it to the question. That's the habit that keeps you out of the post-interview triage conversation. I usually recommend trying to answer 3 things on each exhibit - the what, so what, and now what.

Wrap-up. Tie it together, use the data points you were given, be succinct, and say what you'd do next. It's mechanical, and that's fine. The wrap-up is where you avoid the last ding. Then thank the interviewer for their time. It's a small courtesy, and it's the last thing you leave them with.

What these have in common

None of this is knowledge. Top-down answers, a ninety-second story, a structure that fits the prompt, math broken into components, insight tied back to the question, a clean wrap-up: these are behaviors, and they're observable, which is why an interviewer can score them in real time. They're also practicable. You get them by doing it out loud, with someone pushing back, and finding out which one is holding you back before the real room does.

That's what CaseReady scores: the same four questions, every session, case and behavioral, so you know where you're a clear yes and where you're still in the middle.