Many designers treat a job interview as something that happens to them.

You prepare your portfolio, you rehearse your case study, you make sure you can answer the hard questions. The process is built to evaluate you, and so you show up to be evaluated. That's understandable. But it's also a mistake.

An interview process is the best opportunity you'll ever get to evaluate an employer. You have access to people, information, and candour that disappear the moment you sign. The hiring manager is motivated to impress you. The team wants you to like them. The organisation is, whether it intends to be or not, showing you exactly what it is.

Most designers don't take full advantage of this. They ask polite questions at the end of each stage, wait to see if an offer arrives, and then try to make a decision with whatever information they've managed to gather along the way.

By the time an offer is on the table, the psychology has already shifted. The number is real. A start date starts forming in your head. The questions that felt important start to feel like obstacles.

The right time to ask hard questions isn't after you get the offer. It's at every stage before it. If you're thoughtful about this from the first conversation, you'll arrive at the end of the process having already made your decision, rather than making it under pressure with a deadline attached.

Here's what to actually ask, and why it matters.

What you're actually trying to find out

Before getting to specific questions, it's worth being clear about what you're really assessing.

At a senior level, your impact depends almost entirely on the conditions around you. Your skills aren't in question. What determines whether those skills translate into outcomes is whether design has genuine influence in this organisation, whether you'll be given real ownership, whether the leadership above you understands what good design looks like, and whether the team around you is one you can develop and be developed by.

You're not just assessing the role. You're assessing the system you'd be operating inside. And systems are harder to read than job descriptions.

The questions worth asking

On design's influence in the organisation

"How does design typically get involved in product decisions, and at what stage?"

This is the most important question on the list. The answer will tell you more about the organisation's design maturity than anything else. If design is consistently brought in after the key decisions have been made, your job will largely be execution. That might be fine, but you should know that going in. Listen for specificity. Vague answers about "being part of the process" usually mean the reality is messier than the aspiration.

"Can you give me an example of a time design changed the direction of something significant?"

This forces a concrete answer rather than a cultural one. Any organisation can tell you design is valued. Fewer can point to a specific moment when it actually changed something that mattered. If the interviewer struggles to answer this, that's information.

On ownership and decision-making

"What does design ownership actually look like here? Where does it start and where does it end?"

Senior designers need real decisions to make. Not just executional decisions within a defined brief, but genuine ownership over how problems are framed and how solutions are shaped. Ask directly. If the honest answer is that most design decisions are reviewed and adjusted by product or engineering before anything ships, you need to know that before you accept.

"When designers and product managers disagree on direction, how does that typically get resolved?"

Power dynamics in product teams are rarely stated explicitly. This question surfaces them. There's no universally right answer, but the answer you get will tell you a lot about where design sits in the hierarchy of decisions, and whether a senior designer has genuine standing or just a seat at the table.

On the team and your development

"What does the design team look like right now, and what's missing from it?"

Two things in one question. First, you get a picture of what you'd actually be working with. Second, and more usefully, how a leader describes what's missing tells you a lot about how clearly they're thinking about capability. "We need someone senior" is a different answer to "we have strong craft but no one who can hold the strategic conversation." The latter suggests they've actually diagnosed the gap rather than just felt it.

"How do senior designers grow here? What does progression look like beyond this role?"

This question gets dismissed as something only junior candidates ask. It isn't. A senior IC in an organisation that has no clear path beyond their level, and no culture of investing in the people already there, will eventually plateau. Not because of their capability, but because of the ceiling above them. Know where the ceiling is before you walk in.

On leadership

"What's your biggest concern about this hire?"

Ask this directly to whoever would be your line manager. It's uncomfortable. That's the point. The answer is almost always more useful than anything that comes from a comfortable question. A leader who can answer honestly, who has thought carefully about the risks and trade-offs of this hire, is usually a leader worth working for. One who deflects or gives you a polished non-answer is showing you something too.

"How would you describe the relationship between design and the rest of the business right now, honestly?"

The word "honestly" matters. It signals that you're not looking for the brochure version. Some leaders will still give it to you. But many will take the invitation and tell you something real, about where the friction is, where the work needs to happen, what they're trying to change. That's the information that will actually help you decide.

What you're listening for

Good answers to these questions share a few qualities. They're specific rather than general. They acknowledge complexity rather than smoothing it over. They suggest the person has actually thought about these things rather than reaching for the version they think you want to hear.

Organisations that are genuinely good environments for senior designers tend to answer these questions with some candour about where they're still working things out. Perfect answers are often a warning sign. The best organisations know their limitations and are honest about them. The ones to be cautious about are the ones where everything is already great, the culture is strong, design is respected, and there are no real problems to speak of.

No design function is without its friction. The question is whether the friction is the kind you can work with, or the kind that will slowly drain the thing that makes you good.

Take control of the process

The designers who make the best decisions about where they work aren't the ones who wait to be chosen and then decide. They're the ones who treat every stage of the process as a two-way assessment, gathering information deliberately, asking the questions that actually matter, and arriving at the end already knowing whether they want to be there.

An employer who is put off by a candidate who asks good questions is telling you something important. The ones worth working for tend to respect it.

You are evaluating them as much as they are evaluating you. The process works better when both sides know that.

At Gale & Co., we prepare every candidate we work with for this, not just helping you get the offer, but helping you decide whether to take it. If you're weighing up a senior design role and want a second perspective, get in touch.