Executive Interview Rounds: What Each Round Actually Tests (Director / VP / L6+)

A Senior IC interview loop is 4-5 rounds testing execution: can you code, design a system, work cross-functionally. A Director / VP loop is 5-8 rounds over 3-8 weeks with backchannel references running in parallel — and each round tests a different thing. Mis-read what a round is actually about (say, treating R3 peer-exec as another STAR round when it's specifically probing cross-functional conflict resolution) and the offer dies quietly at R4-R5, not at the round you failed.

The category difference: L4-L5 tests whether you produce good work. L6+ tests whether you build the system that produces work at scale — without your hands on it. That reframe determines what belongs in every answer, every round.

This piece is the round-by-round rulebook: what each of the 5-8 rounds is actually testing, how STAR expands to executive scope, how to structure the 90-day plan without the two overpromising mistakes, how to prepare for the backchannel references that decide the offer more than any single round, and the five common executive-interview mistakes that kill offers.

---

1. Round Map · One Thing Per Round

Full-stack Director / VP loops typically follow this shape. Startups compress to 4-5; late-stage tech and traditional enterprises run 7-8. Each round is testing a different signal — treat them as such.

R1 · Recruiter Screen (30-45 min)

What's tested: Basic fit + your 90-second "why this role, why now" answer. Not a chat — the recruiter is deciding whether to move you into R2.

Common mistake: Vague "looking for growth" framing. At exec level this reads as running from problems. Have a crisp 90-second version of your why-leaving narrative ready with specific pull toward this specific role.

R2 · Hiring Manager (60 min)

What's tested: Whether you understand the function they're hiring you to run — specifically, what the hiring manager's own boss measures the function on. If they're hiring a VP of Engineering, the CEO/CTO cares about delivery velocity, quality bar, and org health. Show you know that.

Common mistake: Discussing what you'd do rather than what they've been trying and what's stuck. This round is about diagnosis first, prescription later.

R3 · Peer-Executive Cross-Functional (2-3 sessions, 45 min each)

What's tested: How you resolve conflict between two executives. The Product VP interviewing an Engineering VP candidate wants to know: when the design team wants ship dates that engineering can't hit without cutting quality, what do you actually do?

Common mistake: Generic "collaboration" stories. R3 specifically wants STAR stories where two executive-level stakeholders had a real conflict and you built the alignment.

R4 · Skip-Level (45-60 min)

What's tested: Self-awareness at the strategic layer. The skip-level (CEO for a Director role, board member sometimes for a VP role) will ask about your two biggest strategic mistakes and what changed in your operating model afterward.

Common mistake: Small tactical mistakes reframed as strategic ones. The skip-level has seen this pattern hundreds of times. Real strategic mistakes with real operating-model changes read as senior; tactical mistakes disguised as strategic read as still-a-Manager.

R5 · 90-Day Plan Presentation (60-90 min, sometimes with slides)

What's tested: Your operating model. The plan itself matters less than how you sequence listening, testing, and structuring — full pattern in the next section.

Common mistake: Overpromising specific outcomes in the first 30 days. This is the #1 offer-killer at Director/VP level.

R6 · Direct-Report Simulation (VP+ only, 45-60 min)

What's tested: How you develop Directors, not just deliver through them. The interviewer plays a struggling Director and probes how you coach, when you'd intervene directly vs let them own the failure, and how you'd measure their growth.

Common mistake: Being too hands-on in the simulation. VPs get evaluated on whether they build a Director-tier team that produces without them, not whether they can execute at the Director tier themselves.

R7 · Board or Executive Committee (VP+ only, 30-45 min)

What's tested: Can you compress the last three years of your work into a 60-second board-ready summary? Board members don't want to hear the STAR — they want the pattern that survived across three years and three contexts.

Common mistake: Trying to fit multiple stories into the 60 seconds. One narrative arc, three specific proof points, done.

R8 · Culture / Team Fit (30-45 min)

What's tested: What your team would say about you if the interviewer called them — which they will. This round is often a formality on the calendar but is the softest layer of the backchannel reference process.

Common mistake: Prepared answers that sound corporate. This round wants signal on how you actually operate day-to-day, and the backchannel calls will validate or contradict what you said here.

---

2. STAR at Executive Scope

STAR (Situation · Task · Action · Result) remains the 2-minute answer structure, but at Director / VP scope, two tells separate execution-level STAR from executive-level STAR:

Tell #1 · Second-order effects. Junior STAR ends with the immediate metric win ("we hit the number"). Executive STAR ends with what continued after you left the role or context — the pattern that ran 18 months post-transition, the framework the next team adopted, the org shape that persisted.

Tell #2 · People development. Executive STAR contains at least one story where the Result names a specific person who grew as a direct consequence of your work — someone promoted, a Director you developed, a peer who became a partner. Executive interviewers pattern-match on this: leaders who don't name people they grew often haven't grown any.

Executive-scope STAR example

Situation — I inherited a 40-person engineering org at a Series C fintech where the on-call rotation was averaging ~14 pages/week and top engineers were flagging burnout as an attrition risk. Two senior ICs had already given notice.

Task — Reduce operational load without slowing delivery, and specifically preserve the senior IC bench that was starting to unravel.

Action — I ran three interventions in parallel over 6 months: (1) rebuilt the on-call rotation to two-week shifts with a paired-support model that halved cognitive load per shift; (2) staffed a dedicated Platform Reliability team (5 engineers hired, one internal Staff engineer promoted to lead it); (3) reframed the CTO-level narrative about reliability from "cost center" to "velocity multiplier" using the delivery data from Q2-Q3 that showed direct correlation with p95 latency incidents.

Result — Pages/week dropped from ~14 to ~4 within 9 months; the two ICs who had given notice both stayed after seeing the rotation change; the Staff engineer promoted to run Platform Reliability shipped the reference architecture that's still the org's operating model now, 22 months later (Tell #1: second-order effect). One of the ICs I convinced to stay was promoted to Principal a year later (Tell #2: named person who grew).

The story is roughly 220 words spoken — hits the 2-minute mark. Both tells land naturally in the Result section.

NDA masking: use ratios and ranges ("~40-person org", "~14 pages/week"), never exact confidential figures. Interviewers understand ranges; they treat exact numbers on confidential ops metrics as a leak signal.

---

3. 90-Day Plan · The Actual Structure

The 90-day plan is R5's centerpiece and the biggest source of offer-killing overpromise. The structure interviewers actually want to hear:

Days 1-30 · Listen

• 1:1s with every direct report (usually 5-12 people)
• 1:1s with every peer executive (5-8 people)
• Skip-level check-in with the hiring manager's manager
• 5-10 customer conversations (usage-based signal, not just NPS)
• Output: A diagnosis memo — what's actually broken, what's working better than the team realizes, what the political geography looks like

No shipping decisions in the first 30 days. Any candidate who commits to a specific outcome in the first 30 days signals they've already decided the answer before hearing the context — which reads as inflexible at exec level.

Days 31-60 · Test

• Take the diagnosis memo to 2-3 direct reports and 2-3 peer executives; refine based on their input
• Pilot low-cost changes only — process changes, meeting cadence, decision routing. Nothing that requires org changes or budget shifts.
• Continue customer conversations to validate what the diagnosis surfaced
• Output: A refined memo with 3-5 specific changes to propose and the case for each

Days 61-90 · Structure

• Propose (never impose) the reshape / refactor / hire plan
• Sequence peer-executive buy-in — get the two most affected peer execs on board before presenting to the skip-level
• Present the full plan with a clear ask of what changes and what stays
• Output: An agreed-on 12-month operating model with peer-executive alignment

The critical framing: 90 days at Director+ is a listening window, not a shipping window. The candidate who presents a plan that ships specific features by day 60 usually loses the offer to the candidate who presents a diagnosis-first plan with proposed changes by day 90.

---

4. Backchannel References

By R5-R6 the hiring manager has usually spoken to 3-5 people including several who aren't on your named reference list. This is not optional and it's not something you can fully control — but you can prepare.

Who they typically reach out to:
- Your named references (3-4 people you provided)
- 1-2 prior managers you didn't name
- 1-2 peer executives who worked alongside you
- 1-2 direct reports (past or current)
- Someone you managed out — this is the highest-signal call. How you exited someone who wasn't working out is often more diagnostic than how you developed a star performer.

The offer-killer: inconsistency between what you said in interviews and what references say. If you claimed to have led a 40-person org and a former peer says it was 25, the offer dies — even if 25 was still an accomplishment.

How to prepare

• Brief every named reference on the specific role and what you emphasized in interviews. Not scripted answers — context so they can be accurate.
• Backchannel yourself — reach out to 2-3 former colleagues who left the hiring company's team in the last 18 months. What they say about the culture is often decisive.
• Assume the person you managed out will be called. Reach out to them ahead of the loop if the relationship allows — a "I'm interviewing at X and expect they may reach out" email lets them anticipate the call and choose how to respond. Even a neutral reference from someone you managed out is a positive signal at exec level.

---

5. Five Common Executive Interview Mistakes

① Treating R3 as a generic STAR round. Peer-executive interviews specifically want stories where the conflict was between two other execs and you built the alignment. Bringing your favorite delivery-heroics STAR to R3 misses the round.

② Overpromising in the 90-day plan. "I'll ship the platform migration by day 60" reads as inflexible and unfamiliar with real Director tempo. Diagnosis-first plans win the offer.

③ Small tactical mistakes framed as strategic at R4. Skip-levels pattern-match on this instantly. Real strategic mistakes with real operating-model changes read as senior.

④ Neglecting backchannel prep. Assuming the hiring manager will only call your named references is the fastest way to lose an offer at the reference-check stage. Prepare for calls to people you didn't name.

⑤ Under-preparing R7's 60-second board summary (VP+). Trying to fit 3 stories into 60 seconds produces 3 half-stories. One narrative arc with 3 specific proof points wins.

---

6. The "Why Leaving?" Question at Director / VP Level

At exec level, "why are you leaving your current role?" is the same Flight Risk assessment as at IC level, just with higher stakes — the cost of a bad exec hire is 3-5× a bad IC hire. Recruiters and hiring managers scan for the same signal: "deliberate direction toward something" vs "running away from something."

The five-part narrative (Recognize · Limit · Explored · Next Layer · Landing) — detailed in the career-narrative piece — applies verbatim, but Step 3 (Explored) carries even more weight at exec level. Directors and VPs who show that they exhausted internal options (internal mobility attempts, cross-functional expansion, restructuring proposals) before looking externally read as pattern-thinking leaders, not tactical job-hoppers.

Executive-level Step 3 examples:
- "I proposed spinning out the Growth function into its own P&L twice, with detailed models both times. Board didn't approve, which is a fair call, but that's the scope of role I need next."
- "I built the case for the international expansion for 18 months across two board cycles. Company priorities went elsewhere, which meant that scope was going to be 3-5 years further out here."

That level of specificity in Step 3 is what separates exec-tier "why leaving" answers from IC-tier ones.

---

7. Automating the Repetitive Work

The four Bullets tools re-tune for exec-scope interview prep:

• Bullet Creator — Capture 8-12 executive-scope wins as X-Y-Z bullets with masked NDA figures. These are your round-agnostic answer bank — the same 8-12 stories expanded to full STAR become R3 conflict-resolution answers, R4 strategic mistakes, R5 operating-model examples, R7 board-summary proof points.
• JD Clipper (Chrome extension) — Paste target Director/VP JDs; extractor surfaces the specific scope words, function priorities, and leadership signals the hiring company uses. Match your language to theirs.
• Resume Generator — Matches the top 8-12 of your library to the JD; assembles the exec-tier resume (Director 2 pages, VP 2 pages with focused bullet count).
• Cover Letter Generator — Drops in the company URL; scanner reads six categories of company signal and drafts the cover letter as an achievement-led 4-part narrative (result → context → action → value, 15/20/50/15%) for the Proof paragraph of the 3-paragraph cover letter (Hook · Proof · Close).

The compounding value at exec level: the same 8-12 bullets that Resume Generator selects for a specific JD are also the top-8-12 STAR stories to rehearse for that company's interview loop. Round-agnostic answer bank means you're rehearsing the exact stories the hiring manager just saw on your resume — consistency is by construction, not by memory.

Start with Bullet Creator → — 8-12 exec-scope wins captured once, reused across every round of every loop.

---

Where this fits

Foundational: What is ATS in 2026 · ATS 7 Rules 2026. Related: SWE Resume by Seniority · Senior IC Triple-Artifact Workflow · Hidden Metrics by Job Role · Career Pivot Framework Mid-Career · Cover Letters 3-Paragraph Playbook.

---

Director/VP interview practice observed across US, UK, Canada, Australia, EU markets as of mid-2026. STAR framing and 90-day plan patterns per behavioral-interview standards at major tech and traditional enterprise employers.