Skip to main content
Your organisation designs hiring in Assess. Candidates apply, take assessments, and join interviews inside the product. You review in the dashboard, or your software listens over the Public API and signed webhooks.

​
What Assess is for

Assess helps you hire data talent end to end:
  1. Attract — publish a job on careers with a custom application form and knockout questions.
  2. Screen — rank CVs with a deterministic match score; optional AI briefs assist humans, they never reorder the list.
  3. Assess — send take-homes with coding, SQL, and other tasks in a live sandbox.
  4. Interview — run AI, human, or hybrid live rooms with analysis and replay.
  5. Decide — keep notes, tags, and scorecards on one candidate profile across jobs.
You can still skip jobs entirely and only send assessment invites. That path remains fully supported.

​
How Assess works

Work happens inside an organisation. Recruiters use the dashboard with no API key. Automations use organisation API keys limited by scopes. Assess runs sessions, scores tasks, screens applications, and delivers webhooks. You control who holds keys, which scopes they have, and how your ATS reacts. Assessment-only path: create an assessment → send an invitation → read results (and webhooks). No job required.

​
What you can do today

​
Core concepts

  • Organisation: Your Assess workspace. Owns plan limits, seats, jobs, assessments, and API keys.
  • Job: A published opening (careers + API). Optional.
  • Application: One person’s apply to a job.
  • Screening (L1–L5): Knockouts → CV parse → L3 match score (sort key) → optional L4 AI brief → human or threshold advance.
  • Candidate profile: Org CRM person (profiles:*). Not the same as assessment session results (candidates:read).
  • Assessment: Take-home or timed test. Must be Active before invites. Identified by slug or UUID.
  • Task: One question on an assessment (platform or org library).
  • Invitation: One candidate’s unique link. API id: invite_token.
  • Result: Score, pass/fail, optional proctoring signals.
  • Pipeline: Multi-stage funnel. Linked jobs can use a cv_screen stage.
  • Interview: Live AI, human, or hybrid room.
  • Soft offer: Letter + PDF + accept/decline link (offers:*, Growth+). Not DocuSign.
  • Webhook: HTTPS callback. Secret whsec_… shown once.
  • API key: ct_live_… or ct_test_… Bearer (Starter+). Empty scopes = full access (legacy).
  • Hiring squad: Growth+ sub-team for filtering jobs, assessments, and pipelines.

​
Where to start

Post a job

Careers apply → screen → advance into assessment.

Invite to an assessment

Quickstart for assessment-only hiring.

Team roles

Invite a developer for API keys without billing access.

Create an API key

Or stay in the dashboard with no key.
SDKs · Build with agents · Using docs with LLMs · MCP
Last modified on September 5, 2026