How to Answer "Tell Me About a Challenging Project" (Senior Answer)

I've sat across the table in more than 10,000 interviews, and this is the question that separates the people who get the offer from the people who don't. And it's almost never decided by the first answer. It's decided by the follow-up.

Why do interviewers ask "Tell me about a challenging project"?

Because job titles mean different things at different companies, and this question tells them what level you're actually at.

You could be head of pre-sales in a three-person team working on $100K deals for a mid-market company. Or you could be head of pre-sales working on eight-figure enterprise deals. Same title, completely different job.

So what the hiring manager wants to find out is your level of responsibility: the stakes, the complexity and the size of the work you were actually responsible for. Your CV's job is to land the interview. It's not what gets you hired.

And you're never interviewing in isolation. There might be 10 other people who could all do the job, maybe just as well as you. The more doubt you leave, the more open questions they have about you, and the less likely they are to hire you.

How does the salary range decide your offer?

The salary range isn't a random number. It's a checklist of what someone has to prove in the interview to earn at the top of it.

Think of it like a bingo card with 10 numbers on it. Hit all 10 and, boom, bingo, you get the $150K offer. Hit at least four and you might get the bottom of the range, say $130K. Fewer than four, and you probably don't get an offer at all.

In my executive search firm, we were working with a candidate going for a sales manager role at a small, growing software company in Michigan. He ticked off everything on their bingo card, then showed them more than they'd asked for. They didn't just offer him the top of the range. They offered him a bigger role, their newly created VP of Sales position.

I've seen the opposite too. A company created its first ever key account director role, looking after its most strategic customers. One candidate was a big hitter from a large IT consulting firm, a sure fit on paper. But he didn't answer direct questions with direct answers. He was vague, and he came across like his track record spoke for itself.

He didn't make it past the first round. The company hired someone who'd achieved less on paper, but who showed they understood the mission and convinced the CEO they could grow into it.

What are interviewers listening for in your answer?

Four things: the stakes, the complexity, the buy-in and the outcome.

1. Stakes What was on the line if it went wrong? Revenue, retention, customers? Was it the first of its kind, or someone else's failing project? And how much of it was down to you?
2. Complexity How many moving parts were there? Different systems, suppliers, sites, a fixed deadline? What went wrong halfway through, and how did you work around it?
3. Buy-in How many people were involved, how many of them wanted different things, and how did you get them all pulling in the same direction?
4. Outcome What was it like before, and what was it like after? What did you save, grow or cut? What happened next?

Stakes is where most people trip up. They say they worked on a $20 million project, when their part of it was only $400,000. The interviewer is listening for how much of it relied on you.

Complexity is how they work out whether something was genuinely hard, or just a lot of work.

Want the 20 questions you'll definitely get asked, and what they're really asking you? Get the free interview guide here.

What does a good answer to "Tell me about a challenging project" sound like?

It sounds specific. Here's the same platform migration, answered by someone at junior level and someone at senior level.

The senior answer hits all four: the stakes (60% of revenue), the complexity (40 different sets of workarounds and half the engineering time), the buy-in (engineering and the account directors) and the outcome (84 days, zero accounts lost, two that grew).

How do you answer the follow-up question?

With the detail you couldn't have made up, because the follow-up is where the bluffer gets found out.

Most interviews ask the same handful of questions, and you can find answers to the obvious ones all over the internet. That's why the first answer only gets you level with everybody else. The magic is in the follow-up.

The more senior the role, the more they'll push back, because they're testing how you handle pushback. Do you crumble, flap and get flustered? Or do you stay calm and explain your point clearly again, instead of repeating the same words but louder?

Say they ask, "What made it genuinely difficult, not just a lot of work?"

Or they ask, "What was your role, specifically, versus the team's?" The junior person says they were coordinating everything. The senior person says engineering did the build, and their call was the order and the risk: which 12 accounts got special treatment, and getting engineering and the account teams to agree to it.

How do you prepare for interview follow-up questions?

Prepare the proof behind your answers, not just the polished answer everyone else gives.

In my executive search firm, we were helping a Series C software company hire a pre-sales engineer. Halfway through the process, their head of pre-sales decided to leave. The candidate we put forward interviewed so well that they offered him the head of pre-sales role instead.

In the debrief afterwards, I found out he'd talked about how he grows, supports and nurtures the teams he'd worked in, and he'd shown he understood the challenges they'd face as they grew. He'd never held the title. But he'd done the things they needed.

How do you answer "Why should we hire you?"

Connect their problem to something you've already solved, then show how you'd solve it for them.

Picture two candidates going for the same head of customer success role at a software company that's at risk of losing its biggest customers at renewal.

They could only say that because they'd asked about the problem earlier in the interview. "Why should we hire you?" isn't the time to sell yourself. It's the time to show you understand their problem, and that you've already solved it.

What mistakes should you avoid when answering?

• Describing effort instead of stakes"Lots of moving parts" and "tight timelines" don't tell them what was on the line. Name the revenue, the customers or the deadline.
• Saying "we" for everythingBe clear what was your call and what was the team's.
• Inflating the size of your partIf your bit of the $20 million project was $400,000, say $400,000. The follow-up will find it anyway.
• Letting your job title do the talkingTitles mean different things at different companies. Prove the level instead.
• Only prepping the first answerPrep the follow-ups too, because that's where the offer gets decided.

The bottom line

When you get asked "Tell me about a challenging project", prove the stakes, the complexity, the buy-in and the outcome, then be ready for the follow-up. That's how you show the level you're really operating at, and how you make landing a six-figure offer predictable.

Read next: How to Answer Interview Questions: The 4 Types Explained · Getting Interviews But No Job Offers? Use the GAP Method

What's your next step?

If you want to work on this with me directly, here's where to start.