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." For sitewide page planning, use website-structure.4---5
6# Pages: Careers
7
8Guides careers page content, structure, and employer branding for recruitment.
9
10**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.
11
12## Initial Assessment
13
14**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for company values, culture, and differentiators.
15
16Identify:
171. **Audience**: Job seekers, passive candidates
182. **Open roles**: List or link to ATS
193. **Employer brand**: Culture, benefits, perks
20
21## Best Practices
22
23### Essential Elements
24
25| 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 |
32
33### Structure
34
35- **Hero**: Employer value proposition; "Join us"
36- **Open roles**: List or embed; filter by department/location
37- **Why us**: Culture, benefits, growth
38- **Team**: Photos, quotes, diversity
39- **Process**: Application steps
40
41### SEO
42
43- Target "company name careers," "jobs at company"
44- Schema: JobPosting for each role
45- Internal links from About, Home
46
47## Output Format
48
49- **Structure** outline
50- **Employer brand** messaging
51- **Open roles** section approach
52- **SEO** metadata and schema
53
54## Related Skills
55
56- **about-page-generator**: Culture and team overlap
57- **schema-markup**: JobPosting schema
58- **title-tag, meta-description, page-metadata**: Careers page metadata
kostja94