You do UX research. You know how to understand what users actually want, how they actually make decisions, and how to design for them specifically, not for a generalised idea of who they might be.

So let me ask you something uncomfortable.

Have you ever applied that same thinking to your own job search?

Have you ever actually tried to understand the recruiter as a user, their journey, their constraints, what they are scanning for at each stage, what makes them stop and what makes them move on?

Almost no designer has. And it is one of the most expensive blind spots in the entire job search process.

Here is the reframe: in a job application, you are the product. The recruiter is the user. Your resume, your portfolio, your interview performance, these are the touchpoints in their experience of you. And you have been designing those touchpoints without doing any research on the person who is actually moving through them.

This blog is that research. Written from the side of the table most designers never sit at.

The Recruiter's Journey: What Is Actually Happening Before You Get the Call

Most designers think the hiring process starts when they submit an application. It does not. By the time your resume lands in a queue, the organisation has already made a set of decisions that will shape everything that follows.

A hiring manager identifies the need and gets budget approved. That request goes to HR or a recruiting team, who will source candidates from multiple places simultaneously: internal referrals, LinkedIn outreach, job platforms, sometimes specialised design recruiters. The pool that comes in from all of these gets reviewed by a human, usually very quickly.

What is actually true about ATS, and why the popular version of this story is both wrong and right:

The widely cited '75% of resumes are auto-rejected by ATS before a human sees them' originated from a 2012 sales pitch by a defunct resume service called Preptel. No methodology was ever published. The claim has been recycled without a source ever since.

(Source: The Interview Guys, 2025)

What IS true: ATS systems are primarily organisational tools, not auto-rejection machines. Enhancv's 2025 study of 25 recruiters across Workday, Greenhouse, and Bullhorn found that 92% do not configure content-based auto-rejection. The software organises applications; humans make the calls.

But here is where the advice to prepare ATS-friendly resumes remains completely correct: Harvard Business School's Hidden Workers study found that 88% of employers acknowledge their ATS configuration screens out qualified candidates, through human-set filters like employment gaps, keyword mismatches, and years-of-experience thresholds. EDLIGO's analysis of 1,000 rejected resumes found 43% failed due to formatting and parsing errors, not skill gaps.

The mechanism is different from the myth. The result for a poorly formatted resume is the same: a human never gets to read it.

The practical implication: your resume needs to be ATS-friendly, clean formatting, keyword-aligned, no complex layouts or graphics that break parsing. Not because a bot will auto-delete it. Because a poorly structured resume gets deprioritised in a pile of 200 that a recruiter has four seconds each to sort through. The outcome is identical. The cause is different.

After the initial screen, the process at design-mature organisations typically moves through: a pre-discovery call to check fit and bracket, then a portfolio walkthrough or assignment, then sometimes a live whiteboard or collaborative session, then cross-functional conversations with a PM or engineering lead, then a cultural fit discussion, then negotiation and offer.

Each stage is evaluating something different. And the biggest mistake designers make is showing up to every stage with the same presentation of themselves, the same story, the same framing, the same level of depth. That is not how good products are designed. Different users, different contexts, different needs at each touchpoint.

If you are clearing early stages and losing it later, that is a specific problem with a specific fix. We covered what is actually happening in Round 2 here: Why UX Designers Get Ghosted After Round 2 Interviews.

What 'Senior' Actually Means, and the Gap Between What You Think It Is and What They Are Testing For

In the Bangalore market, 3 to 5 years of experience typically qualifies someone for a senior UX designer title. But the title is the easy part. What the hiring manager is actually trying to determine is something much harder to prove from a portfolio.

Senior is not 'does more design'. Senior is 'operates differently'.

A senior designer is expected to handle end-to-end flows, not just detailed components, but full user journeys and structural architecture. They own the design delivery for a defined scope, not just execute what someone else has scoped. They run research and connect it to decisions, not just produce research artefacts. They collaborate with product managers, engineering leads, and business stakeholders, not just other designers. And they do all of this with a confidence that comes from having navigated ambiguity before, not from having a checklist.

The four questions a hiring manager is actually asking about a senior designer candidate:

Can they operate at structure level, or are they still thinking at the detail level?
Do they own their work, or do they wait for direction at every step?
Can they connect their design decisions to outcomes the business cares about?
Will working with them be a contribution or a coordination cost?

Notice what is not on that list: Figma proficiency. Tool stack breadth. The visual polish of their case studies.

UXfolio's 2025 hiring research found the same shift: 'Design leads and recruiters no longer want to see endless tool stacks or pixel-perfect UIs. They are looking for signals that you can navigate complexity, communicate strategy, and connect work to business outcomes.'

The specialisation point is also widely misunderstood. At senior level, you are not expected to be a full generalist, someone who does research, interaction, visual, content, and strategy at equal depth. That is unrealistic and not what the role requires. What is expected is that you have gone deep on two or three disciplines, can contribute meaningfully beyond them, and know clearly what you do and do not do.

