Behavioral Interview Questions for Design Managers
By Dara Halloran · Under Pressure
What behavioral questions do design manager interviews ask? Expect a design you had to defend against stakeholders, how you run critique, a disagreement with product or engineering, research that changed direction, and a designer you developed. Answer with real projects, show the reasoning behind decisions, and explain how you make novel ideas feel safe enough for people to accept.
Design managers lead designers, but much of their job is persuading people who are not designers: product managers, engineers, executives. Interviews test both halves. Expect questions about how you develop designers and how you get good design work through organisations that are often uneasy about it.
Why good ideas get rejected
One of the most useful things a design manager can understand, and talk about in an interview, is why stakeholders reject creative work even when they say they want creativity. Jennifer Mueller, Shimul Melwani and Jack Goncalo found that people can hold a bias against creative ideas that is not obvious, and that it shows up when they feel uncertain: under uncertainty, participants favoured practical ideas over creative ones and were worse at even recognising a creative idea.1
That gives a design manager a strategy, and a strong interview answer. When you present a bold design, reduce the uncertainty around it: show the evidence from research, a prototype people can try, a small test, the risk and how you will measure it. The idea stays bold; the uncertainty shrinks.
Defending the work
"Tell me about a design you had to defend against stakeholders." What the design was, the objection, how you made your case (with evidence, prototypes, tests) and what happened.
"Tell me about a time you were wrong about a design." Research or data that proved you wrong, and what you changed.
Critique and quality
"How do you run design critique?" Show the format, how you keep feedback specific and about the work, and how junior designers participate.
"Tell me about raising the quality bar on a team." What you changed: standards, a design system, review steps.
Partnership
"Tell me about a disagreement with product or engineering." About scope, feasibility, priorities. How you understood their constraint and what you agreed.
"Tell me about getting design involved earlier in a product process."
Research
"Tell me about research that changed direction." The finding, how you presented it, and the decision it changed.
People
"Tell me about a designer you developed." Their growth, your part in it, where they are now.
"Tell me about hiring for a design team." What you looked for, how you assessed portfolios and thinking, and a hire you are proud of.
The numbers to have ready
Team size and makeup, the products you shipped, any measured outcomes (conversion, task success, satisfaction), and retention and promotions on your team.
Questions to ask them
Ask how design decisions are made when design and product disagree, where designers sit in the product process (at the brief or after it), how the team's work is measured, and what happened to the last bold design proposal. The answers tell you how much room the role really has.
One answer, told well
"We proposed replacing a twelve-field sign-up form with a two-step flow that asked for almost nothing up front. The head of sales thought we'd lose the lead data his team relied on. Instead of arguing, we ran the new flow for 10% of visitors for two weeks, collecting the same data after sign-up. Completion rose by a third and we lost almost none of the data. The test turned an argument into a decision, and we now pilot any big design change the same way."
For presenting work that stakeholders resist, see presentation tips for product development managers, and for every answer's structure, the STAR technique.
References
- Mueller, J. S., Melwani, S., & Goncalo, J. A. (2012). The bias against creativity. Psychological Science, 23(1), 13–17. https://doi.org/10.1177/0956797611421018