A client asks whether you can find five senior revenue operations people in Austin at $130,000. You say yes, because saying no loses the deal. Three weeks later you have two maybes, one of whom wants $165,000, and a conversation about why the search is taking so long.
That gap is what talent mapping is supposed to close. The problem is that if you go looking for how to do it, page one of Google hands you two different disciplines under one name and never tells you which one you are reading.
Paychex, Rippling, Oyster HR and Indeed all define talent mapping as assessing your existing workforce: skills inventories, succession planning, the nine-box grid. Metaview, SocialTalent and Recruiterflow define it as scoping the outside candidate market before a role opens. Both definitions are legitimate. They describe completely different work, done by different people, using different data, to answer different questions.
Call them the workforce map and the market map. A workforce map looks inward and asks who you already have and who could grow into what. It belongs to HR and people development. A market map looks outward and asks who exists, where, at what price, and how reachable they are. It belongs to whoever has to actually fill the role.
If you are a recruiter, you want the market map. The rest of this is about that one.
What separates a market map from sourcing
They run on the same raw material and they are not the same activity. Sourcing is a search for named people you intend to contact for a specific opening. A market map is a description of a population, built before you commit to anything, and its output is not a list of names.
The output of a market map is a set of numbers and boundaries you can defend in a conversation. How many people plausibly exist. Which cities hold them. What the market is actually paying. Whether the search you just agreed to is easy, hard, or impossible at the budget on the table.
That is why mapping happens before sourcing rather than instead of it, and why it changes what you commit to. Our guide to candidate sourcing covers the find-and-contact work that follows; the split between sourcing and recruiting covers where each ends. A map is the thing you build so that the intake meeting is a negotiation rather than an agreement to whatever the hiring manager wants.
The five questions a market map has to answer
Most published talent mapping guides give you a process with steps and no outputs. Steps are easy to write and impossible to check. A map is finished when it answers these five things, and unfinished when it does not.
| Question | What you need | What it changes |
|---|---|---|
| Size | How many people can plausibly do this role, in the geography you are searching | Whether the role is fillable at all, and whether "we need three of these" is realistic |
| Shape | How that pool splits by seniority and adjacent background | Whether you are competing for a scarce senior tier or fishing in a crowded mid-level one |
| Price | What the market pays for the skills you listed, from job postings rather than salary surveys | Whether the budget is real, and which requirement is the expensive one |
| Competition | Who else is hiring the same profile, and how fast openings close | Your speed target, and how much slack your process actually has |
| Reachability | How much of the pool is realistically approachable rather than merely countable | The difference between a pool that exists and a pool you can hire from |
Size without shape is the classic trap. "There are 327,000 of these people in the US" is a comforting number that tells you almost nothing, because the question was never whether the population exists. It was whether the specific slice you need exists at your price, near your office, and available to talk this quarter. The next section shows what happens when you check.
What a finished map looks like
Concrete beats abstract, so here is a map of a market you already know from the inside: US recruiting itself, using our own 2026 posting and profile data.
On size it looks like the easiest market in the world. There are 327,487 recruiting professionals against 6,836 active postings, which is roughly 48 candidates per vacancy. Compare that with revenue operations, where the same measure is 21.8. Recruiting has more than twice the apparent slack.
On shape that reading falls apart. Specialists are 70.6 percent of the recruiting pool, experts 20.3 percent, leaders 7.1 percent, and entry level 2.0 percent. That last figure is 6,547 people in the entire country. An occupation that spends all day hiring has almost no measured junior supply of its own, and the competition data agrees: campus and early-careers roles stay open longest of any recruiting specialization at 12 days, while talent sourcer roles close fastest at 7 days against an average of 9.3.
So the market with 48 candidates per opening is the market where the junior hire takes longest. Size told you the wrong thing. Shape told you the truth.
On price the median is $72,800 across 7,212 postings, of which 41.2 percent disclose a range. The spread by specialization is where the money is: technical recruiters at $114,400 down to staffing and agency recruiters at $50,000, a spread of about 129 percent, and the seniority ladder runs $49,000 at entry to $170,000 at leader. Note that the ladder is steeper than the specialization spread, which means moving up a tier is worth more than switching what you recruit for.
Skill premiums are the part that reprices a job description. AI sourcing carries a 32 percent premium, recruitment analytics 23.4 percent and talent intelligence 21 percent. The familiar tool skills pay less: LinkedIn Recruiter 15.1 percent, Boolean search 13.4 percent, Workday recruiting 7.8 percent. Employers are paying for the analytical layer above the tooling, not for fluency in one product. If a client wants a data-literate recruiter at the median, the map says no on day one instead of week four.
Then a warning the data itself hands you. Washington is the top-paying state at $79,000, but Seattle at $80,000 trails San Francisco at $91,000 by eleven thousand dollars. A state figure pools metro and non-metro postings in different proportions from one state to the next, so "top-paying state" and "where the money is" are not the same claim. Use the city cut when you are talking about a specific search.
Now take the original question, the client wanting five senior people in Austin at $130,000. A map lets you answer with something better than yes: the national pool supports the volume, the seniority skew makes five senior hires at once the hard part rather than the salary, Austin's median sits below the coastal metros so the budget travels further there, and if data or automation skills are on the must-have list the number moves. That is a different conversation, and you can have it before you sign.
Why one quarter's ratio is not a plan
Here is the part the vendor guides leave out, and we have the receipts on it from our own reporting.
Supply and demand ratios are less stable than they look. When we re-ran the same industry and geography for a banking report with only about 8 percent more posting data, the supply and demand ratio moved from 115.2 to 89.1, a 23 percent swing. The top-paying state changed. The headline role changed. The top skill premium changed from one metric to a different one entirely. Nothing about the actual labor market moved that much in a few weeks. The estimate moved.
Two rules follow, and they apply to any market data you use, ours included.
Treat a ratio as a band, not a number. "Roughly 20 candidates per opening" is a defensible statement. "21.8 candidates per opening" quoted to a client as a precise fact is a hostage you are handing them. The direction and rough magnitude are the signal; the decimal is noise.
And weight the metrics by how stable they are. Pool size and seniority shape move slowly and are safe to plan on. Posting-derived medians and skill premiums are steadier than they look because they aggregate a lot of listings. Single-cut leaderboards, the top state or the top skill in one quarter, are the least stable thing on any market report and the most tempting thing to quote. Use them for orientation, never for a commitment.
How often to redo it
For an active search, the map is a pre-search artifact and it has a shelf life of that search. For a role you hire repeatedly, quarterly is the right cadence, because that is roughly the rate at which posting medians and vacancy counts move enough to change a decision.
The thing that actually goes stale fastest is not the population, it is the competition. Pool size and pay bands drift over quarters. How many companies are hiring the same profile, and how fast their openings close, can change inside a month. If you refresh one number before a kickoff, refresh that one.
Four ways maps go wrong
The most common failure is mapping the job description instead of the market. You take the requirements list as given, count how many people match all of it, find a small number, and report scarcity. What you have measured is the job description, not the talent market. A useful map tests requirements against the data and comes back with which one is doing the damage.
Second, counting people who are not reachable. A population figure pulled from profile data includes people who have been in a role for eight months, people at companies nobody leaves, and people whose compensation is already above your band. Countable and hirable are different sets, and the gap between them is where optimistic timelines come from.
Third, mapping titles rather than capabilities. Title-based counting misses the people who do the work under a different name, which in newer functions is most of them. Revenue operations is a good example: the same work appears as sales ops, marketing ops, GTM engineering and business operations depending on who wrote the org chart.
Fourth, building the map and never using it in the conversation it was built for. A map that does not change what you commit to at intake is a document, not a decision.
Where Glozo fits
Answering the five questions used to mean assembling them from four sources: a salary survey for price, a job board for competition, LinkedIn for population, and guesswork for reachability. That is why most recruiters skip mapping and go straight to sourcing.
Glozo Intelligence exists to answer size, shape, price and competition off one dataset: talent supply and demand, posting-derived pay benchmarks by seniority and geography, and market trends, built from more than 10 million market signals a month. Our published market reports are the same data in fixed form, and the US recruiting market report is where every figure in the worked example above comes from. Read it as a template as much as a data source: it is a market map for one occupation, laid out the way one should be.
Reachability is the one the market has been worst at, and it is where Smart Search does the work: profiles from more than 30 sources, ordered by how closely they match what the role actually needs, with a market compensation estimate and a signal for who looks open to a move. That last pair is what turns a population count into a pool you can actually hire from, before you spend anything contacting people.
The map is still yours to interpret. Data narrows the argument; it does not settle what the client should do.