Track Which Companies Are Hiring Again (2026)

TL;DR

The 2026 layoff wave dominated the headlines. The quieter, more useful signal is the rebound — which companies have started opening requisitions again, and which teams are growing. You can track that yourself by scraping a company's public careers page into a spreadsheet with ScrapeMaster, then re-snapshotting it each week to compare. It's point-and-click, exports to CSV/JSON, and stores everything locally. Be clear on what it is: a manual weekly snapshot tool, not a real-time alert service — and it only captures listings that are publicly visible and loaded on the page.

Layoff trackers look backward. This looks forward.

There's no shortage of layoff trackers. They tell you who cut jobs — useful, but it's a rear-view mirror. If you're a job-seeker deciding where to apply, a recruiter deciding where to source, or an analyst mapping the market, the more valuable question is: who's hiring again, and where?

That signal shows up on companies' own careers pages before it shows up anywhere else:

• New requisitions appearing after a hiring freeze.
• Headcount growing on a specific team — five new backend reqs in a month says something the press release doesn't.
• Roles reopening that were pulled during the downturn.
• Geographic shifts — reqs moving from one region to another.

You don't need a data vendor to see this. You need a weekly snapshot of the pages you care about, in a format you can diff.

The method: snapshot, spreadsheet, repeat

The workflow is deliberately simple, and it's the honest version of "monitoring" — you, on a schedule, taking snapshots.

1. Build your watchlist. Pick 15–40 companies whose public careers or jobs pages you want to track. Bookmark the actual listings page for each.
2. Scrape each page into rows. Open the careers page, click a job title, and let ScrapeMaster auto-detect the other similar listings on the page. It pulls the visible fields — title, team/department, location, date if shown — into a table.
3. Export to CSV or JSON and drop it into a spreadsheet, tagged with the company name and the date you captured it.
4. Re-run weekly. Same companies, same day each week. Now you have week-over-week snapshots.
5. Diff the snapshots. New rows this week = new reqs. A company that went from 2 open roles to 14 is a rebound signal. A team that keeps adding reqs is where the growth is.

Over a few weeks this becomes a genuine hiring-signal dataset you built yourself, for free, with nothing leaving your machine.

What ScrapeMaster actually does here

• Point-and-click visual selection — you click one job listing, no CSS or code.
• Auto-detect similar items — one structure-detection pass finds the rest of the listings that match.
• Exports CSV/JSON — straight into your spreadsheet or notebook.
• Local IndexedDB storage — your captures live in your browser, not on someone's server.

If you've never scraped before, our walkthrough on how to scrape a website without coding covers the basics of point-and-click extraction.

Be honest about the limits (we are)

This is a snapshot tool, and we'd rather you know its edges up front than be surprised later.

• Manual weekly snapshots, not real-time alerts. ScrapeMaster does not run scheduled or automatic scrapes and does not watch a page for changes. You re-run it. The weekly cadence is a habit, not a background service.
• It captures only what's visible and loaded. If listings are paginated or lazy-loaded, scroll and load them first — the tool extracts the data that's actually on the page at capture time.
• It's blockable on hard sites. ScrapeMaster does not rotate proxies or fingerprints, so aggressively defended sites (LinkedIn, Cloudflare-hardened careers portals) can and do block it. It shines on straightforward public careers pages, less so on fortified ones.
• It won't get past logins, paywalls, or CAPTCHAs, and there's no email database or contact-enrichment bolted on. It scrapes the public page in front of you.
• Respect each site's terms of service and robots rules. Scrape public listing data for your own research at a reasonable cadence; don't hammer a site or use it in ways its ToS forbids. This isn't legal advice — if you're doing this commercially or at scale, check the site's terms and get your own counsel. Our guide to whether scraping is legal in 2026 is a useful primer on the landscape.

Setting up your rebound spreadsheet

The dataset is only as good as its structure. A simple layout that stays diff-able:

• Column A: capture date — the date you ran the scrape (not the date the job was posted).
• Column B: company — so you can filter and pivot.
• Column C: job title.
• Column D: team / department — the field that reveals where growth is happening.
• Column E: location.
• Column F: posted date — only if the page shows it.

Each week, you append a fresh block of rows with that week's date. Do not overwrite last week — the whole point is to keep the history so you can compare. After a few weeks you can build a pivot table of open-role count by company by week, and the rebound stories jump out: the company that climbed from 3 to 17, the team that added a req every single week.

Signals worth watching

• Net new reqs week over week. The single clearest rebound indicator.
• Team concentration. Ten new reqs spread across ten teams is broad growth; ten on one team is a specific build-out you can act on.
• Reopened roles. A title that disappeared during the freeze and came back signals confidence returning.
• Seniority mix. A shift toward senior/leadership reqs often precedes a bigger team expansion underneath them.
• Location moves. Reqs migrating between regions can flag a strategic relocation before it's announced.

