# Job openings

Public job-opening signals — active hiring footprint, listing lifecycle, function-family momentum, and mix patterns from roles we can observe.

_Data source — Job-opening signals Propensify detects: hiring footprint, listing lifecycle, function-family momentum, and mix patterns from public openings._

HTML: https://propensify.io/data-sources/job-openings
Markdown: https://propensify.io/data-sources/job-openings.md

## Three questions we ask of the requisition

1. **What function is this, really?** — Sales, warehouse, marketplace ops, RevOps, compliance marketing — the role nouns in the description.
2. **How is the work done?** — Tooling and process language: CRM, list-building, GTM engineering, developer tickets for web changes, 3PL, healthcare ad approvals.
3. **What motion does the copy imply?** — Enterprise versus volume, urgency, hiring freeze versus burst — including spray-and-pray or call-centre language when it appears.

No openings, or a description too thin to read, is unknown — not that they never hire.

- **Also read:** [Company workforce](https://propensify.io/data-sources/company-workforce) — listings ≠ headcount series

plus optional keyword focus when your ICP supplies roles

## Footprint is a gate. Timing is prioritization.

### Footprint

Whether we see active openings, stale opens, closed listings — or none returned for the domain.

### Timing

How listings move — newly seen, long-running, closing fast or slow, and which function families are heating or cooling.

## How job-opening evidence stacks

Three layers — bind the hiring footprint, read lifecycle texture, then see which function families are in motion.

1. **Footprint** — Active / none + texture
2. **Lifecycle** — New, aging, closing
3. **Function momentum** — Heating → quiet by family

- **Always useful:** Active vs none — and stale/closed context when openings exist.
- **Lifecycle texture:** Newly seen, long-running, quick or recent closes.
- **Function motion:** Accelerating → dormant per role family in the returned openings.

## Hiring footprint

First question: do we observe open roles for this domain — and what’s the open/closed texture?

Active and none are exclusive outcomes for a research pass. Stale and closed can appear alongside active listings.

## Footprint States

- **Active openings:** At least one listing meets active-open freshness for the domain.
- **None returned:** No openings in the returned sample — not “never hires.”
- **Stale open:** Still listed but aging — evergreen ATS noise or quiet hiring.
- **Closed listings:** Closed in the sample — closed ≠ confirmed filled.

## Listing lifecycle

How openings age and leave the board — listings can show more than one of these in the same pass.

## Lifecycle texture

Fresh first-seen activity through long-running opens and recent closes — coexisting subject flags, not a single exclusive state.

_Fresh activity → aging / closed_

- **Newly first seen:** Listing entered observation recently — fresh posting signal.
- **Long-running open:** Visible for a long window — not proof of a hard-to-fill role.
- **Quickly closed:** Short observed listing lifetime — not a confirmed quick hire.
- **Recently closed:** Left the board in the recent window — motion without hire proof.

## Function momentum

Per function family in the returned openings — heating, newly emerged, cooling, or quiet.

Listing momentum is not headcount growth. Closure speed is observed listing lifetime — not confirmed time-to-hire.

## Category motion

Exclusive states for a function family in the openings sample — packs see category as the subject.

_Heating → quiet_

- **Accelerating:** Recent first-seen volume exceeds the prior window for the family.
- **Recently emerged:** Family appears in recent openings after a quiet prior window.
- **Cooling:** Family activity stepped down versus the prior window.
- **Dormant:** No recent motion for that function family in the sample.

## Closure Velocity

- **Fast closure:** Median observed listing lifetime is short for the family.
- **Slow closure:** Listings linger longer before leaving the board.

## Mix & clusters

Where openings concentrate — function, location, seniority, remote/hybrid, pay disclosure, and recurring titles.

Clusters reflect the returned openings sample — not an exhaustive careers-site crawl claim.

## Mix Cards

- **Function cluster:** Openings concentrate in one or more function families.
- **Location cluster:** Roles cluster in shared locations or geos.
- **Seniority concentration:** Mix skews toward a seniority band in the sample.
- **Open-mix concentration:** Current opens are concentrated — thin diversity in the sample.
- **Aging cluster:** A pocket of opens is aging together.
- **Remote / hybrid:** Multiple openings share remote or hybrid contract types.
- **Salary disclosed:** Pay bounds appear on one or more listings.
- **Salary band cluster:** Enough disclosures to see a recurring band — not total-comp truth.
- **Recurring title:** Same or near-same title reappears — repost or evergreen pattern.

## Keyword focus

When your ICP supplies focus roles or skills, we can match openings and timing to those keywords.

When your ICP supplies focus roles or keywords, we can match titles, taxonomy, and recent keyword motion — including lower-precision description-only hits.

## Keyword Chips

- Role match
- Title match
- Taxonomy
- Description-only
- Open concentration
- Recent
- Accelerating
- Long-running

## What it looks like in a verified fit

Job-opening evidence lands as findings on the account — with the same Fit and Signals score grammar as the product.

Brightfield Robotics

## Findings

- **Active openings**
- **Function accelerating**
- **Remote / hybrid pattern**

## Boundaries & method

- Public / observable openings for the domain — not every ATS on earth.
- Open listings are visibility — not confirmed hires.
- Closed does not prove the role was filled.
- No openings returned ≠ the company never hires.
- Stale open may be evergreen ATS noise or quiet hiring.
- Long-visible listings aren’t proof of a hard-to-fill role.
- Short listing lifetime isn’t a confirmed quick hire.
- Function acceleration is listing observation — not headcount growth.
- Clusters reflect the returned openings sample for the domain.
- Salary when disclosed uses annual USD bounds — not total-comp truth.
- Keyword focus only when your ICP supplies keywords; description-only matches are lower precision.
- We do not invent open-role volume bands (high / medium / low headcount from listing counts).

## Want job-opening signals on your verified fits?

We’ll map footprint, lifecycle, and function momentum to your ICP and show how they look on real accounts.

- [Get 10 vetted companies →](https://propensify.io/#lead)
- [Book a call](https://propensify.io/book-a-call)


Part of https://propensify.io/data-sources. Full set: https://propensify.io/data-sources.md.