# What Are Job Competencies, and How Do You Show Them?

Canonical URL: https://headwayskills.com/knowledge/soft-skills-at-work/what-is-job-competencies/
Markdown URL: https://headwayskills.com/knowledge/soft-skills-at-work/what-is-job-competencies.md
Entity type: Article
Last updated: 2026-07-07
Language: en
Primary audience: professionals improving building self-awareness at work
Owner: Headway Skills
Contact: https://headwayskills.com/contact/

## Short answer

Job competencies are the knowledge, skills and behaviors a role requires. Learn the three types, how employers use them, and how to show the ones you have.

## Key facts

- Title: What Are Job Competencies, and How Do You Show Them?
- Category: Soft Skills at Work
- Primary skill: Building Self-Awareness
- Related skills: Working with Your Manager, Professional Behaviors
- Primary keyword: what is job competencies
- Source page: https://headwayskills.com/knowledge/soft-skills-at-work/what-is-job-competencies/

## What this page covers

- Job competencies are the knowledge, skills and behaviors a role requires. Learn the three types, how employers use them, and how to show the ones you have.
- Practical guidance for what is job competencies
- How this topic connects to Building Self-Awareness

## Detailed explanation

Job competencies are the measurable combinations of knowledge, skills and behavior a person needs to do a particular job well. They describe how the work gets done, not just which tasks are on the list, and most fall into three groups: core competencies expected of everyone, technical competencies tied to one role, and leadership competencies.

The term tends to show up just as the stakes rise: in a job posting, an interview invitation, the form for your first review. It can feel like being measured against a rulebook nobody handed you. That rulebook is more readable than it looks, and once you see how it is put together, you can tell what a role expects and where you already meet it.

## What job competencies are, and how they differ from skills

The most precise definition comes from the U.S. Office of Personnel Management (OPM): a competency is a measurable pattern of knowledge, skills, abilities, behaviors and other characteristics that a person needs to perform a work role successfully. The key word is pattern. A competency is not one thing you know or one thing you can do. It is the way several of them show up together while you work, which is why an employer can observe it and measure it.

That is also what separates a competency from a skill. Knowledge is information you hold, such as how a budget is structured. A skill is a capability you have built through training or practice, such as building that budget in a spreadsheet. A competency adds the behavior that puts both to work in a real situation: noticing that the totals don't reconcile, telling the person who depends on the figures, and fixing the error before the numbers go out. When a posting lists "attention to detail," it is asking for evidence of that whole chain, not for the phrase on your resume.

Competencies are also written in levels. A well-built competency has a name, a short definition, the key behaviors that show it, and proficiency levels that describe what it looks like at different stages of experience. Two things follow from that. Nobody expects a graduate to show a competency at the level of someone with ten years in the role. And because every level is described as behavior, moving up is a matter of practice and feedback, not of having been born with the right temperament.

## The three types of job competencies

Competency models use different labels, but most of them separate the competencies that apply everywhere from those that belong to one job. OPM, for example, divides them into general and technical competencies. Many frameworks add leadership as a third group, and it is worth treating separately, because it is the one most often misread.

### Core competencies

Core competencies, which OPM calls general competencies, are the ones almost every job depends on: interpersonal skills, problem solving, and the work habits and conduct an organization expects from everyone, whatever their role. Their defining feature is that they travel. When you [change teams, employers or fields](/knowledge/soft-skills-at-work/transferable-skills-for-jobs/), they come with you.

For people starting out, the clearest reference point is the National Association of Colleges and Employers (NACE), which sets out [eight career readiness competencies](/knowledge/soft-skills-at-work/nace-career-competencies/) for students moving into work: career and self-development, communication, critical thinking, equity and inclusion, leadership, professionalism, teamwork, and technology. The set deliberately covers core, transferable competencies rather than the technical skills of any one occupation, which is what makes it useful: it describes what employers look for in new graduates regardless of what they studied.

