LinkedIn Headcount Monitor - Growth & Hiring Signals

"They claim they are scaling. Are they hiring, or just posting jobs?"

An open job posting costs nothing to advertise. Headcount is the number that cannot be faked. B2B sales teams, recruiters, and equity analysts need to track headcount changes and hiring speed across companies over time to spot true expansion signals.

Track headcount trends and open role ratios over time to separate real expansion from a busy careers page.

⬇️ Input

Input takes a list of LinkedIn company slugs (for example google or microsoft). All input parameters carry working prefilled defaults so runs execute immediately without required inputs.

{
  "companies": [
    "google",
    "microsoft"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "maxItems": 100
}

Input Field Specification

Field	Type	Description	Default
companies	Array	List of LinkedIn company URL slugs to monitor.	["google"]
proxyConfiguration	Object	Proxy settings to rotate IPs per request and prevent rate limits.	{ "useApifyProxy": true }
maxItems	Integer	Maximum number of company profiles to fetch in a single run.	100

⬆️ Output

Outputs structured records directly to the default dataset. Each row describes a single company indexed by its stable per-row identifier (companySlug).

Output Field Schema

Field Name	Type	Description
companySlug	String	LinkedIn company URL slug. Stable per-row identifier.
companyName	String	Official company name as displayed on LinkedIn.
companyUrl	String	Canonical LinkedIn company page URL.
employeeCount	Integer	Total employee headcount parsed from profile.
employeeCountText	String	Human-readable employee count text (e.g. "317,984 employees").
openJobsCount	Integer | Null	Active job openings count when available.
headcountTrend	Number | Null	Short-term headcount growth trend percentage.
headcountGrowth12m	Number | Null	Trailing 12-month headcount growth rate.
hiringRate	Number | Null	Monthly hiring rate metric.
netHeadcountChange	Integer | Null	Net employee count change between observations.
changedFields	Array | Null	Attributes modified since previous observation.
reason	String | Null	Explanation note when computed historical metrics return null on first observation.
scrapedAt	String	ISO 8601 timestamp of data collection.

Sample Output Record

{
  "companySlug": "google",
  "companyName": "Google",
  "companyUrl": "https://www.linkedin.com/company/google/",
  "employeeCount": 317984,
  "employeeCountText": "317,984 employees",
  "openJobsCount": null,
  "headcountTrend": null,
  "headcountGrowth12m": null,
  "hiringRate": null,
  "netHeadcountChange": null,
  "changedFields": null,
  "reason": "First observation; headcount trends and net changes require multi-run history accrued over time.",
  "scrapedAt": "2026-08-05T16:36:34.000Z"
}

How it works

1. Company Extraction: Fetches public LinkedIn company pages using HTTP requests.
2. Headcount Parsing: Extracts employee count numbers, official company titles, and canonical URL handles.
3. Time-Series Tracking: Accrues records over time to compute headcount growth rates, hiring rate, and net employee changes across consecutive runs.
4. Resilient Rate Budgeting: Works with proxy rotation to bypass rate limits and return unblocked data.

❓ FAQ

How is company headcount measured?

Employee count is extracted directly from verified LinkedIn company profile headers.

Why do headcountGrowth12m and netHeadcountChange return null on first run?

Trend and growth calculations require comparing observations across multiple runs over time. On the first run, the actor returns null with a clear reason field rather than fabricating unobserved past figures.

Does this actor require a LinkedIn login or session cookie?

No. The actor operates without login credentials or cookies.

💬 Your feedback

Need custom headcount reporting, specific sector filters, or dataset integrations? Contact us at reapxdev@proton.me or visit reapx.dev.

---

Unofficial - not affiliated with LinkedIn. Collects only data visible without logging in. reapx · reapx.dev · reapxdev@proton.me