Six downloadable sets for small businesses without a recruiting team: a framework worksheet, a question bank across eight competencies, behavioral, situational and technical versions of the same competency, a screening call set, an anchored scorecard, and an interviewer probe card. Every question states why it is worth asking and what a strong answer contains.
The first competency-based interview I ever ran was a fake. I had read the phrase, written six impressive-sounding questions the night before, asked them, liked the candidate, and hired him. Two months later I could not have told you which competency any of those questions measured, because I had never decided what I was measuring. The questions were fine. The framework underneath them did not exist.
That is the gap this page is built to close. A competency-based interview is not a style of question. It is a decision, made before you meet anyone, about the five or six things this job genuinely requires, followed by the same questions and the same scoring for every candidate who applies.
At FirstHR we build for small businesses that hire without a recruiting team, where the owner writes the job posting and runs the interview between customer calls. Below are six downloadable sets: a framework worksheet, a question bank across eight competencies, a screening call set, an anchored scorecard, and more. Every question carries a reason it is worth asking.
TL;DR
Competency-based interview questions measure named, job-related competencies instead of exploring a resume. Choose five or six competencies from the actual work first, then ask every candidate the same one or two questions per competency. Score each answer from 1 to 5 against written anchors, alone, before anyone discusses the candidate.
What Competency-Based Questions Are
A competency-based question is one written to produce evidence about a named, job-related competency, and scored against a scale you wrote in advance. The US Office of Personnel Management defines a competency as a measurable pattern of knowledge, skills, abilities, behaviors, and other characteristics that someone needs to perform a work role successfully.
The word measurable is the load-bearing one. If you cannot say what a strong answer contains and what a weak one contains, the question is a conversation starter rather than an assessment. That is the difference between asking someone whether they are a good communicator and asking them to describe a time they explained something technical to a person without the background.
The method draws on three question types for each competency. Behavioral questions ask what the candidate actually did, and they give the strongest evidence. Situational questions describe a scenario and ask what they would do, which works when a candidate has no relevant history. Technical questions test knowledge or ask for a demonstration, and small businesses skip them more often than they should.
Question type
What it asks
Best used when
Behavioral
What you actually did in a past situation
The candidate has done this kind of work before
Situational
What you would do in a described scenario
Career changers, first jobs, or a scenario new to everyone
Technical
What you know, or show me how you would do it
The competency has a verifiable right answer
Resume walk
Tell me about your last job
Context only, never as the assessment itself
Outside the United States, competency-based is simply the standard name for what many American employers call behavioral interviewing. The overlap is real, and the practical distinction is where you begin: with the question style, or with a written framework of what the job requires.
Choose the Competencies Before the Questions
Pick the competencies from the work, not from a list of admirable traits. Write down what the job does in a normal week, then ask which behaviors separate the people who do it well from the people who do it acceptably. Keep five or six. Cut everything else, however impressive it sounds.
The fastest route to an honest list is the person who currently does the job, or did it last. They can usually name the thing that breaks the role in about thirty seconds, and it is rarely the item at the top of the job description. If the role is new, write down the three problems you are hiring to solve and work backward to the behaviors that solve them.
Then define each competency in observable terms. What does it look like when someone has it, and what does its absence look like? Accountability is a slogan. Flagging a slipping deadline before it slips, rather than on the day, is a behavior you can score. The framework worksheet below turns each competency into that second form.
Fix the Framework Before You Meet Anyone
Competencies chosen after you have met a candidate you like tend to describe that candidate. Write the list, the weights, and the minimum acceptable score for each competency before the first interview, and get whoever else is interviewing to agree to it in writing. This one habit does more for hiring quality at a small business than any question you could add to the set, and it takes about an hour per role.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Start with the framework worksheet, always. After that, pick the sets that match where you are in the process: the screening call set for the first round, the question bank and the three-question-types set for the full interview, and the scorecard and probe card in the room itself.
Competency Framework Worksheet
Do this first
Turns the job into five or six competencies with observable behaviors, a weight, and a minimum score for each. Includes a worked example for accountability and a sign-off line you fill in before the first interview.
Core Competency Question Bank
Eight competencies
Three questions each for problem solving, accountability, communication, collaboration, customer focus, adaptability, planning, and learning. Every question carries why it is worth asking and what a 5 and a 2 sound like.
Three Question Types for One Competency
Behavioral, situational, technical
The structure that makes an interview competency-based rather than just behavioral: the same competency asked three ways, with worked examples and blanks for your own competencies.
Screening Call Set
Thirty minutes, three competencies
A first-round call that tests competencies instead of walking down the resume, with a minute-by-minute structure, probes, and a decision block so the shortlist rests on the same three answers.
Competency Scorecard
Anchored one to five
One set of written anchors used for every competency, space for evidence in the candidate’s own words, weighting for the competencies that count double, and a bar you set before you meet anyone.
Interviewer Probe Card
One page, face up
The four probes that convert a vague answer into evidence, the four answer types that need a different response, the questions to keep off the table, and a timing plan for a 45-to-60-minute interview.
6 Free Question Sets to Download
Six files rather than one, because a question bank you have to reorganize before every interview is a question bank you stop opening. Download all six as a single archive or take individual sets. Word format, free, no email form in the way.
Download All Six Sets
Framework worksheet, question bank across eight competencies, three question types, screening call set, anchored scorecard, and interviewer probe card.
Set 1: Competency Framework Worksheet
The one-hour piece of preparation that makes everything else work. Five or six competencies, each defined by what it looks like on the job and what its absence looks like, with a weight and a minimum score. Includes a worked example and a sign-off line.
Competency Framework Worksheet
COMPETENCY FRAMEWORK WORKSHEET
Role: __
Hiring manager: __
Date: _
DO THIS BEFORE YOU WRITE A SINGLE QUESTION
A competency-based interview only works if you decide what you are measuring
first. Fill this in once per role. It takes about an hour, and you reuse it for
every candidate and every future hire into the same job.
Step 1. List what the job actually does in a normal week.
Step 2. Ask which behaviors separate the people who do it well from the people
who do it acceptably.
Step 3. Keep the five or six that matter most. Cut the rest, however good they
sound on paper.
Step 4. Define each one in observable terms, then weight it.
•Commits to a date, then flags the slip early rather than at the deadline
•Closes the loop without being asked twice
What the absence of it looks like:
•Work goes quiet, and you find out it stalled when the customer calls
Weight: double (this is a small team, nobody is chasing people)
Minimum acceptable score: 3
SIGN-OFF
Competencies agreed by: __
Date fixed (before the first interview): __
Note: fix this sheet before you meet anyone. Competencies chosen after you like
a candidate tend to describe that candidate.
Set 2: Core Competency Question Bank
Three questions each for problem solving, accountability, communication, collaboration, customer focus, adaptability, planning, and learning. Every question states why it is worth asking, and most carry what a 5 and a 2 sound like.
Core Competency Question Bank (8 Competencies)
CORE COMPETENCY QUESTION BANK
Role: __
Interviewer: __
HOW TO USE THIS BANK
Pick the five or six competencies from your framework worksheet. Take two
questions from each. Ask the same questions, in the same order, of every
candidate for this role. Each question below carries why it is worth asking,
what a 5 sounds like, and what a 2 sounds like.
1. PROBLEM SOLVING AND DECISION MAKING
Q: Tell me about a problem you solved where the obvious fix would not have worked.
Why ask: separates people who diagnose from people who pattern-match.
A 5 sounds like: names the constraint, the options considered, the trade-off
accepted, and what happened afterward.
A 2 sounds like: a general description of being a problem solver.
Q: Walk me through a decision you made without enough information.
Why ask: small businesses rarely have complete data; this is the daily reality.
A 5 sounds like: states what was unknown, what they did to reduce the unknown
cheaply, and how they decided anyway.
A 2 sounds like: they escalated it and waited.
Q: Describe a time your first solution failed. What did you do next?
Why ask: recovery matters more than being right the first time.
A 5 sounds like: caught it early, owned it, and changed approach on evidence.
2. ACCOUNTABILITY AND FOLLOW-THROUGH
Q: Tell me about a commitment you were going to miss. How did you handle it?
Why ask: tests whether bad news travels early or late.
A 5 sounds like: flagged it before the deadline, proposed a revised plan.
A 2 sounds like: it was late because of somebody else.
Q: What is something that went wrong that was your fault?
Why ask: a candidate who cannot answer this either has not been trusted with
much or will not tell you when it happens here.
A 5 sounds like: a real, specific mistake with a real cost and a real fix.
Q: How do you keep track of what you owe people when nobody is checking?
Why ask: at a small company, nobody is checking.
3. COMMUNICATION AND INFLUENCE
Q: Tell me about a time you had to explain something technical to someone who
did not have the background.
Why ask: most friction in a small team is a translation problem.
A 5 sounds like: they remember the audience and adapted the explanation.
Q: Describe a time you disagreed with your manager. What did you say?
Why ask: you want the actual words, not the principle.
A 5 sounds like: raised it directly, once, with a reason, then committed.
Q: Tell me about a message you got wrong. How did you find out?
Why ask: tests whether they check for understanding or just transmit.
4. COLLABORATION ACROSS ROLES
Q: Tell me about working with someone whose priorities conflicted with yours.
Why ask: in a small business, everyone works across functions by default.
A 5 sounds like: they name the other side’s actual interest, not just their own.
Q: Describe a time you took on work that was not yours because it needed doing.
Why ask: the single most useful trait in a small team, and easy to verify.
Q: When did you last ask a colleague for help, and what for?
Why ask: candidates who never ask for help are usually not telling you
everything about how their projects went.
5. CUSTOMER AND CLIENT FOCUS
Q: Tell me about a customer you could not make happy.
Why ask: everyone has one; the answer shows where they place the line.
A 5 sounds like: they tried a real remedy, held a reasonable boundary, and
escalated at the right moment.
Q: Describe a time you told a customer no.
Why ask: service is not the same as agreement.
Q: What is the most useful thing you learned from a complaint?
Why ask: distinguishes people who absorb feedback from people who survive it.
6. ADAPTABILITY AND RESILIENCE
Q: Tell me about a change at work you disagreed with. What did you do?
Why ask: how someone handles a decision they did not make predicts the first
six months here better than enthusiasm does.
Q: Describe the busiest stretch you have had. How did you get through it?
Why ask: tests method under pressure, not stamina.
Q: What is a tool or process you had to learn quickly? How did you learn it?
Why ask: a small business changes tools often and trains nobody formally.
7. PLANNING, PRIORITIZATION, AND QUALITY
Q: Walk me through how you planned your last busy week.
Why ask: concrete, unrehearsed, and hard to fake.
A 5 sounds like: a real system, named, with what they dropped and why.
Q: Tell me about a time two things were both urgent. How did you choose?
Why ask: prioritization is a decision, not a feeling.
Q: How do you catch your own errors before someone else does?
Why ask: quality control is a personal habit at a company with no QA function.
8. LEARNING AND ROLE DEPTH
Q: What part of this job do you know least well, and how would you close the gap?
Why ask: honest self-assessment is rare and highly predictive.
A 5 sounds like: a specific gap and a specific plan, offered without prompting.
Q: Tell me about something you learned in the last year that changed how you work.
Q: Who taught you the most in your last job, and what did they teach you?
NOTES
__
__
Set 3: Three Question Types for One Competency
The structure that makes an interview competency-based rather than only behavioral: the same competency asked as a behavioral, a situational, and a technical question, with two worked examples and blanks for your own competencies.
Three Question Types for One Competency
THREE QUESTION TYPES FOR ONE COMPETENCY
Competency under test: __
WHY THIS SET EXISTS
A competency-based interview is not one style of question. For each competency
you can ask three kinds, and they fail in different ways:
BEHAVIORAL asks what the candidate actually did before. Strongest evidence,
but useless if they have never faced the situation.
SITUATIONAL asks what they would do in a scenario you describe. Works for
career changers and first-time hires, but rewards good talkers.
TECHNICAL asks what they know or can demonstrate. Verifiable, and the type
most small businesses skip when they should not.
Ask behavioral first. Fall back to situational when the candidate has no
relevant history. Use technical when the competency has a right answer.
WORKED EXAMPLE: HANDLING AN UPSET CUSTOMER
BEHAVIORAL
Q: Tell me about the angriest customer you have dealt with. What did you say?
Listen for: the actual words used, what they did first, and the outcome.
SITUATIONAL
Q: A customer calls about an order we shipped three days late. They want a
refund we cannot give. Walk me through the call.
Listen for: acknowledgement before explanation, a real alternative offered,
and a clear point where they would bring you in.
TECHNICAL
Q: Show me how you would write the follow-up email after that call.
Listen for: plain language, a specific commitment, and no blame shifting.
WORKED EXAMPLE: PLANNING AND PRIORITIZATION
BEHAVIORAL
Q: Tell me about a week when you had more work than time.
SITUATIONAL
Q: It is Friday. Two customers need something today and you can finish one.
How do you decide, and what do you tell the other one?
TECHNICAL
Q: Here is a list of eight tasks with deadlines and dependencies. Order them
and tell me what you would push.
BLANK BLOCKS FOR YOUR OWN COMPETENCIES
COMPETENCY: __
Behavioral:
Situational:
Technical:
COMPETENCY: __
Behavioral:
Situational:
Technical:
COMPETENCY: __
Behavioral:
Situational:
Technical:
RULE OF THUMB
One competency, one question type per interview round. Asking the behavioral and
the situational version of the same competency back to back teaches the
candidate the answer you want before they give it.
Set 4: Competency-Based Screening Call Set
A thirty-minute first round that tests three competencies instead of walking down the resume, with a minute-by-minute structure, ready-made probes, and a decision block so the shortlist rests on the same three answers from every candidate.
Competency-Based Screening Call Set (30 Minutes)
COMPETENCY-BASED SCREENING CALL
Candidate: __
Role: __
Interviewer: __
Date: _ Start: End:
PURPOSE
A first-round call that already tests competencies instead of walking down the
resume. Thirty minutes, three competencies, the same three for every candidate.
The point is to decide who reaches the full interview, not to make the hire.
STRUCTURE
0 to 3 min What the job is, what the process looks like, how long the call is
3 to 8 min Logistics: availability, location or on-site expectations,
compensation range confirmation, notice period
8 to 25 min Three competency questions, one per competency, with probes
25 to 30 min Candidate questions, and what happens next with a date
THE THREE QUESTIONS (CHOOSE ONE PER COMPETENCY)
COMPETENCY A: __
Q: ___
Probe if the answer is a "we" answer: What did you personally do?
Probe if there is no result: How did it end?
COMPETENCY B: __
Q: ___
Probe if the answer is hypothetical: Has that actually come up? Tell me about
that time.
COMPETENCY C: __
Q: ___
Probe for depth: What would you do differently now?
SUGGESTED SCREENING QUESTIONS THAT TRAVEL WELL
•Tell me about the part of your last job you were best at. How do you know?
•Describe a week where the plan fell apart. What did you do?
•What would your last manager say you needed to get better at?
•Why this role, at a company this size, now?
(Small business fit is a real competency. Some strong candidates want the
structure of a large employer and will be unhappy here within a quarter.)
DECISION
Advance to full interview: [ ] Yes [ ] No [ ] Hold
One set of written anchors applied to every competency, space for evidence in the candidate's own words, weighting for the competencies that count double, and a bar you set before you meet anyone you like.
Competency Scorecard (Anchored 1 to 5)
COMPETENCY INTERVIEW SCORECARD
Candidate: __
Role: __
Interviewer: __
Date: _
THE ANCHORS (THE SAME FOR EVERY COMPETENCY)
5 Specific example, clear personal action, measurable or verifiable result,
and a reflection on what they would change. Would handle this here on day one.
4 Specific example with a clear action and outcome. Some detail missing, and
the answer held up under one probe.
3 A real example, but generic in places. Needed probing to get the action or
the result. Acceptable with support.
2 Described what they generally do rather than a specific time. The action was
collective ("we") and the result was absent.
1 No example, or an example that showed the opposite behavior. Deflected,
blamed, or could not answer after two probes.
SCORING
COMPETENCY 1: __ Weight: [ standard / double ]
Score: [ 1 2 3 4 5 ]
Evidence, in the candidate’s words: _____
______
COMPETENCY 2: __ Weight: [ standard / double ]
Score: [ 1 2 3 4 5 ]
Evidence: ___
COMPETENCY 3: __ Weight: [ standard / double ]
Score: [ 1 2 3 4 5 ]
Evidence: ___
COMPETENCY 4: __ Weight: [ standard / double ]
Score: [ 1 2 3 4 5 ]
Evidence: ___
COMPETENCY 5: __ Weight: [ standard / double ]
Score: [ 1 2 3 4 5 ]
Evidence: ___
COMPETENCY 6: __ Weight: [ standard / double ]
Score: [ 1 2 3 4 5 ]
Evidence: ___
DECISION
Weighted total: ______ Bar set before the first interview: ______
Any competency below its minimum? [ ] Yes (which: ___) [ ] No
Recommendation: [ ] Strong yes [ ] Yes [ ] No [ ] Strong no
Signature: __
RULES THAT MAKE THE SCORE MEAN SOMETHING
•Score each answer before the next question starts, not after the interview.
•Write evidence in the candidate’s words, not your impression of them.
•Every interviewer scores alone before anyone discusses the candidate.
•Set the bar and the per-competency minimums before you meet anyone you like.
•Keep completed scorecards with your other hiring records.
Set 6: Interviewer Probe Card
One page to keep face up on the table: the four probes that convert a vague answer into evidence, the four answer types that need a different response, the questions to keep off the table, and a timing plan.
Interviewer Probe Card and Question Boundaries
INTERVIEWER PROBE CARD
One page. Keep it face up on the table during the interview.
THE FOUR PROBES THAT DO MOST OF THE WORK
1. "What did you personally do?"
Use when the answer arrives in the plural. Most incomplete answers are "we"
answers, and this one question converts them into evidence.
2. "How did it end?"
Use when there is a story but no result. A candidate who cannot say how it
turned out was usually not close enough to the outcome to own it.
3. "Walk me through the first thing you did."
Use when the answer is all context and no action. Sequence forces specifics.
4. "What would you do differently?"
Use on strong answers, not weak ones. It separates a rehearsed story from a
reflected one.
FOUR ANSWER TYPES AND WHAT TO DO
THE REHEARSED STORY
Polished, well structured, arrives instantly. Not a red flag by itself.
Response: ask for a second example of the same competency. The prepared story
is usually the only one.
HYPOTHETICAL DRIFT
You asked what they did; they answer what they would do.
Response: "Has that actually happened to you? Tell me about that time."
THE TEAM ANSWER
Everything is "we". Response: probe 1, twice if needed. If the personal action
never appears, score it as a 2 and move on.
THE NON-ANSWER
Two probes, still nothing. Response: stop, score it, and go to the next
question. Do not coach them toward the answer you want.
KEEP THE QUESTIONS ON THE JOB
Ask about the competencies you defined and the work the job involves. Do not ask
about age, race, color, religion, national origin, sex, pregnancy or family
plans, disability, or genetic information, and do not drift there through small
talk about family, hometown, or weekend plans. You may ask whether someone can
perform the essential functions of the job and whether they are legally
authorized to work in the United States.
This is general information, not legal advice.
TIMING FOR A 45 TO 60 MINUTE INTERVIEW
5 min Set up: the role, the format, and that you will be taking notes
35 min Five or six competency questions at five to seven minutes each,
including probes and scoring
10 min Candidate questions
5 min Next step, with a date
Cut the number of competencies before you cut the probes. Four competencies
asked properly beat eight asked in a hurry.
What a Complete Answer Contains
A complete answer has three parts: a specific time, what the candidate personally did, and how it ended. Miss any one of them and you have a story rather than evidence. Most answers arrive missing at least one part, which is why the probes matter more than the questions.
A complete answer
A specific time, not a general practice
What the candidate personally did
How it ended, in verifiable terms
Probes worth memorizing
What did you personally do?
How did it end?
What would you do differently?
Score it as evidence
Write the candidate’s words, not your impression
Score before the next question starts
Every interviewer scores alone first
Red flags
Every example arrives in the plural
No outcome, ever, on any story
The same single story answers three competencies
The single most valuable follow-up is some version of what did you personally do? Incomplete answers almost always arrive in the plural, and that one question converts a team story into something you can score. The second most valuable is how did it end, because a candidate who cannot say was usually not close enough to the outcome to own it.
Watch for the candidate who answers three different competencies with the same single story. It is not always a problem, but it usually means one strong experience is carrying the entire interview, and the STAR pattern that made the story sound complete is hiding how thin the rest is. Ask for a second example of the competency that matters most.
How to Run the Interview
Running it well is mostly logistics: the same questions in the same order, probes ready, and scoring done in the room rather than afterward. The sequence below fits a 45-to-60-minute interview and works whether one person or three are in the room.
Stage
Time
What to do
Set up
5 min
The role, the format, and that you will be taking notes
Competency questions
35 min
Five or six at 5 to 7 minutes each, including probes and scoring
Candidate questions
10 min
What they ask reveals how they think about the job
Close
5 min
The next step, with a date you will actually meet
Ask the behavioral version first and fall back to the situational version only when the candidate has no relevant history. Asking both versions of the same competency back to back teaches them the answer you want before they give it, which is the quiet way a structured interview turns back into a conversation.
If several people interview, split the competencies rather than repeating them. Three interviewers each covering two competencies properly beats three interviewers all asking about communication, and the candidate notices the difference. Running the interview this way also shortens the process, because nobody needs a second round to cover what got missed.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Score each answer against written anchors, before the next question starts. Anchors are short descriptions of what a 5, a 3, and a 2 actually sound like, written once and applied to every competency, so that two interviewers mean the same thing by a 4.
The anchors in the scorecard above are built around completeness rather than charm. A 5 is a specific example with a clear personal action, a verifiable result, and a reflection on what the candidate would change. A 2 is a description of what the person generally does, stated in the plural, with no outcome. Charisma is not on the scale anywhere.
Same Questions, Same Order, Same Rating Scale
The US Office of Personnel Management defines a structured interview as an assessment method that measures job-related competencies by systematically asking about behavior in past experiences or proposed behavior in hypothetical situations, in which all candidates are asked the same predetermined questions in the same order and all responses are evaluated using the same rating scale and standards for acceptable answers. Those two rules are the entire method. Everything else on this page is a way of making them practical for a business without a recruiting team.
Two more rules make the number mean something. Write the evidence in the candidate's words rather than your impression of them, and have every interviewer score alone before anyone discusses the candidate. Independent scoring is the cheapest defense against the person who spoke first anchoring the whole decision, and it costs nothing but the discipline to stay quiet in the hallway.
Set the pass bar in advance too. Decide the weighted total you need and the minimum acceptable score per competency before the first interview, and record both on the framework worksheet. A bar set after you meet a candidate you like is not a bar, and an evaluation form filled in from memory a day later is a recollection rather than a record.
Fair, Legal, and Structured Interviewing
A competency-based interview is easier to defend than a conversation, because every question traces back to a documented requirement of the job. That protection depends entirely on the competencies coming from the work, so any competency you cannot tie to something the person will actually do should be cut from the framework.
The same structure that makes the interview accurate also reduces bias, because it removes the interviewer's freedom to ask the candidate they like about strengths and the candidate they do not about gaps. Consistency is not bureaucracy here. It is what makes a comparison between two people mean anything at all.
Tie every competency to the job
A competency-based interview is easier to defend than a conversation, because each question traces back to a documented requirement of the job. That protection only holds if the competencies came from the work. If a competency cannot be linked to something the person will actually do, drop it. Federal anti-discrimination law, enforced by the EEOC, prohibits basing hiring decisions on protected characteristics, and a competency framework built around the work is the cleanest way to keep questions on the right side of that line. Write the framework down and keep it with the scorecards. This is general information, not legal advice.
Same questions, same order, every candidate
Consistency is the whole method. Every candidate for a role gets the same competencies, the same questions, in the same order, scored against the same anchors. This is what makes the comparison real: if one candidate got three easy questions and another got five hard ones, the scores mean nothing. It also removes the most common source of drift, which is the interviewer who asks the candidate they like about their strengths and the candidate they do not about their gaps. Deciding the set in advance takes that choice away from your mood on the day.
Watch the pattern across candidates, not just each interview
A selection process can be built from job-related questions and still produce lopsided outcomes. The Uniform Guidelines on Employee Selection Procedures give federal enforcement agencies a rule of thumb known as the four-fifths rule: a selection rate for any race, sex, or ethnic group below eighty percent of the rate for the highest group is generally treated as evidence of adverse impact. Most small businesses hire in numbers too small for that arithmetic to say much, but the habit is the point. Keep the scorecards, and look at who advances over a year rather than one hire at a time.
Keep the small talk on the job too
The riskiest moment in most interviews is the friendly two minutes at the start. Questions about family plans, where someone is originally from, their age, their religious observance, or a health condition create legal exposure even when they are meant warmly, and they push the conversation away from evidence. Open with the role, the format, and how long the interview will take instead. A competency-based structure helps here as well: when you have five questions to get through and score, there is less unstructured time for the conversation to drift somewhere it should not go.
Watch the Pattern, Not Only the Interview
Job-related questions can still produce lopsided outcomes across a year of hiring. The federal Uniform Guidelines on Employee Selection Procedures treat a selection rate below four-fifths of the rate for the highest group as evidence of adverse impact, and the EEOC prohibits basing decisions on protected characteristics. Most small businesses hire in numbers too small for that arithmetic to say much, but keeping the scorecards and reviewing who advances is a habit worth building early. This is general information, not legal advice.
Keep the small talk on the job as well. The friendliest two minutes of an interview is where questions about family plans, hometown, or health tend to appear, and they create exposure even when they are meant warmly. Open with the role and the format instead. There is a longer list of questions to avoid if you want the detail.
Competency Interviewing Without an HR Department
At a large employer, the competency framework arrives from a central team and the interviewer runs a script somebody else wrote. At a small business, there is no framework unless the owner makes one, and no second opinion unless the owner asks for it. That is a real disadvantage, and it is also entirely fixable in about an hour per role.
Nobody wrote the competencies down, so every interviewer measures something different
At a large employer, a competency framework arrives from a central team and the interviewer just runs the script. At a small business, there is no framework unless somebody makes one, so two interviewers walk out of the same room with two different reasons to hire. The framework worksheet above exists to close that gap in about an hour. Five or six competencies, defined in observable terms, agreed before the first candidate, and reused for every hire into that job afterward.
The interview is squeezed between everything else you do that day
Founders interview between customer calls, and preparation is the first thing that gets dropped. That is exactly how an interview turns into a chat about a resume. A fixed question set fixes it, because the preparation happened once, weeks ago, and today you only have to open the file. Four competencies asked properly beat eight asked in a hurry, so cut the list rather than the follow-up probes when the calendar tightens.
One strong impression decides the hire, and the paperwork starts from nothing
With a small hiring team, the person who spoke first usually anchors the decision. Independent scoring against written anchors is the cheapest fix available. After that, the job shifts from evaluating to hiring well: the offer, the paperwork, and a first few weeks that actually land. FirstHR fits that side for a small business: send the offer for e-signature, run the new hire paperwork and onboarding workflow, and keep the signed documents and hiring records on the employee’s profile. Applicant tracking is coming soon to FirstHR.
The pattern that keeps this sustainable is simple: do the preparation once per role rather than once per candidate. The framework worksheet, the question set, and the anchors are reused for every applicant and every future hire into the same job, which turns an hour of work into a permanent asset. The interview stops being something you prepare for and becomes something you simply run.
From Interview to Hire
Once the scores are in and the decision is made, the work shifts from evaluating to hiring well: an offer in writing, the new hire paperwork, and a first few weeks built around the same competencies you just measured. A structured interview followed by an unstructured first month wastes most of what you learned.
Fix the framework
Five or six competencies with observable behaviors, weights, and minimum scores, agreed before you meet the first candidate.
Ask and score in the room
Same questions in the same order, probes ready, each answer scored against the anchors before the next question starts.
Make the offer in writing
Confirm the role, pay, and start date, and send it for e-signature so the record of the hire is clean from day one.
Onboard against the same competencies
Give the new hire a structured first few weeks built around the competencies you hired for, so the ramp matches the interview.
FirstHR connects the offer, the e-signature, the paperwork, and the onboarding workflow in one place, and keeps the signed documents and hiring records on the employee's profile, so a small business can run the whole hiring-to-onboarding sequence from one system. Applicant tracking is coming soon to FirstHR. There are more hiring templates in the same library, including a general job description template to write the posting this interview is testing against.
If the role you are hiring for is an HR one, the HR manager job description pairs naturally with this question set, and the job fit questions cover the small-business-specific part of the decision that a competency framework alone does not reach.
Key Takeaways
A competency-based interview starts with a written framework of what the job requires, not with a list of clever questions.
Choose five or six competencies from the actual work, define each in observable terms, and fix the list before you meet a candidate.
Use behavioral questions for candidates with relevant history, situational for those without, and technical where the competency has a right answer.
A complete answer names a specific time, what the candidate personally did, and how it ended; probe until all three appear.
Score each competency 1 to 5 against written anchors in the room, alone, before anyone discusses the candidate.
Set the pass bar and the per-competency minimums in advance, and keep the completed scorecards with your hiring records.
Frequently Asked Questions
What are competency-based interview questions?
Competency-based interview questions are questions written to measure a specific, job-related competency rather than to explore a resume. A competency, in the definition the US Office of Personnel Management uses, is a measurable pattern of knowledge, skills, abilities, behaviors, and other characteristics needed to perform a work role successfully. The method has three parts. First you decide which five or six competencies the job genuinely requires. Then you write questions that surface evidence for each one, usually asking for a specific past example. Finally you score every candidate against the same written anchors. What makes an interview competency-based is not the wording of the questions but the framework underneath them: the same competencies, the same questions, the same scale, for everyone who applies for that role.
What is the difference between competency-based and behavioral interview questions?
Behavioral questions are one type of question used inside a competency-based interview, not a separate method. A behavioral question asks what the candidate actually did in a past situation, which is the strongest single form of evidence. A competency-based interview decides which competencies to measure first, then draws on three question types to measure each one: behavioral for past evidence, situational for candidates without relevant history, and technical for competencies that have a right answer. In everyday use the two terms are often swapped, and outside the United States competency-based is the more common label for the same practice. The practical difference is where you start. Behavioral interviewing starts with the question style. Competency-based interviewing starts with a written framework of what the job requires.
How many competencies should you test in one interview?
Five or six for the full interview, and three for a screening call. Each competency needs one question plus two or three follow-up probes, which takes five to seven minutes once you include the time to score the answer. In a 45-to-60-minute interview that leaves room for the candidate to ask their own questions and for you to explain the next step. Interviewers who plan ten competencies either rush every answer or abandon half the list partway through, and both outcomes destroy the comparison between candidates. Depth is worth more than coverage here: a competency asked with real probes gives you usable evidence, while a competency asked once and accepted at face value gives you a story the candidate has told before. Cut the list before you cut the probes.
How do you choose the right competencies for a role?
Start from the work, not from a list of admirable traits. Write down what the job actually does in a normal week, then ask which behaviors separate the people who do it well from the people who do it acceptably. Talking to whoever currently does the job, or did it last, is the fastest route to an honest answer. Keep the five or six that matter most and cut the rest, however good they look on paper. Then define each one in observable terms: what it looks like when someone has it, and what the absence of it looks like. Weight the one or two that matter most, and set a minimum acceptable score for each. Fix all of this before you meet a candidate, because competencies chosen after you like someone tend to describe that person.
How do you score competency-based interview answers?
Use one set of written anchors applied to every competency, usually on a scale of one to five. A 5 is a specific example with a clear personal action, a verifiable result, and a reflection on what the candidate would change. A 3 is a real example that needed probing before the action or the outcome appeared. A 2 is a description of what the person generally does rather than a specific time, with the action stated as we and no result. Score each answer before the next question starts, write the evidence in the candidate’s own words rather than your impression of them, and have every interviewer score alone before the group discusses anyone. Set the pass bar and the per-competency minimums before the first interview, not after you meet a candidate you like.
Are competency-based interviews better than unstructured interviews?
Yes, for both accuracy and fairness. A structured interview, in the definition the US Office of Personnel Management publishes, asks all candidates the same predetermined questions in the same order and evaluates every response using the same rating scale and standards for acceptable answers. That consistency is what makes the comparison between two candidates mean anything. An unstructured conversation measures rapport, and rapport correlates with similarity to the interviewer rather than with performance in the job. Structure also gives you a record: a written framework, the same questions for everyone, and scorecards you can point at if a hiring decision is ever questioned. The cost is about an hour of preparation per role, reused for every candidate and every future hire into the same job.
What questions should you avoid in a competency-based interview?
Avoid anything that probes a characteristic protected under federal law, which the EEOC enforces: age, race, color, religion, national origin, sex, pregnancy or family plans, disability, or genetic information. That includes the friendly version, so keep small talk about family, hometown, and weekend plans out of the room as well. You may ask whether someone can perform the essential functions of the job and whether they are legally authorized to work in the United States. Beyond the legal line, drop competencies that cannot be tied to the actual work, brain-teaser questions that measure nothing, and any question you only ask some candidates. If a question does not map to a competency in your framework, it is not earning its place in the interview. This is general information, not legal advice.
Can a small business run competency-based interviews without an HR department?
Yes, and the preparation is smaller than most owners expect. The one-time work is a framework worksheet naming five or six competencies with observable behaviors, a weight, and a minimum score for each, which takes about an hour and is reused for every candidate and every future hire into that job. After that, each interview is opening the file, asking the same questions in the same order, and scoring against the anchors while the answers are fresh. The parts that usually go wrong at a small company are all preparation problems: no written competencies, no fixed question set, and a decision anchored by whoever spoke first. Downloadable sets and a scorecard remove most of that. Applicant tracking is coming soon to FirstHR, and the offer, paperwork, and onboarding after the decision already run there.
