Hey everyone, Neil here. You're reading High-Signal Hiring. Hiring systems from 20+ years of global recruitment experience and 500+ technical hires. Zero noise and instantly actionable.
Before this week's issue, a massive thank you to everyone who replied to Thursday's Diagnostic prelaunch email. The response was genuinely humbling and to make 3 sales was way beyond expectations. Thank you again.
I also got some really valuable feedback on the UI / UX, which I’ve taken on board and made some changes over the weekend, which you can check out here (again, feedback very welcome!)
Last issue we covered the Forward Deployed Engineer profile and why most founders write the wrong JD for the role they actually need.
This week I'm not going to give you a play. I'm going to share the hiring debate that's entered the narrative over the past few weeks….
Two AI CEOs have just gone public with the same bet. Hire the 22-year-old with zero experience and no degree, while the rest of the market freezes graduate roles. They're betting the job itself is being rewritten so fast that experience teaches the wrong reflexes.
I'm not sure they're right. I'm not sure they're entirely wrong either. I do know it’s one of the most interesting hiring questions of 2026 and worth a proper look from both sides.
Not a subscriber yet? Sign up here
| The bet two AI CEOs are making
Alon Chen runs Tastewise. $71.6M raised, customers include PepsiCo, Nestlé and Mars. He told Fortune in April that he's actively hiring Gen Z with zero experience. His view is that there are positions where you actively want people who don't have the prejudice or the old way of working.
Ricardo Amper runs Incode, a $1.25B AI identity verification platform. He also told Fortune in February that he hires Gen Z because they're "less biased" and that "too much knowledge is actually bad in tech." He's optimising for character and grit over credentials.
Both are betting against the consensus. 40% of bosses said in early 2026 they'd hire fewer grads this year because AI does the work cheaper. Chen and Amper are running int the opposite direction.
The argument behind it is seemingly solid. 92% of US devs now use AI coding tools. 60% of new code in 2026 is AI-generated. A senior trained on Stack Overflow has a different mental model from a 22-year-old who never wrote a function without an AI pair. That gap matters more in some roles than others.
Here's the honest case from both sides of the fence.
| The case for hiring the 22-year-old
1️⃣ The job itself is being rewritten. A senior with 10 years of reflexes built on a pre-AI workflow can be slower to ship than a junior who started in 2024 and has never known a different way of working. Reflexes that took a decade to build can be a tax in an AI-native shop, not an asset.
2️⃣ The economics are different. Three 22-year-olds at $90K each costs less than one senior at $250-300K, with more shots on goal and less single-point-of-failure risk.
3️⃣ Less ego, more clay. A first-job hire has no 10-year identity invested in "the right way." Easier to adopt new tools, drop old ones, fail in front of you without it being a status hit.
4️⃣ Tenure maths. A 22-year-old in their first real role tends to stay 18-24 months before they look around. A senior at a hot AI startup is poachable inside 14 months on a competing offer. The cheap hire is also stickier than most people would think.
| The case against
1️⃣ No battle scars. When production breaks at 2am, a senior knows it's a DNS issue from five previous outages. The 22-year-old asks Claude and hopes. Failure-mode reasoning lives in the consequences someone has already absorbed, not in a manual AI can read.
2️⃣ No taste yet. Architecture choices, scope debates, when to push back on a founder who's about to make a bad call. All of it needs years of seeing what happens when you get it wrong. Infinite AI leverage on a junior with no judgment ships the wrong thing fast.
3️⃣ The founder absorbs the cost. Juniors need calibration, feedback, context. The founder running five things doesn't have ten hours a week to give. The hire is cheap on paper and expensive in founder bandwidth, especially in the first 90 days.
4️⃣ Two CEOs is not a strategy. Chen and Amper are making the bet publicly. Neither has shown the data yet. Two interesting founders running a contrarian play doesn't make it a pattern. It might look obvious in 2028. It might look like a fad we all remember.
Only time will tell.
| Where I land (tentatively)
I keep coming back to the same split.
For work that's mostly directing AI agents, the 22-year-old hire is more interesting than the market thinks. RAG pipeline tuning, marketing automation, customer-shaped delivery work. The leverage ratio is high. The downside is bounded. The upside is real because the work genuinely is new.
For work that needs distributed-systems judgment or owning a production stack, I still think it's the wrong call. The battle scars argument wins. You don't get to skip those years.
The honest founder question is which of those two categories your next hire falls into. Most founders confuse the two. They want the senior because seniors feel safer, but the work they actually need done is in the first category. Or they want the cheap hire because it's cheap, but the work is in the second category and they're about to find out the hard way.
Issue #14 covered taste and judgment as the engineer skills AI can't fake. Same lens applies here. If the role needs taste, the 22-year-old isn't ready yet. If the role needs leverage, they might be the best hire you make this year.
| What I’d love to hear
This is a debate I'd rather have with you than at you. Hit reply and tell me one of three things.
You've made this hire. How did it go?
You're thinking about it. What's stopping you?
You think the whole framing is wrong. Tell me why.
Can’t wait to here from you all!
Cheers
Neil
