How it works

The section has three tabs: Competencies, Hard facts, and Signals.

Add Competencies

Competencies are the capabilities you expect to see in the candidate. The AI asks about them during the call and scores the candidate on each one.

1. Open Role context and go to Competencies.
2. Click Add competency.
3. Fill in Title (e.g., “Project management”) and Description (e.g., “Leads cross-functional projects from planning to delivery”).
4. Mark it as Required or Nice to have — Required weighs more in the evaluation.

If you leave this empty, the AI will ask generic questions and compare candidates poorly.

Add Signals

Positive signals highlight traits, experiences, and behaviors of good candidates; negative signals flag possible risks, gaps, or excluding factors. They are not requirements — they are nuances that fine-tune the evaluation.

1. Go to Signals
2. Click Add signal
3. Add positive and negative signals
4. Review them so they don’t become disguised requirements.

If you leave this empty, the match label will be less precise and may miss important nuances.

Add Hard facts

Key facts are clear, measurable requirements that can be verified in a conversation: skills, years of experience, certifications, tools, or qualifications. They are grouped into: Legal & documents, Location & availability, Experience & credentials, Compensation & conditions, and Role-specific operational requirements.

1. Go to Hard facts.
2. Click Add a verifiable fact.
3. Fill in Title and Condition (describe the condition candidates must meet).
4. Mark it as Required or Nice to have.

Required facts work as knockout requirements: they are what allows the call to end early when a candidate doesn’t meet them. If you leave this empty, filtering is weaker and you can’t cut calls short when a key requirement fails.