Interviews are the most expensive step in hiring: a wrong decision can result in months of salary, training, and productivity losses. Yet, most interviews still proceed as casual conversations, with decisions hinging on the interviewer's impression of the day. In this article, we explain methods that transform interviews from subjective impressions to comparable evaluations.
What is a structured interview?
A structured interview is a format where the same questions are asked in the same order to each candidate, with answers scored on a predefined scale. Compared to free-form conversations, its biggest advantage is comparability: when you listen to five candidates through the same questions, you evaluate them not by "who was more likable," but by "who demonstrated this competency with concrete examples."
In practice, it consists of three components:
- Question set: Questions prepared for the 5-8 competencies truly required for the position.
- Scoring scale: A 1-5 scale for each question, with written explanations of what each score means.
- Evaluation form: A short form filled out while memories are fresh, right after the interview.
STAR method: turning stories into evidence
Candidates can easily claim "I'm good at teamwork." The STAR method connects this claim to a specific event. You ask the candidate to explain all four components:
- S (Situation): When, where, and in what context did the event occur?
- T (Task): What was the candidate's responsibility in that situation?
- A (Action): What exactly did they do? (Insist on personal contribution if they say "we did.")
- R (Result): What was the outcome, preferably with numbers?
Example question: "Can you describe a situation where you had to reprioritize under time pressure in a project?" If the answer lacks dates, figures, and personal actions, you're likely hearing a general claim.
Examples of competency-based questions
Select questions based on the competencies required for the position; clichéd questions ("Where do you see yourself in five years?") don't produce distinguishing information.
- Problem-solving: "Describe a situation where you encountered an unexpected error and had to find the cause on your own."
- Learning speed: "What was a subject you had to learn from scratch in the last year, and how did you learn it?"
- Collaboration: "How did you proceed in a situation where you disagreed with a colleague on a technical issue?"
- Responsibility: "Can you describe a decision you weren't satisfied with and what you changed afterward?"
- Prioritization: "When you had three urgent tasks at the same time, what did you postpone and why?"
Five common interview mistakes
- Locking onto first impressions: Judgments formed in the first two minutes turn the next forty into a confirmation search. Scoring by question helps break this.
- Similarity bias: Automatically perceiving a candidate from the same school, city, or interest area as more competent.
- Not allowing the candidate to speak: If the interviewer talks most of the time, no evaluative data is gathered.
- Delaying notes: When three interviews are conducted on the same day, details get mixed up. Notes should be written as the interview ends.
- Not providing feedback: A candidate who receives no response remembers the process and the company negatively, which directly impacts employer branding.
Before the interview: bringing the right candidates to the table
No matter how good your interview technique is, if the pool of candidates is weak, the outcome won't change. Therefore, the job ad must reflect the real requirements, applications should be collected in one place, and preliminary screening should be consistent. In a setup where applications are scattered across email inboxes, missing the best candidate is not a technical issue but a statistical result.
A candidate tracking system that follows applications step by step makes it visible where each candidate stands and links interview notes to the candidate's record. This way, two weeks later, there's a written answer to "why did we reject this candidate?"
Frequently asked questions
How long should an interview last?
For a competency-based initial interview, 35-45 minutes is sufficient for most positions. Plan the time according to the number of questions: each STAR question takes an average of 6-8 minutes with follow-up questions.
How many people should participate?
Two interviewers are the ideal balance: one asks questions, the other takes notes and scores independently. More than three people put unnecessary pressure on the candidate and lower the quality of answers.
Should technical tests be before or after the interview?
A short pre-test saves time before the interview; however, the test duration should not exploit the candidate's unpaid effort. The return rate drops significantly for assignments exceeding an hour.
Next step: Once you've written your interview questions, set up a system where you can evaluate candidates step by step on the same screen. In the ProCvLab company panel, you can publish job ads, track applications on the dashboard, and leave notes for each candidate.