Private Pro category · 3 compositions
Careers
Team culture, open-role discovery, and hiring-process explanation. These records are manifest-derived and source-free; an implemented status does not imply manual verification, release readiness, entitlement protection, or availability for purchase.
Manifest items
All 3 records currently carry implemented status. A dedicated detail becomes internally discoverable only after release readiness and a reviewed public preview.
Culture in practice
Hiring path
Category contract
- Purpose
- Team culture, open-role discovery, and hiring-process explanation.
- Declared dependencies
- gummy-typography, gummy-button, gummy-card
- Required review
- light, dark, responsive, keyboard-reviewed, rtl-reviewed, reduced-motion
How to evaluate Careers blocks
Use a careers composition to explain team culture, help candidates discover genuine openings, or make the hiring process understandable. Separate durable information from role-specific details so applicants can tell what applies to the company and what applies to one vacancy.
Connect openings to the actual recruiting source and preserve location, working arrangement, employment type, salary disclosure where required, closing status, and an accessible application destination. Avoid collecting candidate information through a demonstration form or an unmonitored public endpoint.
Have hiring and legal owners confirm every benefit, policy, timeline, and equal-opportunity statement. Test the no-openings state, expired roles, filtered results, long job titles, and external application handoff. Never publish invented employee quotes or an unsupported culture claim.
Record which recruiting system owns each role, how often listings refresh, who approves culture copy, and how candidates receive privacy information before submitting. Supply a deliberate no-openings message and removal behavior for closed roles. The public page should not preserve a vacancy after its application destination or hiring authority has ended. Include a correction route for location, salary, accessibility, and accommodation information that changes during an active search.
Boundary
Public pages contain only approved names, purposes, dependency aliases, requirements, status, and any future reviewed image preview. Editable paid source, test paths, release locations, and entitlement details remain private.