You got the call. You cleared the first round. Maybe you even completed an assignment. You sent a follow-up. You waited.
Nothing. Not a rejection with feedback. Not a call with results. Just automated silence, or a template email that tells you nothing about what actually happened. You are left wondering - was it the portfolio? The assignment? Something you said? Something you didn't say?
This is not an unusual story. We hear versions of it almost every week. Designers who are getting calls, clearing Round 1, sometimes submitting assignments that took them days to complete, and then disappearing into a void. I want to tell you what's actually happening in that silence. Not the polite version. The real one.
First, Understand What Round 1 Actually Is
Round 1 is not an interview. Not in any meaningful sense. It is a vocabulary filter.
A recruiter or hiring manager gets on a call with you for 20 to 45 minutes. They are checking three things: does this person use words that match the job description, do they fall within the budget range, and do they seem human enough to put in front of someone more senior. That is the entire scope of Round 1 for most organisations.
Almost anyone who has been working in design for two or more years can pass one. You know the language. You have done the projects. You can answer 'walk me through your process' well enough to get to the next stage.
Round 1 is designed to filter out the obviously wrong candidates. Round 2 is designed to find the right one. These are fundamentally different problems.
Round 2 is where someone starts asking questions that cannot be answered with vocabulary alone. Why did you make this decision? What did you consider and reject? How did you handle the constraint? What would you do differently? What happened when the PM pushed back? That is a different conversation entirely. And most designers are not prepared for it - because they prepared for Round 1 again.
The Funnel Nobody Told You About
The interview process is a funnel. This is not a metaphor. It is a literal conversion problem, and most designers are treating it like a presentation.
Your resume gets someone to look at your portfolio. Your portfolio gets someone to call you. Your Round 1 performance gets you to Round 2. Each stage has a different audience, different evaluation criteria, and a different version of the question it is trying to answer. What works at one stage will not necessarily work at the next.
Here is where it breaks down. Designers spend enormous amounts of time on the top of the funnel. Resumes are polished. Portfolios are carefully crafted. And then the call comes, and they treat it exactly like the portfolio - as a monologue, a showcase, a performance of competence.
The portfolio is a vehicle. It opens the door. What you say when that door opens is a completely different skill, and most designers have spent almost no time developing it. If the top of your funnel isn't working at all, we cover that separately in why you're not getting UX interview calls.
Nobody Told You That You Are a Salesperson
This is going to sound uncomfortable. I am saying it anyway.
When you are in an interview, you are selling your services. You are the product. The hiring organisation is the buyer. And whether you know it or not, every signal you send in that conversation is either moving the sale forward or killing it.
Here is what that looks like in practice. A recruiter calls. Before the recruiter has had a chance to explain the role, the designer is telling them their salary number. Not exploring the opportunity. Not asking questions. Declaring a position. 'I am not open to negotiating. I want X in hand, fixed, and anything above that is fine.'
I understand where this comes from. Designers have been undervalued. They have been overworked and underpaid. That frustration is legitimate. But what is being communicated in that opening exchange is not confidence. It is resistance. And a buyer who encounters resistance before they have even made a case for why they want to buy will walk away.
Chris Voss - former FBI hostage negotiator and author of Never Split the Difference - is direct about salary conversations: never state your number first. Whoever anchors first loses leverage. Treat every compensation conversation as a discovery exercise: understand what the role is actually worth to the organisation before you price yourself against it.
The cocky opener is one failure mode. The opposite is also common - the designer who is so eager to please that they answer every question with what they think the interviewer wants to hear, contradict themselves twice in the same call, and leave no impression of any distinctive point of view. Neither version sells well.
Selling your services well means knowing your value, being able to articulate it clearly and specifically, asking good questions to understand what the organisation actually needs, and timing your positioning so it lands when it can actually be received.
The Portfolio Went In Fine. The Mouth Broke Everything.
Building a portfolio has never been easier. Templates are accessible, references are abundant, AI can help with everything from copy to case study structure. A designer with two years of experience can produce a portfolio that looks like five years of work if they know what they are doing with the tools available.
What it means is that the portfolio is no longer a reliable signal of depth. It has become a signal of effort and presentation skill. The interview - the actual live conversation - is now where depth gets tested. And that is exactly where the performance breaks down.
Nielsen Norman Group's research on UX hiring makes this gap explicit. Newer designers tend to define craft as visual impressiveness - the extra detail, the polished finish, the Figma precision. Experienced hiring managers define craft as the invisible things: the decisions that were made, the constraints that were navigated, the thinking that informed the outcome. Two completely different definitions of quality.
A hiring manager asks: 'Why did you choose this approach over the alternatives?' The designer who built the portfolio as a skin - who made the screens beautiful without deeply understanding the decisions behind them - has nowhere to go with that question. When pressed, the answer becomes vague. Then longer. Then defensive.
This is not about designers being dishonest. Most of them are genuinely proud of their work. The problem is that building something and being able to explain the intellectual process behind it are two different skills. Many designers have only trained one of them.
If your portfolio itself needs rebuilding around business impact rather than just screens, start with the business-driven portfolio guide. If your best work is locked behind an NDA, we cover five specific strategies for that in the NDA portfolio piece.
The Deflection Patterns That End Careers in Interviews
When a designer cannot answer a question about their own work, something interesting happens. They do not say 'I do not know.' They explain why the work was not their fault.
'My PM did not allow it.'
This is the most frequent. A hiring manager asks why the designer did not do usability testing, or why there is no evidence of research. There is a version of this answer that shows maturity: 'The PM had a different priority, so I had to find ways to bring in user insight without a formal research budget - here is what I did instead.' And there is a version that is a display of helplessness: 'That was not my call to make.' The difference is everything.
'We did not have the budget.'
Budget constraints are real. But 'we did not have the budget' as an explanation for why nothing meaningful happened is not a constraint - it is an exit. What did you do when the budget was not there? What did you propose? What low-cost approach did you find?
'Ours is a service organisation.'
This one is shorthand for: we do not have the luxury of doing things properly. That may be true. It is also true of most design environments to varying degrees. The question is what you did within that reality - how you pushed back, how you carved out space, how you influenced direction even when the structure did not invite it.
Every excuse is a display of who is behind the facade. When a designer describes their constraints instead of their responses to constraints, they are telling you exactly what level they are operating at - and it is not senior.
This gap between having the title and having the influence is exactly what we explore in the piece on moving from delivery person to strategic contributor.
What the Whiteboard Actually Reveals
Collaborative exercises - whiteboarding sessions, live design challenges, real-time problem-solving with a team - are the most revealing thing in the entire funnel. Not because they test whether you can design under pressure. Because they test who you actually are when the script runs out.
Two things happen in a whiteboard session that do not happen anywhere else:
You find out if the designer can collaborate or if they can only perform. Some designers turn it into a solo presentation. They take over the conversation. They generate ideas rapidly and fill the space. They do not ask questions of the other people in the room. Design at a senior level is almost entirely collaborative. The designer who cannot share a problem - who cannot hold space for another perspective - is not a senior designer. They are a solo operator.
You find out how the designer handles not knowing something. In a whiteboard session, gaps in knowledge surface immediately. Do they acknowledge the gap and propose a way forward? Or do they paper over it with confident-sounding language that turns out to be empty? A whiteboard session is the only point in the interview process where you cannot prepare a portfolio entry for it. What comes out is what is actually there. This is also where the gap between surface-level AI tool usage and genuine depth becomes impossible to hide.
What Round 2 Is Actually Measuring
Let me be direct about what Round 2 interviewers are actually trying to understand. It is almost always some version of these four questions:
- Can this person think, or can they only execute?
- Can this person operate in a real environment - with constraints, ambiguity, and people who disagree with them?
- Is the depth behind the portfolio real, or was the portfolio the entire performance?
- Is this a person we will want to work with closely, or is working with them going to be expensive?
Notice that none of these are about whether the work looks good. The work looking good was established in Round 1. Round 2 is about everything underneath the work.
A designer who understands this prepares for Round 2 completely differently. Instead of reviewing the portfolio and practising the walkthrough again, they ask harder questions of themselves. Why did I make each major decision? What did I consider and reject, and why? What would I do differently? How did I work with the people in the room? What happened when the project went wrong?
What to Do Differently - Specifically
Before the call: research the organisation as a buyer, not as a job seeker.
There is a difference between researching a company to answer 'what do you know about us' and researching a company to understand what they actually need from a designer. What problems are they solving? What is the design maturity of the organisation? What constraints are they likely operating under? When you walk into a conversation having done that kind of research, your questions are better, your answers are more relevant, and you demonstrate something no amount of portfolio polish can demonstrate: that you thought about them, not just about yourself.
In the conversation: stop presenting and start selling.
Ask questions early. Find out what the interviewer is actually looking for. Then position your experience against that specific problem. If a recruiter asks about salary before you have had a chance to understand the full scope of the role, it is completely acceptable to say: 'I want to make sure we are looking at the same thing before we talk numbers - can you help me understand what this role is responsible for and what success looks like in the first six months?'
On your portfolio: know the decisions, not just the deliverables.
For every case study, you should be able to answer three questions with specificity and without hesitation: What was the core design problem? Why did I choose this approach over the realistic alternatives? What happened when it was challenged - by data, by stakeholders, by the reality of implementation? If your strongest work is under NDA, that does not excuse you from this - the NDA portfolio strategies we cover show exactly how to present this depth without violating anything.
On constraints: make them the context, not the excuse.
When constraints come up - and they will - your answer should follow a consistent structure: here is the constraint, here is what it meant for the project, here is how I worked within it or around it, here is what I learned from doing so. Four beats. Every time.
On collaboration: show up to exercises as a participant, not a performer.
In any collaborative session, your job is not to be the most impressive person in the room. Your job is to be the most useful person in the room. Ask questions. Build on what others say. Identify what the group does not yet know before you start proposing solutions. The hiring managers watching are not scoring how many ideas you generated. They are watching how you treat other people's thinking.
The Silence Is Not Rejection. It Is Information.
When the ghost comes - and it may - the most useful thing you can do is resist the urge to take it personally and instead read it as data.
You cleared Round 1, which means something about your surface presentation worked. Something about your vocabulary, your portfolio, your initial impression was enough to move forward. That is not nothing.
What the silence is telling you is that somewhere between Round 1 and the end of Round 2, the picture the organisation formed of you became inconsistent. The work said one thing. The conversation said something else. And when they had to choose, they chose the person whose work and words were aligned.
That is fixable. Entirely and specifically fixable. But it requires understanding that the interview is a funnel - not a presentation - and that your job at every stage is to convert the person in front of you, not to perform for the idea of a hiring manager in your head.
You are not being ghosted because your work is not good enough. You are being ghosted because your ability to sell that work has not kept pace with your ability to do it.
Before Your Next Application - A Brief Diagnostic
Read these questions honestly. Not the version of them you would answer in an interview. The actual honest version.
- Can I explain the three most important design decisions in my lead case study - the decision, the alternatives I rejected, and why - in under two minutes?
- In my last interview, did I ask at least as many questions as I answered?
- When was the last time I was asked a question in an interview that I could not answer - and what did I do with it?
- When I talk about projects where things went wrong, do I talk about what I did, or do I talk about what was done to me?
- In a collaborative session, have I ever been the person who dominated the conversation without noticing it?
If any of these landed, that is where the work is. And if you are starting to see that the issue might be deeper than interview technique - that it is about how you are positioned in the market entirely - the PIE model for design influence is the framework we use to address it.
The designers we work with in the Current programme - 2 to 6 years of experience, getting calls but not converting - work through exactly this. Not just portfolio strategy. The full interview funnel: how to present, how to position, how to answer the hard questions, and how to read what is actually happening at each stage.
If you are further along - senior and moving into leadership - the Tide programme is where that work happens.
Book a free 45-minute strategy call - walk away with a clear read on where you are in the process and what specifically needs to change.
Read Next
- Why You're Not Getting UX Interview Calls (It's Not Your Portfolio)
- You're a Senior Designer in Title. You're Still Being Treated Like a Delivery Person.
- AI Isn't Taking Your Job. But This Type of Designer Will.
- Your NDA Isn't the Problem. Your Portfolio Strategy Is.
- Almas Tasneem, Co-founder, Xperience Wave