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-generator
3description: 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." For sitewide page planning, use website-structure.
4metadata:
5 version: 1.0.1
6---
7
8# Pages: Careers
9
10Guides careers page content, structure, and employer branding for recruitment.
11
12**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.
13
14## Initial Assessment
15
16**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for company values, culture, and differentiators.
17
18Identify:
191. **Audience**: Job seekers, passive candidates
202. **Open roles**: List or link to ATS
213. **Employer brand**: Culture, benefits, perks
22
23## Best Practices
24
25### Essential Elements
26
27| Element | Purpose |
28|---------|---------|
29| **Open positions** | List or link to job board/ATS |
30| **Company culture** | Values, team, work environment |
31| **Benefits** | Health, remote, PTO, learning |
32| **Process** | What to expect when applying |
33| **CTA** | Apply, view roles, contact recruiting |
34
35### Structure
36
37- **Hero**: Employer value proposition; "Join us"
38- **Open roles**: List or embed; filter by department/location
39- **Why us**: Culture, benefits, growth
40- **Team**: Photos, quotes, diversity
41- **Process**: Application steps
42
43### SEO
44
45- Target "company name careers," "jobs at company"
46- Schema: JobPosting for each role
47- Internal links from About, Home
48
49## Output Format
50
51- **Structure** outline
52- **Employer brand** messaging
53- **Open roles** section approach
54- **SEO** metadata and schema
55
56## Related Skills
57
58- **about-page-generator**: Culture and team overlap
59- **schema-markup**: JobPosting schema
60- **title-tag, meta-description, page-metadata**: Careers page metadata
kostja94