root
64 lines
3.1 KiB
Markdown
64 lines
3.1 KiB
Markdown
# Careers Section (Home Page) — Implementation Plan
|
||
|
||
## 1. Goals & Scope
|
||
- Attract candidates and showcase company culture directly from the home page
|
||
- Careers lives as a **section on the home page**, not a standalone `/careers` page
|
||
- Section should link out to a full job detail view or an ATS for the actual application step
|
||
- Decide: in-house application handling vs. linking out to an ATS (Greenhouse, Lever, Workable, etc.)
|
||
|
||
## 2. Content Structure (Home Page Section)
|
||
- **Section heading/hero** — tagline + short pitch on why to work here
|
||
- **Culture/values snippet** — a few photos or highlights, benefits teaser (health, remote work, PTO, equity, etc.)
|
||
- **Open positions preview** — short list (e.g., top 3–5) with title, department, location, type
|
||
- **"View all openings" CTA** — links to full listing (could be a modal, an anchor-expanded list, or an external ATS board)
|
||
- **Application CTA** — "Apply Now" per role, linking to a form, email, or ATS
|
||
- **Optional extras** — employee testimonials, office photos/video, perks grid
|
||
|
||
## 3. Data Model
|
||
Fields per job posting:
|
||
```
|
||
title
|
||
department
|
||
location
|
||
employment_type
|
||
description
|
||
requirements
|
||
salary_range (optional)
|
||
posted_date
|
||
status (open/closed)
|
||
apply_link
|
||
```
|
||
Store in a CMS (Sanity, Contentful, Strapi) or a simple JSON/database table if no CMS exists.
|
||
|
||
## 4. Technical Approach
|
||
- **Static list** — hardcode JSON if roles change rarely
|
||
- **CMS-driven** — non-technical team can add/remove postings without code
|
||
- **ATS integration** — pull live listings via API (Greenhouse/Lever both offer public job board APIs) for least maintenance
|
||
- **Application handling** — form → email service (e.g., SendGrid) or direct link to ATS application page
|
||
|
||
## 5. Pages / Routes
|
||
- `/` (home page) — Careers section embedded, e.g. `#careers` anchor for nav linking
|
||
- `/careers/[job-slug]` — individual job detail page (linked from the home section)
|
||
- `/careers/apply/[job-slug]` — application form (optional)
|
||
- Consider adding "Careers" to the main nav, scrolling/linking to the `#careers` section
|
||
|
||
## 6. Design Considerations
|
||
- Keep the section concise — it's part of the home page, not the main focus, so limit to a handful of featured/open roles
|
||
- Mobile-responsive job cards, and ensure the section doesn't overload home page load time
|
||
- Clear, prominent "View openings" / "Apply" CTAs
|
||
- SEO: `JobPosting` schema.org structured data on the linked job detail pages so roles surface in Google Jobs search
|
||
- Make sure the section is reachable via nav (e.g., "Careers" nav item scrolls to the section or links to `/#careers`)
|
||
|
||
## 7. Build Order
|
||
1. Design mockups/wireframe for the home page section (placement, hero, mini job list)
|
||
2. Set up data source (CMS or ATS API) for job postings
|
||
3. Build the home page Careers section + "view all/apply" links
|
||
4. Build job detail page(s) linked from the section
|
||
5. Wire up application flow
|
||
6. Add SEO schema markup on job detail pages
|
||
7. Test on mobile; submit a test application
|
||
8. Launch and monitor applications
|
||
|
||
## Open Questions
|
||
- What is the site built with (React/Next.js, WordPress, Webflow, plain HTML)?
|
||
- Use an existing ATS (Greenhouse/Lever) or handle applications via email/form? |