Let’s be honest. Most hiring processes are basically a coin flip dressed up in a nice calendar invite.
You post a job, collect resumes, run a few interviews where everyone’s on their best behavior, compare vibes in a 20-minute debrief, and pick whoever “felt right.” Three months later, the person who crushed the interview is struggling at the actual job — and you’re wondering what went wrong.
Nothing went wrong. The process was always broken. You just didn’t have a better one.
Competency-based hiring is that better one.
It’s not a buzzword. It’s not HR theory. It’s a structured way to find out — before you make an offer — whether someone can actually do the job. Not whether they’ve done a vaguely similar job before. Whether they can do this job, here, now.
Companies that switch to it see real numbers: 91% report higher employee retention. 81% cut their time-to-hire. And they consistently build more diverse teams — not because they set quotas, but because they stopped filtering people out on credentials that never predicted performance anyway.
Here’s how to actually do it.
What is competency-based hiring?
The longer version — competency-based hiring evaluates candidates on specific, observable behaviors directly tied to success in the role. Instead of asking “did they manage a team before?”, you ask “can they show me how they managed a team, what happened, and what they’d do differently now?”
That shift sounds small. It isn’t.
The concept has been around since Harvard Business Review popularised the term “core competency” in 1990. But most companies still haven’t made the switch, which means there’s a real competitive advantage waiting for HR teams willing to put in the upfront work.
Position-specific vs. organisational competencies
Before you build anything, understand that there are two types of competencies you need to work with.
Position-specific competencies are what someone needs to do this particular job well. A Finance Manager needs financial modelling and stakeholder reporting. A Customer Success Manager needs relationship management and escalation handling. These vary completely by role.
Organisational competencies are what everyone needs to succeed at your company, regardless of their job. Some companies run fast and reward initiative. Others are collaborative by design. Some need people who thrive in ambiguity; others value process. These don’t change by role — they reflect who you are as an organisation.
The most common mistake? Building only position-specific competencies and ignoring the organisational layer. That’s how you hire someone technically brilliant who drives everyone around them crazy within six months.
How it differs from traditional hiring
Traditional hiring Competency-based hiring What you filter on Degree, job title, years of experience Demonstrated behaviors and abilities How you interview Unstructured conversation Structured questions with scoring rubrics How you decide Gut feel Evidence mapped to predefined criteria Bias risk High Significantly lower Talent pool Narrow Wide Predicts job performance? Weak Much more reliably
| Traditional hiring | Competency-based hiring | |
| What you filter on | Degree, job title, years of experience | Demonstrated behaviors and abilities |
| How you interview | Unstructured conversation | Structured questions with scoring rubrics |
| How you decide | Gut feel | Evidence mapped to predefined criteria |
| Bias risk | High | Significantly lower |
| Talent pool | Narrow | Wide |
| Predicts job performance? | Weak | Much more reliably |
The core difference is this: traditional hiring asks “has this person been around long enough that we trust they can do it?” Competency-based hiring asks “can this person show us, right now, that they can do it?” One of those questions has a much better answer.
Why it matters: the business case for HR teams
You’ll probably need to sell this internally before you can implement it. Here’s what actually moves the needle in those conversations.
It kills bias — and widens your talent pool
Most credential filters in hiring weren’t designed to screen for performance. They were designed to reduce the pile on a recruiter’s desk. “Five years minimum” and “degree required” do cut applicant volume — but they also cut out a lot of high-potential people who built their skills differently.
Career changers. People who came up through non-traditional routes. Candidates from underrepresented backgrounds who didn’t have access to the “right” schools or brand-name employers. These people get screened out before anyone ever talks to them.
Competency-based frameworks remove that filter. When you’re assessing what someone demonstrates, their path to developing those skills becomes irrelevant. IBM figured this out and dropped degree requirements for thousands of technical roles. They didn’t lower the bar — they changed the bar to one that actually measured what they cared about.
Diverse companies attract 73.2% more top talent than non-diverse ones. This is one of the most practical structural tools you have to get there.
It massively improves retention
The most expensive mistake in hiring isn’t a slow process. It’s a hire who stays 18 months, underperforms, and leaves — taking all your onboarding investment with them. Replacing an employee typically costs 1.5–2x their annual salary. That’s not a rounding error.
Competency-based hiring reduces this because it creates genuine job fit, not just interview fit. When someone is hired because they demonstrated the exact behaviors the role requires, they hit the ground knowing what’s expected, they perform it consistently, and they feel competent doing it. Those three things are the strongest predictors of engagement and retention we have.
91% of companies using competency-based hiring report an increase in employee retention. That’s a structural shift, not an incremental improvement.
It actually speeds up hiring
This surprises people. More rigour sounds like more time. In practice, it’s the opposite.
When every interviewer is assessing the same predefined competencies with the same rubric, screening calls get sharper. Debriefs take 20 minutes instead of 90. Decisions happen faster because you’re comparing evidence, not impressions.
81% of organisations using this model report reduced time-to-hire. And because roughly a third of candidates abandon slow hiring processes, a faster structured process also improves offer acceptance rates. It’s not a trade-off between speed and quality. Done right, you get both.
Step 1: Build your competency framework
This is the work. If you shortcut this step, nothing downstream will save you.
Identify organisational-level competencies
Pick 4–6 competencies that predict success across all roles at your company. These should be behavioral, specific, and tied to how you actually operate — not a generic list you found on a Google search.
Common ones that hold up across most organisations:
- Communication — adapting how you share information based on who you’re talking to, not just “communicating well”
- Problem-solving — diagnosing root causes, not just fixing symptoms
- Adaptability — staying effective when priorities shift or information is incomplete
- Collaboration — getting things done through people you don’t have authority over
- Accountability — owning outcomes, including the ones that didn’t go well
- Customer orientation — keeping the end user in mind even when it creates friction
To find your list, don’t sit in a room and brainstorm. Go talk to the people who already succeed at your company. Ask them what qualities separate the people who thrive from the ones who struggle. Run a focus group. Send a survey. Pull performance review data.
Quick answer: Organisational competencies are the behaviours that predict success across an entire company, regardless of role. They sit above position-specific competencies and typically reflect culture, work pace, and values. Every candidate should be assessed against them, in addition to any role-specific criteria.
Map role-specific competencies (worked example)
For each role you hire into regularly, define 3–5 role-specific competencies. These come from two places: a job analysis (what does this role actually do, day to day?) and direct input from current high performers and the people who manage them.
Here’s what this looks like in practice for a Content Marketing Manager:
| Competency | What it means in this role | What evidence looks like |
| Strategic content thinking | Plans content around business goals, not just topics | Can map a piece of content to a funnel stage and a revenue outcome |
| Data-driven decisions | Uses performance data to decide what to write and where to publish | Reviews analytics before pitching content; can articulate what didn’t work and why |
| Cross-functional influence | Gets sales, product, and design aligned around a content strategy without formal authority | Has driven a content project that involved stakeholders outside their immediate team |
| Writing quality | Produces clear, compelling copy that’s adapted to specific audiences | Portfolio shows range; passes a live editing task in assessment |
| Project ownership | Manages complex pipelines with minimal oversight | Delivers consistently on deadlines; flags risks before they become problems |
Notice what’s not in there: years of experience, tool proficiencies, or educational background. Those might come up in a screening call, but they’re not the competencies. The competencies are the behaviors.
Validate with your stakeholders — don’t skip this
A framework built in an HR silo will get nodded at in a meeting and quietly ignored in practice. Before you finalise anything, run it past three groups:
- Hiring managers in the roles you’re targeting — do these competencies reflect what they actually need, or do they feel like HR language?
- High performers currently in those roles — do they recognise these behaviors in themselves? Are there important ones you missed?
- Recent new hires (6–18 months in) — what qualities actually helped them succeed that your JD never mentioned?
A simple validation test: give your competency list to a hiring manager and ask them to rank their top five performers. If the competency scores correlate with that ranking, you’re on to something. If they don’t, revise.
Step 2: Rewrite job descriptions around competencies
Most JDs are written defensively. They’re lists of requirements designed to filter down a large applicant pool, not to attract the right one. The result is language like:
That tells a candidate almost nothing about the actual job. It filters on background, not capability. And it quietly puts off a lot of qualified people who don’t see themselves in the credential checklist.
Competency-based JDs do something different. They tell candidates exactly what success looks like — and they invite people to self-assess whether they have it, regardless of how they got there.
What good vs. poor competency JDs look like
Before (credential-based):
“5+ years of B2B marketing experience. Bachelor’s degree in Marketing or a related field. Experience with HubSpot, Salesforce, and Google Analytics required.”
After (competency-based):
“You can build a demand generation strategy from scratch and explain exactly why you made the choices you made. You look at performance data before deciding what to work on next. You’ve managed cross-functional projects — and you can tell us what actually happened, not just the highlights. You’re comfortable presenting to senior stakeholders and you know how to get people aligned without needing formal authority to do it.”
Same role. Completely different signal to the market.
One practical formatting tip: frame the competency section as “You’ll be successful here if you can…” followed by 5–7 behavioral statements. It’s inclusive, specific, and maps directly to your interview questions later.
Step 3: Design the assessment process
One interview is not enough. It never was. A structured competency-based process uses multiple methods so you’re triangulating evidence, not relying on a single data point.
Behavioural (STAR) interviews — with a real question bank
Behavioural questions ask candidates to describe specific past situations that demonstrate a competency. The STAR framework — Situation, Task, Action, Result — gives you a consistent structure for both asking and evaluating.
The basic formula: “Tell me about a time when [situation requiring the competency]. What was your role, what did you do specifically, and what was the outcome?”
Here’s a ready-to-use question bank:
| Competency | Question |
| Adaptability | “Tell me about a time your priorities shifted significantly mid-project. How did you respond, and what was the result?” |
| Problem-solving | “Describe a complex problem you spotted before anyone else did. How did you diagnose it, and what did you do?” |
| Collaboration | “Give me an example of something significant you achieved through people you had no authority over.” |
| Accountability | “Tell me about a project you owned that didn’t go as planned. What happened, and what did you do differently after?” |
| Communication | “Describe a time you had to explain something complicated to someone with a very different background. How did you approach it?” |
| Data-driven decisions | “Walk me through a decision you made based primarily on data. What data, what did it tell you, what did you decide?” |
When a candidate gives a vague answer — and they will — probe: “What specifically was your role in that?” or “What was the measurable outcome?” Candidates who can’t give specific, evidence-based answers are showing you something important about how they actually work.
Situational judgment tests (SJTs)
Where behavioural questions look backward, SJTs test judgment in the present. Useful for candidates who are changing industries or early in their career — people who have the capability but not yet the direct experience to reference.
Design scenarios based on real challenges in the role. For a Customer Success Manager:
“A key enterprise client emails you Friday afternoon saying they’re looking at a competitor. Your renewal isn’t scheduled for three weeks. What do you do in the next 24 hours?”
Don’t score on whether they chose the “right” action. Score on the quality of their reasoning, what they prioritised, and what they said they’d want to know before acting.
Work samples and simulations
Highest validity of anything you’ll use. They test actual job performance — not a proxy, not a personality trait, not a credential. The actual thing.
Keep them realistic and bounded:
- A writing or editing task for a comms or content role
- A data analysis exercise with a real or anonymised dataset
- A 30-minute coding challenge relevant to your stack
- A mock client call or presentation to a panel
- A prioritisation exercise: given this backlog, what do you tackle first and why?
One hard rule: keep work samples under 2 hours. Respect candidates’ time. If the task is substantive, consider compensating for it — it costs you very little and sends a signal about your culture.
Psychometric and cognitive assessments
For roles where cognitive ability, personality, or specific aptitudes are strong performance predictors, validated psychometric tools add a reliable, relatively bias-resistant layer.
Options: cognitive ability tests (strong general predictor), situational judgment tests, work style questionnaires. Use only validated, peer-reviewed tools. Avoid anything that claims to assess “culture fit” without validation evidence — these tend to reintroduce the exact biases you’re trying to remove
Step 4: Score and calibrate consistently
Gathering evidence is only half the job. The other half is turning that evidence into decisions that don’t just reflect whoever argued most confidently in the debrief.
Structured scorecards and rubrics
Each competency needs a 3–4 level proficiency scale with specific behavioural assessment at each level. Here’s an example for Problem-Solving:
| Level | What it looks like |
| 1 – Foundation | Identifies obvious problems when pointed out; applies standard solutions with guidance |
| 2 – Developing | Proactively spots issues; generates a few options and picks the most logical |
| 3 – Proficient | Diagnoses root causes in messy, ambiguous situations; designs novel solutions with trackable outcomes |
| 4 – Expert | Anticipates systemic problems before they surface; shapes how the team or org approaches the problem space |
Assign each interviewer 1–2 competencies to assess. Don’t have everyone assess everything — it creates redundant questions and shallow evidence. Depth beats breadth.
Running a bias-free debrief
Structure it like this:
- Everyone submits their scored rubrics with written evidence — before any group discussion
- Each interviewer shares their scores and the specific behavioral evidence behind them, without commentary from others
- Discrepancies get discussed using evidence, not impressions
“They seemed like a strong cultural fit” is not evidence. “They described restructuring a 12-person team through a product pivot with zero attrition” is evidence.
This structure prevents the three most common debrief failure modes: groupthink, seniority bias (junior interviewers caving to whoever has the most authority in the room), and halo effects (one impressive answer inflating scores across unrelated competencies).
Step 5: Roll out and iterate
Don’t try to change everything at once. You’ll create resistance, lose data quality, and not know what caused what.
Pilot with one department first
Pick a team that hires regularly, has a hiring manager who’s open to the experiment, and where you have performance benchmarks for existing employees. Run two or three hiring cycles using the new framework. Keep your old process running elsewhere as a control.
Measure three things:
- Quality of hire — hiring manager satisfaction at 30, 60, and 90 days
- Time-to-hire compared to your previous average
- Candidate experience — a quick post-interview survey is enough
When that data comes back positive (and it usually does), use it to build the internal case for rollout. Nothing moves a sceptical hiring manager faster than their peer saying it worked.
KPIs to track
| Metric | What it tells you | How to measure |
| Quality of hire | Whether your framework predicts performance | 90-day manager satisfaction survey (1–10) |
| Retention at 12 months | Job-fit accuracy | % of competency-hired employees still in role after 1 year |
| Time-to-hire | Process efficiency | Days from role open to offer accepted |
| Offer acceptance rate | Candidate experience and employer brand | Offers made vs. offers accepted |
| Interviewer score variance | Whether your rubric is being applied consistently | Standard deviation across interviewers on the same candidate |
Review quarterly in year one. Feed the insights back into your framework — if a competency consistently fails to predict 90-day performance, pull it and find a better one.
Common mistakes HR teams make
Most of these are avoidable. Most happen anyway.
Vague competency definitions. “Strong communicator” is not a competency. If two interviewers would assess it differently, it’s not specific enough. Write behavioral anchors until there’s no ambiguity.
Building without hiring managers. Frameworks that HR builds alone get quietly ignored in practice. Build it with them, or plan to rebuild it later.
Assessing too many competencies. Eight is the practical ceiling per role. More than that and you get shallow evidence on everything. Go deep on fewer.
Using the framework for interviews but not for decisions. If your final decision still comes down to who you “liked best,” the framework was decoration. Require scorecards to drive the offer, not justify it.
Never updating the framework. Roles change. Skills evolve. AI has changed what “good” looks like in dozens of functions. Review your competency frameworks at least once a year.
Skipping interviewer training. The best scorecard in the world produces garbage data if interviewers don’t know how to probe for STAR responses or avoid leading questions. 90 minutes of training before the pilot. That’s it.
How SmoothHiring supports competency-based hiring
Running this process manually — tracking scorecards across spreadsheets, coordinating which interviewer covers which competency, aggregating evidence before a debrief — creates real administrative friction. Enough friction that teams either shortcut the process or abandon it.
SmoothHiring is built around the competency-based model. You define your framework inside the platform, assign competencies to specific interviewers, collect structured scorecard responses after each round, and see aggregated evidence before you walk into the debrief. Everything in one place, with a clear audit trail.
If you’re piloting competency-based hiring for the first time, it removes the coordination overhead that usually derails the first few cycles — and gives you the data you need to prove the approach is working.
