Field Guide 01 · Deep Dive
Step 06 — Assess movability › Execution detail

Reading layoff & movability signals

A pool only counts if people will move. This is how you find out — the exact signals, where they live, how to read them with AI, and how to put the whole sweep on autopilot.

AWhat a movability signal actually is

Two tiers. Hard signals are verifiable and public — they hold up in a leadership room. Soft signals are sentiment and chatter — earlier, noisier, and only trustworthy when they corroborate something hard.

Hard signals — verifiable, public
SignalWhere it livesWhat it tells you
WARN Act noticesDOL / state WARN databasesUS employers (100+ staff) must file 60-day notice for mass layoffs. The most underused signal there is — names the site and headcount.
Layoff tracker entrieslayoffs.fyiCompany, date, count, % of workforce for tech layoffs. Fast aggregation, good for trend.
SEC 8-K filingsSEC EDGARPublic companies disclose material restructuring and RIFs. Dry but authoritative.
Earnings-call languagetranscripts, IR pages"Cost discipline," hiring freeze, headcount guidance — leading indicators before formal cuts.
Posting-volume dropLightcast / LinkedIn over timeA sudden fall in a company's active reqs signals a freeze before any announcement.
Funding distressCrunchbase / PitchBookDown rounds, bridge rounds, a missed raise — layoffs at startups usually follow within a quarter.
Soft signals — sentiment & social
SignalWhere it livesWhat it tells you
Anonymous employee chatterTeamBlindLayoff rumors in tech and semi often surface here first, in company-specific channels. Early but unverified.
Community threadsr/chipdesign, r/ECE, r/layoffsAffected-team detail, severance terms, timeline. Mixes real reports with speculation.
Review velocity + sentimentGlassdoorA spike in negative reviews, "layoffs" mentions, or falling CEO approval is a morale and movability tell.
Open-to-work surgeLinkedInA cluster of #opentowork badges or "impacted" posts among one company's alumni = a wave just happened.
Company-specific forumsTheLayoff.comDedicated per-company layoff discussion. Noisy, but sometimes ahead of the news cycle.
Comp erosionLevels.fyiRSU refresh cuts, downward comp drift, frozen bands — quiet signals that people are getting restless.
Semiconductor-specific layer

Semis are cyclical, so movability moves with the industry, not just the company. Watch fab utilization rates and capex cuts in earnings, inventory-correction cycles (SEMI, DigiTimes, EE Times), and named restructurings (Intel, GlobalFoundries, the memory makers). A downturn can make a normally locked-in analog or process-integration pool suddenly movable across the whole sector at once.

BThe source map — where to actually look

Free and public first. You can run a credible sweep without spending a dollar; paid tools just make it faster and broader.

Free · tracker
Best for: fast trend and confirmation of tech cuts at a named company.
Free · official
Best for: hard, site-level proof of mass layoffs. Search "[state] WARN notices."
Free · official
Best for: restructuring disclosures from public companies. Search 8-K filings.
Free · social
Best for: earliest rumor signal. Treat as a lead, never as proof.
Free · social
Best for: affected-team and severance detail. Function-specific subs beat general ones.
Free · review
Best for: sentiment trend and morale shift over time.
Paid · platform
Best for: posting-volume trends and supply movement at scale.
Paid · listening
Best for: social listening across forums at volume, for a real TI function.
CUsing AI to read the signal

AI does three jobs here: real-time sentiment sweeping, multi-source hard-signal compiling, and synthesizing messy forum threads into clean intelligence. Different jobs want different tools.

Real-time sweep. Live X/Twitter access makes it strong for "what's being said right now" about a company's cuts.
Sourced compile. Aggregates recent news and filings with citations — good for the hard-signal pass.
Synthesis. Best at turning pasted forum threads into a credibility-rated read.
Prompt 1 · Real-time sentiment sweep (Grok)
Search X for posts from the last 30 days about [COMPANY] related to:
layoffs, restructuring, hiring freeze, RIF, reorg, or team cuts.

Tell me:
1. Volume of relevant chatter (rough count + trend vs. prior month)
2. Overall sentiment and whether it's shifting
3. Any specifics on which teams/functions are affected
   (I care most about [RF / analog / silicon design] roles)
4. Credibility flag: separate apparent-employee posts from
   outside speculation or news amplification

Be concise. Lead with whether there's a real signal here or just noise.
Prompt 2 · Hard-signal compile (Perplexity / web search)
Compile verifiable layoff and restructuring signals for [COMPANY]
from the last 6 months. For each, give source, date, and a one-line summary:

- WARN Act notices (check the relevant state databases)
- layoffs.fyi entries
- SEC 8-K filings mentioning restructuring or workforce reduction
- Earnings-call language on cost reduction, hiring freezes, or headcount
- Major news coverage of site or fab closures and reorgs

End with: a net read on whether [COMPANY]'s [target function]
talent is becoming more movable, and how confident the public record makes you.
Prompt 3 · Forum synthesis (paste threads in)
Below are forum threads about [COMPANY] from Blind / Reddit / TheLayoff.
Analyze them and extract:

1. Specific layoff signals (dates, teams, scale)
2. Which functions and levels appear affected
3. Timeline — is this rumor, announced, or already done?
4. Credibility per claim — rate each on specificity and corroboration
5. What I should verify against hard sources before acting

Ignore generic venting. I only want signal.

[PASTE THREADS HERE]
DHow to automate the sweep

Three tiers. Start at Tier 1 — it takes thirty minutes a week and covers most of the value. Move up only when monitoring more companies makes the manual version painful.

1~30 min / wk
Manual + AI assist
start here
  • Google Alerts on "[company] layoffs" and "[company] restructuring"
  • Weekly five-minute check of layoffs.fyi and the company's TheLayoff page
  • A saved LinkedIn search for target-company alumni flagged #opentowork
  • Run Prompt 2 weekly; paste any forum threads into Prompt 3
2~1–2 hr setup
Semi-automated
scales to ~10–20 companies
  • A Zapier or Make flow: Google Alert RSS → AI summarizer → Google Sheet or Slack
  • One RSS feed aggregating news + layoff trackers per watched company
  • A scheduled AI sweep — same prompt, run on a weekly cadence automatically
  • Output lands in a shared movability watchlist you skim, not rebuild
3eng support
Programmatic pipeline
for a real TI function
  • Web-search / news APIs (Tavily, Exa, GDELT, NewsAPI) pull on a schedule
  • An AI synthesis layer scores each signal and writes the digest
  • Licensed social listening (Brandwatch, Talkwalker, Meltwater) for forum coverage at scale
  • A weekly scored digest auto-delivered to the team — zero manual collection
Trigger
Alerts, trackers, saved searches
Collect
RSS / search APIs pull sources
Synthesize
AI scores + summarizes
Deliver
Digest to sheet or Slack
EGuardrails
Read before you build the pipeline
!Respect terms of service. LinkedIn, Glassdoor, and Blind prohibit scraping. Use official APIs, manual review, or licensed listening tools — not rogue scrapers.
!Triangulate before you act. Never move on a single forum rumor. A soft signal only earns weight when a hard signal corroborates it.
!Company-level, not surveillance. This is about org movability and market conditions, not tracking named individuals. Keep it aggregate.
!Date-stamp everything. Movability signals decay fast. A six-week-old layoff read is already stale — note the date on every source.