How to Write a Startup Job Description That Attracts the Right People

Most startup job descriptions are either corporate boilerplate that was borrowed from a large company's template, or vague manifestos about "disrupting the industry" that say nothing specific. Neither attracts the kind of candidate who actually does well in an early-stage environment.

The people you want — people who are comfortable with ambiguity, excited by the mission, and good at operating with limited resources — can usually tell within two paragraphs whether a job description was written by someone who understands what the role actually is. If it reads like a LinkedIn profile template, you're losing them before they get to the requirements.

What Most Startup JDs Get Wrong

Too long and generic. A three-page job description with 30 bullet points of requirements is a strong signal that the role isn't clearly scoped. Good candidates are busy. If you can't tell them quickly what the job is and why it's interesting, they'll move on.

Requirements lists that are wish lists. "7+ years of experience, deep knowledge of three programming languages, experience with enterprise sales, MBA preferred" for a role that pays $90K at a pre-seed company. This isn't serious and candidates know it.

Vague about stage and situation. "Fast-growing startup" and "dynamic environment" tell nobody anything. Candidates want to know: how much funding have you raised, how big is the team, what does the business actually do, what will this person actually be working on. The more specific you are, the better.

Hiding the hard parts. If the job involves significant travel, lots of ambiguity, working closely with difficult customers, or solving genuinely hard problems, say so. Candidates who are good at those things will lean in. Candidates who aren't will self-select out — which is the outcome you want.

No information about compensation. In most markets now, failing to include at least a salary range will cost you candidates. Many candidates simply skip jobs without disclosed compensation. The discomfort of putting a number is smaller than the signal you send by not putting one.

The Structure That Works

One-paragraph company summary. What does the company do, how far along are you (stage, funding, team size), and what's the version of the company you're trying to build? This should be written like a human wrote it, not like a marketing department.

Why this role is important now. What problem does this person solve? Why are you hiring this role at this moment in the company's trajectory? This is the part most JDs skip, and it's often the most motivating thing you can put in front of a candidate.

What you'll actually work on. Specific. "Build and own our outbound sales process from scratch" is better than "responsible for driving revenue growth." What are the first three things this person will do in months one, two, and three?

What we're looking for. Keep this short and honest. List the four or five things that are genuinely required. Be clear about what's "must have" vs "nice to have." Don't use job titles as proxies — a "senior engineer at Google" requirement really means "someone who can operate independently and make good technical decisions under uncertainty," which you should just say.

What we offer. Salary range, equity range, benefits, and the honest case for why this is a good role to take. Don't just say "competitive compensation" — give the number or range. For equity, most candidates appreciate some context on what it might mean (even something like "0.5% in a company we believe can reach $X").

A genuine culture note. One short paragraph on what working at this company is actually like. Not a list of values. Something like: "We're 8 people, fully remote, and pretty high-trust — you'll own your work entirely. We communicate mostly async and try to have very few meetings. We work hard but everyone protects their evenings."

Being Honest About Uncertainty

Early-stage startups are uncertain. The strategy will change. The role might evolve significantly. The company might not make it. Pretending otherwise in a job description isn't just dishonest — it sets up a mismatch with candidates who thrive in uncertainty, who are exactly the people you want.

You can acknowledge uncertainty without undermining your pitch. "This is a 0-to-1 role — you'll have a lot of autonomy and you'll need to figure things out without a lot of process" is honest and appealing to the right candidates. "The strategy is still evolving, but the core problem we're solving is clear and we have customers paying us to solve it" is honest and specific. Founders writing their first real hiring materials often benefit from getting outside eyes on the JD before they publish — a platform like Founderboard can give you advisor feedback on whether your pitch reads as credible and compelling to the candidates you're trying to attract.

What to avoid: overselling stability you don't have, overstating progress, or describing a role that doesn't match what you'll actually ask someone to do in month one.

The Equity Disclosure Question

This comes up a lot: should you disclose the equity range in the job description?

The honest answer: yes, you should, but context matters. "0.5% equity" without context tells candidates almost nothing. "0.5% in a company that has raised $2M at an $8M valuation with full standard vesting" tells them something meaningful. The more context you can give — even just a short explanation of the equity package in plain language — the better.

What candidates are usually trying to calculate is: what is this equity actually worth under realistic scenarios? Giving them the tools to do that math shows respect for their time and tends to attract financially sophisticated candidates.

Writing for the Candidate You Actually Want

The most common mistake in startup JDs is writing for the imaginary candidate (maximally qualified, maximally experienced, wants no money, is fully motivated by the mission alone) rather than the real candidate — a smart, capable person who is evaluating you the same way you're evaluating them.

Write the job description from their perspective. What are they currently doing? What would make them leave? What are they nervous about? What would make this role worth taking a risk on?

The answer to those questions is your job description.