MasterMap.pl The map of vacancies in Europe and the world
+ Add an advert +
HR-wisdom

Structured Interview: How to Evaluate Candidates Fairly

👷Author: adminAugust 7, 2026💬 0
Structured Interview: How to Evaluate Candidates Fairly

Why gut-feeling interviews don’t work

“The first candidate seemed great — very confident.” “The second one was kind of quiet.” “The third one was fine, but didn’t feel like our person.” This is a familiar scene, and the real problem is not subjectivity as such — it’s that the three candidates effectively went through three different interviews. One got detailed questions about sales, another about reasons for leaving a previous job, and with the third, half the time went into discussing a former employer. After an interview like that, there is no honest way to answer “who is actually the better fit for this role”: the same traits were never measured the same way.

A structured interview solves exactly this problem. Every candidate goes through a comparable process and is scored against rules set in advance, not against the interviewer’s overall impression.

If you are looking for a job, check which country has vacancies that may interest you

🔥 Urgent job: Heat pump electrician in Germany Bremen
18.00 € / hr (net)
Apply now

What a structured interview actually is

The formula is simple: structured interview = same criteria + same core questions + same rating scale + documented evidence. The structure is built before the candidate walks in, not improvised during the conversation.

In advance, you need to define: what the role actually requires, which traits genuinely drive job performance, which question tests each of them, what counts as a strong versus weak answer, how points are assigned, and which criteria are mandatory versus compensable by other strengths.

Criteria first, questions second

A common mistake is starting preparation with a list of questions like “tell me about yourself” or “where do you see yourself in five years.” The right order is different: first answer the question “what does a successful person in this role actually need to do,” and only then let the criteria and questions grow out of that answer.

A practical trick: instead of asking “what makes a good sales manager,” define which observable actions, three months after hire, would tell you the person is doing well.

Three categories of criteria

Criteria are easiest to manage in three groups.

  • Professional knowledge — what the person knows: tools, methodologies, regulations, technologies.
  • Professional skills — what the person can do: negotiate, analyze data, prioritize tasks, manage conflict.
  • Work behavior — not an abstract “personality,” but concrete behavior the job requires: accountability, initiative, adaptability to change, teamwork.

Phrases like “pleasant person,” “strong personality,” “our kind of person,” or “culturally fits” are practically impossible to operationalize — they can’t be verified or compared across candidates.

Turning personality into observable behavior

A rating of “communication — 5 points” measures nothing, because it’s unclear what exactly is being scored. It’s better to define the criterion as observable behavior — for example, “the candidate clarifies the need, asks questions, adapts the explanation to the listener, checks for understanding, responds appropriately to objections.” The same applies to “accountability”: instead of a general rating, look for evidence that the candidate plans deadlines, flags delay risk early, proposes a solution, and owns their own mistakes.

Must-have versus nice-to-have

Before the interview, split criteria into two more groups. Must-have — without this, the person simply cannot do the job: a required driving license category, a mandatory language, experience with a specific type of accounting. Nice-to-have — desirable, but learnable after starting: experience with your specific CRM or your specific industry. This split protects a strong candidate from being rejected just because they “never used this exact tool,” even after five years of solid work in a comparable one.

Core and follow-up questions, and the STAR method

The core of the interview is 6–10 mandatory questions asked of every candidate — without this, comparison isn’t fair. Around them, you can freely ask follow-up questions: what exactly did you personally do, what was the result, how was it measured, what would you do differently.

Two question types work best. Behavioral questions look at real past experience: “tell me about a time a project started falling significantly behind schedule.” Situational questions present a hypothetical work case: “a client demands a new feature three days before launch, and engineering warns it risks the release — what do you do?”

Answers are easiest to capture with the STAR method: Situation (what happened), Task (what the candidate was responsible for), Action (what they actually did), Result (what came out of it). Pay special attention to Action: candidates often say “we solved the problem,” and asking “what did you personally do” can completely change the score. “Tell me about yourself” can stay as an icebreaker, but shouldn’t be a scoring criterion — the further a question sits from the actual work, the harder the answer is to interpret.

Evidence, not impressions

After an interview, avoid writing “nice guy,” “very confident,” or “didn’t like the energy.” Write something specific instead: “independently ran 15 projects,” “raised conversion rate from 2.1% to 3.4%,” “couldn’t provide an example of a conflict with a colleague.” Before assigning a score, check whether you can finish the sentence “I’m giving this a 4 because the candidate showed that…” If you can’t finish it, the score is probably based on an impression rather than evidence.

A rating scale with behavioral anchors

A universal 1–5 scale works like this: 1 — no evidence of the competency, 2 — weak level, needs significant support, 3 — sufficient for the role, 4 — strong, confident independent application, 5 — expert level, the candidate systematically improves the approach. It’s far more precise, though, to build behavioral anchors for each specific criterion: for “problem solving,” a 3 means the candidate identifies the cause and considers several options, while a 5 also means they improve the process and prevent the problem from recurring.

Weighting criteria and knockout criteria

