How do you write a job description that attracts great people?

A great job description is a piece of honest writing that clarifies what the work actually is — not a legal checklist or a wish list of credentials. The best candidates are looking for a problem they can obsess over, not a benefits package. Write to that obsession and you'll filter in exactly the people you want.

The real purpose of a job description is filtering, not selling

Most founders treat job descriptions like marketing copy: they inflate the role, soften the hard parts, and list every credential they can think of to look credible. This is backwards. A job description is a matching function. Its job is to make the right people excited and the wrong people self-select out — ideally before they apply.

The candidates who will do your best work are not scanning for salary ranges and 401k vesting schedules. They are asking one question: 'Is this a problem I will find impossible to stop thinking about?' If your description doesn't answer that question with specificity, you'll get a pile of competent generalists who are optimizing for career progression, not people who are constitutionally drawn to the exact challenge you need solved.

This is why the most effective job descriptions read less like HR documents and more like honest accounts of what the work actually involves day-to-day — including what is unsolved, what is frustrating, and what would make it genuinely interesting to the right person.

Write the problem, not the role

The standard job description structure — role title, responsibilities, requirements, perks — buries the only thing that matters to an exceptional candidate: what hard problem are they being asked to solve, and why does it matter right now? Reorder your document around that.

Start with the specific situation your company is in. Not 'we're a fast-growing startup disrupting X,' but the actual technical or market challenge that created the need for this hire. If you're looking for a growth engineer, describe the specific funnel problem you're stuck on and why it's hard. If you need a head of sales, describe what's broken about your current motion and what a successful person would do in the first 90 days. This does two things: it demonstrates that you understand the problem well enough to have thought about it seriously, and it gives a high-caliber candidate something concrete to react to.

Paul Graham's observation about writing as a thinking tool applies directly here: the act of writing out the problem precisely will often expose gaps in your own understanding of what you actually need. Founders who write a careful job description frequently realize mid-draft that they were hiring for the wrong thing. That's the process working correctly.

Signal what kind of person will thrive, not what credentials they need

Credential lists — years of experience, degree requirements, specific tool proficiencies — are proxies for what you actually want, and they're poor ones. They filter on past exposure rather than on the qualities that predict exceptional performance: obsessive curiosity about the domain, independent judgment, and the capacity for deep work.

Instead of listing requirements, describe the texture of how the role operates. Is this a position where someone needs to make consequential decisions with incomplete information, or one where they're executing a well-defined process? Will they be working largely autonomously or in close collaboration? What does 'good' look like in the first six months — and is that measurable, or is it more like 'the team trusts their judgment on hard calls'? The answers to these questions will attract different people than any credential list will.

Paul Graham writes about obsessive interest as a core ingredient in people who do exceptional work — people who pursue a topic because they genuinely cannot help themselves, not because it looks good on a resume. Your job description should include enough specificity about the actual intellectual content of the work that someone with that kind of obsessive interest recognizes themselves in it immediately. A vague description attracts people who are optimizing for titles and compensation. A specific one attracts people who recognize the problem.

Be honest about what is hard

Candidates who are excited by a sanitized version of your company will be surprised and disappointed once they're inside. That churn is expensive and damaging. More importantly, the best candidates — the ones with options — are sophisticated enough to be suspicious of descriptions that have no rough edges. An honest account of what is genuinely difficult about a role increases your credibility with exactly the people you most want to hire.

Being honest doesn't mean listing every dysfunction. It means naming the real constraints: the team is small and resources are limited, the technical infrastructure has debt that will need to be addressed before certain things are possible, the market is early and there will be a long period of low signal before it's clear what's working. People who are motivated by solving real problems find this compelling. People who need artificial certainty will self-select out — which is the outcome you want.

This also applies to the company's stage and trajectory. Describe where you actually are, not where you hope to be. A seed-stage company pretending it has product-market fit, or a Series A company implying it has the operational structure of a later-stage business, will attract people who are mismatched to the actual environment. The right person for an early-stage company knows that ambiguity is the job, and they are energized by that description rather than put off by it.

The mechanics: what to include and what to cut

Keep the document short enough to actually be read. Most job descriptions are three times longer than they need to be because they're written by committee or copied from templates. The sections that earn their space: a one-paragraph description of the company's specific mission (not a generic category claim), a clear statement of the problem or gap this role addresses, two to four concrete examples of what the person will actually do in the first few months, and an honest description of who will thrive in the environment.

Cut or condense: generic culture statements ('we work hard and have fun'), exhaustive credential lists, legal boilerplate that can live elsewhere, and anything that reads like it was written to avoid leaving anyone out. The best job descriptions are polarizing — they are deeply appealing to a specific kind of person and actively unappealing to others.

Before publishing, apply a simple test: read your description and ask whether a genuinely exceptional person in this field, who had multiple offers to choose from, would find this more compelling than a competitor's posting. If the answer is no, the problem is almost always that the description is too generic. Get more specific about the work, the problem, and the person. Specificity is the mechanism that attracts people who are actually interested in what you're building — not just interested in a job.

The one thing to do

Rewrite your job description around the specific problem you need solved — not the role title, credentials, or perks — and you'll filter in candidates who are genuinely drawn to the work rather than just looking for a job.

Frequently asked questions

Should I list salary in a job description?

Yes, include a range if you can. Withholding compensation signals a negotiating posture that makes strong candidates — who have options — move on. Transparency here also filters for candidates who are aligned with what you can actually offer, saving time on both sides.

How long should a job description be?

Short enough to be read in full: usually 300–500 words for the core content. If you find yourself going longer, it's usually because you're listing credentials and generic responsibilities rather than describing the actual work and problem. Cut the former, keep the latter.

Should I require specific years of experience?

Only if years genuinely predict performance in this specific role, which is rare. Most experience requirements filter out unconventional candidates who might be the best hire, while letting through people who have the credential but not the interest or capability. Describe what someone needs to be able to do, not how long they've existed in an industry.

How do I attract people who are truly obsessed with the problem we're solving?

Describe the problem with enough depth and specificity that only someone who has already been thinking about it will recognize what you're talking about. Generic descriptions attract generalists. Precise descriptions of hard, interesting problems attract people who've already lost sleep over them.

Sources

More playbook answers · Growth Prophet home