First, so the results are read against the right bar — what level are the roles you're going for?

Senior individual contributor / specialist

Head of / Director — leading managers or a function

Executive — C-level, VP, or board-facing

Moving between levels, or not sure yet

"Tell me about a project you owned." Your opening line is closest to:

It ran about eight months, twelve people, and I owned the planning and coordination

There were two viable approaches; we took the slower, more expensive one because the risk was materially lower

It was one of the most important projects in the organisation that year

The problem we had to solve was that our costs had risen about forty percent

An interviewer asks what you see as the biggest challenge facing this role. You'd most likely:

Walk through how I'd diagnose it in the first few weeks

Take a similar challenge from my last role and describe how I handled it there

Name the two or three most likely, then say which I'd take first and why

Say I'd need more context from inside before judging

In "tell me about yourself", how long before you reach something directly relevant to this specific role?

I start at the beginning and work forward chronologically

I open with the achievement I'm proudest of, whether or not it fits this role

Within the first twenty seconds — I open with the thread that fits this role

I give the full arc and tie it back to the role at the end

When you prepare examples for a specific interview, you tend to:

Use recent projects, since I remember the detail best

Go through the job description and decide which example answers each part

Keep one strong all-purpose story and adapt it to most questions

Prepare my strongest examples and decide in the moment which to use

Describing a project, roughly how does your airtime split?

Mostly context and process; the outcome lands in the last sentence

Roughly even thirds — background, what I did, what happened

I open with what changed, then work back through the decisions that got there

Brief setup, then mostly what I did, with the outcome as a closing line

When you talk about results, you're most likely to say:

What the team achieved together

The number it moved — money, risk, time — and exactly where I sat in that

What I improved, and let them judge what it was worth

Only the part I can strictly attribute to myself, even if that undersells the scale

When an outcome is genuinely hard to quantify, you:

Say it improved things significantly

Describe what changed qualitatively, but don't try to evidence the scale

Find a proxy — cycle time, rework, escalations, adoption — and use it to show the scale

Explain what became possible afterwards, without anchoring it to any evidence

Asked how you drive work across teams that don't report to you, you'd mostly describe:

The mechanism I set up — the forum, the cadence, the tracker

What made it worth their while, so the work held without me pushing

Breaking it into who owns what, then following up

Getting a sponsor to make it a shared priority, then keeping it moving myself

Explaining a move between industries or functions, you'd lead with:

What wasn't working in the previous role

What the move gave me that this role specifically needs

That the opportunity came up and I took it

A long-standing interest in this field

An hour later, the interviewer sums you up to the panel in one sentence. You'd want that sentence to be:

That I came across as professional and answered well

One specific judgement I made that maps onto the problem they're hiring for

That my track record is solid, with no gaps to worry about

That I'm strong in this area and genuinely want the job

An interviewer pushes back on something you just said. You:

Add more detail to support what I said

Explain the constraints I was working under at the time

Check which part they're questioning, then answer that part directly

Concede the point and offer a different angle

You're asked about something you genuinely haven't done. You:

Steer towards the closest thing I have done, without naming the gap

Say I haven't, give the nearest real experience, and name the difference

Say I haven't, then talk through how I'd approach it

Describe how it's generally done

Senior Interview Readiness Scorecard

"I thought I nailed it — so why didn't I get the offer?"

Experienced candidates rarely lose offers on competence. They lose them on how it comes across:
answering at the wrong level,
describing responsibilities instead of decisions,
sounding credible without being compelling.

Twelve situations. About five minutes.
Where you land across four dimensions, and the one habit to change first.
No trick options — every answer is something an experienced person really says. What differs is the level.