Collaborations

One hiring conversation, four sides of the table.

Echobotics is a hiring platform. Voxio Agents is the voice inside it — the same engine that runs the calling agents and the 3D avatars, pointed at interviews instead of consultations. Four products sit on one engine because the hiring journey is really one long conversation seen from four positions.

The partnership

Echobotics: one engine, four products

The recruiter screening, the candidate applying, the student rehearsing, the institution placing them — four people standing around the same job, and the same conversation engine facing each of them. The scoring, the evidence gathering and the two scores do not change between the four. What changes is ownership and who is allowed to see what — and that is the product, not a skin.

Evidence over wording. The system will help someone present what they have, and refuse to help them claim what they do not. When something is genuinely missing, the answer is not a better sentence — it is a scoped piece of work that produces the missing evidence.

Hiring OS

The recruiter · N candidates → 1 shortlist

Voxio Agents inside it
  • The whole calling stack — inbound, outbound and scheduled, on real numbers
  • Turn-taking and barge-in: it stops when the candidate cuts in, and finishes the lines that must be said in full
  • Answering-machine detection, so a run of calls is not a folder of voicemail greetings
  • Structured output written back as fields, not a transcript

Screening at a volume no team could staff. It runs the first-round conversation on every applicant instead of the twenty someone had time for, and hands back a ranked shortlist rather than a call queue.

This is the end of the platform that runs on the phone, on real numbers, inbound and outbound — so the constraint is not the model, it is the line. It is already talking as the candidate says hello, because a silent beat on answer is the pause that makes people hang up on an unknown number. Answering-machine detection ends the call rather than interviewing a recording.

The ranking carries its reasoning. A shortlist a recruiter cannot interrogate is a shortlist they will re-do by hand, so every verdict arrives with the answers it was drawn from and the requirement it was judged against — and it reaches the recruiter’s systems as structured fields, not a transcript to read.

First-round screening at volumeRanked shortlist with reasoningInbound & outbound callingStructured output

Career OS

The candidate · 1 candidate → N openings

Voxio Agents inside it
  • The interview the candidate practises against, aimed at the specific job they are applying for
  • The same roleplay engine as Training OS and the SIT and MSF deployments — different room, one engine
  • Under 500ms before it answers, and follow-ups that push when an answer is thin

The scoring and the resume repository are Echobotics’. Our part starts the moment the candidate has to say any of it out loud.

The candidate points the system at the actual job they want and gets a straight answer: where they already match, where they are weak, and what closes the gap. Not improve your communication skills — either this fact is in your resume but buried on page two, which is an edit, or this requirement has no evidence anywhere, which is a project.

Two scores, never blended. Fit asks how much of what the job wants the resume’s substance actually satisfies. Conveyance asks how findable that substance is. Two resumes with identical facts, one crisp and one badly structured, have the same fit and different conveyance. A single blended number would hide exactly the thing the candidate needs to know.

A resume is a repository, not a file. Every change is an immutable version; it can branch into a data-analyst line and a devops line that evolve independently; any two versions diff line by line, and one is pinned as the one that actually goes out. Gaps marked missing generate a scoped project with milestones, tracked by hand with an artifact attached, that lands back in the resume as a reviewable diff.

Fit & conveyance scoringVersioned resumesGap-driven projectsAnchored edit diffs

Training OS

The student · rehearsal under real pressure

Voxio Agents inside it
  • The interview agent itself — the same roleplay engine as the SIT and MSF deployments
  • Under 500ms before it answers, which is what stops the student performing for it
  • Follow-ups that push when an answer sounds thin, rather than a fixed question list
  • The agent’s own state on screen: waiting, listening, thinking, speaking
  • Two-channel recording — agent on one side, student on the other

A final-year student in a placement programme alongside three hundred classmates. The traditional version is a set of workshops, a couple of mock interviews if they are lucky, and no idea how they would actually perform under pressure.

It is the same practice engine as the medical and frontline training — the avatar that plays the anxious patient for Singapore’s universities and the resident who has decided no for its ministries — pointed at a job interview instead of a consultation. Not a similar idea reimplemented: the same engine, already in production in rooms with more at stake. See it running

Here that becomes a live, AI-run interview that behaves like the real thing: questions that adapt to the answers, follow-ups that probe when something sounds thin, and feedback afterwards naming exactly where they stumbled, turn by turn, with the video to prove it. The student picks which resume and which versionthey are presenting before it starts, and that version is pinned to the session permanently — so the score beside the session and the words spoken in it refer to the same document. Your paper says X and you said Y about X out loud are finally comparable.

The room shows the agent’s own state — waiting, listening, thinking, speaking — because a silent agent that is thinking and a silent agent that has crashed look identical otherwise. The whole session records: webcam video plus a two-channel mix, agent on one side and student on the other.

Adaptive live interviewVersion-pinned sessionsTurn-by-turn feedbackTwo-channel recording

Placement OS

The educator & placement officer · N students → 1 drive

Voxio Agents inside it
  • Per-student and per-class configuration of what the agent weights, set by the teacher before the session
  • Accommodations that change how the agent behaves, not just how it scores — it can be told not to probe or counter on eye contact
  • Push-to-talk, chosen by the student, so a stammer or a long pause never ends a turn early
  • Every number on the page derives from interviews our engine ran — which is why bail-outs and turn counts exist to be counted

Not another dashboard. What an educator gets is a short list of names: the students where coaching demonstrably failed to land, so a human can step in. Students with nothing stuck are omitted entirely — it is a to-do list, not a roster. That is also the answer to does this replace teachers: no, it hands them the people it could not reach.

Around that sit the numbers a placement cell actually decides on. A requirement × class heat map, where 212 of 300 fail production deployment experience is a curriculum decision. Class trajectory plotted by session ordinal rather than by date, because students start on different days and a calendar series measures scheduling, not learning. Bail-outs counted separately, because a three-turn session is not a short session, it is someone who quit, and counting it as completed flatters every other number on the page. And drive readiness: before a company visits, how many eligible students clear its bar.

The teacher decides what the interview is for. Before a session runs, they set what it should lean on for a particular student or a whole class — the requirement a cohort keeps failing, the thing this one person needs to be pushed on. It is not a difficulty slider: it changes what the agent asks about and what it lets go.

That is also where accommodations live, and they are behavioural rather than cosmetic. An autistic student can be marked so the agent does not probe eye contact and does not counter them on it — the agent stops doing the thing, rather than doing it and then discounting the result. And the student picks push-to-talk if they want it, so a stammer or a pause for thought never ends their turn early and costs them the interview. Nobody should lose a round to the microphone.

The machine never has the final word about a person. Readiness is computed as an advisory band and then has to be conferred by a named human who saw the basis for it. Two fields, never one; the default is not-ready, and a computed band moving to ready promotes nobody — it moves them into a review queue.

Per-student & per-class tuningBehavioural accommodationsPush-to-talkCoaching triage listClass gap mapDrive readinessHuman-conferred readiness
Also with Echobotics

AI calling agents

Beyond the four OS products, Echobotics runs the Voxio Agents calling agent itself.See the deployment

In their words

What the partner says about it

People lose jobs over how they answer, not over what they know. That only works if the interview pushes back when an answer is thin and does not wait a beat too long before it speaks — Voxio is the reason ours does. Candidates stop performing for it after about a minute.

EchoboticsEchoboticsHiring, Career, Training & Placement OS

Want to build on the same platform?

You bring the domain. We bring the agents, the avatar and the calling stack.