Skip to content

Screening & assessments

Screen at volume without letting a filter make the decision.

Configure must-have questions and a screening standard for each role, invite candidates to calibrated assessments and coding tests, and review the results in clear categories. Closing out applicants always takes two separate human steps.

Create a workspaceTalk to us

hireiq / jobs / data-analyst / screening

Sample data
  • Top

    Complete and above the standard

    24
  • Possible fit

    Comparable, outside capacity

    61
  • Weak evidence

    Below the configured standard

    118
  • Doesn’t meet stated requirements

    Never closed automatically

    37
  • Needs review: insufficient information

    A person must look

    9

Close-out awaiting approval

  1. 1. Proposed by a recruiter: Weak evidence · “Below screening standard”
  2. 2. Approver confirms the exact count before anything changes
Illustration of screening categories and a two-step close-out awaiting approval.

The problem

Volume tempts teams into automatic rejection.

Knock-out filters are fast, but they reject people nobody has looked at and cannot explain themselves later. HireIQ organizes applicants into reviewable categories and requires a recruiter to propose, and another confirmation to approve, any bulk close-out.

How it works

The workflow, step by step.

  1. 1

    Set the screening policy

    Define must-have answers and a screening standard for the role. Policies are recorded with the job so later reviews use the same rules.

  2. 2

    Invite to assessments

    Each invite draws a fresh mix from the question bank — 40% easy, 40% medium, 20% hard — with practical tasks and coding tests where the role needs them.

  3. 3

    Review by category

    Applicants are grouped as Top, Possible fit, Weak evidence, Doesn’t meet stated requirements, or Needs review when results cannot be compared.

  4. 4

    Close out with approval

    A recruiter proposes a frozen list with a reason. It closes only after approval that confirms the exact count. Candidates under human review are skipped.

Capabilities

What’s included in screening & assessments.

  • Calibrated question bank

    Questions carry difficulty tiers and weights. Exposure is counted on every invite, and over-exposed questions can be retired while past results stay intact.

  • Coding tests in the browser

    Candidates write code in a full editor. Submitted code runs only in an isolated runner; if none is configured, grading stops and a person reviews the answer.

  • Practical assignments

    Take-home tasks are scored against explicit criteria, with each score recorded by source so manual and automated grades stay distinguishable.

  • Assessment AI policy

    Decide per assessment whether candidates may use the built-in AI assistant, so the rules are explicit before anyone starts.

  • Expert review and technical evaluation

    Dedicated stages capture reviewer judgment and technical evaluation separately from automated results.

  • Auditable stage history

    Screening decisions and stage changes are written to the audit trail with the actor and reason.

Controls and safeguards

  • No screening category closes an application by itself.
  • Bulk close-out is limited to 1,000 applications and expires after seven days if not approved.
  • “Doesn’t meet stated requirements” is never closed automatically.
  • Assessment results remain separate evidence rather than being folded into match coverage.

Who it helps

Recruiters
Clear the queue by category while every rejection keeps a reason and an approver.
Technical interviewers
Review code and practical work alongside the criteria it was scored against.
Administrators
Manage the question bank, its difficulty balance, and exposure over time.

Works together with

FAQ

Screening & assessments: common questions

Can HireIQ reject candidates automatically?

No. Screening categories organize the queue. Closing applications requires a recruiter’s proposal and a separate approval that confirms the exact number of applications affected.

Where does candidate code run?

Only in an isolated runner — a Judge0-compatible service or a network-less Docker container with strict limits. Code never runs inside the HireIQ application process.

How do you keep assessment questions from leaking?

Each invite draws a different difficulty-balanced set, every inclusion is counted, and administrators can retire questions that have been shown too often.

Bring structure to your next requirement.

Create a workspace, post your first role, and see every applicant’s evidence in one pipeline.

Create a workspaceTalk to us