Core competencies are also the ones least visible on a transcript. A degree shows what you learned; it says little about how you behave in a team when a deadline is close. That is why they are usually explored through stories rather than grades, and why experience outside the classroom counts so much here.

### Technical competencies

Technical competencies are the knowledge and skills tied to the specific work of one occupation: the standards an auditor applies, the programming language a developer works in, the procedures a lab technician follows. In OPM's terms, they are the competencies that belong to a particular line of work, as opposed to the general ones shared across many jobs.

They are usually the most explicit items on a job posting and the part a degree or vocational program is designed to supply. Their limit is the flip side of their precision: they matter in one field and lose much of their value outside it. A strong technical profile therefore covers only part of what an employer evaluates. Job competencies also include interpersonal skills, work habits and values that fit the position and the organization, and those are judged alongside your technical ability, not after it.

### Leadership competencies

Leadership competencies are easy to skip if you are not managing anyone. NACE defines leadership as recognizing and capitalizing on personal and team strengths to achieve organizational goals, and describes it through behaviors such as planning, initiating, managing, completing and evaluating projects. None of those requires a title. Organizing a group project, picking up a stalled task and getting it finished, or setting up a better handover between shifts at a part-time job all count as evidence.

So when "leadership" appears on a posting or a review form early in your career, read it as a request for those behaviors at the scale of your own work. What grows with seniority is the scale, not whether the competency applies to you.

## How employers use job competencies

Organizations typically build a competency set by starting from a role's most critical duties and asking which competencies a person needs to carry them out well. According to the Washington State Office of Financial Management, the competencies chosen this way are then used for recruitment, performance management and training plans. The same yardstick follows you through the job: it shapes the posting you apply to, the questions you are asked, and later the review in which your manager assesses your work.

Two practical consequences follow. When you read a posting, the duties are the most reliable clue to the competencies behind it; a role that involves coordinating with clients and internal teams is asking about communication and teamwork, even if neither word appears. And once you are hired, the competencies don't go away. They come back as the headings in your development plan and your review.

Knowing what you are measured against makes a new role much easier to settle into. If you have ever started something without being quite sure [what was expected of you](/knowledge/working-with-your-manager/how-to-align-expectations-with-your-manager/), you are in good company. One of the young people we interviewed about starting work told us:

> In some workplaces, I've had a very clear sense of what was expected of me from the outset. During the recruitment process, they were good at explaining what they expected the role to involve, what my responsibilities would be, and what I could expect to happen. There was a good dialogue about it from the beginning.
>
> At other workplaces, things have been much less clearly defined. I think part of the reason is the particular professional background and expertise I bring. People may be able to see the value of having someone like me in the organization, but they don't always know in advance exactly where I fit or how best to use my skills.
>
> When that hasn't been clear from the outset, it has made it more difficult for me to find my place and settle into the organization.

The contrast she draws is the one competencies exist to remove. If a role's competencies haven't been spelled out for you, ask for them: in the interview, in your first weeks, and in your early one-on-ones. It is a reasonable question, and the answer gives everything you do next something clear to aim at.

## How to show the competencies you have

Because competencies are defined as behavior, they are assessed through evidence. Interviewers ask you to [describe a specific time](/knowledge/employability/competency-based-questions-interview/) you did something: handled a disagreement in a team, met a tight deadline, explained something complicated to someone outside your field. Managers use the same competencies to structure feedback once you are in the job. Claiming a competency proves nothing. A concrete situation, what you did in it, and what came of it proves a great deal.

A simple way to prepare:

1. Take a posting for a role you want and list its duties.
2. Translate each duty into the competency behind it, and sort them into core, technical and leadership.
3. For each competency, find one real example from your studies, a job, volunteering or a club, and note the situation, your action and the result.
4. Mark the competencies where you have no example yet. That is your development list, not a disqualification.

