Job post
The role to fill, what it's made of, its statuses and its conditions.
In Spanish: Vacante.
What it is
The job post is the role to fill. Everything else hangs from it: sourcing, candidates, interviews and the report.
| Part | What it is |
|---|---|
| Role details | Title, level, employment type, work mode, location with state or province, positions, start date, application deadline, assignee and members |
| The description | The role, the responsibilities and how the company presents itself |
| The requirements | What's asked for, split into must-have and nice to have, with at least one must-have. It's what applicants read |
| Compensation | The base salary, variable pay, like a bonus, commission or equity, and the benefits |
| The three sets of criteria | Sourcing criteria, screening questions and evaluation criteria. See Criteria |
| The conditions | What gets negotiated with each candidate: expected salary, availability, commission |
| The ideal profile | The portrait of who you're looking for, which the searches come from |
| The client | Whether the job post answers a CRM request. It's optional |
What it's for
It defines once what the client asked for, so sourcing, the pipeline and the report all measure against the same thing. A well-defined job post shows in everything that follows: whatever isn't clarified here gets paid for later in searches that miss.
Where you see it
In the job post list, and in the sidebar, where each job post has its Overview, its Sourcing, its ATS and its edit. On your careers page it shows as a role.
| Status | What it means |
|---|---|
| Draft | Being created. Sourcing doesn't run and it isn't published |
| Active | Being worked on |
| Closed | It's over |
Only draft belongs to the job post. With a request, the job post follows it: it opens when the request is Sent or In progress and closes when it's Closed or Canceled. Without a request, it opens when it leaves draft and you close it. There are no paused job posts anymore: to stop taking applications, unpublish it from the careers page. See Edit job post.
What it gets mixed up with
| Mixed up with | The difference |
|---|---|
| A search | A search is a query that sourcing runs. A job post has many |
| The request | The request is what the client orders in the CRM, with what it's worth. The job post is how that request gets worked. See Request |
| Screening questions | They look like conditions, because both ask about things like salary. But screening filters, with pass or fail, and the condition keeps what gets negotiated, in free text. One asks whether they're in range; the other, the number you agree on |
| Requirements and sourcing criteria | Requirements are what's promised to applicants. Criteria, what they're measured with. See Criteria |
Why it works this way
Sourcing criteria and the ideal profile aren't written when the job post is created. The role is defined once with the client; how and where to search is adjusted run after run. That's why they're prepared in Sourcing, when you're about to search.
Conditions are chosen per job post. Commission matters for a sales role and not for a design one. An empty condition isn't an error: it feeds the questions for the next interview.
The client is optional so an agency that's just starting, or a company hiring for itself, can start from the job post without going through the CRM.
The job post follows its request so the status changes in one place. If the request says the client closed the search, the job post can't stay open on its own.