A senior designer who says 'I do everything' is usually someone who does nothing at the depth the role actually needs. On what depth actually looks like vs the surface-expander pattern: AI Is Not Taking Your Job. But This Type of Designer Will.

The Signals That Kill Candidacies: What a Hiring Manager Notices and Does Not Say

The rejection almost never comes with honest feedback. But the patterns that cause it are consistent enough that after reviewing hundreds of designer profiles at Xperience Wave, they are predictable.

The tools trap

The designer who leads with tools is flagging something they do not know they are flagging. 'I am proficient in Figma, Maze, Miro, Hotjar, and Adobe XD', this says nothing about how they think, what they own, or what they have produced that mattered. It says they know how to use software.

At senior level, tools are assumed. Nobody asks a surgeon which scalpel they prefer. If the tool conversation is taking up real estate in your resume or your portfolio or your opening presentation of yourself, you are optimising for the wrong audience.

The silo worker

Design that happens in a vacuum and gets presented as finished work is a senior-level red flag. A hiring manager is not just evaluating the output, they are trying to understand how you work. Did you make assumptions that a PM would have caught? Did you design something engineering cannot build? Did you validate with users or just with your own judgment?

Working in opacity and 'revealing' the work is the pattern of someone who is afraid of in-process feedback. That fear is expensive at senior level, because senior designers need to be able to operate in the open, sharing early thinking, incorporating input, adjusting direction before the full solution is complete.

The constraint blamer

'I did not have enough time for proper research.' 'The PM did not allow it.' 'The org does not value UX.'

We covered these exact patterns in a blog specifically about Round 2 interviews, they are the phrases that end candidacies. At senior level, constraints are not explanations. They are the context within which you demonstrated what you could do. The hiring manager wants to know what you actually did within them, not what they prevented. Why UX Designers Get Ghosted After Round 2 Interviews.

The language mismatch

A senior designer who can only present work in design language is a designer who will only ever influence other designers. If you cannot say, clearly, without jargon, what the business problem was, what your solution changed about it, and what the measurable result looked like, you are not yet speaking senior.

This does not mean abandoning design thinking. It means translating it. The hiring manager across the table is often a design director or a product leader who is trying to answer the question: will this person be able to operate credibly with our PM team, our engineering leads, our business stakeholders? The portfolio walkthrough is where they test that.

The Signals That Win Candidacies: What 'Yes' Actually Looks Like

The positive signals are less about impressing the room and more about making the hiring manager's decision easy. They need to be able to go back to their team and say: this person can do what we need, and here is the evidence.

They own outcomes, not just deliverables

The designer who can tell you specifically what changed after the thing shipped, a conversion number, a drop in support tickets, a user behaviour metric, is demonstrating something that a polished portfolio cannot. That they stayed attached to the outcome, not just the output. That they tracked what happened. That they have an opinion about why it worked or did not.

This is not about having big impact numbers on every project. Some projects do not have clean metrics. But the ability to frame impact, even qualitatively, is the difference between a case study and a resume entry. On why the ₹30L designer stays attached to outcomes while the ₹12L designer moves to the next ticket: The Difference Between a ₹12L and ₹30L UX Designer.

They can hold ground without making it a fight

Anna Rowe, Senior UX Director at Indeed, describes what she is looking for in portfolio presentations: practice telling your story to someone who is not familiar with the work. 'Your goal: they understand it in minutes, and they are excited.'

That requires the ability to read the room, to know when to go deeper and when to zoom out, to know when to hold on a decision and when to fold gracefully. A senior designer who can defend a decision under questioning without becoming defensive is showing something rare: that they are confident enough in their thinking to subject it to scrutiny.

They validate and communicate risk

A senior designer who can say 'here is what I do not know yet, here is the assumption I am making, here is the risk if that assumption is wrong' is more valuable than one who presents everything as solved. The hiring manager has worked with enough designers to know that everything is not solved. The designer who pretends otherwise is the one they do not trust.

Highlighting risk early, communicating it clearly, and having a hypothesis about how to test it, this is what senior design judgment looks like in practice.

They make the collaboration feel easy

The cross-functional conversation that happens in most senior hiring processes, with a PM or engineering lead, is not a formality. It is a check on whether the person sitting across from them will create coordination problems or reduce them. The signal they are looking for is not charisma. It is: does this person ask good questions? Do they listen before they position? Do they seem interested in what we are building, or only in presenting themselves? A designer who shows genuine curiosity about the product, the team, and the constraints is a designer who will be useful to work with.

Five Things Designers Get Wrong About Senior UX Hiring

1. 'They want a full generalist who can do everything.'

No. They want someone who has gone deep on two or three disciplines and can contribute meaningfully across adjacent ones. A senior designer who does research, interaction, visual, content, strategy, and systems design with equal depth does not exist. What does exist, and what gets hired, is someone who is genuinely strong in their core area, credibly functional in adjacent areas, and honest about where they stop.

2. 'The portfolio is the job application.'

