Job Description Generator
Generate comprehensive job descriptions, hiring plans, interview rubrics, and organizational materials for any role.
You need to hire a Senior Backend Engineer but your job description is a bullet list of 'requirements' that reads like every other posting on LinkedIn. No wonder your best candidates aren't applying — they can't tell your role apart from 200 others.
Who it's for: hiring managers writing job postings for the first time, HR teams standardizing job descriptions across the company, startup founders who've never written a JD, recruiters creating compelling postings that attract top talent, teams building complete hiring packages with rubrics
Example
"Create a job description and hiring plan for a Senior Product Manager" → Complete package: compelling JD with clear responsibilities and growth path, structured interview rubric with scoring criteria, hiring timeline, and evaluation scorecard — designed to attract strong candidates
CLAUDE.md Template
New here? 3-minute setup guide → | Already set up? Copy the template below.
npx ccplaybooks add job-description-generator# Job Description Generator
## Your Role
You create comprehensive hiring materials including job descriptions, interview rubrics, hiring plans, and evaluation criteria. You ensure materials are inclusive, clear, and effective at attracting the right candidates.
## Information Gathering
### Essential Context
- Role title and level
- Team and reporting structure
- Key responsibilities (top 3-5)
- Required skills vs. nice-to-haveGet new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Create professional job descriptions, interview rubrics, and hiring plans. From a rough idea of the role to a complete hiring package with evaluation criteria.
Quick Start
Step 1: Create a Hiring Folder
mkdir -p ~/Documents/Hiring
Step 2: Download the Template
Click Download above, then:
mv ~/Downloads/CLAUDE.md ~/Documents/Hiring/
Step 3: Run Claude Code
cd ~/Documents/Hiring
claude
Step 4: Describe the Role
Say: "Help me create a job description for [role]"
Example
Input:
I need to hire a senior frontend engineer.
- React/TypeScript stack
- Remote-first company
- Series A startup, ~20 people
- They'll lead our design system work
Output:
## Senior Frontend Engineer
### About the Role
Lead frontend architecture and design system development
for a fast-growing Series A startup. Remote-first culture
with emphasis on autonomy and ownership.
### Responsibilities
- Own and evolve our React/TypeScript codebase
- Lead design system development and documentation
- Mentor junior engineers on frontend best practices
- Collaborate with design on component specifications
### Requirements
- 5+ years frontend development experience
- Expert in React and TypeScript
- Experience building design systems
- Strong communication for remote collaboration
### Nice to Have
- Experience at early-stage startups
- Contributions to open source
- Background in design or UX
### Compensation
- Competitive salary + equity
- Full benefits package
- Home office stipend
What You Get
| Document | Contents |
|---|---|
| Job Description | Role summary, requirements, responsibilities |
| Interview Rubric | Evaluation criteria, scoring guide |
| Hiring Plan | Timeline, stages, interviewers |
| Screening Questions | Phone screen and application questions |
| Take-Home Project | Technical assessment (if appropriate) |
Hiring Package Example
Interview Rubric
| Competency | Questions | Signals to Look For | Red Flags |
|---|---|---|---|
| Technical Depth | "Walk me through..." | Clear explanation, trade-offs | Buzzwords without depth |
| Leadership | "Tell me about a time..." | Ownership, impact | Blame, vagueness |
| Culture | "How do you prefer..." | Alignment with remote | Resistance to async |
Interview Stages
| Stage | Duration | Interviewer | Focus |
|---|---|---|---|
| Phone Screen | 30 min | Recruiter | Basic fit, interest |
| Technical | 60 min | Eng Lead | Workflows assessment |
| System Design | 60 min | Senior Eng | Architecture thinking |
| Culture | 45 min | Team | Values alignment |
Tips
- Be specific: Vague descriptions attract wrong candidates
- Show don't tell: Describe work, not just requirements
- Include salary: Transparency attracts better candidates
- List must-haves only: Long lists discourage good people
- Highlight growth: Top candidates want to learn
Commands
"Create a job description for [role]"
"Write an interview rubric for [position]"
"Design a hiring process for [role]"
"What screening questions should I ask?"
"Create a take-home project for [role]"
"Benchmark salary for [role] in [location]"
"How should I structure the interview?"
Troubleshooting
Description too generic Add more context: company stage, team size, specific projects
Requirements too long Ask: "Separate must-haves from nice-to-haves"
Not attracting right candidates Ask: "Make this more compelling for [target candidate type]"