A weekly routine that actually sticks

The failure mode here isn't the tool — it's forgetting to run it. Make it a 20-minute Friday ritual:

1. Open your watchlist bookmarks folder.
2. For each careers page: scroll to load all listings, click one job, let ScrapeMaster auto-detect the rest, export CSV.
3. Paste into the master spreadsheet, stamped with today's date.
4. Glance at the week-over-week counts and jot one line of notes.

Because there's no automation running in the background, the discipline is yours — but 20 minutes a week for a proprietary hiring-signal dataset is a good trade.

Comparison: ways to track hiring rebound

Manually eyeballing pages works — but by week three you won't remember what last week looked like. The spreadsheet is what turns "I think they're hiring more" into "they went from 3 to 17 open roles, mostly on the data team."

When a careers page fights back

Not every careers page cooperates, and it's worth knowing the patterns before you hit them:

• Embedded ATS widgets. Many companies render jobs through Greenhouse, Lever, Workday, or Ashby embeds. Often the listings still show up as normal page elements you can point-and-click; sometimes they load inside an iframe or via a delayed API call. Scroll and give the page a moment to fully render before selecting.
• Infinite scroll and "load more" buttons. ScrapeMaster extracts what's loaded, so click through "load more" or scroll to the bottom until every listing is on the page first.
• Heavy anti-bot defenses. On Cloudflare-hardened portals or LinkedIn, expect to be blocked — ScrapeMaster doesn't rotate proxies or fingerprints, and that's by design, not a bug. For those, fall back to eyeballing or find the company's direct ATS URL, which is often less defended than the LinkedIn mirror.

The pragmatic move: build your watchlist around companies whose careers pages are straightforward public HTML. You'll get clean weekly data with almost no friction, and skip the handful of fortified sites that would eat your time.

Turning the data into decisions

A spreadsheet of reqs is raw material. What you do with it depends on who you are:

• As a job-seeker, sort by the teams and locations that fit you, then apply the week a relevant req first appears — early applicants get seen before the pile grows.
• As a recruiter, spot companies staffing up a function and reach out to passive candidates there, or pitch the company itself before your competitors notice the momentum.
• As an analyst, chart open-role counts over time as a leading indicator; a sustained climb across a sector is a rebound story you can quantify rather than assert.

Who this is for

• Job-seekers — apply to companies on the way up, not the way down, and time your applications to when reqs actually open.
• Recruiters and sourcers — spot which companies are staffing up a function before your competitors do.
• Market and equity analysts — hiring velocity on the careers page is a leading indicator that lands before the earnings call.

If part of your job hunt is also saving the listings you find so they don't vanish, that's a different tool — a PDF converter — and we cover it in save job listings as PDF during layoffs.

And if your research means watching a pile of long recruiter webinars or company all-hands recordings, our sibling extension CineMan AI turns video into readable notes so you can skim the substance.

Frequently asked questions

Does ScrapeMaster automatically check careers pages for me?

No. It takes manual snapshots when you run it. The "weekly monitoring" is a habit you keep — you re-scrape the same pages on the same day. There are no scheduled or automatic scrapes.

Will it work on any company's careers page?

It works well on straightforward public careers and jobs pages. It does not rotate proxies or fingerprints, so sites with heavy anti-bot defenses (LinkedIn, some Cloudflare-hardened portals) may block it. It also can't get past logins, paywalls, or CAPTCHAs.

How do I turn snapshots into a rebound signal?

Export each week's scrape to CSV with the company name and date, then compare week over week. New rows are new reqs; a jump in count or a team repeatedly adding roles is your rebound signal.

Where is my scraped data stored?

Locally, in your browser's IndexedDB. Your captures aren't uploaded to a server. You export to CSV or JSON whenever you want to work with the data.

Can it get past a "sign in to see jobs" wall?

No. ScrapeMaster only extracts data that's publicly visible and loaded on the page. If a listing requires login to view, it's out of reach.

Is it legal to scrape careers pages?

Scraping publicly visible listing data for your own research is generally lower-risk, but it depends on the site's terms of service and how you use the data. Respect robots rules and reasonable rates. This isn't legal advice — for commercial or large-scale use, check the site's ToS and consult your own counsel.

How many companies can I realistically track this way?

A watchlist of 15–40 companies is very manageable as a weekly routine. Beyond that the manual re-scraping starts to take real time, since there's no automation doing it for you.

Bottom line

The layoff story is over-told. The rebound story — who's opening reqs again and where teams are growing — is sitting in plain sight on public careers pages, and you can turn it into your own weekly dataset for free. ScrapeMaster does the point-and-click extraction and CSV export; you supply the weekly habit and the spreadsheet. Just keep it honest: manual snapshots, visible data only, and respect each site's terms. More on the tool page.