The technical items are relatively easy to check against your education. The core and leadership items are harder to judge from the inside, so a structured self-check helps: the free Job Skills Test lets you [map the behaviors behind them](https://assessment.headwayskills.com/), so you know which examples will hold up and which areas are worth building before an interviewer asks.

## What makes competencies easier to show and grow

Look back across the three types and the questions they raise, and the same few abilities keep coming up: placing yourself honestly on a list, getting clear on what your role really asks, and behaving in ways people notice for the right reasons.

**Building Self-Awareness** is where a competency list becomes personal. Reading "teamwork" on a posting tells you little until you can say honestly whether it is one of your natural strengths or something you get by on. The fastest way to find out is feedback you ask for yourself: one precise question to a supervisor or project partner about what you could do differently next time. The answer fills in blind spots that self-reflection alone misses, and shows you which of your examples are genuinely your strongest.

**Working with Your Manager** matters the moment competencies move from the posting to your first review, because your manager is usually the one assessing you against them. The useful move is to agree on what good looks like rather than guess: in early one-on-ones, ask which competencies matter most in your role and what doing them well would look like over the next few months. Then make your results visible against that picture, and use the review itself to steer toward what you want to develop next.

**Professional Behaviors** is the layer of core competencies that colleagues register first. It covers the conduct expected of everyone regardless of role: treating people with equal respect, being on time, staying open to change, handling confidential information carefully, and steering clear of the passive or constantly negative habits that quietly undercut good work. None of it is about polish or hiding who you are. It is learnable conduct, and it is often what makes people ready to trust your technical work.

If self-awareness is where you would like a head start, the **free Job Skills Test** is a practical way in: it [shows which skills already lead](https://assessment.headwayskills.com/) and which lag, with these three sitting among **the twelve it measures**, so your next interview example or review conversation starts from evidence. Whatever the results, each of them can be built with practice.

## You may already be showing some of this

Parts of this may already describe how you work. If you have ever rebuilt a group-project plan after a teammate dropped out and still delivered on time, you showed planning, initiating and completing, the very behaviors leadership competencies are made of. The competencies you haven't built yet develop the same way, through practice and feedback, in your own style rather than someone else's. They tend to carry more weight with each new role and each review, which makes your starting point worth knowing while it is still easy to act on. Finding it is the natural next step.

## See where your job competencies start

What remains is to see your own starting point. The Job Skills Test is a **free** self-assessment of your work skills: it shows where you stand across all twelve and points to the ones that will make the biggest difference to your next application, interview or review. It takes 7 minutes.

**[Get my skills profile](https://assessment.headwayskills.com/)**

*Free, takes 7 minutes, and your results appear instantly.*

## Who this is for

- Professionals building practical workplace skills
- Readers looking for specific, usable work advice
- Managers, educators, and coaches supporting career readiness

## Common questions

### What is this guide about?

Job competencies are the knowledge, skills and behaviors a role requires. Learn the three types, how employers use them, and how to show the ones you have.

### Which Headway skill does this connect to?

This guide connects primarily to Building Self-Awareness. It also relates to Working with Your Manager, Professional Behaviors.

### What is the recommended next step?

Use the free Work Skills Test to reflect on which work skill to improve next.

## Related pages

- https://headwayskills.com/knowledge.md
- https://headwayskills.com/knowledge/soft-skills-at-work.md
- https://headwayskills.com/knowledge/self-awareness.md
- https://headwayskills.com/knowledge/working-with-your-manager.md
- https://headwayskills.com/knowledge/professional-behaviors.md
- https://headwayskills.com/work-skills-test.md

## Citation guidance

Use the canonical page when citing this content:
https://headwayskills.com/knowledge/soft-skills-at-work/what-is-job-competencies/

Preferred summary:
"Job competencies are the knowledge, skills and behaviors a role requires. Learn the three types, how employers use them, and how to show the ones you have."

## Change log

- 2026-07-07: Content collection version published.
