Most startup job descriptions are written backwards. They start from a template pulled off a big company's careers page, swap in the company name, and end up describing a role nobody at an early-stage company actually needs filled. The result is predictable: a pile of applicants who are wrong for the stage, or worse, no applicants at all.
If you're a founder or the person doing hiring without an HR team, the job description is doing more work than you think. It's not a formality before the real interview starts. It's the first filter, the first trust signal, and often the first place a candidate decides whether your company is worth their time. Get it wrong and you spend weeks screening people who were never going to be a fit. Get it right and you spend less time screening because the wrong people self-select out before they apply.
Here's how to write one that actually attracts candidates who are ready for startup work, not just candidates in general.
Start with the first 90 days, not a list of duties
Skip the bullet list of responsibilities lifted from a bigger company's job posting. Instead, write two or three sentences describing what this person needs to have figured out or shipped by the end of their first quarter. "Own our onboarding funnel and cut drop-off by double digits" tells a candidate far more than "responsible for product analytics and user experience improvements."
This matters more at a startup than anywhere else because the role itself is often underdefined. Writing the first 90 days forces you to define it, which is useful for you even before it's useful for the candidate.
Be upfront about the stage and what that actually means
Candidates who are genuinely suited to early-stage work aren't scared off by ambiguity, limited resources, or a small team. They're scared off by discovering those things after they've accepted the offer. Say plainly where you are: how many people are on the team, whether there's already a codebase or a customer base, whether this hire is your first in the function or your fifth.
This single change does more filtering than any skills requirement. Someone who wants structure and a large team will opt out on their own. Someone who wants to build something from scratch will lean in.
Cut the buzzwords
"Rockstar," "ninja," "wear many hats," "fast-paced environment," "work hard, play hard." These phrases don't describe anything and experienced candidates read them as a warning sign that the company hasn't thought carefully about the role. Replace every adjective with a specific fact. Instead of "fast-paced," say "you'll ship weekly and priorities can shift mid-sprint." Instead of "wear many hats," list the actual second and third responsibilities the role covers.
Separate must-haves from nice-to-haves, and keep the must-have list short
A long requirements list doesn't attract better candidates, it attracts fewer candidates, including the ones you actually wanted. Strong candidates frequently skip applying if they don't check every box, even when they're qualified. Limit true must-haves to three or four items that would genuinely disqualify someone. Put everything else, tools, nice-to-have industry experience, specific frameworks, under a clearly labeled "nice to have" section so candidates know it's not a hard filter.
This is especially important for engineering and product roles, where the gap between "has used this exact stack" and "can learn this stack in two weeks" is often smaller than the job description implies. For more on judging that gap without a technical background, see how non-technical founders can vet engineering candidates.
Put a real number on compensation and equity
A salary range, even a wide one, filters out mismatched applicants before either side wastes time. If equity is part of the offer, say roughly what percentage range or share count is typical for the role and stage rather than just writing "competitive equity." Candidates who are startup-ready have usually been burned by vague comp language before and will read specificity as a signal that you respect their time.
Tell candidates exactly what your process looks like, and then follow it
This is the part most job descriptions skip entirely, and it's the part that does the most to attract candidates who take the role seriously. Say how many rounds there are, roughly how long the process takes end to end, and when they can expect to hear back after applying. If you commit to responding within a set number of business days, write that down and stick to it.
This matters because ghosting is the norm candidates have come to expect from job postings generally, and a startup that breaks that pattern stands out immediately. It also works in your favor as the hiring founder: candidates who value a transparent process are usually the same candidates who'll be comfortable with the ambiguity and direct feedback loops of early-stage work. If you're posting through a platform like WellHired, which requires employers to commit to real response times and doesn't allow listings to sit stale or unanswered, put that same commitment directly in your job description. It reinforces the trust before the first interview even happens, and it costs you nothing but the discipline to follow through.
Describe culture with examples, not adjectives
"Collaborative," "innovative," and "mission-driven" describe every company on every job board. Instead, describe a real behavior: how decisions get made when two people disagree, what a typical week looks like, whether the team is remote-first or expects in-person overlap and how often. One concrete sentence about how your team actually works will tell a candidate more than five adjectives ever will.
Write the headline for the role, not the department
"Software Engineer" gets lost in a sea of identical postings. "Founding Engineer, Backend" or "Product Manager, Zero to One" signals immediately what kind of work this is and what kind of candidate should apply. Startups have an advantage here that big companies don't: the title can describe the actual nature of the work rather than a generic HR level.
Where to post it once it's written
A well-written job description still needs distribution to the right audience. Generalist boards flood postings with volume but not necessarily fit; a description built for startup-ready candidates works best on platforms and communities where people are already looking for early-stage work. For a rundown of low-cost distribution options, see the best places to post a startup job for free or nearly free, and for finding people specifically comfortable joining an unproven company, see where to find candidates willing to join an unproven startup. If you're setting up a repeatable hiring process rather than a one-off posting, /employers is the place to start.
FAQ
How long should a startup job description be?
Aim for 300 to 500 words. Long enough to cover the first 90 days, stage, comp range, and process, short enough that a candidate can read it in under two minutes without skimming past the important parts.
Should I include a salary range even if it's wide?
Yes. A wide range still filters out mismatched applicants and signals transparency. Vague phrases like "competitive salary" tend to be read as a warning sign by experienced candidates rather than a reassurance.
How specific should the required skills list be?
Keep true must-haves to three or four items that would genuinely disqualify someone. Everything else belongs in a separate "nice to have" section, since long requirement lists discourage qualified candidates from applying at all.
Does mentioning response times in the job description actually make a difference?
It does, mainly because most job postings never commit to one. Candidates who've been ghosted before will notice a specific, followed-through response time commitment, and it tends to attract people who value the same transparency in how they'd want to work day to day.
What's the biggest mistake founders make writing their own job descriptions?
Copying a template built for a large company. It brings in candidates who expect structure, defined scope, and layers of process that an early-stage company doesn't have yet, which leads to mismatched hires and early attrition.