What competency-based interviews are and why they work
Competency-based interviews are a structured evaluation method where specific examples of past behavior are requested to predict future performance. The premise is well supported by organizational psychology research: past behavior in similar situations is the best available predictor of future behavior.
The alternative, hypothetical questions ("what would you do if...?"), measures something different: the candidate's ability to construct plausible answers in the moment. A candidate with limited experience can give an excellent hypothetical response. The competency-based method makes that kind of answer much harder to fake because it requires specific details that can be probed and verified.
The STAR method: how to structure questions and evaluate responses
STAR is the standard framework for competency-based interviews:
- Situation: the context the candidate was in.
- Task: the specific responsibility they had in that situation.
- Action: what the candidate concretely did (this is where evaluation should focus).
- Result: what happened and what the candidate learned from the experience.
The most common interviewer error is accepting responses that never reach the "Action" level. When a candidate says "my team solved the problem" or "we worked together to reach the goal," they are using the plural to avoid specifying their individual contribution. The follow-up question should always be: "What did you specifically do in that situation?" Candidates who cannot answer that question precisely either were not as involved as implied, or lack the self-awareness to articulate their own contribution. Both are relevant signals.
Question bank for key competencies in the Latin American market
Influence without authority
"Tell me about a time you needed someone who did not report to you to do something they initially did not want to do. How did you approach the situation and what happened?"
Decision-making under uncertainty
"Describe a situation where you had to make an important decision with incomplete information. What was the decision, how did you arrive at it and what resulted?"
Handling failure
"Tell me about a project or initiative you were responsible for that did not go as expected. What happened and what would you do differently?"
Prioritization under pressure
"Describe a period when you had more work than you could handle. How did you decide what to prioritize and what consequences did that have?"
The most common mistakes in competency-based interviews
Telegraphing the expected answer
"We value initiative a lot here, can you tell me about a time you took initiative?" tells the candidate exactly what you want to hear. Questions should be formulated without signaling which behavior you are looking for.
Accepting generic responses
"I always look for ways to solve problems" is not a STAR response. It is a character description that cannot be evaluated or verified. The response you are looking for has a specific situation, a specific action and a measurable result. If you do not have it, keep probing.
Not exploring inconsistencies
If the timeline does not add up, the result is vague, or the candidate keeps using the plural without specifying their role, those are signals worth exploring. "You mentioned the project ended successfully. What specific metric do you use to define that success?" is a legitimate follow-up question that separates prepared answers from real experiences.