BASE
Written from live job ingest, not inferred later
BASE
AI-relevant hiring, consolidated into one timeline row.
Job openings grouped by cleaned title and location, depth-scored before they ever become a signal — so three hiring signals on a company is not the same as three raw job posts. Hiring is the foundation that refreshes Tools and Velocity and can contribute evidence to Funding + AI.
- Many openings can collapse into one hiring signal
- Depth 0–1 never ships — only qualified groups become rows
- Feeds Tools, Velocity, and Funding + AI downstream
- Snapshots keep the job ids behind every label
Sample signalBASE
Hiring · ML Engineer
3 openings consolidated · depth scored · sample
ML EngineerSF · Remote
ML EngineerSF · Remote
ML EngineerSF · Remote
same title + location →
Hiring · ML Engineer
3 openings · depth 4 · conf 75
Depth → confidence
D5
100
D4
75
D3
50
D2
20
D0–1—
Depth 0–1 never becomes a signal
BASE
Role
2–5
Depth gate
title + loc
Consolidate
At a glance
How this signal shows up in the store
2–5
Depth ladder that maps to confidence 20–100
1 row
Per company + cleaned title + location group
3+
Downstream paths: Tools, Velocity, Funding+AI
What it is
One sentence for a job group that matters
A Hiring signal is an AI-relevant (or depth-qualified) job opening group turned into one timeline sentence — with department, role family, seniority, and title when VeilStrat can resolve them. It is a BASE signal: written from external job data, not computed from other VeilStrat rows.
Under the hood, many raw openings can share a cleaned title and location. Consolidation collapses those into a single scored row so listings, This Week, slices, and company sheets all read the same store without double-counting noise.
- Depth scoring runs on the consolidated group, not every raw post
- Jobs already covered by an existing hiring snapshot are not written again
- After a Hiring write, the same process recomputes Tool adoption and Hiring velocity
Signature story
Consolidation theater + depth gate
Three raw openings with the same cleaned title and location become one hiring signal — only after depth clears the bar.
Many posts → one row
Consolidation
ML EngineerSF · Remote
ML EngineerSF · Remote
ML EngineerSF · Remote
same title + location →
Hiring · ML Engineer
3 openings · depth 4 · conf 75
Depth ladder → confidence
D5
100
D4
75
D3
50
D2
20
D0–1—
Depth 0–1 never becomes a signal
Downstream cascade after a Hiring write
Tools refreshVelocity refreshMay feed Funding+AIWeb priority
How it forms
From job ingest to a scored timeline row
Hiring is a BASE signal — written from live job data via scheduled company/global pulls and event-driven pulls when other signals suggest urgency.
- 1
Pull openings
Job data arrives from the hiring source (Fantastic / Bedrock pipeline). Scheduled and event-driven company pulls keep the graph fresh when funding or web activity suggests urgency.
- 2
Classify and consolidate
Titles are classified into role families. Openings that share the same company, cleaned title, and location collapse into one group before scoring — so volume on the board does not equal volume on the timeline.
- 3
Depth score the group
An LLM depth pass scores the group on AI relevance. Depth 0–1 never becomes a signal. Depth 2–5 ships with a mapped confidence score and human-readable label.
- 4
Write the row and fan out
A label and snapshot (including the job ids in the group) land on the company timeline. The same process then refreshes Tools and Velocity and may contribute evidence toward Funding + AI.
Confidence
Scored from depth at write time
Hiring confidence maps directly from the depth ladder at write time. Higher depth means a stronger, more AI-relevant opening group — not a black-box intent score refreshed quarterly.
BandConfidenceNote
- Depth 220Qualifies as a signal
- Depth 350Clear AI-relevant role group
- Depth 475Strong AI hiring evidence
- Depth 5100Highest depth band
- Depth 0–1—No signal written
Stock vs flow
Hiring signals vs static headcount lists
Traditional databases sell stock — contacts and firmographics refreshed on a schedule. Hiring signals sell flow: timed, consolidated, depth-gated events you can act on the same week.
Layer
Traditional
VeilStrat
Source
Where the fact comes from
Stale job boards & scraped lists
Often weeks behind openings that matter
Live hiring ingest + classification
Scheduled and event-driven company pulls
Unit of truth
What you count
Every job post as a separate ping
Noise looks like pipeline
One row per title + location group
Consolidation before the timeline write
Quality gate
What ships
Any “AI” keyword in a title
False positives clog outreach
Depth 2–5 or nothing
Depth 0–1 never becomes a signal
Downstream
What happens next
Ends in a spreadsheet cell
No computed follow-ons
Refreshes Tools & Velocity
May feed Funding + AI composition
Source
Where the fact comes from
Traditional
Stale job boards & scraped lists
Often weeks behind openings that matter
VeilStrat
Live hiring ingest + classification
Scheduled and event-driven company pulls
Unit of truth
What you count
Traditional
Every job post as a separate ping
Noise looks like pipeline
VeilStrat
One row per title + location group
Consolidation before the timeline write
Quality gate
What ships
Traditional
Any “AI” keyword in a title
False positives clog outreach
VeilStrat
Depth 2–5 or nothing
Depth 0–1 never becomes a signal
Downstream
What happens next
Traditional
Ends in a spreadsheet cell
No computed follow-ons
VeilStrat
Refreshes Tools & Velocity
May feed Funding + AI composition
Example snapshots
What a Hiring row looks like on the timeline
Illustrative labels — real product rows include confidence, patterns, and a snapshot of the underlying job ids.
Consolidated group
Hiring · ML Engineer (SF · Remote)
Three openings sharing the same cleaned title and location collapsed into one depth-4 signal.
Depth 4 · Confidence 75 · 3 job ids in snapshot
Senior AI seat
Hiring · Head of AI Platform
Seniority and role family resolved; depth gate cleared after classification.
Depth 5 · Confidence 100 · Feeds velocity window
No ship
Depth 1 group discarded
Openings that never clear depth 2 do not become timeline rows — the store stays clean.
Depth 0–1 · No signal written
GTM moments
Roles before vendors
Use Hiring when you need companies investing in AI seats — not another firmographic filter.
Pipeline
Fill lists with in-market AI hiring
Surface accounts opening ML, AI platform, and AI GTM seats before they show up on static intent databases.
Timing
Reach teams mid-build
Act when seats open — the same week the signal fires — instead of waiting for quarterly headcount refreshes.
Personalization
Lead with the role, not a pitch deck
Labels and snapshots give reps the exact role family and title angle for the first touch.
Cascade
Unlock Tools and Velocity
Every Hiring write refreshes computed follow-ons so stack motion and acceleration stay in sync.
Consolidation
Many job posts → one hiring signal
Openings that share the same company, cleaned title, and location collapse into a single row. Jobs already covered by an existing hiring snapshot are not written again. Depth scoring runs on the group — not on every raw post — so “3 hiring signals” on a company is not the same as “3 job posts.” That consolidation is why slices and This Week stay readable.
Related signals
How this connects on the timeline
Roles before vendors — explore the signals that feed or follow this type.
FAQ
Hiring signals, answered
How consolidation, depth, and downstream recomputes work for Hiring.
A Hiring signal is one scored timeline row for an AI-relevant (or depth-qualified) job opening group. It includes a human-readable label, a confidence score from 0–100, optional patterns, and a snapshot that retains the underlying job ids.
Catch AI hiringthe day the seats open.
Hiring signals land scored on company timelines — consolidated, depth-gated, and ready for This Week and your slices.
© 2026 VeilStrat. All rights reserved.All systems operational