Meritello for hiring teams

Every score, with the evidence
it came from.

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.

Rubric fixed before the first invitation
Recording, code history and test runs kept per round
Screen, DSA, low-level design, system design, behavioural
Integrity timeline from what the room recorded
A dossier, as a reviewer sees it
Sarah JenkinsStaff
Staff Distributed Systems Engineer · System design · round 2 of 4
4.60 / 5
weighted round score
Integrity 96
Transcript18:24

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.

Rate limiter · whiteboard + capacityDiagram, capacity, API contracts
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
Scores, each with its citation
Concurrency and consistency5/5

#transcript:1104000

Capacity reasoning4/5

#transcript:1290000

Failure modes5/5

#transcript:1611000

Communication4/5

#transcript:820000

A decision posts the scorecard to every connected ATS.

5

Kinds of round in one assessment

Low-level design with running tests, system design on a whiteboard, DSA, a technical screen and a behavioural round, each configured per stage.

1:1

Scores to evidence

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.

0

Assumed integrity signals

The integrity timeline shows only what the room recorded - focus, full screen, pasting, camera, connection. What was not captured is shown as not captured.

3

ATSs, in both directions

Greenhouse, Lever and Ashby: a stage change invites the candidate; a submission and a decision post the scorecard back, signed with your secret.

What the workspace holds itself to
  • Rubric fixed before the first invitation
  • Blind review: names masked while reading
  • Overrides need a written reason
  • Every automatic action leaves a note

The hiring workspace

One pipeline, every round in it, every score with its evidence.

Openings, assessments, applications and dossiers in one place. Click a stage to filter; click a candidate to open the evidence.

M

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 month

Candidates

148

every score cites evidence

Interviews This Week

34

22 completed · 12 scheduled

Completion Rate

92%

of invitations submitted within 14 days
Pipeline(Click stage to filter)
98 total in flight
Recent submissions
Click a candidate to open the evidence
Alex Chen4.8 / 5.0ParkingLotService.java:34
Posted to Greenhouse

“Put spot selection behind a strategy, so a new bay type is a new class, not a new branch.”

The assessment studio

Compose the loop once. Every candidate takes the same one.

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.

DraftSenior

Backend Engineer

165 min across 4 rounds
Proctoring, for every round
Webcam and audio recorded, paste events audited, flagged after 3 tab switches.
  1. Round 1screen

    Technical screen

    Resume-aware · fundamentals and the job description

  2. Round 2dsa

    Data structures & algorithms

    One problem · Java or Python · tests run in the room

  3. Round 3lld

    Low-level design

    Parking lot · Java · running tests

  4. Round 4behavioral

    Behavioral

    Ownership, problem solving, collaboration

The rubric studio

Define what good looks like before the interview starts.

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.

Criteria first.→Evidence second.→Decision last.
Competency Weighting

L5 · Senior Engineer

Total: 100%
Architecture & Low-Level Design (SOLID)25%
Thread Safety & Concurrency Primitives25%
Algorithmic Optimizations & Invariants20%
Defending Architectural Trade-offs20%
Production Resiliency & Failure Modes10%

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.

Five anchored levels

Focus on resilient architecture, optimistic concurrency, and system modularity

Scored 1 to 5, each with a citation

The dossier

Every score names what it saw.

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.

01. InterviewCode, speech and test runs, as they happen
02. EvidenceKept with timestamps: recording, code history, runs
03. EvaluationThe rubric applied, each score with a citation
04. ReviewA reviewer checks the citation, overrides with a reason
05. DecisionRecorded, and posted to the ATS

Dossier · one criterion, opened

Low-level design round · Parking lot · Java

Rubric chosen before the invitation

Object design

5 / 5 · weight 30%
#code:ParkingLotService.java:14-22

“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.”

ParkingLotService.java · lines 14 to 22version at 01:14:32
// 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.

Every version of the file is keptscrub to any moment

One record. Who sees what is the hiring team’s call.

Reviewers see the dossier with names masked while reading, and the scorecard posts to the ATS on a decision.

Commitments & Principles

Trust built on radical transparency.

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.

  • 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.

    Principle 1 of 6
  • The candidate sees what the company sees.

    Complete symmetry of information. There is no secret back-channel evaluation or separate shadow scorecard kept out of the interviewee's hands.

    Principle 2 of 6
  • The interviewer always identifies itself as AI.

    Disclosed clearly at the start of every session. Meritello never mimics a human interviewer deceptively or masks its machine nature.

    Principle 3 of 6
  • Session signals describe what happened; they do not accuse.

    Window blurs or audio disconnections are recorded as neutral, timestamped operational facts. They never become accusations of cheating on their own.

    Principle 4 of 6
  • Recordings belong to the person in them and can be deleted on request.

    Stored privately in encrypted storage. You retain absolute ownership and can permanently purge your recordings, code, and dossiers at any time.

    Principle 5 of 6
  • Criteria are published before evaluation.

    Rubric anchors, competence weightings, and stage requirements are transparently published before the timer starts, so no one walks in blind.

    Principle 6 of 6

Pipeline

What happens on its own, and how the ATS hears about it.

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.

Rules run when an application is submittedEach fires once per application · every firing leaves a note
The note it leaves in the dossier

“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

Start with a pilot on a real opening

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.

Beta pilot

Available now

Talk to us

Run a real opening on the employer workspace with us while the platform is in beta.

  • All five kinds of round in one assessment, any order
  • Rubric studio: weighted criteria with five anchors each
  • Evidence dossiers with recording, code history and test runs
  • Greenhouse, Lever and Ashby connectors

Growth

Planned after beta

$299/ month

For a team running one or a few openings at a time.

  • Up to 50 completed assessments a month
  • Unlimited reviewers
  • Everything in the pilot

Enterprise

Planned after beta

Custom/ annual agreement

For teams running many openings, with setup done together.

  • Unlimited assessments and openings
  • Custom problems for your own stack
  • A named contact who answers

Frequently Asked Questions

Questions from engineering leaders

Can our engineers review the candidate's code and listen to audio recordings?

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.

How does Meritello integrate with our ATS (Greenhouse, Lever, Ashby)?

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.

How do custom rubrics work across engineering levels (L4, L5, Staff)?

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.

How does the platform handle cheating or copy-pasted code?

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.

Get Started Today

Build better interviews.

Practice with structure. Hire with evidence.

Free candidate practice No credit card required Recorded with consent, deleted on request