For Recruiters
Jobs & candidates
A job is a JD plus its candidate pipeline. Adding a candidate is what starts the interview process.
A job is the job description plus its pipeline — the set of that job's interviews, grouped by state (see Interview lifecycle). Everything a recruiter does — reviewing plans, monitoring interviews, reading assessments — happens against a job's pipeline.
Creating a job
Give the job a title and description, and set its role family and seniority (entry / mid / senior / lead / exec). You don't have to write the description by hand — you can ask AI to generate it, auto-extract skills from it, or upload a JD PDF instead.
On creation, Teamcast auto-seeds a role profile — a competency weighting (HITL-0) — from role-family defaults. You can tune it later; see Analytics & role profiles. The job's company blurb and salary are editable at any time; the blurb also grounds how Maya introduces the company to candidates.
Adding a candidate
Provide the candidate's name and email, then paste their résumé text or upload a résumé PDF. Duplicate candidates on the same job are rejected.
Optional résumé↔job match
Where enabled (feature-flag gated), Teamcast can surface a match verdict — matched and missing skills against the job — to help you decide whether to proceed before generating a full plan.
Duration and rubric
Pick the interview duration, and review the competency rubric radar — a visual summary of what the interview will weigh, inherited from the job's role profile.
GENERATING_PLAN. Nothing is sent to the candidate yet; the plan still needs recruiter approval (HITL-1). See Reviewing the plan.