The portfolio is the door. What happens after you walk through it is determined by everything else: how you present the thinking, how you respond to questions, how you handle the moment when the interviewer challenges a decision you made. A beautiful portfolio from a designer who cannot defend their own work is a liability. It raises expectations that the conversation then fails to meet.

3. 'I will drive design decisions at a vision level.'

At senior level, you influence decisions. You do not drive them. The people who set product vision and philosophy are almost always above you in the structure, a Head of Design, a CPO, a founder. Your job is to make those decisions better through the quality of your thinking and the strength of your relationships. Misunderstanding this is one of the fastest ways to arrive in a new role expecting authority you were never going to have.

4. 'A fancy designed resume will show my design skills.'

The resume is read by an ATS system and then by a human who has 200 others on their list. A complex, graphically rich resume is frequently the one that parses badly, displays oddly, or gets skimmed past because the signal-to-noise ratio is too low. Use a clean, readable format. Put the outcomes front and centre. Design the resume for the person reading it, not for you.

5. 'I will get full authority to do proper research.'

Research happens when you make the case for it and the organisation agrees to the cost. At senior level, that is your job, not to assume research time will be given, but to build the argument for why this specific research, for this specific decision, is worth the investment. Designers who wait for permission to do research get less of it. Designers who show why it matters get more.

So How Do You Actually Prepare For This?

Run user research on your own hiring process.

Talk to someone who has hired at the level you are targeting. Not to get tips, to understand what the job looks like from their side. What are they actually afraid of when they are making this hire? What went wrong with the last person in this role? What does success look like for them in six months?

That information changes how you present yourself completely. Because instead of telling your story, you are telling the part of your story that answers what they actually need to hear.

The hiring manager is not looking for the best designer in the pool.

They are looking for the designer who makes their specific problem easiest to solve.

The more you understand their problem, the easier it is to show that you are that person.

Map your portfolio to their questions, not to your journey.

Most portfolio presentations walk through projects chronologically, or in order of personal pride. The better move: identify the two or three capabilities the role most needs, and lead with the evidence for each. The hiring manager's job is to answer four questions about you. Make those answers obvious before they have to search for them.

Know your two or three pillars deeply.

Not everything at shallow depth. The most common interview collapse at senior level is the moment when the questioning goes below the surface of a case study and the designer has no depth to offer. If you cannot explain, in two minutes, to someone who does not speak design, why you made a specific decision, what you considered and rejected, and what you would do differently, you are not ready to present that project. On defending your thinking in Round 2, the specific questions that expose hollow portfolios: Why UX Designers Get Ghosted After Round 2 Interviews.

Empower your design manager. The last thing: understand that the hiring manager is not your evaluator only. They are going to be your collaborator, your sponsor, your translator to the business. Going into an interview trying to impress them misses the point. Going in trying to understand them, what they are building, what they need, how you can make their job better, is a different conversation entirely. And it is the conversation that converts.

Ready to Map Your Candidacy From the Hiring Manager's Perspective?

At Xperience Wave, we review portfolios and interview readiness 1:1, not with generic feedback, but with the specific diagnosis of where your candidacy is losing people and what to change. Book a free 45-minute strategy call.

Book your strategy call →

Sources & References

Enhancv / HR Gazette (2025) — Does the ATS Reject Your Resume? 25 structured interviews across industries covering 10 ATS platforms. Finding: 92% of recruiters do not configure content-based auto-rejection.
Harvard Business School / Accenture (2021) — Hidden Workers: Untapped Talent. Global study surveying 8,720 employers. Finding: 88% acknowledge their ATS configuration screens out qualified candidates through human-set filters.
EDLIGO (2025) — Analysis of 1,000 rejected resumes across Workday, Taleo, and Greenhouse. Finding: 43% of rejections were due to formatting, parsing, or arbitrary filter failures, not qualification gaps.
The Interview Guys (2025) — Investigation tracing the '75% auto-rejection' claim to a 2012 sales pitch by Preptel. No methodology was ever published.
UXfolio (2025) — UX Designer Skills: What Hiring Managers Actually Look For. Design leads and recruiters no longer prioritise tool stacks or pixel-perfect UIs.
Indeed Design — UX Interview Advice from Hiring Managers at Indeed, Facebook, and Google.
The Growth UX Studio (2025) — Interview Process for a Senior UX Designer. Key insight: 'Mid-levels seek direction. Seniors create direction.'
hackajob (2025) — UI/UX Designer Interview Preparation Guide. Strategic thinking separates executional from senior/leadership-ready candidates.
Xperience Wave — direct observation. Portfolio review patterns and candidacy failure patterns drawn from reviewing hundreds of designer profiles and mentoring 140+ designers.

Almas Tasneem is Co-founder at Xperience Wave, where she leads sales, strategy, and client success. She has personally reviewed hundreds of designer profiles, salary situations, and interview processes, and has sat on both sides of the hiring conversation across the Bangalore product design ecosystem.