Originally published on Product Tribe

The market did not shrink - it changed what it needs. AI did not take your job; it changed the definition of the job, and exposed how many designers were executing inside frames they didn’t build.

You have a theory about why you’re not getting hired.

You’ve been applying for six months, maybe eight, maybe longer. Your portfolio is solid - you know it is, because people tell you so, and because you can see it yourself when you look at it honestly. You’ve worked at real companies. You’ve shipped real products. You understand the process. And yet the market is treating you like you don’t exist.

So you developed a theory. AI happened, companies panicked, headcount froze, and now there simply aren’t enough jobs for the number of designers who need them. Structural problem. Happening to everyone. Not about you.

A wrong diagnosis leads to wrong treatment. And if you’ve been treating the wrong problem for six months, that’s six months you can’t get back.

Theory one: AI is eating the market

Start with the most common version. AI arrived, companies realized they could automate design work, hiring collapsed. Supply stayed the same, demand fell. You’re collateral damage in a structural shift nobody could have anticipated or avoided.

It’s a reasonable theory. It fits the experience of sending fifty applications and hearing back from three.

Jared Spool wrote at the start of 2025: more UX professionals are employed globally than ever before, more than 2 million people. More open UX positions than at any point in history. The field is growing at its fastest rate ever. And at the same time - more unemployed UX designers than ever. Spool has been watching this industry’s hiring patterns longer than most of us have been in it. He’s not given to panic.

Both things are simultaneously true. Which is exactly why AI-kills-the-market fails as a model. If it were right, both numbers would be going down. Only one is.

Figma surveyed 906 designers and hiring managers in February 2026. 82% of organizations say their need for designers has increased or held steady. More than a quarter say it increased by 25% or more. Designer Fund - a VC firm focused on design-led companies - estimates job postings across their portfolio were up roughly 60% in 2025 compared to 2024. Not numbers from an industry in collapse.

The peak was 2022 - an unsustainable bubble inflated by cheap capital and pandemic-era digitization. UX research job openings grew 466% relative to 2018. Not 46%. 466. Then the bubble burst and the market corrected toward something closer to baseline. But it corrected into a market that was structurally different from the one in 2018. The jobs came back. Different jobs.

Theory one is wrong. The market did not shrink. It changed what it needs.

Theory two: the market shrank and I’m caught in the squeeze

This one is more sophisticated. You’re saying the market got smaller. Not that AI ate it - that there’s simply less work than there used to be. Fewer products being built. Tighter headcount. Design cut first because it can’t show direct ROI fast enough.

There’s something true in here. The 2022–2024 correction was real and painful. About a third of organizations reported cutting UX staff in 2024, according to the UXPA salary survey - the highest rate since they began tracking it. UX researcher roles were hit disproportionately harder than other design functions. If you were caught in one of those cuts, the experience was not abstract.

Those two things look identical from the outside. They’re not. And the treatment is completely different.

LinkedIn measured in 2025 that 69% of recruiters see a mismatch between available talent and what companies need. Not “not enough designers.” Mismatch - skills available pointing in one direction, skills required pointing in another. The same recruiters note that nearly 40% of job seekers are applying to more roles than ever but hearing back less. More applications, fewer responses. That is not what a contracting market looks like. It’s what oversupply in one category looks like while there’s undersupply in another.

Two independent academic studies - Harvard analyzing 62 million profiles and job postings, Stanford using ADP payroll data covering millions of workers - reached the same conclusion in 2025. Companies adopting generative AI reduced junior employment by 7.7% while senior employment kept rising. Among workers aged 22–25 in the most AI-exposed roles, employment dropped 13% from late 2022. Figma translated the consequence into numbers: 56% of hiring managers report growing demand for senior hires. Only 25% are hiring junior.

The market bifurcated. Two categories with completely different trajectories - both involve making design decisions, both use Figma, both produce screens. On one side: execution capacity, now cheaper per unit and competed for by a much larger pool. On the other: strategic judgment, scarce, hard to hire for, actively sought and rarely found.

Theory two is closer than theory one. The market did squeeze certain categories hard. But the squeeze was selective, not uniform - and understanding which category you’re in matters more than understanding that the squeeze happened.

Theory three: my portfolio needs work and then I’ll be competitive

This one feels productive. Which is part of why it’s dangerous.

You look at your portfolio. You see things that could be better - the case study structure, the visual presentation, the way you’ve articulated your process. You start working on it. Two weeks tightening the copy, redesigning the layout, adding a metrics section to each project. It feels like progress. It is not progress.

The portfolio is not the problem. Or rather: if the portfolio is the problem, fixing its presentation will not fix it.

Tom Scott, who writes about design hiring with unusual precision, described in February 2026 what he keeps seeing: the designers struggling to get interviews have a gap between what they say and what they can demonstrate. Portfolios built for polished presentations. Process theater. The double diamond, the full case study deck. And something that hit harder than anything else he wrote - designers whose strategic thinking, when you actually probe it in an interview, turns out to have been done largely by a product manager. They were shielded for years without realizing it.

