Landing Your Next Design Role

Happy Tuesday, UI Collective!

After spending the 8 years on both sides of the interview table, I've noticed a striking pattern: most candidates focus on what they think design leaders want, rather than what actually influences hiring decisions. Let's change that.

But first, a new YouTube video! We just released a new video on building a design token library using a two tiered architecture. Although we reccomend a three-tiered approach, take a look at this alternate method on setting up your design system!

The Hiring Reality Check

In recent conversations with Michael Carrick, CEO fo Experience Design Systems, an interesting trend emerged: most candidates emphasize their visual design skills, but the majority of rejections happen due to gaps in problem-solving ability and strategic thinking. Let's break down what really matters.

Beyond the Beautiful Portfolio

Your portfolio needs to do more than showcase pretty screens. Last month, I was reviewing portfolios with a design director, and she put it perfectly: "I can teach someone to make better buttons. I can't teach them to think strategically about user problems."

What catches our attention:

• Clear problem definitions

• Alternative solutions considered

• Business constraints addressed

• Impact measurements

• Lessons learned from failures

The Responsive Design Question

Here's something most candidates miss: responsive design isn't just about making things fit different screens. In a recent interview, a candidate stood out by explaining how they approached responsive design as a content strategy problem, not just a layout challenge.

They showed how they:

• Prioritized content across breakpoints

• Made strategic decisions about feature parity

• Considered performance implications

• Designed for variable content

• Thought through interaction patterns

This demonstrated not just technical knowledge, but strategic thinking about user needs across contexts.

Real Problems Over Dribbble Shots

During portfolio reviews, I often ask candidates to walk through their most challenging project—not their most visually impressive one. Those who can articulate their decision-making process, especially when dealing with constraints, almost always move forward in the process.

A recent hire stood out by sharing:

• Initial project assumptions that proved wrong

• How they adapted to user feedback

• Conflicts with stakeholders and their resolution

• Technical limitations they worked around

• Business impacts of their decisions

The Technical Understanding Gap

While you don't need to code, you do need to understand technical implications. One candidate recently impressed us not by knowing React, but by showing how they adapted their design system to improve developer efficiency. They demonstrated:

• Understanding of performance trade-offs

• Awareness of implementation costs

• Knowledge of platform constraints

• Collaboration with engineering

Stakeholder Management Skills

Design leaders consistently rank stakeholder management as a top hiring criterion. Show examples of how you:

• Navigate competing priorities

• Build consensus across teams

• Present and defend design decisions

• Adapt your communication style

The Interview Deep Dive

During interviews, we're looking for:

Strategic Thinking

Don't just explain what you did—explain why. Share the business context, user needs, and how your decisions served both.

Learning Agility

Instead of claiming expertise in everything, show how you approach learning new things. One candidate documented their process of learning about blockchain for a crypto project—their learning approach was more valuable than deep crypto knowledge.

Collaboration Style

Through your stories, demonstrate how you:

• Work with different personalities

• Handle conflict

• Give and receive feedback

• Support team members

Red Flags We Notice

The Perfection Trap

Candidates who only show perfect work raise concerns. We want to see how you handle constraints, mistakes, and iterations.

The Solo Designer Syndrome

If every story starts with "I" rather than "we," it suggests potential collaboration issues.

What to Prepare

1. Project Stories
   Document your most significant projects using the STAR method (Situation, Task, Action, Result), but add an extra R for Reflection.

2. Question Framework
   Prepare thoughtful questions that demonstrate:

• Strategic thinking

• Business acumen

• Growth mindset

• Cultural awareness

The Follow-Up That Works

After interviews, successful candidates:

• Send specific, thoughtful thank-you notes

• Address key points from the conversation

• Share relevant resources discussed

• Demonstrate continued interest and engagement

Looking Ahead

The design job market constantly evolves. Currently, we're seeing increased emphasis on:

• Business impact measurement

• Cross-functional collaboration

• Systems thinking

• Product strategy

Your Next Steps

This week:

1. Audit your portfolio through this lens

2. Document your impact metrics

3. Practice articulating your decision-making process

4. Prepare your responsive design examples

Remember, getting hired isn't about being the best designer—it's about being the right designer for the team and challenges at hand.

Talk soon, UI Collective

Kirk McNeill

This newsletter is brought to you by Design System Labs - the design system agency backed by UI Collective, focusing on Enterprise Design Systems, coded components, design system audits, and much more!