# Recruitment: Reviewing Applications Against Role Criteria

Go beyond the CV: compare role requirements, declared experience, and working conditions to prepare a more useful recruitment interview.

- Canonical URL: https://www.harmate.com/en/blog/predictive-recruitment-why-matching-beats-simple-selection
- Author: Harmate Team
- Published: 2025-12-08
- Updated: 2026-10-12T02:56:24.038925+00:00
- Language: en

## Content

# Recruitment: Reviewing Applications Against Role Criteria

A CV, cover letter, or questionnaire response contains statements about a person’s experience and work history. Those statements can help prepare a structured review. They do not reveal someone’s personality, prove a skill on their own, or predict how they will perform in a particular team.

To compare applications carefully, start with the work the role requires. State the job-related criteria, record what each application contributes as evidence, separate observations from interpretations, and identify what still needs to be checked with the person. A human remains responsible for the hiring decision under the process that applies.

## Start with the work, not an ideal profile

Before reviewing applications, turn the role description into a short set of observable criteria that matter to the work. For each one, clarify:

- what is required on entry;
- what can be learned after joining;
- what information could support the criterion in an application or interview;
- the actual working conditions the person would need to meet.

Avoid vague labels such as “good fit,” “dynamic personality,” or “strong team culture.” They do not say what the work requires and can let a subjective impression stand in for a criterion. Describe the work situation instead, such as “explain an analysis to non-specialist colleagues” or “coordinate shared work against agreed deadlines.”

For comparable interview questions, the [U.S. Office of Personnel Management’s guidance on structured interviews](https://www.opm.gov/policy-data-oversight/assessment-and-selection/structured-interviews/) describes a method built around job-related competencies and questions set in advance. Employment rules vary by jurisdiction; use the applicable local guidance as well.

## Read a contribution without overstating it

A contribution is an item in an application that can be connected to a criterion. It might be a described experience, a work sample, a qualification, or an answer to a question. Record its source and context, then state what it supports without extrapolating.

| Role criterion | Information provided | What it supports | What it does not establish |
|---|---|---|---|
| Explain an analysis to a non-specialist audience | The applicant describes presenting results to a sales team | They report experience presenting to that audience | The quality of the presentation, current proficiency, or ability to repeat it here still needs checking |
| Coordinate work across contributors | The application mentions project coordination | Coordination experience is reported | Their precise contribution, constraints, and outcome are not yet established |

These examples are fictional. A statement on a CV is not independent verification. Information missing from an application means “not documented here,” not “skill absent.” A difference in wording or career path does not by itself show a difference in ability.

If you use a table or support tool, keep every observation linked to its criterion. Any review position should remain readable and open to challenge: show the criteria involved, the information considered, and the unknowns. Do not turn a total or queue order into a recommendation to hire or reject.

## Surface unknowns before the interview

A useful review does not fill gaps with intuition. It prepares the checks that matter. For each criterion, ask:

1. Which item in the application supports this observation?
2. Is it specific enough to understand the person’s contribution, context, and result?
3. What open question would clarify the point in the same way for comparable applicants?
4. Is a job-related, accessible work sample needed?
5. What conditions of the role must be explained so the person can answer with context?

For example, if an application mentions coordination but not the person’s role, ask: “Could you describe a project where you coordinated several contributors, what you were responsible for, and how deadlines were tracked?” The answer adds information; it does not establish a stable personality trait.

## A review grid to adapt

Copy this grid to prepare a role-specific review. Keep the criteria consistent across applications being compared, and record answers separately from open questions.

| Job-related criterion | Required on entry or learnable? | Information and source | Reported contribution | Unknown to check | Question or verification step |
|---|---|---|---|---|---|
| [observable criterion] | [entry / learnable] | [CV, response, interview…] | [described fact, without a label] | [what the application does not show] | [question or work-related exercise] |

After an interview, add what was actually observed, differences between reviewers, and limits in the evidence. Do not rewrite an impression as a fact. If new information changes a criterion, record why and apply the same rule to the relevant applications.

## Keep the decision human and traceable

Assisted review can help show where an application appears to address a written criterion, where a contribution deserves a question, and where information is missing. It does not decide who deserves a job. The recruiter must be able to explain the decision against the role requirements and checked information, consider the limits of the application, and correct a mistaken reading.

Do not infer honesty, motivation, emotional intelligence, cultural compatibility, or potential from writing style, a photo, a name, presumed age, apparent emotion, or a personality test. Do not add sensitive data or criteria unrelated to the work. Calling something “culture fit” does not make it objective.

For a practical interview method, see the [semi-structured interview guide](/en/blog/semi-structured-interview-guide-method-steps-and-15-examples); for a discussion of response context, see the article on [anonymity](/en/blog/anonymity-when-it-helps-when-it-hurts-response-quality).

## Use written answers as material to review

Open-ended answers can surface examples, reservations, or questions that a CV does not contain. They remain statements made in a particular context: they do not automatically represent all applicants, prove an experience by themselves, or replace an appropriate check. Read excerpts in context and preserve the person’s wording when summarizing them.

Harmate's [Open Questions](/en/product/open-questions) supports human review of written answers alongside source excerpts. [Response Import](/en/product/response-import) supports structured CSV, JSON, and XLSX files. These workflows help reviewers inspect the material provided; they do not provide a recruitment-specific assessment, infer personality, or make or recommend a hiring decision. Keep each answer in context and treat it as material to examine, not as a verified fact about the person.

The most useful review does not claim to know a person from an application. It clarifies what the criteria ask for, what the available information supports, and what the interview still needs to check before a human decides.