When everyone's portfolio is correct

I had fifty tabs open last week. A studio I know got hit, a project got folded, and the portfolios started arriving in a stack. That’s what a layoff looks like from the reviewing side: a hundred strong designers job-hunting in the same two weeks, and me giving each link maybe ninety seconds before I decide whether it earns a real fifteen.

Here’s the part that unsettled me. The good ones all looked the same.

The advice worked, and that’s the problem

Everyone read the same guides. Everyone leads with one deep piece, shows the blockout before the art, names a constraint, captions the images, walks me from greybox to final. I’ve written that advice myself, so I can’t pretend it’s wrong. It’s right. It’s also the floor now. When a format is universal, executing it cleanly stops telling me anything, because the person in the next tab executed it just as cleanly. Twenty case studies with the same section headers blur into one case study I’ve read twenty times.

So I’m not here to hand you a better template. A better template gets copied by next month and we’re back where we started. I don’t have the trick. What I have is the question I keep asking as the tabs close: why would I remember this one?

What I actually remember

The pieces that survive a stack aren’t the most polished. They’re the ones with a fingerprint. A designer who spent a paragraph on a decision she got wrong, and defended the wrong version for two weeks before she saw it. A greybox built around one idea about verticality that I disagreed with and still think about. Those weren’t cleaner than the rest. They belonged to a specific person who wanted a specific thing.

The uniform portfolio has the opposite quality. It’s competent and it’s nobody’s. You could swap the name at the top and nothing would break. That’s the thing to be afraid of, more than a rough edge or a missing playtest diagram.

One thing you can actually do

Invent a constraint and hold yourself to it. A real level is built under limits someone else set; a portfolio piece has none, which is the problem. So make one up and commit. No key can be backtracked for. Every fight readable from one screen away. The player is never told where to go. A self-imposed rule turns a pretty space into an argument, and it forces your taste to show even to you.

Questions I’d sit with

I can’t tell you what your fingerprint is. But if I were updating my own portfolio into this pool, these are the questions I’d make myself answer honestly.

What do I believe about level design that most portfolios never say out loud? A real position I’d defend in a review, knowing some studios will disagree and screen me out for it. A portfolio safe to show everyone tends to land with no one.

What did I build because I wanted to, before any template told me how to present it? The weird small level, the mod nobody asked for. That work usually carries more of me than an assignment reverse-engineered into a case study.

If someone stripped my name off the pages, would they still sound like me? Read your own captions aloud. If they read like every other portfolio, the process was right and the voice went missing in the polish.

None of this is a guarantee. Standing out is genuinely harder when the whole field got better at once, and I won’t pretend there’s a move that fixes it. Correct is table stakes now. The rest is whether there’s a person visible under the competence, and I’m still working out how I’d prove that about mine.