Before anyone opens a req, answer the only question that matters: can we actually find this person, and at what cost? A supply snapshot turns "let's try" into a defensible yes, stretch, or no.
Reach for a supply snapshot whenever a hiring decision hinges on whether the talent even exists. It is feasibility analysis, not sourcing.
A hiring manager wants to open a role and you need to know if it is realistically fillable before committing.
The req has a comp band, location, and skills combo that may not exist together in the market. You need leverage to push back.
Leadership is weighing a new site or team build-out and wants to know if a metro can actually support it.
You have ten open reqs and limited time. The snapshot tells you which ones are hard and deserve a head start.
Strip the wishlist down to the 3 to 5 skills a person genuinely cannot do the job without. The job description's "nice to haves" artificially shrink the pool and make every role look impossible.
Count how many people match the core profile in your target geography. This is your raw supply number. Pull it from your labor market platform and sanity-check against LinkedIn.
Find where the pool clusters. Scarce skills concentrate in a handful of hubs, which changes everything about location strategy and relocation expectations.
A pool of 2,000 means nothing if 80 companies are hiring the same profile. Pull active posting volume and the named competitors going after this talent. Demand intensity is the difference between "available" and "winnable."
What does the market actually pay for this profile in these metros? Compare against the req's band. A pool can be plentiful and still unwinnable if your comp is two tiers below market.
A big pool of happy, long-tenured people is not a real pool. Look at tenure patterns, recent layoff signals, and how often this profile changes jobs. Movability turns raw supply into addressable supply.
Collapse everything into one call — feasible, stretch, or unrealistic — backed by a single headline number and the levers that change the math. The hiring manager should not have to interpret a spreadsheet.
A strong snapshot is one page, leads with a verdict, and earns trust by sourcing every number. If the reader has to scroll, you over-built it.
Leads with the verdict — feasible, stretch, or unrealistic in the first line, before any data.
One headline number — the single stat that frames the whole picture.
Shows the levers — if you flex location the pool grows by X; if you flex comp the competition drops by Y.
Every number is sourced — platform and date noted, so it survives scrutiny in a leadership room.
~2,400 senior RF/mmWave engineers in the US · 60% concentrated in 3 metros · 14 companies actively hiring the profile · market comp runs 25% above the current band. Levers: open the role to hybrid in San Diego (+40% pool) or lift the band to market (drops you from 6th to 2nd most competitive offer).
Using the job description's full wishlist as your search criteria, which makes nearly every role look unfillable.
Always size against the true must-haves first. Layer the nice-to-haves on only to show how much they cost you in pool size.
Reporting a raw supply count with no demand context — "there are 2,000 candidates" — as if availability equals winnability.
Always pair supply with demand intensity. The ratio of available talent to competing employers is the real story.
Dumping data and leaving the hiring manager to interpret it. No verdict, no recommendation, no levers.
Lead with a call. Your credibility comes from the judgment, not the data pull. The data backs the verdict; it is not the deliverable.
Fill this in as you work the seven steps. By the time the last row is done, your snapshot is written.