Hiring signals

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.

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

/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, not as separate touches.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Required evidence

Decide whether to route it

Prepare the review file

Write from the role, not the surveillance

​Required evidence

​Decide whether to route it

​Prepare the review file

​Write from the role, not the surveillance

Required evidence

Decide whether to route it

Prepare the review file

Write from the role, not the surveillance