Shielded. In a well-run team, a senior PM and a senior designer work on strategy together, and that’s normal and good. The problem surfaces when the designer leaves after four years and discovers they never actually practiced strategic thinking on their own. The PM framed the problem. The PM defined the constraints. The designer executed brilliantly inside a frame they didn’t build. The portfolio shows the execution. The interview asks about the frame.

No amount of case study polishing fixes that gap. Because the gap is not in the portfolio. It’s in what the portfolio is documenting.

The apprenticeship layer is dissolving. AI does not remove roles wholesale - it removes the glue work, the repetitive tasks through which juniors used to learn by doing. Harvard and Stanford both documented this, independently, in 2025. Someone once had to make fifty button variants. In making them, they learned what the system was, where its edges were, how it broke under pressure. Now AI makes those variants in under a minute. The junior either skips them or touches them briefly. The way you used to get good at this was by doing it badly, many times, until you weren’t. That path is disappearing.

The pipeline that used to produce senior judgment through accumulated junior experience is thinning. And the designers who went through it are discovering that the experience they accumulated may have been narrower than they realized.

(One more data point that makes this concrete: 60% of files created in Figma Make last year - Figma’s AI prototyping tool - were made by non-designers. Prototyping stopped being a design function and became part of everyday collaboration. When a tool becomes universal, fluency in it stops signaling anything about you specifically.)

Theory three - fix the portfolio - mistakes the symptom for the cause. If what you’ve been practicing is execution inside frames other people built, the portfolio accurately reflects that. Making it shinier does not change what it reflects.

I ran hiring processes recently. Multiple candidates, multiple portfolios. Several of them had the same problem I’ve been describing - but the way it showed up was not what I expected.

The portfolios were trying hard at first scroll - custom cursor effects, hijacked scrolling, animated transitions between sections. All of it breaking basic usability conventions, all of it signaling that someone had spent serious time on the wrong problem. A lot of effort had gone into the container. Then I started reading the actual case studies, and something was missing - the same thing, across almost all of them. Why the project existed: not there. What problem it solved: not there. What was considered and rejected, and why: not there. Whether the design moved any metric after shipping, or what was learned when it didn’t: not there either. The work went to production and stopped. Fire and forget. Nobody went back. Nobody checked. And apparently nobody thought that was strange.

What I was looking at was documentation of execution. Proof that someone had made screens, made them look polished, and shipped them. What was absent was any evidence that the designer understood the problem well enough to have made a different decision, or that they cared what happened after the handoff.

These designers did not fail because their portfolios were ugly. They failed because their portfolios were honest. They showed exactly what had been practiced: making things look good and shipping them. The cursor effects were almost a tell - a lot of energy on the container, very little on what the container was supposed to communicate.

Most of them did not get to the next stage.

What I can tell you from watching designers navigate this: none of the ones who successfully repositioned did it by updating their portfolio. They changed what they do in rooms.

(I’m aware this sounds like advice that’s easy to give and hard to act on. It is. I’m also aware it’s useless if your current environment doesn’t give you room to ask different questions - which is why the environment question matters as much as the posture question.)

In projects - even bad ones, even ones they hated - they started asking different questions. Not “what should this look like” but what is this actually for, and is this even the right solution to the underlying problem. A flow that wasn’t working stopped being a smoothness problem and became a question of why users were dropping off there at all - and what would need to change earlier in the process. A gap in the design system became a proposal with a rationale, not a workaround. (None of this is dramatic. It doesn’t feel like a transformation when you’re doing it. It feels like slowing down slightly in a meeting.) Small shifts in posture, consistently applied, that compound over time into work that looks different because it was produced differently.

The catch is that this requires working somewhere that gives you room to ask those questions. Many people are stuck in execution roles where nobody wants strategic questions - just deliver the screens. If that’s your situation, the repositioning question is inseparable from the environment question - and that’s a harder conversation than this letter can hold.

For now, one question worth sitting with. Not about your portfolio - about your actual recent work. What percentage of your decisions in the last year were judgment calls, where you weighed competing considerations and made a choice, versus execution calls, where you knew what good looked like and produced it? If the ratio is heavily skewed toward execution - and be honest, because this is the one question you’re allowed to answer badly - that tells you something about your current environment, your habits, and what an interviewer will find when they probe.

AI did not take your job. It changed the definition of the job - and exposed how many designers were executing inside frames they didn’t build, asking questions they weren’t asked to ask, making decisions that were never fully theirs.

The problem is inside the work itself, not in the market or the correction or the presentation. That requires honesty about what you’ve actually been practicing, versus what you believed you were doing.

The market is not punishing you for being a good designer. It’s rewarding a specific kind of thinking that didn’t used to carry a premium because execution was expensive enough to obscure it. Now execution is cheap. The thinking is what’s left.

Whether you changed with the definition of the job is a question worth answering for yourself, before the market answers it for you.