> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hotfix.jobs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Call them jobs, not postings, listings, or roles.
> To act for an employer, connect to the MCP server at https://mcp.hotfix.jobs/hiring and sign in with a Hotfix account. API keys are for HTTP scripts, not MCP.
> Only describe the routes, tools, and numbers these docs publish. If something isn't documented, say so instead of guessing.
> Webhooks are managed in the app under Settings > Connections > Webhooks. An API key or MCP client can't create or change them.
> Hotfix is the applicant tracking system. Applications land on the job in Hotfix and aren't sent to another ATS.
> Creating a draft, offer, or booking link sends nothing. A person sends the email from Hotfix.

# Jobs and the careers page

> What a job on Hotfix holds, where it shows, how applying works, and what knockout questions do.

## A job

A job on Hotfix has a title, where it is and its work style, pay, a department and team, the description, and its apply form. What the job needs lives in the description, usually as a **What you'll need** list. There's no separate requirements field.

Your agent writes a job's search fields (a summary, skills, years, and education) with the post. If a job is saved without them, Hotfix fills them in after it's published, and never over ones you gave.

| Status | Meaning |
| - | - |
| **Draft** | Saved, not live. Drafts don't count toward your plan. |
| **Open** | Live and taking applications. |
| **Paused** | Off Hotfix search and closed to applications after a paid plan ended. Paying again reopens it. |
| **Closed** | Final. To hire for the role again, post a new job. |

## Where a job shows

An open job is on your [company page](https://docs.hotfix.jobs/company-page.md), `hotfix.jobs/companies/{slug}`, grouped by department and team, and in Hotfix job search, where people whose alerts match hear about it the day it goes live. Each job has its own page at `hotfix.jobs/jobs/{job_id}` with **Overview** and **Apply** tabs. Search engines index your company page and job pages, with Google for Jobs markup.

## Applying

Candidates apply on the job's **Apply** tab. Every form has name, email, resume, the equal opportunity questions where the law asks them, and a privacy and AI notice. The rest is yours: phone, LinkedIn, GitHub, a website, and a cover letter, each required, optional, or off, and up to 20 questions of your own.

When someone applies, Hotfix:

* confirms their email with a code, or by their signing in
* keeps their resume's text beside the PDF, read from the file without a model
* refuses a second application from the same person to the same job
* runs your knockout questions
* sends your **Application received** email

Only confirmed applications reach you.

## Knockout questions

A knockout is one of your apply questions with an answer that ends the application: a yes/no that ends it on one answer, or a number that ends it below a minimum. Use them only for hard limits, like work authorization or a minimum of experience.

An application that fails a knockout is declined at once, and the candidate isn't told why. On the person's page, the status says which knockout they failed.

## Where applications came from

Add `?source=` to any link to your company page or a job, like `?source=linkedin`, and applications through it carry that channel. See [Where they came from](https://docs.hotfix.jobs/applications.md#where-they-came-from).

## Counts over time

Ask your agent how a job is doing: applications per day, views and apply clicks, where applications came from, hires, and how far people got. It never counts per person.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.