Docs

Docs hub for recruiter-led AI interview evidence operations.

Find practical guidance for getting started, role setup, candidate invites, structured interview flow, evidence packet review, scorecard interpretation, follow-up questions, recruiter operations, security/privacy review, troubleshooting, and API/integration evaluation.

Documentation categories

Getting started, Role evidence plans, Candidate invitations, Interview workflow, Evidence packets, Recruiter review, Exports/integrations, Permissions/security, Retention/deletion, and API evaluation.

  • Getting started: Understand the core workflow: role setup, candidate invite, structured AI interview, evidence packet, recruiter review, and handoff.
  • Role setup: Set screening criteria, role-specific interview topics, and recruiter review expectations before invitations go out.
  • Candidate invite and experience: Explain what candidates receive, how they complete the structured interview, and where support routes live.
  • Evidence packet review: Review summaries, transcript excerpts, scorecards, risks, missing evidence, suggested follow-up questions, and recruiter notes.
  • Scorecard interpretation: Read scorecards beside transcripts, risks, missing evidence, and recruiter follow-up questions before deciding next steps.
  • API and integration evaluation: Evaluate object models, auth expectations, events, endpoint availability, security boundaries, and workflow handoff.
  • Security and privacy review: Review controls, retention, DPA, subprocessors, responsible disclosure, and privacy request routing.
  • Troubleshooting: Resolve invite, access, browser, microphone, camera, billing, workspace, and recruiter workflow issues through the right support path.

For recruiters

  • Set role criteria and interview topics.
  • Review an evidence packet.
  • Record decision notes.
  • Download a PDF for authorized team review.

For candidates

  • Understand the interview flow.
  • Prepare camera, microphone, browser, and network.
  • Get support for invite or access issues.

For technical teams

  • Review integrations and API evaluation.
  • Understand data movement.
  • Prepare security and retention questions.
This static fallback is provided for search engines, accessibility tools, security scanners, procurement reviewers, and users when JavaScript is unavailable.