Healthcare Recruitment Demand — Facilities Hiring with Urgency Signals

Built for Mehdi 🇲🇦 (SSM) by Saad Belcaid.

Find US healthcare facilities hiring with demand-signal urgency — repost frequency, hiring surges, multi-location duplicates, traveler/locum/per-diem language, and expansion signals (new clinics, openings).

If you sell to healthcare facilities (CRO services, staffing, lab equipment, EMR/software, regulatory consulting, recruitment) — these are the facilities to call this week, ranked by how badly they need help.

---

The dumb-simple version

A hospital posting one nurse job is normal. A hospital posting 15 nursing jobs across 4 locations with "$10K sign-on bonus" language and one of those jobs has been open 60 days — that's a hospital in pain. Pain = budget. Budget = buying signal.

This scraper reads thousands of healthcare job postings and tags each one across 5 demand-signal axes:

1. Urgency tier — fresh (just posted) → critical (30+ days, can't fill)
2. Hiring surge — count of OTHER openings the same employer has posted
3. Multi-location score — same role × distinct locations under same employer
4. Urgency language — "stat", "traveler", "locum", "per diem", "$X sign-on bonus", "immediate hire"
5. Expansion language — "new clinic", "grand opening", "newly built", "new location"

The signal sentence per row reads like: "Valley Spring Behavior Health (hospital) hiring psychiatry (Child & Adolescent Psychiatry Position) — open 60+ days, can't fill; 4 parallel openings at this employer; sign-on bonus; new clinic". CRM-ready.

---

Volume

The default run pulls ~1,500 healthcare job postings in 5–10 minutes. The source has 3,750+ active listings — bump maxJobs to 3000+ if you want the full universe.

---

Max-value playbook

Day 1 — first run, get volume

maxJobs: 1500
maxPages: 80
minUrgencyTier: "fresh"

Hit run. Wait ~5–10 min. Expect 1,000–1,500 rows.

Day 1, hour 2 — triage by who you sell to

Open the dataset. Filter by:

If you sell...	Filter by
Locum/travel staffing	urgency_language contains "locum" or "traveler" or "per diem"
Permanent placement (recruiters)	urgency_tier = critical AND surge_score >= 3 (employer is stuck and is paying)
Sign-on bonus competition (recruiters)	urgency_language contains "sign-on bonus" — they're paying premium = budget exists
Multi-site healthcare orgs (CROs, EMR, group purchasing)	multi_location_score >= 3 — same role × 3+ locations = real org, real budget
New facility build-outs (equipment, IT, design, consulting)	expansion_language is non-empty — they just built or are about to open
Specialty-specific	specialty = "oncology" (or cardiology, ortho, ED, etc.)
Facility-type-specific	facility_type = "urgent_care" (or hospital, clinic, surgery_center, nursing_home)

Day 2 onwards — daily drip

Schedule cron 0 8 * * 1-5 (8am UTC, Mon-Fri) with maxJobs: 500. Each weekday pulls fresh signals. Built for "build once, run daily, never come back."

---

Filter recipes (copy-paste)

"Just give me the desperate ones"

minUrgencyTier: "critical"
requireSurge: true

"Travel/locum agencies — hot leads"

requireUrgencyLanguage: true
roleFunctions: ["physician", "nurse"]

"New facility openings (sell equipment, EMR, build-out)"

requireExpansionLanguage: true

"Multi-site health systems"

requireMultiLocation: true

"Oncology hiring (sell to cancer centers)"

specialties: ["oncology"]

---

Output — one row per healthcare hiring signal

Field	Example
job_title	Cardiology Opening in Elkin, NC
company_name	Archway Physician Recruitment
facility_type	hospital / clinic / urgent_care / nursing_home / surgery_center / rehab / home_health / telemedicine
role_function	physician / nurse / physician_assistant / nurse_practitioner / allied_health / admin_executive / tech_imaging / pharmacy / mental_health / dental
specialty	oncology / cardiology / orthopedic / pediatric / emergency / neurology / psychiatry / obgyn / radiology / anesthesia / family_medicine / internal_medicine / GI / endo / rheum / pulm / urology / derm / ophthal / pathology
location	Elkin, NC, US
date_posted	2025-09-13T...
days_listed	89
urgency_tier	fresh / normal / high / critical
surge_score	5 (this employer has 5 OTHER openings)
multi_location_score	3 (same role at 3 distinct locations)
urgency_language	["stat hire", "relocation package"]
expansion_language	["new clinic", "newly built"]
is_likely_repost	true (same employer posted near-identical title to same location before)
salary_text	$400,000–$500,000 / year
apply_url	direct link to apply
signal	"Archway Physician Recruitment (clinic) hiring cardiology (Cardiology Opening in Elkin, NC) — open 89+ days, can't fill; stat hire / relocation package"

---

Why each signal axis matters (in plain English)

Signal	What it tells you
surge_score >= 3	Employer has 3+ other openings = real growth or real attrition. Either way, they're staffing up and have budget.
multi_location_score >= 2	Same role at 2+ locations under same employer = multi-site organization. Bigger ticket sales.
urgency_language non-empty	Sign-on bonuses, traveler/locum, "stat", "immediate" = they're paying premium because regular hiring failed. They need help NOW.
expansion_language non-empty	"New clinic", "grand opening" = greenfield build = they're buying equipment, IT, services, contractors RIGHT NOW. Highest ticket-size signal.
is_likely_repost = true	Same role posted multiple times at the same location = previous hire fell through OR turnover problem. They will pay a premium recruiter to fix it.
urgency_tier = critical (30+ days open)	Job has been live a month or more = market clearance failed = they will entertain ANY conversation.

---

Architecture

• Apify Actor, TypeScript, pure HTTP (no Playwright needed for v1)
• Source: HospitalRecruiting.com — verified 3,750+ active US healthcare job postings, JSON-LD JobPosting on every detail page
• Cross-row aggregator computes surge / multi-location / repost scores AFTER all jobs are fetched
• Bounded concurrency (default 8) for fast detail-page fetching
• Polite delay (250ms default) — easy on the source

Costs

• Apify compute: ~5–10 min per run × 256 MB ≈ trivial CU
• No paid keys needed

---

Connector OS Station integration

Pipe the dataset into Station as the demand side. Each row's signal field plugs straight into the I Layer for evaluation against your supply network (staffing agencies, CROs, EMR vendors, healthcare IT, equipment, regulatory consultants).

Flow: scrape → dataset → paste dataset ID into Station → match against your supply → scored introductions.

---

Built by Saad Belcaid for Mehdi's SSM workflow. 🇲🇦