On the job experiences
A learner spends a day inside a real role. An inbox, colleagues, deadlines, a deliverable. They come out with evidence of what they can actually do.
Built for middle school, high school and university first. Employers next.
Our go-live is Friday and my exec team is watching. Can you give me an honest status? Are we on track, and if not, what's the plan?
Sofia's handover lists three gaps. The go-live checklist in Knowledge Base says only the SSO ticket blocks launch. Worth confirming before you answer Delphine.
Every experience is a single working day in a real role at a fictional company. The pressure arrives the way it does at work: in the inbox, in chat, and on the calendar, some of it at once. A few moments in the day are the ones that matter, and the learner does not know which.
A lead hands over a client's setup file with gaps in it, and a question: which blanks actually block Friday's launch?
A VP writes in: her executives are watching and she wants an honest status. What the learner says, and does not promise, is the first thing that gets scored.
"Don't assume the status column is right." The knowledge base has the answer, if anyone looks. Judgement, not recall.
An outage, an escalation, a stakeholder who needs an answer now. The learner has to decide what to do first, and who to tell.
A go-live risk read, a reconciliation, a recommendation. Addressed to a person, with a decision in it. That artefact is what a reviewer reads.
Every person the learner meets during the day, and the day itself, is Ayvido's work. It is built into the experience, not bolted on beside it.
Given a job description and a role's reference sheet, Ayvido writes the day: the messages, the timing, which moments are critical and which are noise.
The client who wants the truth, the colleague with a hint, the candidate on a screening call. Each one replies in character and remembers the thread.
A work assistant in the sidebar. It answers questions about the company and the task. It does not do the work, and it does not know the answer key.
What the learner wrote at each moment is read against what a strong professional would have done, and every judgement names the evidence it rests on.
Ayvido never makes a hiring or grading decision on its own. It produces a record for a person to read.
The first users are students. Employers arrive later, and only with consent, because a school's work is the student's to share.
Middle and high school
Career exploration with the boring parts left in: a full inbox, a colleague who needs something, a deadline. Students find out what a role actually feels like before they choose a path toward it.
University and capstone
An experience can stand in for a capstone or sit inside one. The deliverable is real enough to grade, and the record of the day shows how the student got there, not just whether they did.
Employers, next
Subscribe for talent-pool access, or commission an experience built from a real role for recruitment or upskilling. Every result an employer sees was disclosed by the person who earned it.
Not a personality type and not a quiz score. A record of what the learner did at the moments that mattered, next to what a strong professional would have done.
Each role is built from a reference sheet: what the work actually is, which tools it lives in, who the stakeholders are, what strong and weak behaviour look like, and what the day's deliverable is. The scoring categories come from that sheet, so a sales day scores discovery and qualification, and a helpdesk day scores triage and the honesty of a status update.
Eleven roles across six families today, each with its own scenarios and pressure days.
Named the three open gaps, said which one blocks launch, and did not commit to a date the team had not agreed.
Stakeholder honesty · strongFound the past-due account marked Current after a colleague's hint, and corrected the risk read.
Verification · strongTold the client it was being handled before anyone had picked it up. The commitment was right; the sequence was not.
Escalation judgement · riskThese are not policy statements. They are constraints the system enforces, written down here in plain language.
At registration we work out the date a learner becomes an adult and keep only that. The platform only ever needs to know whether someone is a minor, never how old they are.
Only by choice. A result from a school or university cannot be disclosed to an employer unless an adult, or a verified guardian for a minor, explicitly consents.
Who viewed a result, and when, is recorded as it happens and never deleted. "Did anyone see my work?" has an answer.
Work in progress is kept for 30 days after the last save and results for 12 months, then swept. A deletion request removes a person's runs, results and identity in a single operation.
Sign-in is by emailed link, so there are no passwords to lose. We are preparing for the assurances schools ask for, including a SOC 2 report and a VPAT, and will say plainly what is and is not yet in place.
A pilot is a single role, a single group, and a conversation afterwards about what the evidence showed. Tell us the roles your students are curious about.