Skip to content

For companies

Read the work, then talk

See real work before you talk

Candidates do a real mission with AI; you read the result piece by piece against the level each piece requires. People at your company decide.

Agree on the hiring question before inviting

Start with what the role actually does, then pick work evidence that helps answer that question.

  1. Define what you need to learn

    For example, how does someone inspect logs before fixing an issue, or verify AI-generated edits? A mission gives your interview a real starting point.

  2. Assign the readers

    Identify the round manager, technical readers and interviewers separately from candidate recipients.

  3. Check eligibility

    Check your plan, credits, and available presets for this round. Practice missions aren't automatically eligible for hiring.

Choose a preset and inspect its scope

  1. A new title does not create new scoring rules

    Pick a published preset eligible for your hiring round. Your custom title and description add context for candidates—they don't change scoring weights, pass thresholds, or Defense topics. Active attempts lock in the original version and preset, so don't compare results by display name alone.

    Selection and measurementDiagram
    Title and description
    Candidate-facing context
    Preset
    Published assessment rules
    Started attempt
    Keeps accepted terms

Three entry paths with different terms

Each path depends on plan, organisation authority, eligible missions and participant consent.

PathParticipant entryOrganisation access
Public mission linkUses their own account and start eligibilityRequires the candidate to share an eligible result; opening the link alone shares nothing
Company-funded invitationReads and accepts the offer’s termsWithin disclosed context and result permissions
In-app job postSelects profile, CV and eligible resultsSelected application data and separately authorised details

Validate recipients before confirming invitations

Assessment recipients and staff invitations are separate lists. An invitation sent is not an attempt started.

  1. Review prepared recipients

    Add individuals, paste a list or import CSV. Inspect accepted entries and duplicates before confirmation.

  2. Check credits and deadlines

    Eligible funded issuance reserves organisation credits. Available controls offer completion windows of 1 to 14 days.

  3. Follow recorded states

    Track issued, accepted, started, and result-ready states. Check failure reasons before acting—resending doesn't fix every issue.

Assign readers with access for their job

Organisation roles, round access, and result permissions work together. A role title alone doesn't open every record.

  1. Organisation administrator

    Manages members, plan and funding, subject to each operation’s permission checks.

  2. Round manager

    Works with recipients, stages and admitted readers for the assigned round, not every round.

  3. Technical reader and interviewer

    Reviews permitted work evidence and notes job-relevant follow-up questions.

Use the result to prepare the next conversation

  1. Bring your role questions to the permitted work evidence

    Start with the task and whether requirements were met. Keep interview notes beside the evidence your role can access, separating observations from follow-up questions. If detail access costs credits, confirm the quote first. See Who sees what for shared summary limits.

    Sample interview notes
    Job question
    How were the changes checked?
    Work evidence
    Permitted retained sections
    Follow-up
    Ask about an inspectable moment

Read the details

Compare with the conditions in view

Eligible comparisons support up to five people and saved sets. Missing data stays blank.

CheckBefore a numeric differenceWhen incompatible
Mission and versionCheck each attempt's exact mission and versionA shared name is insufficient
Weights, starter and BUILDRequires available compatible measurementsNo unsupported numeric delta
Result state and useRead issued results and authorised hiring useBlank isn't zero

Keep review decisions beside the evidence

Track the stage

Use a board or table to move stages manually and keep notes, tags, and shortlists beside applicants. Filters help you find records—they don't make hiring decisions.

Export the available scope

If your role and plan allow, request the round-summary CSV and track Requested, Ready, or Failed. Download when ready. It excludes code and Defense transcripts, grants no extra access, and downloaded copies can't be recalled.

Prepare shared questions

Keep observations distinct from opinions and retain mission/version context so the next reader knows which work a question concerns.

Choose assessment methods for the question

Methods complement each other. Your team still judges what fits the role and where limits apply.

MethodWhat it helps revealFollow-up needed
Take-homeQuality of the delivered artifactProcess and conditions available to each person
Live codingResponses and discussion in a shared windowRelevance of the exercise to the role
Standard testAnswers within a defined formatAI use and responsibility for delivered work
InterviewExperience, reasoning and contextInspectable work evidence
OperatorRank missionSubmitted work under defined terms and captured contextResult limits, comparability, and other job-relevant context

Teams and classes keep their own purpose

Personal practice never flows into an organisation or class automatically. Each path requires its own authority, funding, and consent.

  1. Team rounds

    Enabled reports separate started, submitted and scored counts. Averages and changes need available measurements and comparable participants.

  2. Schools and courses

    Authorised teachers follow eligible class-funded work with learner consent and add feedback beside it.

  3. Teacher feedback

    Adds teaching context without changing checked scores or verdicts, or turning private practice into hiring evidence.

Connect your organisation’s AI within its access

  1. MCP follows organisation authority

    When customer MCP is enabled and your organisation is eligible, create a scoped connection with group limits, audit activity, and revoke anytime. Every result read still requires permission. Supported sensitive actions need confirmation. Connecting AI never exposes a participant's full account or private data.

    Connection boundariesDiagram
    Select scope
    Allowed operations and groups
    Read a result
    Requires result authority
    Manage
    Inspect activity and revoke

Prepare the organisation for its first round

Today, an eligible verified account’s first organisation has a 30-credit trial. Check its entitlement and expiry in the account.

  1. Separate creation from membership

    One account can create up to five active organisations. Joined organisations don't count toward this limit—and this doesn't mean five separate free trials.

  2. Invite staff by role

    Owner, Admin, Manager, and Viewer have distinct permissions. Staff invites expire; active members and pending invites are tracked separately.

  3. Describe a mission need

    If no eligible preset fits, describe the work context, assessment question and audience for discussion with the team. A request does not guarantee a new mission or custom scoring.

A worked example before the first invitation

An illustrative preparation exercise, not a customer account.

What the team findsDiagram
Recipients
A duplicate email in the CSV
Preset
No eligible preset for this purpose
Reviewer
Round access not assigned
  • Read validated recipients

    Confirm from the validated list, not the source row count.

  • Resolve preset eligibility first

    Don't send an invite without an eligible preset. Describe what your team needs and check available options.

  • Assign the intended reader

    Check role and round admission before collecting applicant evidence.

Before you start

Does our team write the task?

You pick from published mission presets that fit the role, then review the work and results.

Does an invitee pay?

For company-funded invitations, the mission uses your organisation's credits. Check who pays on the invitation terms before sending.

Does AI make the hire?

No. Results are supporting evidence for your team to review alongside other hiring context.

Prepare a round for your team’s question

Check eligible work, reviewers and funding before sending invitations.