HIRING GUIDE
# Make the role clear.
See the evidence.

Give candidates and their AI apps a shared starting point.

## Start in the right workspace

List your authorized clients and choose one before any write. Company context, job drafts and team access remain scoped to that workspace. A self-declared authority statement is not independent employer verification.

## Prepare, review, publish

Import authorized source text or a public source. Complete role facts, working conditions and application questions. Inspect readiness and the exact publication preview, approve in the browser, then publish the unchanged version.

```
In my selected Afina workspace, prepare a private job draft.
Ask for missing pay, location, requirements and application questions.
Show me the publication review. Do not publish yet.
```

## Review what the applicant chose to send

Read the submitted packet and its job contract. Inspect supporting evidence and unresolved questions. Private applicant preferences and unrelated saved answers are not automatically available to recruiters.

## Keep the team’s work separate

The ATS workstream adds configurable pipelines, team roles, private notes/tasks, separate applicant timelines and bounded preparation. A stage change is a reviewed action; an assistant does not autonomously hire or reject people. See [availability](/docs/status) for the implementation and validation boundary.

## Keep external delivery explicit

Greenhouse is the first planned employer-authorized handoff. Local synthetic tests do not establish a live integration. Applicant disclosure and recruiter delivery approvals are separate, and unresolved writes require reconciliation rather than blind retries. Public job-board access is not permission to submit.

[Browse hiring tools ↗](/docs/tools?role=recruiter)
