What Are Competencies? (Definition + Examples)

A competency is the combination of knowledge, skills, abilities, and behaviours a person needs to perform a specific job effectively. The competency meaning that matters in hiring is narrower than "talent" or "capability", it is the observable, assessable version of ability, tied to a role.

If you are hiring for engineering, sales, or any bulk role, competencies are what you are actually screening for. Job titles change, tools change, and job descriptions get copy-pasted, but the competencies underneath, whether that is analytical thinking, structured problem solving, or cold-call resilience, are what decide who performs. That is why competency frameworks sit under almost every serious interview process, and why Fabric's AI Round 1 interviews are built to test them directly rather than infer them from a resume.

This post walks through the competencies meaning that hiring teams actually use day to day, how the KSA framework fits in, worked examples (including analytical thinking), and how to move from a competency list to an interview process that assesses them.

The competency meaning, in plain terms

A competency is a cluster of knowledge, skills, abilities, and behaviours that predicts whether someone can do a specific job well. Cambridge Dictionary defines competency as "an important skill that is needed to do a job," which is directionally right but misses what makes the term useful at work: a competency is observable, assessable, and tied to real outcomes, not a trait you either have or do not have. The academic literature, including Austin's 2019 review of competency in professional practice, stresses this same distinction: competency assessment is central to professional education because it forces vague ideas of "capable" into measurable behaviours.

In hiring, the useful working definition is that a competency is what a hiring manager can watch someone demonstrate. If you cannot describe what "good" looks like in a specific behaviour, you do not have a competency. You have a wish.

The gap between "we need strong communicators" (not a competency) and "structured written communication under a 20-minute constraint" (a competency) is the gap between an unreliable interview and a defensible one.

Define competency vs. skill vs. ability: what KSA actually means

The KSA meaning most people learn on the job is: Knowledge, Skills, Abilities. Each layer describes something different, and confusing them is one of the most common reasons interviews miss.

• Knowledge is information a candidate has learned. Example: "understands how OAuth 2.0 works." Testable with questions.
• Skills are the applied use of knowledge. Example: "can implement OAuth 2.0 in a Node.js service." Testable with a task.
• Abilities are the underlying capacity to acquire or apply skills. Example: "learns new authentication protocols quickly." Testable through observation over time or a proxy task.

A competency wraps all three plus the behaviours that make the person effective on a team. So the definition of KSA feeds into competencies, but a competency is broader: it is what you are ultimately hiring for.

What is KSA useful for on its own, then? Job descriptions. Grading rubrics. Structured interview scorecards. It is the vocabulary that keeps a competency from staying abstract.

The SHRM Body of Applied Skills and Knowledge (BASK, formerly the SHRM Competency Model) uses this same layered logic: nine HR competencies, each defined by specific behaviours and proficiency levels, so what "competent" means at an entry level differs from what it means at a director level.

The four types of competencies you will see in hiring

Most competency frameworks group into four buckets. Names vary, the buckets do not.

1. Technical competencies. Role-specific skills like coding, financial modelling, sales prospecting, or clinical procedures. These are what most people mean when they say "hard skills."
2. Behavioural competencies. How someone works: communication, collaboration, adaptability, resilience under pressure. SHRM's BASK model calls these the behavioural competencies that let technical knowledge actually translate into performance on the job.
3. Core competencies. The ones every employee at the company needs regardless of role. Common examples: customer focus, integrity, ownership.
4. Leadership competencies. Reserved for people-manager roles: coaching, delegation, strategic thinking, decision-making under ambiguity.

For any role you are hiring, you will pick a handful from each bucket, define what "good" looks like at the target level, and turn that into an interview plan. That is what a competency framework is.

Worked example: what is analytical thinking as a competency?

"Analytical thinking" appears on almost every job description and almost no interview scorecard. That is because most teams write it as a trait ("we need an analytical thinker") rather than as a competency (what does an analytical thinker actually do, and how would you see it in an interview?).

A workable definition: analytical thinking is the ability to break a complex or ambiguous problem into components, examine each with relevant data or logic, and arrive at a defensible conclusion.

As a competency, that looks like:

• Restating a problem in their own words before jumping to solutions.
• Naming the data or information they would need to answer it.
• Identifying what they do not know and what they would need to find out.
• Structuring the answer so a listener can follow the reasoning.

That description is now assessable. You can watch a candidate do it in a case study, a guesstimate, or a technical debugging exercise. You can score it against a rubric. You can compare candidates on the same behaviour instead of on how confident they sounded.

