How to Write a Job Description That Attracts the Right Candidates

How To Write a Job Description as a Real Recruiter, Not AI

Most founders write job descriptions the same way they write investor updates: professionally, carefully, and completely disconnected from how real people actually read them.

The result? A posting that sounds like it was written by a committee, attracts 200 unqualified applicants, and somehow still misses the one person you actually needed.

AI can help you move faster in a lot of areas, but a job description is a conversation with a real person before they even apply. That part can't be automated.

That's why we built a template for writing job descriptions (especially for remote positions). Spoiler alert: It’s nothing fancy, just the exact structure our recruiters use. Copy it, edit it, make it yours. Download it here.

‍

Why Most Job Descriptions Fail

It's worth understanding why most job descriptions don't work — because the mistakes are almost always the same.

They try to speak to everyone. When you write for "any motivated, detail-oriented professional," you're writing for no one. The best candidates — the ones who are already employed, slightly overqualified, and selective about where they apply — need to feel like the role was written specifically for them. 

They list tasks instead of outcomes. "Manage the CEO's calendar" tells a candidate what they'll be doing. "Own the CEO's time so she can focus entirely on fundraising and product" tells them why it matters. That difference is the difference between someone who shows up and someone who takes ownership.

They confuse requirements with wish lists. Every time you add a "required" qualification that you'd actually waive for the right candidate, you're lying — and candidates know it. It makes the whole posting feel unserious, and it filters out people who might have been perfect.

They're written for compliance, not conversion. Job descriptions evolved from HR paperwork. Most still read like it. They're designed to document a role, not to sell it. In a competitive hiring market, that's a losing strategy.

‍

The 4 Sections That Actually Matter

A job description has one job: get the right person to apply and get the wrong person to self-select out. Everything else is noise. Here are the four sections that do the work.

⚡ 1. Position Overview

This is the first thing a candidate reads and often the only thing they read before deciding whether to keep going. Don't waste it on generic filler.

In 3–4 sentences, answer these four questions:

• What is the role, actually?
• Who will this person work with and support?
• Where is the company right now (stage, size, momentum)?
• What kind of person genuinely thrives here? 

Think of it less as a description and more as a pitch. You're selling the role just as much as they're selling themselves. The best candidates have options. Give them a reason to keep reading.

What to avoid: Opening with "We are a fast-growing company looking for a dynamic self-starter." Every company says this. It means nothing. Start with something specific: it can be a number, a milestone, a real challenge the person will be walking into.

Fill-in-the-blank: "We're a [stage] company in [industry] that [what you do in one line]. This role supports [who] directly and owns [core function]. You'll thrive here if you're someone who [trait] and wants [what this role offers that others don't]."

💪 2. Key Responsibilities

List 5–8 responsibilities. If you have 10 things on this list, you either have two roles disguised as one, or you haven't thought hard enough about what actually matters.

Start every bullet with an action verb. Not "responsible for," not "will help with", but a real verb that implies ownership:

• Manage, Own, Lead, Drive (high ownership)
• Draft, Build, Create, Design (execution)
• Coordinate, Facilitate, Support (collaboration)
• Analyze, Track, Report, Monitor (ops/data)

The more specific you are, the easier it is for the right candidate to picture themselves in the role, and the easier it is for the wrong candidate to realize it's not for them. Both outcomes are good.

What to avoid: Vague bullets like "support the team on various projects" or "handle day-to-day operations." These don't tell anyone anything, and they attract candidates who are equally vague about what they can do.

A useful test: Read each bullet and ask yourself, "Could I evaluate whether someone is doing this well or not?" If the answer is no, the bullet is too vague. Rewrite it until the answer is yes.

✅ 3. Qualifications (Must-Haves)

This is where most founders over-engineer it. They write down everything they'd want in a perfect candidate and label all of it "required." Then they wonder why nobody strong applies.

Split your must-haves from your nice-to-haves, and be ruthlessly honest about which is which.

For each qualification, ask yourself: "Would I reject an otherwise exceptional candidate for not having this?" If the answer is yes, it's a must-have. If you'd make exceptions, it's not — move it to Nice to Have or cut it entirely.

Must-haves should typically include:

• Years of relevant experience (be specific: "3+ years in an ops role at a startup," not "several years of experience")
• Hard skills that are genuinely non-negotiable (specific tools, languages, certifications)
• Working style requirements (fully async, on-call availability, timezone overlap)

What to avoid: Degree requirements as a default. If you genuinely need a degree for the role, keep it. But if you'd hire a great candidate without one, remove it — it filters out strong people for no reason.

😊 4. Nice to Have

Keep this to 2–3 items max. These are bonuses, not dealbreakers, so treat them that way in how you write them.

Nice-to-haves serve a real purpose: they tell candidates what will make them stand out, and they give your team a tiebreaker when two candidates are otherwise equal. But when this section has 6+ items, it stops functioning as a bonus list and starts functioning as a second requirements section (which breaks the whole logic of the posting).

If you find yourself listing more than three things here, apply this filter: pick the two most meaningful ones and cut everything else. The ones you cut probably belonged in Qualifications if they really mattered, or they were noise.

Good nice-to-haves are specific and differentiating. "Experience with Notion" is fine. "Has previously built a Notion-based operations hub for a distributed team" is better; it tells a story about what good looks like without making it a requirement. 

A Note on Tone

The way you write a job description is the first signal a candidate gets about what it's like to work at your company. Bureaucratic, generic, copy-pasted? They'll assume the culture matches. Clear, specific, human? They'll want to know more.

Write it the way you'd explain the role to a smart friend over coffee. Then clean it up slightly for professionalism. That's the right calibration.

Avoid corporate filler phrases entirely: "fast-paced environment," "wears many hats," "passionate about excellence," "team player." Every company uses these. They add no information and make your posting blend into the noise.

Before You Post: A Quick Checklist

• Position Overview answers: what, who, where we are, who thrives here
• Responsibilities are 4–6 bullets, each starting with an action verb
• Every "required" qualification is something you'd actually enforce
• Nice-to-haves are 3 or fewer, and are genuinely bonuses
• No filler phrases or generic language
• Someone who's wrong for the role would know it after reading this
• Someone who's right for the role would feel excited after reading this

‍