Questions to Ask a VP of Design
A VP of Design is the person who can say where design sits in the company, what it gets to decide and how far a designer's career can go there. These questions to ask a VP of Design are for the designer or design manager who gets half an hour with one, in the final round of an interview loop, in a skip-level or in the question slot at an all-hands. They run from design's standing beside product and engineering, through the roadmap, research and the design system, critique and the quality bar, to hiring, the career ladder and how design's impact is measured.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Where design sits
How is the design team organized: one central group, designers embedded in product teams, or a mix?
Why ask it
Each setup trades something. A central group usually protects consistency and shared critique, while embedded designers sit closer to the product decisions and can drift apart from one another. The arrangement before this one is worth a follow-up, because the reason it changed is the problem the VP was trying to fix.
Who do you report to, and how does that compare with the heads of product and engineering?
Why ask it
A VP of Design who reports to the CEO alongside product and engineering argues as a peer. One who reports into the head of product has a boss on the other side of most disputes, which can work well when the two are close and badly when they are not. The chart is only part of it, so follow up with who is in the weekly executive meeting.
How would you describe the working relationship between design, product and engineering here?
Why ask it
Most VPs will call it a partnership, so listen for the detail that makes it one: a trio that plans together, a shared review, designers in the engineering standup. Then ask where it strains. A leader who can name the sore spot, such as handoff or who writes the brief, is describing the relationship as it is.
What state was design in when you took this job, and what have you changed since?
Why ask it
A VP who arrived to a handful of designers taking tickets has a different story from one who inherited a mature team. The changes they list, in the order they list them, show what they think a design org needs first: people, process or a seat in planning. Someone only a few months into the job will have a plan in place of a record, which is worth hearing too.
Which product decisions are design's to make, and on which does design only give advice?
Why ask it
One example of each from the past quarter makes this concrete. If everything design decides is visual, such as type, color and layout, it is being treated as a finishing step. Flows, naming and what gets cut from a release are the signs of real authority.
Where is design here weakest today, and what are you doing about it?
Why ask it
This is the biggest-challenge question with the polish taken off. Motion, content, research depth, front-end skill and management experience are common gaps, and the one named may be the reason a role is open. A fix with an owner and a date counts for more than a frank admission with nothing behind it.
Which disciplines sit under you: product design, research, content design, brand, design operations?
Why ask it
The title covers different territory from one company to the next, so get the map before you ask about any one part. Whatever sits elsewhere, such as research under product or brand under marketing, is work the VP can only influence, and it is fair to ask how.
How many designers are there for each product manager and each engineering team, and is that the ratio you want?
Why ask it
There is no correct figure, and the VP's opinion of their own ratio is the informative part. A designer spread across three teams spends the week triaging requests, so candidates should ask what the number is on the team they would join.
When a designer joins a product team, who sets their priorities: their design manager or the product lead?
Why ask it
This is the dotted-line question, and it decides who you go to when two requests collide. Either arrangement can work. A VP who says 'both' should be able to tell you what happened the last time the two disagreed.
How do product design and brand or marketing design work together here?
Why ask it
Customers meet the marketing site, the emails and the product as one thing, whoever made each part. The shared pieces, such as the logo, color, illustration and voice, need one owner, and the answer should say who that is. Where brand sits under marketing, you also learn how far this VP's say runs outside the product.
Roadmap
At what point in planning does design come in: before the problem is chosen, or once a feature is already on the list?
Why ask it
This is the plainest test of design's say in the roadmap. Ask the VP to walk through how the last large project started and to name the meeting where a designer first appeared. Arriving after the scope and date are fixed means the job is mostly drawing a decision someone else made.
When did design last get something onto the roadmap that product had not asked for?
Why ask it
A recent example with a name on it shows that design can propose work as well as receive it. Listen to how it got there: a prototype shown to the CEO, a research finding, a count of support tickets. That is the route you would have to take too.
What was the last thing you and the head of product disagreed on, and how did it end?
Why ask it
The subject of the argument is as useful as the outcome. A dispute over a date or a scope cut is everyday business, while one over whether a feature should exist at all means design is in the strategy conversation. If it went up to the CEO, find out how often that happens.
What happens to a design when engineering says there is not time to build it as drawn?
Why ask it
It happens on every project, so the answer describes ordinary life on the team. The better versions have the designer in the room choosing what to cut and a named way for the rest to come back later. 'We ship a first version and return to it' deserves the follow-up: when did you last return?
How much of a designer's week goes to discovery, and how much to producing screens for work that is already scoped?
Why ask it
A rough split is all you need. Put the same question to a designer on the team if you get the chance, since the view from the top of a design org is often rosier than the calendar of the person doing the work.
Is any design and engineering time reserved for fixing what has already shipped?
Why ask it
Rough edges pile up in a product the way technical debt does in code, and they get fixed only when somebody has protected the time. A standing budget, a rotating polish week or a tracked list are all real answers. 'When we can' usually means when a customer complains loudly enough.
What was the last launch you asked to delay or change because the experience was not ready?
Why ask it
Holding a launch costs a VP something with their peers, so a real example tells you they are willing to spend it. How it ended matters less than you might expect: being overruled once is no bad sign, but never having asked is.
Research and systems
Is there a dedicated research team, and does it report to you?
Why ask it
Research may live in design, in product, in a separate insights group, or nowhere, with designers running their own sessions. Each is workable. The thing to find out is who a designer goes to with a question about users, and how long an answer takes.
How often does a designer here watch or talk to a real user?
Why ask it
A date is a better answer than a policy. Weekly sessions that anyone can join put designers in front of users as a habit. If access runs through sales or a single researcher's calendar, expect to design from secondhand accounts much of the time.
What did research find in the past year that changed a decision above the team level?
Why ask it
Findings that only adjust a button are useful but small. One that moved a roadmap item, a pricing page or a company priority shows that leadership reads the work. If the VP has to think for a long while, ask where research reports go once they are written.
Who decides what gets researched: the researchers, the product teams or you?
Why ask it
When product teams commission every study, research can end up confirming what is already planned. Some share of the agenda set by the researchers themselves, or by the VP, is how the uncomfortable questions get looked into. The proof is a recent study that nobody on the product side requested.
Who owns the design system, and is it staffed as a product of its own or kept up on the side?
Why ask it
A system with named designers and engineers assigned to it tends to get maintained. One that depends on volunteers slows down whenever the roadmap gets busy. Ask how many people work on it full time and whose budget they sit in.
How closely do the components in the design files match the ones in code?
Why ask it
This gap is where handoffs go wrong: a designer picks a component that looks right, and the coded one behaves differently or does not exist. An honest VP will name the areas that are out of step. Closing the gap takes engineers as well as designers, so listen for whether engineering leadership has signed up to it.
When a team needs something the design system does not have, what are they allowed to do?
Why ask it
The options are usually to wait, to build a one-off, or to contribute the new piece back. Find out which is normal and how long a contribution takes to be accepted. A slow or unclear path is how a product ends up with five kinds of dropdown.
Where does accessibility get checked: in the design system, in a review, or by each designer alone?
Why ask it
What a company owes on accessibility, by law or by contract, differs with the product, the customers and the country, and the VP should know which rules bind this one. The sharper half of the answer is who can stop a release that falls short. If nobody can, the commitment is a preference.
How are designers here using AI tools today, and what are they not allowed to put into them?
Why ask it
Two answers are folded in here. One is the rule, which each employer writes for itself: the approved tools, and whether customer data or unreleased screens may be pasted into an outside service. The other is the VP's view of what these tools change about a designer's job, which matters if the team's way of working is about to shift.
Quality bar
How does critique work here: how often, who is in the room, and do you attend?
Why ask it
Get the mechanics. A weekly session across teams, with work shown early, is a different culture from an occasional review before launch. A VP in every critique can raise the bar or make people show only finished work, so ask a designer which it is.
Can you show me a piece of recent work that sets the quality bar, and tell me what makes it the standard?
Why ask it
Adjectives about quality are free. An example forces a choice, and the reasons given show what this VP values: visual finish, how errors and empty states are handled, the clarity of the writing, or the result it got. Candidates can hold it up against what is in their own portfolio.
Which work do you review yourself before it ships, and which never reaches you?
Why ask it
Nobody at this level sees everything, so there is a filter, and it is worth knowing what it catches. Find out whether the review is a gate or advice, and how late in a project it comes. Feedback from the top a week before release is expensive for everyone.
What shipped recently that you were not happy with, and why did it go out anyway?
Why ask it
Any VP of Design who still looks closely at the product has one. The reason, whether a date promised to a customer, a missing engineer or a lost argument, shows which pressures outrank design here. Follow with whether it has been fixed since.
After handoff, who compares what engineering built with what was designed?
Why ask it
In some teams the designer signs off on the build before release, and in others the first time they see it is in production. What separates the two is whether a design check of the build is a step in the release process or a favor between colleagues. It is a cheap place to catch a drop in quality, before customers do.
How do you keep the product feeling like one product when many teams design parts of it?
Why ask it
The usual tools are a shared system, written principles, cross-team critique and a person with the authority to say no. Ask which of these does the most work here, and for a place in the product where it has not worked yet.
How early are designers expected to show unfinished work, and to whom?
Why ask it
Good for a skip-level, since the VP's answer is permission you can use afterwards. A rough sketch gets shown on day two only where it is safe to be wrong in front of others. If polished decks are the norm, ask what happened the last time someone brought something half-formed.
When you disagree with a designer's direction in a review, what happens next?
Why ask it
The answer shows how much the designer's own judgment counts. Some leaders state the concern and leave the call with the designer and their manager, and others expect the change to be made. The telling follow-up is a time a designer held their ground and turned out to be right.
Which part of the product would you redesign first if you had a free quarter?
Why ask it
A fast, specific answer means the VP uses the product and keeps a list. It also tells you where design has been losing the priority argument. Candidates can ask whether the role they are up for touches that area.
Team and ladder
What do you look for in a designer's portfolio that most candidates leave out?
Why ask it
Mostly for candidates. If the portfolio review is still ahead of you, the answer tells you what to add, and if it is behind you, it tells you how yours was read. Common replies are the reasoning behind a decision, what was tried and dropped, and what happened after launch, though every VP has a favorite.
How many design roles are you hiring this year, and are they new seats or replacements?
Why ask it
New seats mean the company is adding to design, and replacements only keep it level. A candidate promised a growing team should hear which of those roles has a signed-off budget now, because the rest can vanish in the next planning round. For people already inside, the mix of roles shows what the VP thinks is missing.
How do you make the case for more designers, and what did the last request run into?
Why ask it
Engineering headcount is often argued from a roadmap, and design has to find its own argument: a ratio, a list of teams with no designer, work that slipped. What the CEO or finance pushed back on shows how the company sees the function.
Is there a written career ladder for design, and when was it last revised?
Why ask it
Ask to see it. A ladder borrowed from engineering with the nouns changed tends to be vague about craft, and one written years ago may describe a smaller team. Candidates should also ask which level this role maps to and who decided that.
How far does the individual contributor track go, and how many staff or principal designers are on it today?
Why ask it
A track that exists on paper with nobody at the upper levels is a promise that has not been tested. Where there are people at those levels, what they work on and whether any were promoted from inside show if the track is real. If the only way up is into management, it is better to know before you join.
What separates a senior designer from a staff designer here, in work you could point to?
Why ask it
Push past 'scope' and 'influence' to an example: a system others build on, a flow that crosses several teams, a direction the company adopted. The clearer the example, the easier it is to plan your own next two years.
When a designer is up for promotion, who judges the case: design leaders alone, or product and engineering too?
Why ask it
A design-only panel can weigh craft directly. A mixed one has to be shown why the work was hard, which tends to reward designers who write their decisions down. Whichever runs here, the practical thing to learn is what a successful case looked like in the last cycle.
Are designers leveled and paid on the same bands as engineers and product managers at the same level?
Why ask it
Whether design levels line up with engineering and product levels is a fact about structure, and most VPs can speak to it even where pay figures are off limits. A design level that sits a step below its engineering equivalent says something about standing that no values statement will. How pay is set varies by employer and location, so take the answer as true for this company only.
Apart from promotion, how does a designer here keep getting better at the work?
Why ask it
Mentoring from a staff designer, a rotation onto an unfamiliar product area, a budget for courses or conferences: what exists differs from one employer to the next, so get the specifics. 'Critique', offered alone, is a thin answer, because critique is aimed at the piece of work on the table. Managers can ask what is in place for their own development.
Do design managers here still design, and what do you judge them on as managers?
Why ask it
Some orgs keep managers on project work and some pull them off it entirely, and the two make for different jobs under one title. On the judging half, a list that stops at shipped projects leaves out the people: whether designers on that team grow, stay and get promoted. Managers asking for themselves can add how many reports is typical.
Impact
How do you measure the impact of design, and who sees those measures?
Why ask it
Expect a mix: product metrics shared with the teams, usability or satisfaction scores, and softer signs such as how early design is invited in. No single number captures it, and a VP who claims one should be asked what it misses. The audience matters as much as the measure, since a figure only the design team reads changes little.
Are designers held to the same product metrics as their product managers and engineers?
Why ask it
Sharing the team's targets gives a designer standing in the argument about what to build next. It can also pull every decision toward what is easy to count. Ask how a designer's own review weighs the team's numbers against the quality of the work.
What does the CEO expect from design this year?
Why ask it
The answer should be short enough to repeat: a rebuilt core flow, a second product that feels like the first, fewer support contacts. If the expectation is only that things 'look better', the VP is still teaching the company what design is for, and part of that teaching will fall to the team.
How do you explain the value of design to the CEO or the board?
Why ask it
The vocabulary is what to listen to. Revenue, retention, cost to support and speed of delivery are words that move budgets, and a VP fluent in them will usually have an easier time defending the team. The question the CEO asked about design most recently, if the VP will share it, shows what the top of the company is still unsure of.
What result from the past year would you credit to design, and how do you know it was design?
Why ask it
The second half keeps the answer from being a launch announcement. Clean attribution is rare, since product, engineering and marketing all had a hand, so a careful answer admits that and still makes a case. Note the kind of result chosen, because it is what gets celebrated here.
How do you account for quality that no dashboard shows, such as consistency or trust?
Why ask it
Some of what design does will never show up in an experiment. Leaders handle that with a quality review, a scorecard of their own, or by simply insisting. The method matters less than whether the CEO and the head of product accept it as evidence.
When an experiment favors the version the designers think is worse, which one ships?
Why ask it
A real case beats a policy here. Shipping the winner every time means the metric is in charge, and overriding it every time means the tests are for show. The interesting answers describe what else was checked, such as a longer time frame or a second measure, before deciding.
What do you want design at this company to be known for in two years?
Why ask it
A closing question that suits an all-hands as well as an interview. Hold the answer against everything you heard earlier: if the ambition is craft and no time is reserved for polish, or influence and design joins planning late, ask how the distance gets closed.
Getting real answers from a VP of Design
Practical guidance for the conversation itself
Doing the groundwork
Use the product before you ask about it
Spend twenty minutes in the product, or in whatever is public if you are a candidate: the sign-up flow, the marketing site, the help pages. Note two places where it stops feeling like one product. A question under Quality bar that points at a real screen gets a straighter answer than one about principles, and it shows you looked.
Read the open design roles
The company's job postings show what the design org has and what it is short of. A first researcher, a design systems lead or a content designer on the careers page tells you which of the middle groups will get the liveliest answers. The postings also hint at how far the VP's title reaches, since at one company it covers product design alone and at another research, brand and design operations as well. If you still cannot tell, open with the question about disciplines.
Choose as a designer or as a manager
An individual designer's decision usually turns on Roadmap, Quality bar and how far the non-management track goes. A design manager needs the ratio of designers to teams, the headcount argument and what managers are judged on. Mark the five or six that bear on your own next move and let the rest go, since an interview loop may leave time for only two or three of them.
Know your own answers
Before asking how critique runs or what a staff designer does, be ready to say how it worked on your last team. A VP of Design will often turn the question round, and the comparison is how you will judge what you hear.
Three settings, three ways to ask
As a candidate in the loop
The VP is deciding about you while you ask, so lead with Where design sits and Roadmap. They show you understand that a design job is shaped by design's standing in the company. Save the blunter questions under Team and ladder, such as pay bands and who judges a promotion case, for a final round or for after an offer.
In a skip-level
You already know the org chart, so pass over the first group and go to Quality bar, Team and ladder and Impact. Tie each question to something you have seen: 'In our last two launches design joined after scoping. Is that how you want it to work?' Tell your manager beforehand what you plan to raise, so nothing you ask lands on them as a surprise.
At an all-hands
Pick something the whole design team shares, such as the ladder, the hiring plan or where the design system is headed, and word it so the answer can be a commitment. 'When will the revised ladder be published?' can be answered with a date, while 'What are your thoughts on growth?' invites a speech. Anything about one team, one person or one review belongs in a smaller room.
Ask to see the thing
Design orgs write a lot down: the ladder, the critique schedule, the system's contribution guide, a research report. 'Could I see it?' is a fair follow-up to nearly any answer in the middle groups, and a document tells you more than a description of it. A candidate may be told some of it is internal, which is a reasonable reply.
What the answers are telling you
Owned or invited
Through every group, listen for whether design decides or is consulted. 'We are brought in early' and 'we set the direction for that flow' sound alike in the moment and describe different jobs. When you cannot tell which you heard, ask who made the final call on the last project the VP mentioned.
Craft words and business words
Notice which vocabulary the VP reaches for. One who speaks only of polish and delight may have a hard time in a budget meeting, and one who speaks only of conversion may not hold a launch for quality. You are listening for someone who moves between the two, because a design team needs both arguments made on its behalf.
Hold the answers up to the product
You used the product before the meeting, so compare. If the VP describes a high bar for consistency and the sign-up flow has three styles of button, the distance between the two is a rough measure of how much authority design has had so far. Raise it as a question about history and not as a gotcha: 'What is the story behind the onboarding flow?'
A young design org is not a worse one
A team of eight with no written ladder and a design system still being built can be the better place for someone who wants to help set things up. The reverse holds for a designer who wants deep critique and a long individual track from the first day. Sort the answers by what you want from the next two years, not by how finished the org sounds.
What to leave out
Asking for a portfolio review
Asking what a VP of Design looks for in portfolios is fair. Asking what they think of yours is not, unless they offer. In a loop, that feedback comes through the recruiter. In a skip-level, ask for it from your manager or in critique, where the people who know the work can answer.
Opening with tools
Which design tool the team works in is a fact a recruiter or any designer can give you. Leading with it tells a VP you are thinking about files while they are thinking about the org. The one tooling question worth the slot is the one on AI, because it is about rules and where the job is heading, not about software.
Design against everyone else
Questions framed as a grievance, such as why product always wins or why engineers ignore the specs, leave the VP defending colleagues. Ask how the decision gets made and let the answer show you who wins.
Arriving with a redesign
Candidates sometimes bring a list of what is wrong with the product, or a mocked-up fix for it. Without the constraints behind a screen, that reads as a verdict on the work of people you are hoping to join. Turn the observation into a question, such as what the history of that flow is, and let the VP say whether they see the same problem.