The Occupation-Demand Resume Build, From Labor Data to a Positioned Draft

You want a resume built for where the hiring actually is in your occupation, not for one posting and not for a generic list of trendy skills. This guide is for a job seeker who is willing to spend a few hours reading their whole occupation before they write a word, and it delivers a fixed eight-step sequence that turns public labor-market data and aggregate posting demand into a positioned draft. At each step you get a checkable output, so you always know whether the draft is done.

Most market-and-resume advice does one of two things: it scores a single dimension, or it walks one worked posting end to end. This is the whole build, sequenced. You read an entire occupation's demand across many postings plus public labor data, so the resume is aimed at the market rather than at a single ad.

What "occupation demand" means, and which sources publish it

Occupation demand is the combination of how many roles an occupation is projected to open, what they pay, and which skills those roles reward. No single page hands you all of it, so you read four public federal products plus one posting-derived layer and reconcile them.

Four US federal products anchor the labor-market side, each covering a different slice:

On top of those, ONET adds skill and technology importance ratings. ONET rates 35 skills on a one-to-five scale measuring importance to job performance, and separately publishes "In Demand" technology skills, defined as software and technology requirements frequently included in the employer job postings for a particular occupation. The posting layer is what makes this a market read rather than a textbook read.

The reason to use all of them is that they disagree in useful ways. The Employment Projections skills framework tells you what is durable and growing. The O*NET In Demand list tells you which named tools show up in real ads. Posting tallies tell you the frequency the local market rewards this quarter. A resume that carries only one of these is guessing on the other two.

Two signals that disagree, and why you carry both

The most important thing to understand before you rank anything: "important now" and "growing" are different lists in the federal data, and the gap between them is the leverage this build gives you. If you optimize for only one, you either look current but stagnant, or forward-looking but thin on what the job needs today.

The Employment Projections skills framework maps 104 O*NET elements into 17 skill categories, then scores each per occupation two ways. One score is the weighted change in skill importance over the projection decade. The other is a regression coefficient measuring how strongly a skill category associates with employment growth. They do not rank the same.

Read the two columns side by side. Problem solving and decision making tops the growth-correlation column at 7.77 but sits only mid-pack on weighted score change at 0.23. Critical and analytical thinking leads the change column but ranks below problem solving on correlation. A resume that leads only with the fastest-changing skills can miss the ones most tied to where jobs are being added, and the reverse is equally true.

The practical move is to keep a small top tier of skills that score high on both dimensions, and a secondary tier for skills that are strong on only one. The failure to avoid is treating a single BLS chart as the answer.

The step-by-step build

Run these eight steps in order. Each has a checkable output, so you never move on unsure. Budget three to four focused hours the first time; a rebuild later is faster because the crosswalk work is done.

One note on ordering. Sources disagree on whether the posting tally (step 5) or the skills framework (step 4) comes first. Posting-frequency-first guides tally before they consult any framework; BLS-anchored logic reads the 17-category structure first. I put the framework first because it stops the tally from being dominated by whatever tool happens to be hot this quarter, but the two feed the same merge in step 6, so the order between them matters less than doing both.

Choosing the target title when your occupation maps to several

Lead the resume with one standard title, and choose it by ranking the candidates on demand you can actually evidence. Your occupation almost never maps to exactly one title, and the choice is the highest-leverage decision in the build because the applicant tracking system filters on it first.

There is no published formal rule here, so treat this as a reader-assembled decision rather than a named framework. The mechanics are documented: ONET crosswalks convert a code or title from military, education, OOH, SOC, or ESCO systems into matching ONET-SOC occupations, and OEWS plus Employment Projections give each title a median wage, projected openings, and growth. That gives you everything needed to rank.

The candidate you pick has to clear two independent bars. It must show strong demand in the data, and your own history has to be able to evidence it. A title with huge openings that you cannot back with quantified bullets is a filter you pass and an interview you fail.

This is not abstract. In Refolk's index, two adjacent titles in the same US market differ sharply in size:

Data Analyst is 2.21x larger, but that is stock, not hiring velocity. A larger population can mean a saturated field rather than more open roles. The count tells you the title exists at scale; only the projected openings tell you whether it is opening up. That is exactly why step 2 forces you to write openings and growth beside every candidate before step 3 lets you choose.

The same title is a different market by country. In Refolk's index, Data Scientist counts 28,220 in the US against 5,229 in Germany, a 5.40x gap.

If you are aiming at a different country than the one you trained in, re-run the demand read there. The preferred title, the certifications that show up, and the skill priorities all shift, and a US-tuned resume dropped into a market a fifth the size, structured differently, will miss.

When you need to see who actually holds and moves between these titles in a given market, a profile search answers it faster than manual scanning. Refolk reads its index of professional profiles so you can compare the real population behind two candidate titles before you commit to one.

Building the weighted priority list

