One requirement.
Its supporting words.

Role requirements come from the brief. Your team adds context and deal-breakers, checks the brief and publishes. aikho then prepares the interview and the way each requirement will be rated. You can read its plan at any time.

The purpose is to assess relevant experience against the role. The interview can follow up differently with each candidate while keeping those requirements as its standard. A conversation’s path can change without changing the work the role needs.

Each requirement gets one rating with the candidate’s supporting words. Your team can read the conversation rather than taking the assessment on trust. The interview carries most of the weight in the overall view; the CV adds career context when available.

The stored example below shows one skill rating. It is not an overall candidate result. The site does not publish the numerical scale, a pass threshold or the weighting between sources. Read the band alongside the actual account and its limits.

If a topic did not come up, aikho reports that the interview did not establish it. That absence is not counted as a failed requirement. The evidence should help your team identify what still needs checking.

A requirement rule may act on an established failure, never on missing or uncertain information alone. Optional low-score closure has separate conditions. Human oversight explains those actions and the decisions that remain with your team.

It does not spot lying. A convincing story that holds up under questioning sounds convincing. Check references before you hire, as you always would.

aikho assesses candidates and explains its results. Suggestions are selected using defined scoring rules. Your team decides whom to shortlist and hire. Neither a strong interview nor a detailed CV independently verifies a claim or guarantees future performance.