Careers Page Content Checklist for Startups

A careers page should help a candidate decide whether the work, expectations and process are worth exploring. For a startup, it must stay accurate as the team and hiring plan change. Use this agenda with the employer-brand owner, role owner, people or privacy owner and final approver. It is general educational information, not legal advice.

Open with the audience and role promise

Name the audience, role family and decision the page should support. "Great people wanted" is not a role promise. A useful promise says what problem the person will work on, how they contribute and what the company can offer today. Separate company-wide copy from role-specific details.

Use this opening in the meeting:

CAREERS PAGE CONTENT AUDIT
Review date / page version / page owner:
Audience and role family:
Candidate decision this page should support:
Role promise in one sentence:
Evidence owner / privacy or people owner / final approver:
Publication deadline and next review date:

Ask: What will I build or operate? How are decisions made? What learning and support exist? Where and when is the work done? What is the interview process? Which compensation and benefits details are confirmed? Put unknown answers in the action log, not optimistic prose.

Inventory proof and publication permission

Create one row per claim with source, owner, observation date, permission status, expiry or review date and page section. Evidence can be an approved technical-work description, learning practice, event recording, consented quote or current benefits document. A public page is not automatically permission to reuse a photograph, quote or story.

Metaview's Events page and Engineering resource collection, both checked 5 September 2026, illustrate event and technical-work proof surfaces. They are source-type examples, not evidence for another startup. Pin's employer-branding guide, published 24 March 2026 and updated 23 May 2026, is vendor context for reviewing EVP and reputation; it does not validate your claims or provide a universal benchmark.

Write specific work without guarantees

For each role, name technical work, constraints, collaborators, decision rights and likely first problems. Describe learning as a supported practice, such as pairing, design review or a budgeted course, not a rapid-promotion promise. Describe support through observable commitments: who reviews work, how incidents are handled and how feedback is requested.

Compensation language must match an approved range, location rule, currency and effective date. If a range or benefit is unapproved, say it is being confirmed or remove it. Avoid guarantees about promotion, equity value, visa support, flexibility, job security, impact, speed or outcomes. One employee's experience is not a promise for every hire.

Check inclusion, accessibility and privacy

Use plain language, explain jargon and state the application or contact route. Test keyboard navigation, focus, headings, text alternatives, captions, contrast, zoom and reflow. WCAG 2.2 is a W3C Recommendation dated 12 December 2024; it provides web-content guidance, not a guarantee that a hiring process is fair or accessible. Keep an accessible alternative and named adjustments contact.

Collect only information needed for the stated purpose. Keep candidate names, demographic inferences, health details and application content out of page analytics. The ICO's recruitment AI considerations, dated 6 November 2024, discusses minimisation, transparency, responsibilities, lawful basis and impact assessment. It is UK guidance, not a universal legal answer; ask the responsible adviser about the jurisdiction.

Close the audit with questions, freshness and ownership

Give candidates a short FAQ for location, interview stages, accessibility contact, compensation status, privacy and next step. Every proof point needs a freshness rule: retain, re-verify, revise or archive. Set section owners and one final approver. Preserve the prior version, change reason, source update and approval date.

For analytics, define the event before reading a rate. A page-view denominator may include eligible sessions; an application-start denominator includes sessions reaching the approved event. Record dates, traffic source, exclusions, bot treatment, missing events and immature sessions. Report counts beside rates and label small, partial or unreconciled samples UNKNOWN. Do not invent a benchmark or infer candidate quality from clicks.

Use these gates:

EVIDENCE: claim, source, permission, date, owner and page location are recorded.
UNKNOWN: audience, source, permission, freshness, accessibility or denominator is unclear.
HOLD: an approver, privacy decision, adjustment route or correction is still open.
STOP: a material claim lacks permission, sensitive data is exposed, the page is inaccessible,
      or nobody accountable can withdraw or correct it.

A fictional startup example

In this fictional example, Northstar Labs is hiring a platform engineer. Its draft promises fast growth, remote work and meaningful equity. The owner replaces it with verified deployment-reliability work, a weekly design review, the approved location policy and compensation language subject to the current offer policy. An employee quote stays on HOLD until permission is recorded. The analytics owner defines application-start as the denominator and marks first-week partial data UNKNOWN. The approver archives the old copy and schedules a 30-day review. This is an example, not a benchmark.

Where Talent Summoner fits

Talent Summoner is our product for public-source candidate sourcing and CV ranking. Candidate sourcing starts from a role brief; candidate ranking organises an existing CV set for human review. It does not publish careers content, verify employer-brand claims, manage applicant analytics, process adjustments or make employment decisions. Your team owns evidence, permissions, privacy and approval.

Copy this checklist into the audit meeting note, assign each evidence row and approval action, and keep the page on HOLD until the role promise, proof permissions, accessibility route and measurement definition are clear.