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

# Hiring signals

> Qualify a relevant job posting as account evidence before outreach.

[Human guide: work with your agent →](https://deepline.com/docs/human/plays/signal-hiring.md)

> [!NOTE]
>
> Interpret a dated hiring signal and prepare a role-relevant account review.

An open role can show that a company is building a function. It does not prove
budget, a vendor evaluation, or the right person to contact. This page owns the
checks that turn a posting into a reviewable account signal. The shared
collection, owner, suppression, and activation steps live in [signal
playbooks](https://deepline.com/docs/plays/signal-playbooks.md).

## Required evidence

Keep these fields for every candidate:

* The live posting URL and observed or posted date.
* The exact role title and a short reason it is relevant to your product.
* The account match and ICP-fit result.
* The affected function and a proposed contact role.
* Any existing customer, opportunity, owner, or suppression state.

Treat an old, removed, or unrelated posting as no action. A recently refreshed
post still needs an account-fit and relevance check.

## Decide whether to route it

| Evidence result | Decision |
| - | - |
| ICP-fit account and a current role directly relevant to your category | Draft a role-specific research or outreach angle for review. |
| ICP-fit account and an adjacent role | Keep as a lower-confidence research candidate. |
| Generic hiring volume, missing source, or unclear role relevance | Record the evidence but do not route an outreach action. |
| Existing customer or active opportunity | Route the evidence to the account or deal owner. |

## Prepare the review file

```text theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
/deepline-gtm Review target-accounts.csv for current job postings relevant to
[our product category]. For each candidate, return the posting URL, observed
date, exact role, relevance explanation, ICP-fit result, account owner, and one
proposed action.
```

## Write from the role, not the surveillance

If a reviewed draft is appropriate, use the function and the public role
context—not a claim that you tracked the company. Do not state that hiring
proves budget, initiative timing, or a named person's authority. Combine a
hiring signal with another verified account change only through the
[signal-combination policy](https://deepline.com/docs/plays/signal-deal-risk.md), not as separate touches.

***

**Related:** [Champion Tracking](https://deepline.com/docs/plays/signal-champion-tracking.md) | [Fundraising Signals](https://deepline.com/docs/plays/signal-fundraising.md) | [Company News & Social](https://deepline.com/docs/plays/signal-company-news.md) | [Competitive Intelligence](https://deepline.com/docs/plays/signal-competitive-intel.md)

## Verify this task

Check the company, role, source date, and whether the opening remains relevant. Keep inferred business needs explicit.

Ask your agent to explain a failed check before repeating work or expanding the scope.


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