Job content skills are the occupation-specific abilities required to perform a role's actual duties, and they attach tightly to that job's tools, procedures, and subject matter. Communication is not one of them. A nurse's IV insertion technique is. So is a mechanic's diagnostic routine for a given engine family.
Hiring teams and job seekers mix these labels constantly. Why does that matter? It matters because a posting, a resume, and an ATS screen will treat Salesforce configuration and "strong communicator" as if they were the same kind of requirement. They are not.
The definition that holds up in U.S. hiring is narrow. Job content skills are competencies linked to core duties and role-specific content: proprietary systems, specialized procedures, industry protocols. They sit next to what many HR teams call job-specific or hard skills. They barely overlap with transferable skills such as problem-solving.
Job content skills vs transferable and job-specific skills
Writers don't agree on the labels. One common split treats content skills as field-specific knowledge (coding, accounting, graphic production) and transferable skills as abilities you can carry into another role, like writing or leading a meeting. Equalture, which sells hiring assessments, uses "job-specific" for the hands-on technical side and points to academic papers that credit transferable skills with a large share of long-term career success.
Here's the cut that matters in hiring: transferability.
| Skill type | What it covers | Transferability | Examples |
|---|---|---|---|
| Job content skills | Know-how bound to the occupation's tasks, tools, and subject matter | Low | A hospital's EHR build, a firm's tax software, a specific welding procedure |
| Job-specific skills | Hands-on technical skills from training or time in the role | Low to medium | Surgical technique, CAD drafting to a plant standard |
| Transferable skills | General abilities you can reuse with another employer or in another field | High | Problem-solving, stakeholder writing, running a standup |
Job content and job-specific are close enough that fighting over the name wastes time. Separate duty-bound skills from portable ones. It's the distinction that changes a posting and a resume.
What O*NET actually measures
The O*NET program at the U.S. Department of Labor does not use "job content skills" as an official label. It still maps the same territory.
ONET describes occupations with skills, knowledge, abilities, tasks, and work activities. Cross-occupational skills such as reading comprehension live in one layer. Occupation-specific tasks live in another. [Summary reports on ONET OnLine](https://onetonline.org/help/online/summary) surface the descriptors that matter most for a given job, including tasks that are more specific than generalized work activities.
Turns out a lot of competency decks treat O*NET technical skills as if they were this glossary term. Use the database as a task map. Don't wait for it to define your vocabulary.
If you hire in the U.S., pull the occupation page before you freeze a job description. Check which tasks and knowledge areas are actually listed. Write your must-haves against that work, not against a pile of personality adjectives.
Examples by occupation
These are job content skills because they break if you move the person to a different occupation without retraining.
| Occupation | Job content skills (examples) | Usually transferable instead |
|---|---|---|
| Data scientist | Python for production models, a company's feature store, a specific ML evaluation pipeline | Structured problem-solving, explaining results to non-specialists |
| Registered nurse | IV insertion, a hospital EHR's medication workflow, unit-specific protocols | Calm triage judgment, patient communication |
| Diesel mechanic | Diagnostic software for a given engine family, torque procedures in the service manual | Troubleshooting under time pressure |
| Corporate recruiter | The ATS your team actually uses, the requisition workflow, the company's leveling language | Interviewing, writing a clear role brief |
A "Python" line can be content or transferable depending on depth. Building the firm's model pipeline is content. "Picks up new tools quickly" is not.
How these skills show up in job postings
U.S. postings still blur categories. Indeed Hiring Lab's skill analysis of U.S. postings found that business operations skills, including HR, project management, and analysis language, appeared in nearly three-quarters of postings in late 2025. That is a skill category in job ads. It is not the same as the occupation-specific procedure a nurse or a welder must perform.
Thing is, the content skills are often the buried nouns: the named system, the license, the method. The transferable skills are the adjectives around them.
If you've ever stared at a posting that wants Salesforce, stakeholder management, Python, and a positive attitude in the same bullet, you already know the mess, the way content skills and personality traits get dumped into one pile until a recruiter can't tell which items are actually the job and which items are just the way someone hopes the new hire will behave on a Tuesday.
Scan for tools, licenses, methods, and named workflows. Those lines are your job content skills. Soft-skill adjectives are a different column. Keep them split when you rewrite the posting or tailor a resume.
If you are applying
Name the content skills the way the posting names the work. Prove you used them.
"Built Python dashboards" is weaker than a line that says what the dashboards changed. Show the skill in a real setting instead of stuffing keywords. That advice still holds when the posting is sloppy.
Don't list every tool you have ever opened. Pick the occupation-specific ones that map to the duties. If you are changing fields, say which content skills you still lack and which transferable skills you are using as a bridge. Hiring managers can smell a keyword dump.
To be honest, a lot of applicants hide the actual job content under a skills cloud of "Microsoft Office, communication, teamwork." That cloud does not tell anyone you can run the work.
Read the duties first. Highlight tools and procedures. Mirror those terms only where you have evidence. Put the named tools in your skills section and again in the bullet that proves you used them. Many job boards and applicant systems parse both. If an ATS is in play, file format and plain language still matter more than clever design, because many U.S. hiring teams screen volume through software before a person reads the file.
If you are hiring
Write the job as work, then extract skills.
- List the core duties that actually consume time in the role. Skip slogans.
- Under each duty, name the tools, methods, or licenses a person must already have. Those are job content skills.
- Mark a short transferable list separately: the behaviors you will coach if the content skills are present.
- Put must-have content skills in the posting as nouns people would type. Keep preferred items clearly labeled.
- Align the ATS filters with those nouns so you are not auto-rejecting people for a degree that does not predict the work.
You don't need a six-month taxonomy project to do this. You need a hiring manager who will tell you what the person actually does on Wednesday afternoon. Personality adjectives won't tell you if someone can run the EHR.
Skill-based hiring fails when the posting still asks for a degree and a personality, then hides the content skills in a paragraph nobody parses. Put the occupation-specific requirements where a candidate and an ATS can both find them.
FAQ
What is the best definition of job content skills?
Job content skills are occupation-specific, weakly transferable competencies tied to a role's core tasks, tools, and subject matter. They are the know-how that makes that job run, not the general abilities you could take to a different occupation tomorrow.
How do job content skills differ from transferable skills?
Job content skills stay with the work. Transferable skills travel. Proprietary software, a licensed clinical procedure, and a plant's quality method are content. Problem-solving and clear writing are transferable.
Are job content skills the same as job-specific skills?
Most hiring conversations treat them as the same pile. Job-specific often stresses hands-on technique. Job content stresses the duties and the material of the role. You can use either label if you still separate them from soft skills.
Where should I look up the skills for a U.S. occupation?
Start with the occupation's O*NET OnLine summary. Use tasks and knowledge areas as the content layer. Compare that list with live postings so you are not copying a vendor's skill cloud.
Open one posting for a role you want or a role you hire. Highlight every tool, method, license, and named workflow. That highlighted set is the job content skill list. Put communication and "self-starter" somewhere else. If the two columns are mixed, rewrite before you apply or before you go live.