Skip to main content
Using the app at app.hotfix.jobs? Start with Help instead. This section is for building on Hotfix.
Hotfix is hiring software (an ATS) for small tech teams. Know who fits before you open a single resume.

​
Why Hotfix

  • Fewer applications to wade through. Requirements show on the apply form, screening questions reject a disqualifying answer for you, and every applicant confirms their email before reaching Applicants.
  • See who fits at a glance. Each job has up to five requirements, written as their own list, separate from the description, so applicants are checked against what matters, not the whole posting. For each one, an LLM finds the line in the applicant’s resume or answers, quoted word for word, or marks it not found. Hotfix rejects any quote that isn’t in the text. Sort Applicants by requirements and start with the people who have all of them.
  • Their words, not a score. Requirements never score, rank, or reject anyone. The hiring team decides.
  • Less busywork. Candidates book their own interviews on Meet, Zoom, or phone. Rejections send the next business day, or in three. Closing a job can email everyone still in the pipeline. Automations run fixed steps, and Agent drafts mail that waits for a person to send.
  • Live the moment you post. Every open job is on your company page, in the embed on your own site, and in Hotfix job search. People apply without an account.
  • Built for your own agents. The REST API, webhooks, and MCP are on every plan.
  • Priced by open jobs. Starter is 10 open jobs at 79amonth,Growth50at79 a month, Growth 50 at 179, and Business 200 at $279, with unlimited seats and the same product on every plan. See pricing.

​
Ways in

Hotfix hiring has three ways in. HTTP under /v1/employer and MCP share the same jobs, applications, interviews, offers, mail, and automations. To show your open jobs on a careers page you design yourself, read them from the public company and job routes.

​
Read these first

  1. Authentication for MCP sign-in and which HTTP routes take a key.
  2. Jobs, Applications, Interviews, Offers and mail, and Automations before you chain tools.
  3. MCP get started to wire a client, then Supported tools for the tool list.
The API reference is the HTTP playground and operation detail. Each page names the matching MCP tool when one exists. Do not treat rest.hotfix.jobs/openapi.json as the hiring spec.

​
Rules that surprise people

Creating a job, an offer, a booking link, or a draft does not send email. A person still hits Send in the app. The one exception is an automation’s schedule_email action, which schedules a letter from the creator’s Gmail. GET resume accepts a session, an API key, or the MCP access token. That path returns the PDF. Hiring stats are not published. Do not invent them. Webhooks are set up in the app, not with an API key or MCP. Start hiring on hotfix.jobs/pricing. The app is on app.hotfix.jobs.