Risenoow's sample report is a full AI candidate assessment for one applicant: five scored interview dimensions, each carrying the candidate's own quoted words, every claim checked against their CV, a list of what the interview actually got through, a question to ask next, and the requirement decisions as they stood on the day.
One illustrative candidate, one real report layout. Every name, quote, score and requirement below is written for the example. No real applicant appears on this page, and no figure here is a claim about anyone.
Last reviewed: 11 September 2026Applied through the Risenoow job board. Spoken screening in English, written answers and a CV supplied. Report written in the language of the role. The name and every detail on this page are illustrative and belong to no real person.
Alex can do the core of this job and has done it in production, with specifics that held up when the interviewer pushed on them. The gap is ownership: the written answers claim a performance target they told the interviewer was somebody else's call, and that contradiction is the one thing worth an hour of your time. Interest in this role in particular was thin, and nothing in the conversation touched team size.
This report is scored because there was enough to judge. When there is not, no number is produced, and the report says so in its first line rather than leaving a gap for a reader to interpret.
A dimension the conversation never evidenced is reported as low confidence with no quotes under it, never flattered into a number. Silence is a gap, never a strength.
Each dimension is scored out of a hundred and shown with its band. Intelligence is not measured and neither is sentiment: reasoning and engagement are measured instead, and communication is judged on substance, never on accent, grammar, vocabulary or filler words.

They named the queue, the retry policy and the two failure modes it does not cover, without being asked for any of it.
Jump to this moment in the conversationAsk next: Ask them to walk through the schema change case end to end, including how they would deploy it.
The answer was structured and held up when followed, and they separated what they knew from what they were guessing.
Jump to this moment in the conversationAsk next: Ask what they would have done if moving the join had not worked, and how they would have known.
Answers were clear, ordered and specific. Judged on substance only, never on accent, grammar or filler words.
Jump to this moment in the conversationAsk next: Ask them to explain the same change to somebody outside engineering.
The first answer changed once the interviewer asked who set the target, and the detail thinned rather than sharpened.
Jump to this moment in the conversationAsk next: Ask who set the target and who reported on it, and what they personally decided.
Interest in this role in particular was thin. They asked nothing about the team or the work.
Nothing in the interview evidenced this either way, so read this reading lightly. The interview gave little to go on here.
Ask next: Ask what drew them to this role rather than to the field, and what they want to be doing in a year.
These five are one reading of one conversation, each with the candidate's own words underneath it. Weigh them. They are not a test result.
A claim in writing the CV does not support, or a skill on the CV they could not speak to, is worth more to you than either source on its own. Two claims are supported, two are unclear and one is contradicted.
So a thin report is never mistaken for a thin candidate. Four questions were answered, three were asked and not really answered.
Two reference lines, neither of them invented. The average is a fact about the applicants. The other is the lowest score your team has actually shortlisted for this role, which is the bar you have been setting in practice.
The per dimension comparison is withheld entirely when too few people have been measured for it to mean anything, and the chart says so rather than drawing a line out of one or two readings.
Questions this role marked as requirements, answered before the interview. Nothing here is inferred from a CV, and this is the rule as it stood when the application was judged. Changing which answers you accept tomorrow never rewrites a decision already made about a real person, and a requirement added later is shown as never asked.
A requirement set to decline turns the application away before any interview runs, marks it declined, and emails the candidate the reason in the words you set. That record says no interview was run and no report was produced, and links to the control that puts it back.
The technical interview is read on the same five dimensions, so the movement is the point rather than a second number to hold in your head. One sentence at the top of the assessment says what it did to the first reading, and the first stage score itself is left untouched.
Technical interview confirmed Reasoning and moved Composure when pushed from first reading score to second reading score.

Every quote above links here and highlights the line it came from. The recording plays inside the record, with seeking. Only the candidate's turns are evidence about the candidate: the interviewer's questions are not.
Fourteen days free, no card, ten interviews included.
Describe the role once and the first report arrives as soon as somebody applies.