Not every competency matters equally: for a project manager, schedule and risk management might each carry 20% weight, while tool proficiency carries just 10%. The final score is the sum of score times weight, and the weights are set before the interview — not after a specific candidate turns out to be likeable.

It’s also worth defining knockout criteria — competencies that a high overall score can’t compensate for. A manager might score high on strategy and commercial thinking, but if the role requires managing a team of thirty and they score a 1 on team management, the average can still look strong — which is a real risk unless you set a rule in advance, such as “minimum score on team management is 3.”

Avoiding cognitive bias

The halo effect happens when one striking trait — a well-known employer, a prestigious degree, charisma — makes the interviewer unconsciously inflate scores on other criteria that were never actually tested. Similarity bias is an unconscious preference for candidates who studied at the same school or worked at a similar company: “we instantly clicked” is a pleasant fact, not evidence of job capability. Confidence bias mistakes a confident delivery for competence, even though a candidate can sound confident and be wrong, or sound cautious and be highly competent.

The best defense against all three is independent scoring: each interviewer fills out a scorecard on their own, and only then does the discussion begin. When scores diverge sharply, don’t just average them — ask what evidence backs each score. Often it turns out the interviewers were evaluating different things entirely.

A ready-to-use Interview Scorecard

Below is a universal structure you can adapt to any specific role.

  • Competency, weight in percent, core question, evidence from the answer, score from 1 to 5.
  • A separate knockout criteria block marked “met / not met.”
  • A section for “key risks” and “confirmed strengths.”
  • A final weighted score and a decision: strong hire, hire, borderline, no hire, strong no hire.

The rule is simple: score every criterion first, and only then base the decision on those scores — never the other way around.

Three ready-made scenarios

For high-volume hiring (for example, a warehouse worker), the interview can take 10–15 minutes and should check shift availability, discipline, understanding of instructions, and reaction to one’s own mistake. For an office role (for example, a junior specialist), check work organization, reaction to a weak result, and the ability to learn quickly. For a manager, the key questions cover managing an underperforming employee, an unpopular decision, and their own management mistake: a weak manager usually answers “there probably weren’t any serious mistakes,” while a strong one can walk through the full chain — decision, mistake, consequences, lesson, process change.

Candidates should be compared against the pre-set job profile, not against each other — this matters especially when interviews happen on different days, since otherwise the last candidate is effectively competing against someone the interviewer barely remembers.

The legal angle

In the EU, equal treatment in employment is a legal principle, and discrimination based on gender, age, disability, ethnic origin, religion, or sexual orientation is prohibited. The practical takeaway for phrasing questions is simple: instead of “you have young kids, can you stay late,” ask every candidate the same question about the actual job requirement — “this role needs work until 8 PM twice a month, can you work that schedule.” That checks the same requirement without probing anyone’s personal situation.

Where recruiters find candidates

Some of the candidates you invite to a structured interview arrive through the mastermap.pl vacancy map — a platform where each vacancy is shown alongside related services such as nearby housing, legalization help, and legal support. It’s worth factoring this into how you build your questions:

  • Candidates who search for Warsaw jobs for women cleaning tend to ask first about the shift schedule and commute — worth covering right at the start of the interview.
  • If the role includes housing, some candidates come specifically through Jobs in Warsaw with Accommodation searches, so it helps to have concrete questions about living conditions ready rather than leaving them for later.
  • Candidates from Jobs in Poland for Moldovans searches often need clarity on required documents and permits early on — worth building into the interview checklist.
  • Many applicants, especially students and candidates with no prior experience, look for Easy Jobs in Europe or Work in Europe for Free — meaning roles with no fees charged to the candidate; being upfront about that at the interview stage builds trust fast.
  • For roles paid from abroad, it helps to explain up front how Salary for Work from Abroad is actually calculated — that removes a good share of questions before the first call even ends.
  • It’s also useful to keep an eye on broader market context: a look at Where in Europe People Work Least helps set realistic, evidence-based expectations with candidates about workload and schedule.
  • For frontline roles, many candidates search Work in Poland as a Laborer — situational questions about following instructions and owning a mistake, covered earlier in the high-volume hiring scenario, work particularly well with this group.

About mastermap.pl

mastermap.pl is Master Map, a Europe-wide vacancy map where recruiters post job openings, with related services shown right next to each listing: housing close to the workplace, local language courses, legal and legalization services. Vacancies on the map can be filtered — with accommodation included, for women, for men, urgent, with fast-track processing — or you can simply search a job title and see which city or country already has it open. Candidates contact the recruiter directly, with no extra fees charged by the platform, which keeps this sourcing channel transparent and predictable for a hiring team.

Conclusion

The point of a structured interview isn’t to figure out whether you like the candidate — it’s to gather enough comparable evidence to predict whether they can actually do the job. This doesn’t remove the recruiter’s professional judgment; it changes the order it’s applied in: not impression first and arguments second, but evidence first, decision second.

💬

Comments 0

All comments are published after review.

No comments yet. Be the first!