Evaluation Templates - intervyo.ai

An evaluation template is the blueprint for a role or assessment. It defines:

Stages — how many rounds (single-stage screen, multi-stage funnel)
Rubrics per stage — what gets scored
The AI’s persona — name, voice, tone
The application flow — public apply URL, HR approval gate, OTP
Branding — logo, colors candidates see during the interview

Once configured, the template can be shared with thousands of candidates or invoked programmatically — the rubric and conversational behavior are identical every time.

Create one, step by step

Create a template in the dashboard or over the API — same result either way.

Dashboard (UI)
API

Open Evaluation Templates

In the team dashboard, click Evaluation Templates in the left sidebar.

Start a new template

Click New (or Create template).

Describe the role or assessment

Fill in the Name, pick the Use case (Hiring, Admissions, Training…), and write the Objective — the one thing the interview should determine.

Add skills and the pass bar

List the Skills to probe and the Requirements a candidate must meet to pass. Set the default duration and difficulty.

Save, then add stages

Save the template, then add one or more Evaluation Stages to it.

Name it and pick the use case

Set template_name and use_case. Add a description and objective.

Add skills and the pass bar

Set skills, requirements, default_duration_minutes, and default_difficulty.

Send the request

curl -X POST "https://www.intervyo.ai/api/v1/evaluation-templates?accountSlug=<slug>" \
  -H "x-api-key: iv_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "template_name": "Senior Backend Engineer",
    "use_case": "hiring",
    "description": "Backend role focused on distributed systems.",
    "objective": "Decide if the candidate can own backend system design.",
    "skills": ["Go", "PostgreSQL", "Distributed Systems"],
    "level": "Senior / 5+ years",
    "default_duration_minutes": 45,
    "default_difficulty": "advanced"
  }'

Save the ID

The response returns the template id. Use it when creating stages and participants.

When to use one template vs many

One template per role

The default. Each open role gets its own template so the rubric and AI persona are tuned to the work. Same person applying to two roles gets two participant rows — one per template.

One template per program cohort

For L&D, certifications, or admissions — define stages, pass thresholds, and the AI persona once per cohort. Participants progress through automatically.

Templates are cheap. If you’re hesitating between forking and reusing, fork. Two templates with subtly different rubrics is easier to reason about than one template with conditional scoring.

Single-stage vs multi-stage

The simplest template has one stage — a single AI interview, scored, done. That’s the right shape for most first-round screens. For programs and senior hiring, chain stages:

  Stage 1: Phone Screen        Stage 2: Technical          Stage 3: Behavioral
  ────────────────────────►    ────────────────────────►   ────────────────────
  Communication: 8.5           Code quality: 7.8           Ownership: 8.2
  Domain: 7.0                  Trade-offs: 8.1             Collaboration: 7.5
                                                            
  passed → auto-advance        passed → auto-advance       passed → recommend
  failed → auto-decline        failed → auto-decline       failed → archive

Each stage has:

Its own rubric and pass thresholds
Its own AI persona (a screening persona for stage 1, a senior engineer persona for stage 2)
Its own question bank or coding-problem pool

The platform routes candidates between stages automatically based on pass/fail decisions. Recruiters can override (promote a borderline candidate, hold a candidate pending review) but the default flow needs no human in the loop.

Branding + persona

Two surfaces let you make the interview feel like yours:

AI persona

Name your AI (“Mia”, “Aki”, “Alex”) and pick a voice, tone, and register from the persona library. Candidates ask for the interviewer by name; you keep continuity across interviews.Configure per template via the Persona tab on the template detail page, or set personaId on the API.

Branding

Logo, colors, fonts, and (optionally) custom domain. Candidates see your brand from the apply page through the interview and into the feedback email — no third-party watermark.Workspace-level by default; enterprise plans support per-template overrides for multi-brand workflows (agencies, multi-product orgs).

The public apply flow

Every template ships with a public apply URL at https://intervyo.ai/apply/<token>. Candidates:

Open the URL
Verify their email with a 6-digit OTP
Upload a CV (PDF / Word / scan)
Get screened by the AI immediately

Apply URLs are rotatable in one click from the template detail page — the old URL stops working immediately if compromised. You can require HR approval between application and interview. With approval on:

The candidate’s application lands in the panel with status pending
Recruiter reviews CV match score + skim the resume
Approve → candidate gets the interview link
Reject → candidate gets a polite decline

With approval off (auto-approve), the apply page hands the interview link to the candidate immediately. Use auto-approve for high-volume roles where reviewing every CV is the bottleneck.

Per-template participant model

Each candidate is bound to one template at a time. The same email applying to two templates produces two participant rows — one per template. This keeps each role’s funnel clean and prevents accidental overwrites. You can move a participant between templates from the participants page — the platform creates an approved application row on the new template so they show up in that template’s panel. See the participant edit flow in the workspace UI for the move action. Templates support two share modes:

Single-candidate share — one URL that shows one candidate’s interview history. For sharing with hiring panels or panels of one.
Multi-candidate share — one URL that bundles multiple candidates side-by-side, ranked. For client submissions in agency workflows.

Both modes:

Expire on a configurable date (7 / 30 / 90 / 180 days)
Are revocable in one click
Show view counts and last-viewed timestamps
Always show the latest session per stage (so retries surface automatically)
Need no login on the recipient side

Configure shares from the template’s Share panel on the detail page.

​Create one, step by step

​When to use one template vs many

One template per role

One template per program cohort

​Single-stage vs multi-stage

​Branding + persona

​The public apply flow

​Per-template participant model

​Sharing candidate profiles

Create one, step by step

When to use one template vs many

Single-stage vs multi-stage

Branding + persona

The public apply flow

Per-template participant model

Sharing candidate profiles