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, I covered the 300-character outreach framework and why most founder messages get ignored. If your outreach isn't landing, start there.
This week, I'm going one step earlier. Before you write outreach, before you even write a job description, there's something most founders skip entirely. And it's the reason their JD reads like every other listing on the internet.
You'll learn why traditional job descriptions fail for early-stage teams, what a 90-day mission is and how to write one in under 10 minutes, and how it transforms everything downstream, from your JD to your outreach to your interviews.
Not a subscriber yet? Sign up here
| Your job description isn’t working
Most early-stage founders write job descriptions the same way corporates do. Paragraph about the mission, list of tasks, list of responsibilities, tech stack. It feels normal because that's what everyone else does.
But a senior engineer reads it and thinks: "What am I actually owning here?"
This applies whether you have a formal JD on a careers page or a rough brief you're pasting into LinkedIn DMs. The problem is the same. Tasks tell a candidate what you think you need. They don't tell them what success looks like, what the business needs first, or whether you've actually thought the role through. The result is a description that looks identical to every other "fast-paced, collaborative environment" listing. It attracts generalist applications and repels the specific person you actually want.
If the role is unclear, so is the outreach. And unclear outreach gets ignored. (If you missed it, Issue #1 covers exactly why this happens and how to fix the message itself.)
| Tasks vs. missions
Tasks feel operational. Missions feel meaningful.
Tasks say: build X, integrate Y, maintain Z. A mission says: "Ship the first customer-ready version of our product in 90 days."
One line. High clarity. Instant signal.
Strong candidates don't join to do tasks. They join to own outcomes. When an engineer sees a task list, they have to guess what actually matters. When they see a mission, they know immediately whether they're the right person for it, and whether the opportunity is worth their time. That self-selection is exactly what you want. It filters out the wrong people and pulls in the right ones before you've even had a conversation.
| What a 90-Day Mission Actually Looks Like
A clear mission only requires three lines:
Outcome: Ship the v1 billing system that supports usage-based pricing for our first 10 enterprise customers.
Why now: We close our first enterprise deal in 90 days. Without billing, we can't charge them.
Constraint: You'll be the only backend engineer. The existing codebase is a monolith. No time for a full rewrite.
That's it. Compare that to "responsible for backend infrastructure and API development" and you'll see why one gets replies and the other doesn't.
If you're earlier stage and hiring your first engineer, the same structure works: "Ship our MVP to 5 beta users. We have paying design partners waiting. You'll own the full stack, solo, with a non-technical founder."
Notice what the mission does that a task list can't. It tells the engineer exactly what they'd ship, why it's urgent, and what they'd be working within. A strong candidate reads that and either thinks "I've done exactly this" or "that's not me." Both responses are useful. (The worst outcome in hiring is ambiguity. Candidates who aren't sure tend to say yes for the wrong reasons and leave in four months.)
| Write yours in under 10 minutes
Ask yourself three questions:
What is the one outcome this engineer must deliver in the next 90 days?
Why does it matter right now?
What constraint are they operating within?
Write three short lines. If it takes more than 10 minutes, the role isn't ready. That's a signal worth paying attention to. If you can't articulate what this person needs to deliver, you're not ready to hire them yet.
A 90-day mission doesn't replace your job description. It comes before it. A JD written after the mission becomes focused and credible because it has a clear anchor. A JD written before the mission is almost always vague, because you're describing a role that hasn't been properly defined yet. This is the sequence most founders get wrong.
🔗 Download the 90-day mission canvas (Google Doc): A simple G-Doc you can copy and use immediately: Click here to open the document
| What happens when you lead with a mission
Everything downstream sharpens. Your JD becomes focused because you know what the role is actually for. Your outreach becomes high-signal because you can tell a candidate exactly what they'd own. Engineers reply more often because they can see whether this is a fit before the first conversation. Interviews get easier because expectations are aligned from day one.
I've watched founders go from zero outreach replies to booked calls within a week, just by rewriting the top of their message with a mission instead of a task list. The content of the opportunity didn't change. The clarity did.
A job description explains the role. A 90-day mission defines it. Start with the mission.
Next week: the founder interview loop that actually works.
Cheers
Neil