Why I Stopped Trusting Job Titles When Hiring Designers

The title said senior. The capability said mid-level. Here is how I learned to spot the difference.

Don Crowley · March 2026

Three years ago, I interviewed a candidate with "Senior Brand Designer" on their CV and eight years of experience. Portfolio looked solid. References checked out.

Ten minutes into the conversation, I asked them to walk me through their process for a major rebrand project.

They described making logos and visual assets.

No brand strategy. No stakeholder alignment. No system thinking. Just execution work dressed up in senior language.

The title said senior. The capability said mid-level.

This was not an outlier. After hiring designers across multiple markets for over a decade, I have learned something uncomfortable: job titles are almost meaningless when assessing design talent.

The title inflation problem

Here is what I see constantly: print designers rebrand as "Senior Brand Designers" overnight, product owners become "Product Managers" without shipping strategy, UI designers with three years of experience become "Senior Product Designers" without ever owning a product end-to-end, and "Design Leads" who have never led anyone.

This is not about dishonesty. It is about inconsistency.

The global design market is maturing at different speeds. What "Senior Designer" means in San Francisco does not match what it means in Amsterdam, Dubai, or Singapore. Not better or worse: just different definitions shaped by different market pressures.

What I actually look for

I have stopped looking at titles and years entirely. Instead, I focus on five questions that reveal actual seniority, regardless of what the CV says.

1. What problems have they solved independently?

Junior designers need direction. Mid-level designers execute well within constraints. Senior designers identify the right problem to solve, then solve it. I listen for autonomy. Did they wait to be told what to design, or did they shape the brief?

2. Can they articulate strategic thinking, not just execution?

A mid-level designer says: "I created a new onboarding flow with better visuals." A senior designer says: "Activation was dropping at step three. I hypothesised the value prop was not landing, tested two variants, and improved completion by 20%." Same work. Completely different framing.

3. Have they led projects from research to launch?

Senior designers should have owned the full arc: discovery, definition, design, iteration, launch, and learning. If they have never seen their work hit real users and adapted based on feedback, they are missing a critical growth experience.

4. Do they talk about business impact or design outputs?

Output-focused: "I delivered 47 screens and a complete design system." Impact-focused: "We reduced support tickets by 30% after the redesign, and NPS improved by 12 points." Outputs are necessary. Impact is what matters.

5. Can they explain a decision they disagreed with?

This is my go-to interview question: "Tell me about a project where your design recommendation was rejected. What happened next?"

Immature designers complain about stakeholders who "did not get it." Senior designers explain the tradeoffs, acknowledge the constraints, and describe how they committed to the decision even when they disagreed. Real seniority is not about being right. It is about being effective.

A framework for hiring across markets

Titles tell you what someone was called. This framework tells you what they can actually do.

The 15-minute filter

Here is what I have learned after hundreds of design interviews: A-players reveal themselves in the first 15 minutes. They talk about problems solved, not tools used. They own outcomes, not just deliverables. They describe collaboration as a skill, not a frustration. They are curious about your challenges, not just their opportunity.

You do not need a three-hour panel interview to spot seniority. You need the right questions and the discipline to listen for what is not being said.