You spent three weeks rewriting your case studies. You cleaned up the typography, swapped in sharper mockups, cut the fluffy paragraphs, and sent the revised link to a dozen open roles. Two weeks later, the automated rejections started landing again. The notes are polite, uniform, and completely unhelpful.
Nobody tells you what fell short. The recruiter won't jump on a call to explain which screen lost them, and the hiring manager has already moved on to the next batch of thirty candidates. You're about to open your site builder and start tweaking layouts again, but guessing feels like the only option left.
You will rarely be told, so work it out yourself. First set aside only the rejections you know had nothing to do with the portfolio. Then test your case studies for three gaps that look the same from the outside, each with its own test: the role (does the work show the type of skill, the level, and the complexity the posting asks for), the evidence (can a reviewer see what changed because of your work in a first look), and the reasoning (can someone who has never seen the project rebuild your decisions from the page). Fix the gap that fails, change one thing at a time, and get one specific read from someone who reviews portfolios at the level you're applying for.
Why nobody tells you, and what the silence is worth
In a 2022 report on Talent Board research, 57% of North American candidates received no feedback after being rejected during the screening and interviewing stage. Among the rejected candidates who did receive feedback, only 37% said it was useful. That research covers applicants across every kind of job, not design alone.
A platform survey points the same way. In a 2022 preprint surveying recent job applicants on the Australian platform FlexCareers, 29% of the 141 survey respondents said an employer explained why their application was unsuccessful.
The authors of that study offered their own explanation for why companies default to form rejections:
"Perhaps, a more plausible reason is that it is easier for the employer to send out generic information that does not reveal the true reason for the rejection. The true reason may be unique to each applicant or the employer may prefer to keep the true reason secret, such as the position was withdrawn or was earmarked for an internal candidate."
That's the researchers' guess from one Australian survey, not something they measured directly. Still, it's a good reason not to read a form letter as a verdict on your craft. A generic rejection note can stand in for decisions that have nothing to do with your case studies.
Even when interviewers attempt to give feedback, their stated rationale might not reflect what drove their decision. In an experimental study of 29 corporate interviewers evaluating 64 hypothetical candidates for a position in a financial services organization, researchers found that interviewers weighed the same criteria differently, and some described their own decision process poorly. That's one 1992 study of corporate interviewers, not of designers, so it's no reason to dismiss specific, craft-based feedback. But a vague note like "we went with someone whose experience was a tighter fit" may not name what actually drove the decision. In an excerpt from his book on design hiring, Dan Shilov advises reading vague rejection notes between the lines and checking them with an experienced colleague rather than taking them literally.
Stop waiting for a company to diagnose your portfolio. You have to run that diagnosis yourself.
Set aside the rejections that say little about the portfolio
Before you start rewriting case studies, sort what you've got. In an essay for Adobe Design, Eric Snowden puts it plainly: "Silence, or even a no, may not be about you, sometimes it’s about them." Mark each recent rejection in one of three groups:
- Confirmed. You know the cause: a recruiter wrote back to say the opening was canceled, headcount was frozen, the role was filled by an internal transfer, or the team decided to hire for a different discipline. When that happens, the outcome says little about your portfolio, even if someone looked at it first.
- Possible. A cold application up against referred ones, or a market that was shrinking, might explain the outcome, but a portfolio gap could sit alongside it.
- Unknown. A standard automated rejection arrived with no context.
How you applied can tilt the odds too. In a study of nine large firms across call centers, trucking, and tech, researchers found that referred applicants were more likely to be hired than nonreferred ones. That research isn't about design hiring. If you submitted a cold application through a public board while ten internal referrals landed in the hiring manager's inbox, your case studies might have been passed over without a thorough review.
Market contractions also reduce the number of open seats. In February 2025, US tech job postings on Indeed for senior and higher-level roles were down 19% from February 2020, and postings for standard or junior roles were down 34%. Closer to design, 35% of the 408 respondents to the 2024 UXPA salary survey said their organization's UX group lost staff in the past 12 months, even while 70% of the 99 respondents with hiring authority planned to hire at least one person for 2025. Both are snapshots from 2024 and early 2025, not today's market.
The rule for sorting is straightforward: only set aside the Confirmed group. The Possible and Unknown rejections stay in your review pool. They are the applications you will test across the three gaps.
The three gaps side by side
The silence looks identical whether the problem is what you do, how you prove it, or how you explain your thinking. I sort portfolio rejections into three categories: role mismatch, evidence gap, and reasoning gap. Each needs a different test and a different evaluator.
| Gap | What it looks like from outside | The test | Who can judge it |
|---|---|---|---|
| Role mismatch | A form rejection or silence | Line-by-line comparison of your case studies against the posting's craft, scope, and problem complexity | You or a peer familiar with the team's product area |
| Evidence gap | A form rejection or silence | A three-minute look: can a reviewer find your measurable results and the product change your work made without reading the whole case study? | Any designer or recruiter, for whether the result is findable. A designer at your target level, for whether the work holds up |
| Reasoning gap | A form rejection or silence | A cold read: can a stranger write back what you did, why, under what constraints, and how the solution evolved? | Anyone who has never seen the project, for clarity. A designer at your target level, for the thinking |
Test 1, the role
I start with the role, especially when the rejections cluster around one kind of posting, because a strong senior portfolio can still be the wrong type of portfolio for a team.
Take your stack of rejected applications and lay each job posting beside the case studies you submitted. Check three specific factors:
- Craft focus. Does the posting ask for design systems architecture, complex user research, or high-fidelity interaction and visual craft?
- Operational scope. Is the team looking for individual contributor execution, or cross-functional team leadership and mentoring?
- Problem complexity. Does your portfolio show problems of comparable scale?
In an Adobe Design feature on standing out in hiring rounds, Shannon McCready pointed to complexity as a primary screen: "Is the experience of similar complexity to the work this team does?" If a team builds enterprise developer tools with complex permissioning models and your portfolio only shows consumer onboarding flows, a reviewer asking that question may well pass.
A craft mismatch can sink a portfolio without anyone saying so. Atlassian's design interview guide asks candidates to "show us examples that demonstrate your skills in the specific craft you are interviewing for". Snowden puts the hiring manager's side of it:
"You can be the best visual designer, but if I’m looking for a motion graphics designer, you’re not getting the job. This isn’t a reflection on the quality of skill, but the type of skill. For one job you could be the perfect candidate, but for another I’m looking for a different tool set."
Read your rejections with that split in mind. If the postings that turned you down wanted research-heavy or systems work and your case studies are mostly interface polish, a stronger version of the same projects won't change the answer.
A cluster of rejections on one kind of posting doesn't rule out weak evidence or poor reasoning, but if your work does match the posting line by line, you can move on to Tests 2 and 3.
Test 2, the evidence
Next I look at how the case study carries its proof. In a 2021 article on outcome-driven portfolios, Gabi Moore wrote that one of the most common patterns she found reviewing portfolios as a design manager was "very long case studies primarily focused on describing a process".
In its 2019 guidance on UX design portfolios, Nielsen Norman Group noted that hiring managers often have little time for each candidate's portfolio. In an essay analyzing senior product design hiring, Micka Touillaud detailed his screening process, separating a 30-second check from a three-minute look. In that initial glance, his primary question was: "Is there a visual match?"
Other reviewers say they look for the outcome. In their public overview of hiring designers, Intercom's design team asked: "What changed because of your work?" Moore's own first move was to scroll to the end: "Invariably, the first thing I would do was to scroll all the way to end to see what the actual result was."
When running this test, you have to separate two different failure modes:
- A presentation gap. The project achieved clear results, but you buried them at the bottom of a four-thousand-word case study under twelve wireframes and three journey maps.
- A quality gap. The result is easy to find, but the work itself falls short of the target level.
In an essay on portfolio mistakes for Atlassian's design publication, Mark Parnell warned that following a process is no guarantee of good design, noting that you can "still deliver subpar crap if your design decisions are poor". Nielsen Norman Group's guidance adds that hiring managers rarely read a portfolio word for word, which is one reason to keep it scannable.
If your outcome is buried, that's a presentation gap, and it's the one to fix first. If your outcome is visible but your design decisions were questionable, restructuring the page won't solve the problem. That requires an evaluation from an experienced designer who reviews work at your target level.
Test 3, the reasoning, and what "needs more process" may mean
Before you add more steps, wireframes, or workshop snapshots to your case studies, test whether your decisions are visible on the page. My first hypothesis when a designer tells me they received feedback requesting "more process" is that reviewers could see the final interface but not the decisions behind it.
Some reviewers genuinely do want more process documentation. In the Adobe Design discussion on how applicants can stand out, Matthew Carlson favored depth over breadth: "Fewer case studies with deeper process examples are better than a broad, shallow portfolio." If your decisions are already stated plainly and reviewers continue asking for more process, Carlson's perspective might be what they expect.
Parnell is specific about what he learns from in a portfolio:
"I learn much more about how well you can design by seeing how well you can articulate and reflect on design decisions. I learn rather less from hoary old cliches about the design process that an interviewee thinks I want to hear."
I'd read "needs more process" with that in mind first. Before you add a research slide, check whether a stranger can find the choice you made, the option you dropped, and the cost you accepted.
To test whether your reasoning carries across to a reader, run a cold read. In an article on what they look for in design applicants, the team at UX studio described how they read a submission:
"As we read, we are trying to reconstruct your decision-making process. We want to understand what you did, why you did it, what constraints existed, and how the solution evolved over time."
That's a test you can run without them. Hand someone who has never seen the project one case study and the posting it went to. Ask them to write those four things back to you. Where they can't write one of those four back, the page isn't carrying the decision, however many process slides it has. And where what they wrote back doesn't match what the posting asks for, you're back at Test 1.
Who evaluates the cold read matters. I recommend a practical split: use a reader unfamiliar with the project to test whether the narrative is clear on its own, and use an experienced designer at your target level to evaluate the quality of your design thinking.
Research on judging creative work points the same way, with limits. In an experimental study examining how people evaluate creative writing and engineering designs, researchers concluded that "Some domains may require more expertise than others to properly evaluate creative work." That study evaluated short stories and mousetrap designs using student and expert raters rather than product design hiring loops, so take it as a reason for the split, not proof of it. A study of creativity ratings of student graphic design work found that judges' preferences for technical execution differed, so one reader's view of your polish is one view. And as Carlson and Parnell show, reviewers differ on how much process they want to see.
If your cold read reveals that your decisions are missing or unclear, our guide on how to write a UX case study that passes the hiring manager's cold read is the place to start.
Change one thing, then get one specific read
Once you've run the three tests, pick the single gap that failed. Do not redesign your entire portfolio from scratch.
If you change your layout, rewrite every project, swap out your hero images, and adjust your case study text simultaneously, you'll have no idea what caused the next rejection or interview invite. If the gap that failed needs a rebuild, use our guides on how to build a product design portfolio that shows business impact or how to build a UX portfolio that actually gets interviews. For one case study, use how to write a UX case study that passes the hiring manager's cold read.
What if your portfolio passes all three tests and the rejections continue? Passing these tests doesn't tell you what the employer weighed internally, and it doesn't mean your portfolio needs another rewrite. A shrinking market or a referred candidate could be doing the work.
Either way, another round of guessing on your own won't help. You need one specific read from someone who reviews portfolios at your target level. When you ask for feedback, don't ask a generic question like "what do you think of my portfolio?" Ask one narrow question tied directly to the gap you tested: "Can you tell within three minutes what changed because of my design in project two?" or "Does the complexity in this enterprise case study match what you look for in senior roles?"
On MentorCruise, you can browse product design mentors and pick someone whose background shows they have interviewed designers at your target level. Someone who's conducted design interviews can give you feedback from the evaluator's perspective, not just the candidate's. In a session you might review a portfolio piece or case study together. Between meetings, async portfolio reviews and document feedback carry the guidance. Every mentorship includes async messaging. Mentors can't tell you an employer's private criteria or promise you an interview, but they can tell you whether your work reads the way you think it reads.
FAQs
Should I ask the company why I was rejected?
Yes, once, if you reached an interview stage, and keep your request focused on a specific part of your work. In Atlassian's design interview guide, the company states a goal of providing feedback to candidates who interview with their team regardless of the outcome. Don't chase recruiters after an automated screening rejection.
Should I stop applying while I fix my portfolio?
No. Keep applying to roles where your experience matches the job requirements, but change one thing at a time and track which version went to which company. Tracking versions won't tell you why any one rejection came, so the specific read in the previous section is the clearer signal. Continuing to apply keeps your search moving while you run the three tests, instead of halting it for weeks to build another portfolio nobody has tested.
