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.
This is the first issue, so let me set the scene. Every week I'll break down one hiring problem and give you something you can use immediately. If it isn't practical, it doesn't make the cut.
This week, I'm starting with the thing that kills most hiring pipelines before they even begin: your opening message to candidates.
You'll learn why top engineers ignore outreach, the three traps most founders fall into, and a simple constraint that will sharpen every message you send.
Not a subscriber yet? Sign up here
| The Tumbleweed problem
When early-stage founders reach out to software engineers, they expect replies. Instead, most get silence. Complete tumbleweed. And when the product is your life, that silence feels personal. Is the comp wrong? Is the product boring? Do they think you don't have the chops?
Maybe. But the far more common truth is simpler than any of that.
Your opening message isn't clear enough.
Engineers aren't ignoring you. They're ignoring vague messages. Top candidates decide in seconds whether something is worth their time. If your message is heavy, unclear, or reads like a pitch deck crammed into paragraph form, they move on.
They've got 20+ other messages sitting in their inbox that day, and most of those aren't much better (which is actually your opportunity, if you think about it).
| Outbound works. Yours probably doesn't
Let me be direct here. Elite engineers do respond to outbound. I've placed hundreds of them this way. It works, but only when the message is good.
Most founder outreach falls into one of three traps. Too much vision, too many words, or too little clarity. Sometimes all three at once.
Strong candidates can smell unclear thinking instantly. If your outreach reads like a pitch for everything and nothing, they assume the role is equally undefined. And in a candidate's mind, unclear roles are high-risk roles.
Why would anyone leave a stable position for something the founder can't even articulate in a message?
| What you should be communicating
Founders think they need to explain the role. This is the wrong approach. What you need to communicate is the essence of the opportunity.
Most opening messages are overcrowded with product descriptions, mission statements, backstory, task lists, tech stack breakdowns, and some vague "selling the dream" language. I've reviewed thousands of these messages over the years and the pattern is always the same.
Founders try to fit everything into one message because they're afraid of leaving something out. But the result is a wall of text that communicates nothing.
What candidates need is signal. Here's what a strong outreach message covers, in roughly this order:
Greeting. Use their name. Sounds obvious, but you'd be surprised.
Why they should care. Your vision or mission in a few words. Not a paragraph. A few words.
What they will own. This is your main hook. Engineers care about ownership and impact, not job titles.
Why this matters now. Creates urgency. What's happening that makes this role critical today?
Comp reference. Even a range builds trust instantly. Leaving it out signals you're hiding something.
Suitability reference. Why them specifically? This is your personalisation. Without it, you're just spamming.
CTA. One clear next step. Not "let me know your thoughts" (which means nothing).
That's seven elements, but in practice they compress into a few sentences. If you can't articulate them cleanly, candidates will assume you haven't thought the role through. And if you haven't thought the role through, why would they reply? (They won't.)
| The 300-character constraint
So how do you fix this? Force yourself to write your first outreach inside the 300-character limit of a LinkedIn connection request.
This isn't a LinkedIn hack. It's a clarity constraint you can deploy across any channel, whether that's email, WhatsApp, or text. Inside 300 characters, you cannot hide unclear thinking. Every word has to earn its place.
If you can express the role in 300 characters, your entire hiring narrative tightens. Your JD gets clearer. Your interview loop sharpens. Your offers land faster. The constraint doesn't just fix the message. It fixes the process.
And if you can't hit 300 characters cleanly? That's useful information too. It means the req needs more work before you start spending time on outreach. I've seen founders spend weeks doing outreach for a role they couldn't describe in two sentences. The market will reveal that gap eventually. Better to find it yourself first.
| Try it right now
Take your current open role and compress it into 300 characters. Include the role, why it matters now, and why this specific person should care. Then read it back and ask yourself one question: would this message get my attention?
If yes, you're ready to start outreach. If not, the constraint just saved you weeks of wasted effort and a lot of ignored messages. Either way, this takes five minutes. It might be the most leveraged five minutes in your entire hiring process.
Clarity at the start forces clarity everywhere else. Better to learn that in five minutes than five weeks.
This is part 1 of the 4-part Clarity-First Hiring Series.
Next week: your role is not a job description, it's a 90-day mission.
Cheers
Neil