Pages: Careers
Guides careers page content, structure, and employer branding for recruitment.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for company values, culture, and differentiators.
Identify:
- Audience: Job seekers, passive candidates
- Open roles: List or link to ATS
- Employer brand: Culture, benefits, perks
Best Practices
Essential Elements
| Element |
Purpose |
| Open positions |
List or link to job board/ATS |
| Company culture |
Values, team, work environment |
| Benefits |
Health, remote, PTO, learning |
| Process |
What to expect when applying |
| CTA |
Apply, view roles, contact recruiting |
Structure
- Hero: Employer value proposition; "Join us"
- Open roles: List or embed; filter by department/location
- Why us: Culture, benefits, growth
- Team: Photos, quotes, diversity
- Process: Application steps
SEO
- Target "company name careers," "jobs at company"
- Schema: JobPosting for each role
- Internal links from About, Home
Output Format
- Structure outline
- Employer brand messaging
- Open roles section approach
- SEO metadata and schema
Related Skills
- about-page-generator: Culture and team overlap
- schema-markup: JobPosting schema
- title-tag, meta-description, page-metadata: Careers page metadata
1---2name: careers-page-generator3description: When the user wants to create, optimize, or audit a careers or jobs page. Also use when the user mentions "careers," "jobs," "hiring," "open positions," "company culture," "careers page," "job listings," "we're hiring," "join our team," or "recruitment page."4---56# Pages: Careers78Guides careers page content, structure, and employer branding for recruitment.910**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.1112## Initial Assessment1314**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for company values, culture, and differentiators.1516Identify:171. **Audience**: Job seekers, passive candidates182. **Open roles**: List or link to ATS193. **Employer brand**: Culture, benefits, perks2021## Best Practices2223### Essential Elements2425| Element | Purpose |26|---------|---------|27| **Open positions** | List or link to job board/ATS |28| **Company culture** | Values, team, work environment |29| **Benefits** | Health, remote, PTO, learning |30| **Process** | What to expect when applying |31| **CTA** | Apply, view roles, contact recruiting |3233### Structure3435- **Hero**: Employer value proposition; "Join us"36- **Open roles**: List or embed; filter by department/location37- **Why us**: Culture, benefits, growth38- **Team**: Photos, quotes, diversity39- **Process**: Application steps4041### SEO4243- Target "company name careers," "jobs at company"44- Schema: JobPosting for each role45- Internal links from About, Home4647## Output Format4849- **Structure** outline50- **Employer brand** messaging51- **Open roles** section approach52- **SEO** metadata and schema5354## Related Skills5556- **about-page-generator**: Culture and team overlap57- **schema-markup**: JobPosting schema58- **title-tag, meta-description, page-metadata**: Careers page metadata
dvcrn