Ask five interviewers on the same panel what they’re actually looking for in a candidate and you’ll often get five different answers. One wants “someone sharp.” Another wants “a team player.” A third can’t get more specific than “I’ll know it when I see it.” None of that is written down anywhere, which means every interview is really a vibe check dressed up as a process.
A behavioral competency model fixes that by naming, in specific and observable terms, what good performance actually looks like in your company, for your roles, and building interviews and evaluations around it. This guide walks through building one from scratch, with an example you can adapt, the mistakes that quietly sink most attempts, and how to put the finished model to work instead of letting it sit in a slide deck.
What Is a Behavioral Competency Model?
A behavioral competency model is a defined set of skills, behaviors, and attributes tied to success in a specific role or role family, described in terms specific enough that two different people would score the same candidate the same way. It’s the difference between a value like “collaboration” sitting on a poster in the break room and a competency like “shares progress updates proactively and adjusts their own priorities to help teammates hit shared deadlines,” which is something an interviewer can actually ask about and score.
Company values tend to be aspirational and company-wide. Competencies are specific, tied to actual on-the-job behavior, and usually differ somewhat by role or role family, since what “problem-solving” looks like for a support rep is different from what it looks like for a finance manager.
Why Building One Is Worth the Effort
It standardizes interviews across panels. Everyone is evaluating the same defined behaviors instead of their own personal sense of what matters.
It reduces reliance on gut feel. Anchoring decisions to observable behavior, rather than a general impression, closes off some of the more common ways bias creeps into hiring decisions.
It creates a shared language. The same competency framework used in hiring can carry through to performance reviews and promotion decisions, so expectations don’t reset every time someone moves through a new stage of their career at the company.
It makes structured interviewing possible. Without defined competencies, there’s nothing concrete to build interview questions or scorecards around.
Step-by-Step: Building Your Competency Model
Step 1: Start With the Roles That Matter Most
Step 1: Start With the Roles That Matter Most
Don’t try to build a model for every role in the company in one pass. Pick a role family that’s either high-volume (you’re hiring for it constantly) or high-impact (getting it wrong is expensive), and start there. A customer support team or a first-line manager population are common starting points because the payoff from getting hiring right shows up quickly.
Step 2: Study Your Top Performers
Sit down with current high performers in the role, and separately with their managers, and ask for specific past examples rather than opinions. Instead of “what makes someone good at this job,” ask “tell me about a time this month you handled a difficult customer” or “walk me through how you prioritized your work last week when three things came in at once.” This is the same behavioral interviewing technique you’ll eventually use with candidates, applied first to understand what good actually looks like.
Step 3: Draft Competencies in Observable Language
Turn what you heard into competency statements that describe behavior, not personality. A weak competency reads like an adjective: “team player.” A useful one reads like a description of something you could watch someone do: “actively shares information with teammates without being asked, and adjusts their own workload to help others meet shared deadlines.”
Aim for five to eight competencies per role family. Beyond that, no interviewer can realistically evaluate all of them in a single conversation, and the model becomes a checklist nobody actually uses.
Step 4: Build Behaviorally Anchored Rating Scales
For each competency, describe what it looks like below expectations, at expectations, and above expectations, in concrete behavioral terms rather than a 1-to-5 number with no context. This is what turns a competency from a nice idea into something that produces consistent scores across different interviewers.
Example: Customer Focus
| Level | What It Looks Like |
|---|---|
| Below Expectations | Follows a script closely even when it doesn’t fit the customer’s actual problem; escalates issues rather than adapting the approach |
| Meets Expectations | Adjusts explanations and tone based on the customer’s situation; resolves most issues without needing to escalate |
| Exceeds Expectations | Anticipates follow-up problems before the customer raises them; proactively suggests solutions the customer didn’t think to ask for |
Step 5: Validate With Stakeholders Across the Business
Share the draft with hiring managers, current employees in the role, and anyone else close to the day-to-day work. Ask specifically: does this match what actually separates strong performers from average ones, or does it read like generic HR language that could apply to any company? Adjust based on what comes back.
Step 6: Map Competencies to Interview Questions and Assessments
Assign specific behavioral interview questions to each competency, and decide which stage of the hiring process evaluates which one. A pre-employment assessment might test problem-solving competencies before a candidate ever reaches an interview, while a structured conversation later in the process, tracked through your interview scheduling software and scored inside your applicant tracking system , covers competencies like collaboration or customer focus that are harder to assess without a real conversation.
Step 7: Train Interviewers and Calibrate Scoring
Run a calibration session before rolling the model out live. Have every interviewer independently score the same recorded or practice interview against the new competencies, then compare notes and talk through any big gaps in scoring. This step gets skipped constantly, and it’s usually the reason a good competency model fails to change anything in practice.
Step 8: Review and Update on a Schedule
Revisit the model at least once a year, or sooner if a role changes meaningfully, like after a new product launch or a restructuring that shifts what the job actually involves day to day. A competency model built for how a role worked two years ago quietly stops helping once the role has moved on without it.
Common Mistakes When Building a Competency Model
Too many competencies. Ten or twelve competencies per role sounds thorough but is unusable in a 45-minute interview, so interviewers end up focusing on two or three anyway, defeating the purpose of defining the rest.
Vague, adjective-only definitions. “Strong communicator” means something different to every interviewer. Without a behavioral description attached, the model doesn’t actually standardize anything.
No interviewer training or calibration. A well-written model that interviewers were never trained to use consistently is functionally the same as not having one.
Building it once and never updating it. Roles evolve. A model that isn’t revisited becomes disconnected from what the job actually requires.
Disconnecting it from actual assessments and scorecards. A competency model that lives in a document but isn’t tied to real interview questions or evaluation forms tends to get ignored the moment hiring gets busy.
How SmoothHiring Helps You Put a Competency Model Into Practice
A competency model only pays off once it’s built into the actual mechanics of hiring, not left as a reference document nobody opens. SmoothHiring’s applicant tracking system lets you build structured scorecards around your specific competencies so every interviewer is evaluating candidates against the same defined behaviors, while interview scheduling software keeps multi-stage, multi-competency interview loops organized without the usual back-and-forth. For competencies that are easier to assess before a live interview, pre-employment assessments and video assessment software can screen for specific behaviors and problem-solving skills earlier in the funnel, and predictive hiring tools can eventually help you see which competencies actually correlated with strong performance once enough hires have gone through the model.
Frequently Asked Questions
What’s the difference between a competency and a company value?
What’s the difference between a competency and a company value?
A company value is aspirational and applies broadly across the organization, like “integrity” or “innovation.” A competency is specific to a role or role family and described in observable behavioral terms an interviewer can actually evaluate, like “adjusts communication style based on the audience.”
How many competencies should a role have?
Most role families work best with five to eight competencies. Beyond that, interviewers can’t realistically evaluate all of them in a single conversation, and the model becomes impractical to use consistently.
Do different roles need different competency models?
Often, yes, though roles can share a common core. A company might define a handful of company-wide competencies that apply to everyone, then add role-specific competencies on top for individual role families.
How do behaviorally anchored rating scales help with interview bias?
They give every interviewer the same concrete description of what a low, average, or strong response looks like, which reduces the chance that personal impressions or unrelated factors influence the score.
Can a small business build a competency model, or is this only for large organizations?
Small businesses can build one, and often benefit from it faster since a single bad hire has a bigger relative impact. The process scales down easily: start with one or two key roles rather than trying to cover the whole organization at once.
How often should a competency model be updated?
At least once a year, and sooner if a role’s day-to-day responsibilities shift meaningfully, such as after a reorganization, a new product line, or a significant change in the tools the role uses.
What happens if we build a competency model but don’t train interviewers on it?
The model tends to sit unused. Interviewers fall back on their own instincts and questions, which is exactly the inconsistency a competency model is meant to solve. Calibration training is what actually makes the model function in practice.
Conclusion
A behavioral competency model turns “I’ll know it when I see it” into a defined, shared standard that every interviewer can apply the same way. The work is front-loaded: studying top performers, drafting behavior-specific definitions, building rating scales, and training your team to use them consistently. Once that groundwork is in place, hiring stops depending on which interviewer happened to be in the room and starts depending on whether a candidate actually demonstrates the behaviors your best people already show.
If you’re ready to put a competency model into practice rather than leaving it in a document, look at how SmoothHiring’s applicant tracking system and interview scheduling software can build structured scorecards around your specific competencies, and request a demo to see it set up for your own roles.
