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.
Last issue, we covered the four readiness tests that separate real hiring needs from wishful thinking. If you passed those tests, you're ready to hire.
This week, we're moving forward.
You've decided you need an engineer. Now the question is: what kind of engineer? This is where most founders completely screw it up.
You'll learn why the profile you're searching for is probably wrong, what "startup-ready" actually means in practical terms, and how fixing this one thing can cut months off your hiring timeline.
Not a subscriber yet? Sign up here
| The reason your hire is taking months
It's not the market. It's not your comp. It's not your employer brand.
It's the profile you're searching for.
Most founders write a job spec for an engineer who doesn't exist, doesn't want to work at early stage, or would be a bad fit even if they joined. Then they spend months wondering why nobody's biting.
Wrong profile = longer search, more rejections, worse fit, slower ramp-up. Right profile = faster sourcing, better conversations, quicker decisions.
The profile mistake doesn't just lead to bad hires. It adds months to the timeline. For an early-stage founder, months are everything.
| Stop chasing logos
Here's what I see constantly: a founder gets a CV from someone at Google or Meta, and their eyes light up. Big logo, must be good.
Not necessarily.
Big-company engineers are used to infrastructure that doesn't exist at your startup. They move slower because they're wired for process. They often struggle with ambiguity. And they want to over-engineer everything.
I've seen startups hire "blockchain experts" for a regular SaaS. Machine learning engineers where simple statistics would do. GraphQL APIs for an application with three endpoints.
These engineers aren't bad engineers. They're just wrong for your stage. They want to build "the right way" when you need "the fast way." That mismatch kills early-stage momentum.
| Specialists vs. generalists
The other trap is over-specifying. "5+ years React experience." "Kubernetes expert." "Senior backend engineer with distributed systems experience."
You've just eliminated 90% of people who could actually do the job.
Here's what most founders miss: a good engineer can ramp into a new domain quickly. A specific programming language is a matter of weeks for a strong engineer, especially now with AI tools. What you actually need is someone who can build an MVP fast, wear multiple hats, make pragmatic tradeoffs, and ship.
The team that built Dropbox's custom replacement for Amazon S3 hadn't spent 20 years building distributed systems. They were strong generalists with a passion for learning. They figured it out.
Hire problem solvers, not code writers.
| What "startup-ready" actually looks like
Forget credentials. Here's what actually predicts success at early stage:
Problem-solving over stack knowledge. Can they figure things out when there's no playbook?
Low ego. In a 3-5 person startup, there's no room for lone wolves. Your first engineer will talk to customers, might present to investors, and will definitely do things outside any job description.
Comfort with ambiguity. Requirements will change weekly. If they need a detailed spec before writing a line of code, they'll struggle.
Communication. They'll interact with founders every day and need to explain technical decisions to non-technical people without making anyone feel stupid.
Bias toward shipping. You need 80/20 solutions, not perfect architectures. Speed is survival at this stage.
If a candidate has these traits but their CV doesn't look "impressive" by traditional standards, they're probably a better hire than the one with the fancy logos.
| Why this is a speed problem
The wrong profile doesn't just cause bad hires. It causes slow hiring. Four reasons:
Smaller candidate pool. Narrow specs eliminate most people who could do the job well.
More rejections. Candidates who fit your narrow spec have more options and are more likely to choose bigger companies over yours. (Funny that.)
Longer evaluation. When you're not clear on what you're looking for, every interview feels inconclusive. You keep adding rounds.
Analysis paralysis. Without a clear profile, you can't make a confident decision. You keep searching for "just one more candidate."
Fix the profile, and the rest of the process speeds up dramatically.
| The fix
Before you write a single job description, answer three questions:
What's the 90-day mission? (We covered this in Issue 2) What does this person need to deliver in their first 90 days? That defines the role, not a title.
Generalist or specialist? If you're pre-product-market fit, you almost certainly need a generalist. If you're scaling a specific system, maybe a specialist. Be honest about where you actually are.
Would this person thrive in chaos? Not "could they survive it." Would they enjoy it? That's the difference between someone who stays two years and someone who quits in four months.
Get these right before you do anything else and the rest of your hiring process becomes dramatically easier. You know who you're looking for. Your outreach is targeted. Your conversations are productive. Your decisions are faster.
Clarity first, speed follows.
Next week: how to evaluate engineers without dragging it out.
Cheers Neil