Evidence, never a verdict.
Every rating cites the moment it came from. Scores are backed by lines of code, test outcomes, and quoted speech—never by an unexplainable verdict.
Compose an assessment from five kinds of round, fix the rubric before anyone is invited, and review a dossier where each score cites the code, the transcript or the test run behind it.
Interviewer
“Twenty gateways share the limiter. Where does the count live, and what happens when two check it in the same instant?”
Candidate · 18:24
“One key per client in Redis, and the read, the count and the write in one Lua script so there is no gap between them. I'd put a p99 budget on the round trip rather than guess.”
Cited as #transcript:1104000 - a link that opens this moment in the recording.
Components: gateway ×20 → limiter → services
Store: Redis, "rl:{clientId}", sliding window (ZSET)
Atomicity: single EVAL - check + increment together
Capacity: 100k req/s, ~5k checks/s per gateway#transcript:1104000
#transcript:1290000
#transcript:1611000
#transcript:820000
A decision posts the scorecard to every connected ATS.
Low-level design with running tests, system design on a whiteboard, DSA, a technical screen and a behavioural round, each configured per stage.
Every criterion score cites code lines, a transcript moment or a test run from the round. A citation that points at nothing is dropped, not stored.
The integrity timeline shows only what the room recorded - focus, full screen, pasting, camera, connection. What was not captured is shown as not captured.
Greenhouse, Lever and Ashby: a stage change invites the candidate; a submission and a decision post the scorecard back, signed with your secret.
The hiring workspace
Openings, assessments, applications and dossiers in one place. Click a stage to filter; click a candidate to open the evidence.
Meritello
Acme Engineering · sample data
Blind review is on
Names are masked while a reviewer reads a dossier. Overrides need a written reason.
Active Assessments
12
2 activated this monthCandidates
148
every score cites evidenceInterviews This Week
34
22 completed · 12 scheduledCompletion Rate
92%
of invitations submitted within 14 days“Put spot selection behind a strategy, so a new bay type is a new class, not a new branch.”
The assessment studio
Up to five kinds of round, each with its own problem and length; one proctoring profile; one rubric. Activate it and invitations can go out - by email, by a public link, or from a stage change in your ATS.
Technical screen
Resume-aware · fundamentals and the job description
Data structures & algorithms
One problem · Java or Python · tests run in the room
Low-level design
Parking lot · Java · running tests
Behavioral
Ownership, problem solving, collaboration
The rubric studio
Weighted criteria, five anchored levels each, written by the hiring team and chosen before the first invitation. Every candidate in the opening is scored against the same one.
L5 · Senior Engineer
What the rubric holds still
The rubric is chosen when the assessment is activated and applies to every candidate invited to it. A reviewer who disagrees with a score overrides it in the dossier with a written reason, which stays on the record next to the original.
Focus on resilient architecture, optimistic concurrency, and system modularity
The dossier
A citation is a link: to lines of code, to a moment in the recording, to a test run. A reviewer clicks it and looks. A score without one is not stored.
Dossier · one criterion, opened
Low-level design round · Parking lot · Java
“Spot selection sits behind a strategy. When asked about EV bays at 01:14:32, said a new bay type is a new class, and the tests agree.”
// 14 private final SpotAssignmentStrategy assignmentStrategy; // 15 // 16 public Optional<Ticket> parkVehicle(Vehicle vehicle) { // 17 ParkingSpot spot = assignmentStrategy.findOptimalSpot(vehicle, availableSpots); // 18 if (spot == null) return Optional.empty(); // 19 spot.occupy(vehicle); // 20 return Optional.of(new Ticket(UUID.randomUUID(), vehicle, spot, Instant.now())); // 21 } // 22
Why these lines
The anchor for a 5 reads “extends by adding a class, not a branch; says so before being asked.” The strategy field is the class; the transcript at 01:14:32 is the saying so.
Reviewers see the dossier with names masked while reading, and the scorecard posts to the ATS on a decision.
Commitments & Principles
Automated technical hiring earned its bad reputation by scoring engineers on hidden signals and refusing to explain itself. Meritello is built on six non-negotiable commitments.
Every rating cites the moment it came from. Scores are backed by lines of code, test outcomes, and quoted speech—never by an unexplainable verdict.
Complete symmetry of information. There is no secret back-channel evaluation or separate shadow scorecard kept out of the interviewee's hands.
Disclosed clearly at the start of every session. Meritello never mimics a human interviewer deceptively or masks its machine nature.
Window blurs or audio disconnections are recorded as neutral, timestamped operational facts. They never become accusations of cheating on their own.
Stored privately in encrypted storage. You retain absolute ownership and can permanently purge your recordings, code, and dossiers at any time.
Rubric anchors, competence weightings, and stage requirements are transparently published before the timer starts, so no one walks in blind.
Pipeline
A stage change in Greenhouse, Lever or Ashby invites the candidate. When they submit, rules the team wrote can move the application, and the scorecard is posted back - signed, with the rounds and the dossier link.
“Moved to final review automatically: score 4.40 is at least 4.20.”
Signed by nobody: the platform wrote it. A reviewer’s override that moves the score runs the rules again; one that already fired does not fire twice.
Employer Pricing
Priced by completed assessments, not by seats. During the beta, teams run a pilot with us; the paid plans are the prices we plan to charge after it.
Talk to us
Run a real opening on the employer workspace with us while the platform is in beta.
$299/ month
For a team running one or a few openings at a time.
Custom/ annual agreement
For teams running many openings, with setup done together.
Frequently Asked Questions
Yes. The dossier keeps the recording, the transcript, every version of the code and every test run from the round. A score's citation opens the exact lines or the exact moment it refers to, so a reviewer checks the claim rather than trusting the summary.
Connect a provider with its API key and a webhook secret. When a candidate is moved into the stage you name, they are invited to the opening's assessment. When they submit and when you decide, the scorecard and a link to the dossier are posted back, signed with your secret.
You write the criteria and their weights, and an anchor for each of the five levels. Different openings can use different rubrics; within an opening every candidate is scored against the same one. A reviewer can override a score, with a written reason that stays on the record.
The room records focus changes, full-screen exits, pastes, camera and connection events with timestamps, and the High Stakes profile blocks pasting in the editor. The dossier shows that timeline and a score that is a fixed sum, not a verdict. The stronger check is the interview itself: the interviewer asks about the code that was written, and the answer is on the recording.
Practice with structure. Hire with evidence.