I have hired designers for fifteen years. I have screened thousands of portfolios, run hundreds of interviews, and built teams across a multi-billion-dollar eCommerce org and a string of smaller shops. For most of that time, my screen was stable. I knew what good looked like in five seconds. Then the last two years changed what I look for more than the prior twelve combined.
The short version is this. I am not hiring hands anymore. I am hiring judgment.
The cleanest portfolio used to be the answer
There was a time when a clean portfolio told me almost everything I needed to know. Tight grids. Confident type. A case study that walked me through a problem and landed on a polished screen. If the craft was there, I could trust that the person could execute. Craft was scarce, so craft was the signal.
That world is gone. A competent first pass is now cheap. The tools produce clean layouts, sensible spacing, and reasonable type on demand. A junior with good taste and a good prompt can hand me something that looks like the work of a mid-level designer from a few years ago. The floor came up fast, and it came up for everyone at once.
So when a portfolio is clean, I no longer feel the relief I used to feel. Clean is the baseline. It tells me the person can meet the new floor. It does not tell me whether they can do the part that still matters.
Skill is the floor, not the ceiling
I want to be careful here, because this gets misread. I am not saying craft is dead. I am saying craft stopped being the thing that separates people. When everyone can produce a competent result, competence stops differentiating. It becomes the price of entry, not the reason to hire.
Think about what that does to a screen built around polish. If two candidates both hand me clean work, and the clean work is partly the tool talking, then the polish tells me very little about which one I want on my team. I have to look past the surface to find the difference. The surface is where I used to stop looking. Now it is where I start.
I wrote a whole piece on this shift because it deserves more than a paragraph. The gist is that craft alone no longer tells you who is good, and that has consequences for how you evaluate people. If you want the longer argument, I made the case that the gap is not skill anymore, and that the real separation happens somewhere else entirely.
Here is where it happens. When the first pass is free, the value moves to everything around the first pass. What problem are we actually solving. Which of the hundred reasonable options is the right one. What did we choose not to do, and why. Those questions were always part of design. They were just buried under the labor of making things. Now the labor is gone and the questions are standing in the open.
Judgment under abundance
Here is the situation a designer faces now. You ask the tool for options, and it gives you a hundred. They are all plausible. Most of them are fine. A few are good. One or two are right for this specific user, this specific moment, this specific business. The work is no longer making the options. The work is choosing among them and being able to say why.
That is judgment, and judgment under abundance is harder than it sounds. When you had to make every option by hand, scarcity did some of the deciding for you. You only had time to try three things, so you picked the best of three. Now you can see a hundred things in a minute, and the temptation is to pick the one that looks the prettiest in isolation. The prettiest one is often wrong. The right one usually requires a reason that lives outside the screen.
So in interviews, I push on the reason. I will put options in front of a candidate and ask them to choose. I do not care much about the choice. I care about the explanation. Can they connect the pick to a user need, a business constraint, a tradeoff they are making on purpose. The designer who picks the right one and explains why is doing the part that did not get automated. That is the part I am paying for.
The ones who struggle here tend to struggle in a specific way. They can tell me what looks good. They cannot tell me what is good for the situation. They treat the hundred options as a buffet of taste instead of a field of decisions. Taste matters, but taste without judgment just picks the prettiest wrong answer faster than before.
My favorite question now
My favorite interview question these days is simple. What did you make that nobody asked you for.
I love it because it cannot be faked with a tool. Anyone can generate a polished screen. Not everyone has the itch to build something because they noticed a problem and could not leave it alone. That itch is the thing I cannot teach and cannot prompt. It is curiosity with follow-through, and it is the closest signal I have found to predicting who will be valuable when the easy work is automated away.
The answers tell me so much. Some people freeze, because the answer is nothing. They do excellent work when assigned, and that is real, but they wait to be pointed at a problem. Other people light up. They built a little tool to fix a workflow that annoyed them. They redesigned a thing nobody complained about because they saw it could be better. They shipped a side project that taught them something. Those people do not need a brief to start moving. In a world where the assigned work gets cheaper every month, the people who start moving on their own are the ones who compound.
There is a close cousin to this that I weight heavily now, which is whether a designer can actually build. The line between design and engineering keeps thinning, and the people who can carry an idea from sketch to working thing have an edge that grows every quarter. I have written about why I bet on the designers who build, and the short version is that making the thing real is no longer a separate job you hand off.
What this looks like in practice
Let me make this concrete with where I have seen it pay off. In the multi-billion-dollar org, we built an agent that took a workflow from around three hundred and twenty hours down to about one. The interesting part was not the time saved, although that number gets attention. The interesting part was who drove it. It was not the person with the cleanest mockups. It was the person who looked at a painful, repetitive process and asked whether it needed to exist in that form at all. That is judgment. That is nerve. The craft was table stakes.
I see the same thing at Story Genie, the company I am building now. Agents write and illustrate personalized hardcover children’s books, and humans supervise the output. A customer sees a full book and a preview in about sixty seconds before they pay a cent. None of that works if the team treats the AI as a magic box that spits out finished work. It works because people exercise judgment at every step. Which output is good enough to show a parent. Where the model gets the child’s likeness wrong. When a charming mistake is actually a defect. The machine produces. The people decide. That division of labor is the whole game now.
Across Kinjo, Supply Drop, The Mysterious Package Company, Surf Studios, and Enverus, the pattern held even before the tools got this good. The designers who mattered most were rarely the ones with the most beautiful files. They were the ones who saw the real problem, picked the right path through it, and had the nerve to build something nobody had asked for yet. The tools just made that pattern impossible to ignore.
Why curiosity and nerve beat polish
Curiosity is what makes someone notice the problem in the first place. Nerve is what makes them act on it without permission. Polish is what happens after both of those, and polish is now the cheapest part of the sequence. If I optimize my hiring for polish, I am optimizing for the part a tool can do. If I optimize for curiosity and nerve, I am optimizing for the part it cannot.
This also changes how I read a resume. A spotless career of well-executed assigned work used to read as low risk. Now it reads as a question mark. Did this person ever push on something that was not handed to them. A messier path with a few self-started swings in it tells me more than a clean one full of tickets closed. I would rather hire someone who tried three weird things and shipped one than someone who executed forty briefs flawlessly and never asked why.
I am not lowering the craft bar to make room for this. Craft still has to be there. The point is that craft alone is no longer enough to clear the bar, because the bar moved. Curiosity and nerve are what sit on top of craft and turn a competent designer into a valuable one.
The old green flags that now just get you to the starting line
For most of my fifteen years hiring designers, a clean portfolio was a strong yes. If someone showed up with crisp case studies, tidy typography, and screens that looked agency-polished, I leaned in. That work signaled care. It signaled that the person could finish things and make them look right. I trusted it because it was hard to fake and harder to produce at volume.
That signal has not become worthless. It has just become baseline. The tools got good. A motivated designer can now produce a portfolio that looks expensive in a fraction of the time it used to take. Polish is more available than it has ever been, so it tells me less about the person behind it. When everyone can clear the old bar, the old bar stops sorting people. It just confirms they showed up.
Pixel-perfect execution is the clearest example. I used to weight it heavily because precision was a proxy for discipline. Now I care far more about how someone moves when the brief is vague and the right answer is not obvious. Show me a project where the requirements changed twice and you still landed somewhere good. That tells me more than a flawless mockup of a problem that was handed to you fully formed.
Another one I have downgraded is the phrase I follow the process. It used to sound like maturity. A designer who respected research, defined the problem, and ran the steps in order felt safe to hire. But a process is only as good as the thinking that questions it. The stronger answer now is I changed the process. Tell me where the standard playbook was wrong for the situation and what you did instead. That is judgment, not compliance.
I am not being cynical about any of this, and I want to be fair to the people who built those skills. The craft still matters. At Story Genie our agents draft and illustrate whole books, and humans supervise every one before a customer pays. None of that supervision works if the person doing it cannot tell good from almost-good. Taste and precision are real, and I still hire for them. They have just moved from the thing that wins the job to the thing that lets you keep it.
So here are the new green flags I actually chase. A portfolio that shows its own dead ends, not just the clean final. Someone who used the new tools to go further instead of just faster. A story about a constraint they pushed back on and were right to. Evidence that they shipped, watched what happened, and changed their mind in public. Those signals are harder to manufacture because they come from how a person thinks, not from what a piece of software can polish. That is the part I am hiring now.
I am not hiring hands anymore. I am hiring judgment, and judgment shows up as curiosity and nerve long before it shows up as polish.
What this means if you are building a team
If you lead design, your hiring screen is probably still tuned to the old world. Mine was, and I had to retune it on purpose. Stop using the cleanest portfolio as your filter. Start asking what people made on their own, how they choose among options, and whether they can explain a decision in terms of the user and the business instead of the screen. The tools raised the floor. Your job is to find the people who operate above it.
This is one of the harder parts of leading design right now, and it is a big reason I spend time helping teams think through how to hire and structure design leadership for this new reality. The org chart and the rubric both need to change, not just the headcount.
Some teams are not ready to make a full-time leadership hire while they figure this out, and that is fair. It is part of why I work with a few companies as a fractional design leader, helping them rebuild the screen and the team around judgment before they commit to a permanent structure. The mistakes are cheaper to fix early.
Here is what I keep coming back to. The competent first pass got commoditized, and that is a good thing, because it freed up the part of design that was always the point. The deciding. The noticing. The nerve to build the thing nobody asked for. I spent twelve years getting good at reading craft in five seconds. I spent the last two learning to read for something harder to see and far more valuable. I am not hiring hands anymore. I am hiring judgment, and I am better at my job for the change.