Nye's Digital Lab is a weekly scribble on creativity in an age of rapid change.
This year's distilled advice for the outgoing crop of creative graduates.
Nye's Digital Lab | #82
May 2026
Recruiting, as it exists inside any sufficiently large company, is an outsourcing function.
A hiring manager said I need talent, but I don't have time to find talent, and that need got handed off to a department whose job is to amass and filter candidates at scale.
Note: I believe that good recruiters are valuable. This is not a knock on recruiters.
The ones I've worked with are sharp, networked, and good at their jobs. But their job is not (and structurally cannot be) understanding what makes a great game developer. Or a great technical artist. Or a great anything in a creative-technical field. That understanding takes years of doing the work. Recruiters don't have years of doing the work. They have a req, a timeline, and a stack of resumes that they use AI to process.
So they default to #tags.
Must have Unreal Engine experience.
5+ years shipped AAA. Maya, ZBrush, Substance.
The tags become a proxy for capability, and the proxy becomes the gate.
A developer who has shipped on three other engines but never touched Unreal will get filtered out, while someone who has Unreal on their resume because they took one class will get through. The tag is a terrible signal for the thing it's pretending to measure. Versatility, quick thinking, adaptability. None of it fits in a keyword filter.
This is the recruiting trap today. It might change, but for now, the system is optimized for legibility, not for value.
And if you build your career around being legible to that system, you will spend years being slightly the wrong shape for every door you try to walk through.
What the trap cannot see is the person who goes beyond the brief.
The student who, on a weekend, vibe-codes a tool that cuts a pipeline step from eight hours to twenty minutes. The junior who notices that the rig everyone hates could be rebuilt, rebuilds it, and quietly hands it back to the team. The artist who writes a camera-shake script and open-sources it onto the studio's GitHub because the cameras needed shake and nobody had gotten around to it.
These people are absurdly valuable!
They are also completely invisible to the funnel, because the funnel is asking:
ahem, do you have the tags?
and they are answering a question the funnel never thought to ask:
Can you see the problem and fix it?
That second question is the only one that matters, and it is the question every actual hiring manager is desperate to find an answer to. They just can't get the answer through the system that's supposed to deliver it to them.
So here is the move to avoid the recruiting trap:
Stop applying to jobs.
Start solving problems.
If you find a company whose work you respect, whose aesthetic, mission, or culture pulls you in, don't check their careers page. Check their output. Play the game. Read the postmortem. Watch the GDC talk. Find the seams. Every shipped product has seams. Every pipeline has friction. Every team has something they can't get to because the urgent keeps eating the important.
Then go to them with the seam. Not with a resume. With an observation, a prototype, a pitch, a fix.
I had a student who did exactly this. He went into an interview with a game he'd built, and the technical director on the other side of the table. He started asking him the things they have tried, and the approaches they were working on. That interview wasn't an interview anymore. It was the first day of work. He was already inside the culture of building, and the company recognized it immediately, because the culture of building is what they were starving for.
You will hear that this approach is annoying. That you'll be a pest. That cold-pitching solutions is presumptuous. Some of that is true. If your ideas are bad, you won't get anywhere. And yes, you will annoy some people. I seem to be ok, and I've definitely done that.
You will also, every so often, hit the exact nerve of someone who has been staring at a problem for six months with no bandwidth to solve it, and they will look up and say who are you? I know because sometimes those people just appear in front of me, with exactly the ideas I am looking for.
That single hit is worth a thousand silent applications.
The thing under all of this is systems thinking.
The ability to look at a working operation and see not just what it does, but where it strains. Where the load concentrates. Where one good intervention would unlock ten downstream effects.
Most people operate inside systems.
They take the inputs, do their part, hand off the outputs. Systems thinkers see "the matrix." They see why the inputs are shaped the way they are, why the handoff happens at that particular seam, why the autonomous vehicle takes the left instead of the right. And when something breaks, they don't just patch the symptom. They route through the chain.
This is the skill I'm trying to build in every student who I interact with. Not Unreal proficiency. Not Python. Not any specific tool. Tools change. The job I have is to make you the best creative-technical problem solver I can, because problems are where opportunity lives. When something is working, the people who built it own all the upside. When something breaks, the door opens for whoever can see the fix.
Let's make sure we get this, because I think it's important.
When things work, nobody pays for them.
When things break, money flows toward whoever can make the problem go away.
Be that person. Be relentlessly that person. Make the problems go away.
Here's a thought for you.
Stop polishing the resume for one week.
Pick three companies you actually want to work for. For each one, write down: what is the problem I think they have, and what would I do about it?
You will be wrong about some of them. That's fine, being wrong in specific is more valuable than being right in general, because being wrong in specific is a conversation, and a conversation is a door.
But the work will be there. Yes, even with the F'n robots coming, the work will be there. Because the problems are everywhere, and the people who can see them are rare.
That's the game. Find the problems, solve them, stop labeling the jobs.
Have a great career.
Make it Happen.
Nye Warburton is an artist and educator from Savannah, Georgia.
These essays start as improvisations. Writing is shaped with personalized data sets, Claude agents, and finally edited by hand in Obsidian. Collected essays are available as a printed book at nyewarburton.com/book.
Confronting the Backlash - On dealing with the hatred of AI reaching new levels
The Two Currencies of Creativity - On working as a creative artist and contractor
Education by Mission Command - On managing creative education during rapid acceleration

