In last Saturday’s free issue I made the case that a design leadership interview is a different event from the one you’re preparing for.
An IC loop evaluates you against a bar.
A leadership loop is a negotiation about how much authority the room will hand over, and most of it happens while you are somewhere else, exactly the way 5 sharks turn away from a founder mid-pitch and start discussing her in the third person.
And I want to deal with the obvious objection first ↴
You cannot really “research” the pain points or worries of the people who are interviewing you. If you are lucky you get their job titles in a calendar invite the afternoon before. You will never be told that the VP of Product has spent 3 years owning the roadmap and does not fancy sharing it, and you will certainly never be told what any of them argued about in last month’s leadership offsite.
Fine.
You do not need to know WHO these people are. The SEAT tells you what they are protecting.
A VP of Product sitting on a design leadership panel is losing something specific, and it is the same something at every company, whoever is in the chair.
That is the part you can prepare, the personal detail is a bonus you collect in the first 5 minutes of actually meeting them, and I will show you how.
My client had done 3 final rounds in 14 months (Senior design manager, 8 years in, one promotion behind where she should have been). Every loop had gone well on the surface, with good, warm conversations, encouraging noises from the recruiter, and then a version of the same feedback each time: they had gone with someone with more experience at that scope.
She had read that as a verdict about her, so she had spent a year making her “excellence case” louder. With sharper case studies, and a crisper story about her impact. None of it was the problem.
She had been preparing to be measured, and she was walking into rooms where nobody was measuring anything.
When she came to me, she was in her fourth interview loop for the Director of Design role at a B2B company.
All she had was a job description, a recruiter’s phone number, and 4 job titles of the interviewers/panelists.
That turned out to be plenty.
In this issue:
Why “they went with someone more experienced” is almost never about experience
What each of the interviewers’ roles is protecting
The most underused source in the entire process
How to test your guess live and respond to “tells” that are actually visible in a conversation
Client’s original answer to the metrics question + the version we replaced it with
The ONE sentence we wrote for the debrief she would not be in
4 questions that stop a leadership role you said “yes” to from shrinking between the offer and a start date

Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.