How to write a startup job description that converts senior candidates in 2026

The single biggest predictor of reply rate on a cold outbound message is not the recruiter, the comp, or the logo attached to the sender. It is the job description you link to. A great JD sells the mission in the first ninety words, gives the reader something specific to react to, and cuts every corporate cliche. A weak JD burns the outreach before the recipient finishes their coffee.

This is the framework we use across the Startup Roles platform to write job descriptions that convert senior candidates. It works for engineering, product, design, and commercial roles at pre-seed through Series B.

Why most startup job descriptions fail

The average startup JD in 2026 is 780 words long, opens with a company boilerplate paragraph that could belong to any of a hundred competitors, and buries the actually interesting content beneath a wall of requirements. Senior candidates scan the first two paragraphs and leave. Junior candidates apply anyway, which then floods your funnel with the wrong shape of applicant.

The fix is structural, not stylistic. You do not need a better copywriter, you need a better skeleton.

The five block structure that converts

Block one: the one line hook (20 to 40 words)

Say what the company does, in plain English, plus why now. Not the mission, not the values, not the round announcement. The hook.

Bad: "We are a mission driven, category defining B2B SaaS company reimagining the future of work."

Good: "Startup Roles is the AI powered hiring platform used by fifty plus seed and Series A founders in the UK. We turn a rough JD into a warm shortlist inside 24 hours."

Block two: the problem this role owns (80 to 120 words)

Describe the messy, real problem this specific role will own for the next twelve months. Name the surface. Name the constraint. Name the current gap.

Senior candidates buy problems, not roles. If the problem is clear and interesting, they will convert. If it reads as "help us scale", they will not.

Block three: what you will actually do (5 to 7 bullets)

Every bullet starts with a verb. Every bullet describes a specific artifact or outcome, not a vague responsibility.

• Bad: "Own the product roadmap."
• Good: "Ship the first version of our activation dashboard by end of Q3, working directly with our two design partners in London."

Block four: what good looks like (the scoreboard)

Replace the "requirements" list. State the outcomes you will judge success on at 30, 90, and 180 days. This is the single highest converting section of a modern startup JD, because it lets a senior candidate mentally cast themselves into the role.

Example for a founding engineer:

• Day 30: First production PR merged, plus a written architecture note on our billing stack.
• Day 90: Owns the payments and webhooks surface end to end. On call rotation with the founder.
• Day 180: Interviewing and closing engineer number three. Shipped our second design partner integration.

Block five: comp, equity, location, and interview plan

All in the JD. Do not make people ask. Every field a candidate would negotiate over goes here.

• Base band. A number with a range, not "competitive".
• Equity band. Percentage or share count with an assumed valuation.
• Location. Fully remote, hybrid with named days, or fully in office. Named city, not "UK".
• Interview plan. Number of stages, format, expected time to offer.

Length matters

Across the roles we have run on Startup Roles in the last twelve months, reply rate on outbound linked to a JD peaks between 350 and 500 words. Above 700 words, reply rates drop by roughly a third. Below 250 words, the role reads as unfinished and reply rate drops by roughly half.

Words to cut, always

The following words and phrases are correlated with lower reply rates in every dataset we have looked at:

• "Rockstar", "ninja", "wizard", "guru"
• "World class", "best in class", "category defining"
• "Fast paced", "hyper growth", "we work hard and play hard"
• "Passionate about" (unless followed by a specific noun a candidate can react to)
• "Competitive salary and equity"
• "Must have X years of experience" (see below)

The "years of experience" trap

Years of experience is a lazy proxy for skill and it filters out exactly the candidates you want. Replace "5+ years of experience with distributed systems" with "shipped at least one production system that handled more than 1000 requests per second". Specific artifacts, not tenure.

Publishing comp is now table stakes

In the UK, most of the EU, and a growing number of US states, publishing a salary band is now a legal requirement or a de facto default. In every candidate survey we run, an undisclosed band is a soft signal that comp is below market. If your comp is genuinely competitive, publishing it costs you nothing and lifts reply rates by around fifteen to twenty percent.

A copy-paste template

[Company] in one line, plus why now.

The problem
[80 to 120 words on the messy real problem this role owns for the next 12 months.]

What you will do
- Ship [specific artifact] by [date]
- Own [specific surface] end to end
- Partner with [named team] on [specific outcome]
- [3 more bullets in the same shape]

What good looks like
- Day 30: [outcome]
- Day 90: [outcome]
- Day 180: [outcome]

Comp and logistics
- Base: [band]
- Equity: [band]
- Location: [named city, hybrid pattern, or fully remote]
- Interview plan: [number of stages, format, time to offer]

How to apply
- One paragraph on why this role, plus a link to work you are proud of.

Before and after: a real rewrite

Before (642 words, 4% reply rate on outbound): "We are a mission driven, category defining B2B SaaS company reimagining the future of work. We are looking for a world class senior product designer to join our rapidly scaling design team..."

After (398 words, 19% reply rate on outbound): "Acme is the AI powered ops platform used by 200 UK plumbing and heating businesses. We just closed our Series A and are hiring a senior product designer to own our installer app end to end, working directly with our two lead engineers and our first three design partners in Bristol..."

Same company, same comp, same team, six week gap between the two versions. The only change was the JD.

Frequently asked questions

Should the JD live on our careers page or in the outreach message?

Both. Link to a hosted version on your own domain so the recipient can share it. Never paste the full JD into the first outbound message.

Should we A/B test JDs?

Not at seed stage. Volume is too low for the test to converge. Rewrite once with the framework above, then trust the reply rate signal for six to eight weeks before iterating.

What about "nice to haves"?

Delete the section. If it is a nice to have, it is not a decision criterion. If it is a decision criterion, it belongs in the scoreboard.

How often should we refresh a JD?

Every 90 days on an open role, plus every time the round, team size, or product surface materially changes. Stale JDs signal a stale company.

For more on the sourcing side, see our sourcing passive candidates playbook and our 2026 outbound tools comparison.