This is where the KSA layers become useful. The knowledge an analytical thinker draws on varies by role (business math, code, market data). The skill is applying a structured approach under time pressure. The ability is the underlying capacity to reason under unfamiliar conditions. You test all three. You score the competency.

How competencies drive real Round 1 interviews

Competencies are only useful if they change what you do in an interview. Otherwise the framework sits in a shared drive and interviews still happen by vibes.

The link between a competency list and an interview format is what a good interview methodology solves. Structured interviews, behaviourally anchored rating scales (BARS), and role-specific tasks all exist to force interviewers to score the same competency against the same rubric across candidates. Our guide to structured vs. situational interviews walks through when each format is the right fit, and interview methodologies explained covers the wider set.

Fabric's Round 1 interviews are built directly around competencies. Formats are tailored by role: pair programming and OpenRound for tech competencies, case studies and guesstimates for analytical and problem-solving competencies, cold-call and cold-email simulations for sales and customer success competencies, and prompting exercises for AI fluency in non-tech roles. Cheating detection runs alongside every format, so the competency score you are looking at came from the candidate, not from a co-pilot on a second screen.

Fabric's Interview Engine screens, scores, and shortlists candidates on those competencies. It is designed to give a recruiter a panel-ready view of how each candidate performed against the same rubric. The recruiter or hiring panel makes the final decision.

Building a competency framework: a short checklist

If you are starting from scratch:

1. Pick the job. Not "engineers." A specific role at a specific level.
2. List the 5 to 7 outcomes someone in that role has to deliver in year one.
3. For each outcome, ask: what does the person need to know, be able to do, and be able to keep learning to deliver this? That is your first pass at KSAs.
4. Group related KSAs into competencies. Aim for 6 to 10 per role, not 30.
5. For each competency, write one sentence describing what "meets expectations" looks like, in observable terms. Use verbs.
6. Attach each competency to an interview format that can actually test it. A behavioural competency needs a behavioural question or a task, not a technical quiz.
7. Write the scorecard against those competencies before the first interview.

The step most teams skip is step 6. A competency framework that never touches the interview loop is decoration.

Where the competencies get codified first is the job description. If the JD lists 30 vague qualities, the interview will too.

Common mistakes when defining competencies

• Confusing a competency with a personality trait. "Passionate" is not a competency; it is not observable at a Round 1 stage.
• Listing 30 competencies per role. The point of a framework is to focus interviews on the ones that predict performance, not to catalogue every desirable quality.
• Using the same competency definition across levels. What "problem solving" looks like for a junior engineer is not what it looks like for a staff engineer. Define proficiency levels.
• Assessing a competency with the wrong format. Trying to score "cold-call resilience" from a resume review or a behavioural question about "a time you were resilient" is not the same as watching someone make a simulated cold call.

Related Posts

• What Is a BARS (Behaviorally Anchored Rating Scale)?
• Structured vs. Situational Interviews: Which Should You Use?
• Interview Methodologies Explained
• What Is a Job Description? How to Write One
• The Recruitment Process Explained: A Complete Guide

FAQ

What is the meaning of the word competency?

A competency is a cluster of knowledge, skills, abilities, and behaviours needed to perform a specific job effectively. In hiring, the useful definition is narrower: it is what a hiring manager can actually watch a candidate demonstrate.

What does competency mean at work?

At work, a competency is a role-specific bundle of KSAs and behaviours that predicts on-the-job performance. It is the vocabulary teams use to write job descriptions, structure interviews, and score candidates against the same rubric.

What is competence in simple words?

Competence is the basic ability to do something to an acceptable standard. Competency, the term used in HR, is the more specific version: it names the exact combination of knowledge, skills, and behaviours that "acceptable" requires for a given role.

What is an example of competency?

Analytical thinking, defined as the ability to break a complex problem into components, examine each with data or logic, and arrive at a defensible conclusion, is a common competency across engineering, consulting, and product roles. It is assessable in case studies, guesstimates, and pair-programming exercises.

What is KSA and how does it relate to competencies?

KSA stands for Knowledge, Skills, and Abilities: the three layers that make up a competency. Competencies bundle KSAs together with the behaviours that make someone effective in a role.

How many competencies should a job role have?

Aim for 6 to 10 per role, split across technical, behavioural, core, and (where relevant) leadership buckets. Longer lists dilute interviews, shorter ones miss important dimensions of performance.

What is the difference between a competency and a skill?

A skill is one component of a competency: the applied use of knowledge. A competency wraps a set of skills, plus the underlying knowledge, abilities, and behaviours, into what a role actually requires.