Merge three inputs into one ranked list: the Employment Projections skill scores, the O*NET In Demand tools, and your own tally of many postings. Resolve conflicts toward posting frequency for named tools and toward the EP framework for durable skills. The output is a top five and a secondary tier, and it is the backbone every bullet on the resume serves.

Start by keeping durable skills and named tools in separate columns. Durable skills are the 17 EP categories: critical thinking, problem solving, project management, adaptability. Named tools are the O*NET In Demand technologies and the specific software from postings. They behave differently over time, and mixing them hides that.

O*NET publishes over 2,400 In Demand skill linkages across 285 occupations and 176 Employer-Based Hot Technologies producing over 11,500 occupation linkages, so the named-tool layer is well populated for most occupations. Use it to seed your tally, then let the posting frequency confirm or demote each tool.

For the merge itself:

• A skill that is high on the EP framework and frequent in postings goes top tier. Both signals agree, so the evidence is strongest.
• A tool that is frequent in postings but has a short half-life goes in only if postings clearly demand it, and you check it again at the next rebuild.
• A skill rated highly by ONET importance but rarely seen in current postings does not go top tier on the ONET rating alone. Importance is not the same as market frequency.
• A durable EP skill that postings underweight still earns a place, because postings lag the projections. This is where you trust the framework over the tally.

Cap the top tier at five. The keyword guidance you will verify against wants three to five priority terms each appearing two to three times, and 15 to 30 distinct terms total. A top tier larger than five dilutes the density you can give each one.

How this goes wrong

The build fails in specific, recognizable ways. Most of them come from trusting one signal and skipping the reconciliation, or from mistaking a proxy for the thing it stands in for. Each failure below has a check that catches it.

Two of these deserve extra weight. Single-posting contamination is the failure this whole method exists to prevent: the moment your priority list traces back to one ad, you have rebuilt the generic tailoring workflow and lost the market read. If you cannot name at least a handful of postings behind each top-tier skill, go back to step 5.

Keyword stuffing is the failure that looks like success. Overloading a resume with repeated keywords appears unnatural and can cause its own applicant tracking system issues, and it always fails the human reader who opens the file after the filter passes it. The fix is structural: a keyword only counts if it lives in a bullet that describes something you did, ideally with a number attached.

The churn failure sets your rebuild cadence. With cited technical skill half-life under three years and WEF projecting that 39% of core skills will be obsolete by 2030, the tools you list this year drift out of date within about a year. That is why the heuristic is rebuild the skills backbone annually, tailor the wording per application. Treat that as a defensible rule of thumb, not a measured per-occupation constant; the exact half-lives are not established publicly.

Try the market read on real profiles

Before you commit to a target title, it helps to see the people who already hold it and the paths into it. A profile search answers that in one query where manual scanning would take hours.

Use a query like this to sanity-check a title decision against reality. If a transition you are planning barely shows up in the target market, that is a signal to re-run the demand read there before you build.

Verifying the draft before you call it done

A finished draft leads with one standard title and gives every top-five skill a quantified bullet, with priority terms at the right density and nothing that reads as a keyword list. Verification is a fixed check, not a judgment call, so run it the same way every time.

The density targets are documented: your three to five highest-priority keywords should each appear two to three times across different sections, secondary keywords at least once, for a total of 15 to 30 distinct keyword terms. Fewer than that and you underweight the market; more and you drift toward stuffing.

Here is a compact rubric you can paste beside the draft and score it against.

Title match: leads with a standard title from the crosswalk or postings ................ [ ]
Openings verified: chosen title paired with EP projected openings, not headcount ....... [ ]
Top-five defined: five priority skills, each high on framework or frequent in postings . [ ]
Evidence attached: every top-five skill has a quantified bullet ....................... [ ]
Density: priority terms 2-3x each, 15-30 distinct terms total ........................ [ ]
No stuffing: every keyword lives in a real bullet .................................... [ ]
Multi-posting basis: priority list drawn from many ads ............................... [ ]
Country checked: demand re-read if target market differs from training market ......... [ ]

Keeping the build current

Re-run the demand read on a schedule, because the market moves faster than your resume does. Rebuild the skills backbone roughly once a year and tailor the wording per application; that split follows the arithmetic of skill churn rather than any calendar habit.

The full annual rebuild means repeating steps 4 through 8: pull fresh EP scores and the current O*NET In Demand list, re-tally recent postings, re-merge, and re-verify. The title decision from steps 1 through 3 changes less often, so revisit it only when your background shifts or you aim at a new market. If you are moving countries, that revisit is mandatory, given the 5.40x gap the same title can carry between markets.

Between rebuilds, tailor per application by adjusting phrasing and emphasis toward a specific posting, without disturbing the market-built backbone. When Refolk tailors a resume to a posting and scores the fit, that per-application layer sits on top of the priority list you built here, so you keep the market read and still speak to the individual ad. Re-check the two federal signals each cycle, because a skill that is merely growing this year may be both important and growing the next, and that is exactly when it earns a promotion to your top tier.