---
name: hiring-signals-jobs
description: "Step-by-step job recipes for the Hiring Signals MCP server: Company hiring brief; Watch companies for new and closed roles; Watchlist hiring digest. Use when the user asks things like \"What is Snap hiring for right now?\" or \"Watch Airbnb, Spotify and Snap for new roles.\""
license: MIT
---

# Hiring Signals jobs

Each section below walks through one job with the tools of the `hiring-signals` MCP server. The same recipes are MCP prompts (prompts/list) on `https://hiring.openkrill.app/mcp`.
Connect the server at `https://hiring.openkrill.app/mcp` in your MCP client settings (remote streamable HTTP, no key), then call its tools as normal tool calls. They are not command line programs: Bash, curl and scripts cannot reach them.

## Company hiring brief

Job: Company hiring brief, with the Hiring Signals MCP server.

Use the `company_hiring_brief` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "What is Snap hiring for right now?"

Steps:
1. Call `company_hiring_brief` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `company`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"company":"greenhouse:airbnb"}`
4. For the request "What is Snap hiring for right now?", a correct answer looks like this: Open roles, top departments and countries, the 5 newest roles and the board token workday:snapchat.wd1/snap.
5. Follow the server's own rules:
   - Use company_hiring_brief when the user asks what a company is hiring for or how fast.
   - Later calls with that watch_key return new and closed roles since the last call.
   - Velocity is empty until a board has snapshots that old; say so rather than guessing.
   - Never invent a watch_key.
   - Do not look up or contact people at the companies.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `company_hiring_brief`).

## Watch companies for new and closed roles

Job: Watch companies for new and closed roles, with the Hiring Signals MCP server.

Use the `watch_new_roles` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Watch Airbnb, Spotify and Snap for new roles."

Steps:
1. Call `watch_new_roles` as a normal MCP tool call, with the request's values in the fields of its inputSchema.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"companies":["greenhouse:airbnb"]}`
4. For the request "Watch Airbnb, Spotify and Snap for new roles.", a correct answer looks like this: A watch_key, baseline true, 3 boards and their open role count, no new roles.
5. Follow the server's own rules:
   - Use watch_new_roles to follow companies: the first call returns a watch_key and records the open roles (baseline true, nothing new yet); tell the user to keep the key.
   - Later calls with that watch_key return new and closed roles since the last call.
   - Velocity is empty until a board has snapshots that old; say so rather than guessing.
   - Never invent a watch_key.
   - Do not look up or contact people at the companies.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `watch_new_roles`).

## Watchlist hiring digest

Job: Watchlist hiring digest, with the Hiring Signals MCP server.

Use the `watchlist_digest` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Which companies on watch hs_0123456789abcdef0123456789abcdef are hiring fastest?"

Steps:
1. Call `watchlist_digest` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `watch_key`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"watch_key":"hs_00000000000000000000000000000000"}`
4. For the request "Which companies on watch hs_0123456789abcdef0123456789abcdef are hiring fastest?", a correct answer looks like this: One row per watched board with open roles and 7 and 30 day opened and closed counts, fastest first.
5. Follow the server's own rules:
   - Later calls with that watch_key return new and closed roles since the last call.
   - Use watchlist_digest with the key to rank the watched companies by hiring pace.
   - Velocity is empty until a board has snapshots that old; say so rather than guessing.
   - Never invent a watch_key.
   - Do not look up or contact people at the companies.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `watchlist_digest`).