← Recruitment Toolkit Pipa

Job Description Starter

Attract the right people by being specific and honest. Fill in each section — a ready-to-copy JD assembles at the bottom.

Role summary
What this role is, in 2–3 sentences
Signal what matters. Be specific about scope, not vague about potential. Candidates read dozens of these — say something real.
Responsibilities
What they'll actually do — 3 to 5 things
Concrete, not generic. "Drive strategic alignment" tells a candidate nothing. "Own the design system and lead a weekly design review" tells them everything.
Requirements
Must-haves — then nice-to-haves separately
Keep the must-have list short. The longer it gets, the more you're describing a wishlist, not a role. Nice-to-haves signal what you value without eliminating good candidates.
Must-haves
Nice-to-haves
Benefits
What you offer beyond the salary
Health insurance, paid time off, equity, learning budget, parental leave, flexible hours — anything candidates would want to know. Be specific where you can.
About the team
Truthful, not promotional
Don't write the version you wish were true — write the version a candidate will recognize on day one. Honest JDs attract better matches and reduce early attrition.
About the company
What you do, in plain language
A few sentences a candidate can use to decide if they care about what you're building. Not the brand-deck version — what you'd say to a friend asking what your company does.
Application
How to apply and what to send
Be specific. "Send us your CV and a short note on why this role" is better than a generic application form that signals you don't really care who applies.

Turns your draft into a finished JD a candidate would actually want to read.

Saved