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.
An AI interviewer that questions the code as it is written, across design, systems, algorithms and behavioural rounds - and a dossier where every score cites what was said and done.
Real questions. Recorded evidence. Better decisions.
Meritello AI
Low-Level Design · Concurrency
Interviewer Question (Turn 1 of 3)
“Walk me through your approach to handling concurrent payment requests in PaymentService.”
Candidate Audio Stream (Speech-to-Text)
“I'm using Redis with a TTL as a fast-fail gatekeeper before the primary database transaction. Then in the finally block, we guarantee lock cleanup even if the network call fails...”
1class PaymentService {2private readonly idempotencyStore: RedisClient;3private readonly gateway: PaymentGateway;45async processPayment(req: PaymentRequest): Promise<PaymentResult> {6const lockKey = `pay_lock:${req.idempotencyKey}`;7const acquired = await this.idempotencyStore.setNx(lockKey, "locked", 30);8if (!acquired) {9throw new DuplicatePaymentError(req.idempotencyKey);10}11return await this.gateway.charge(req);12}13}
“Candidate proactively stated idempotency requirement and identified race conditions.”
Low-level design, system design, DSA, technical screen and behavioural - each on its own engine, all in one assessment.
Every criterion score cites code lines, a transcript moment or a test run. A citation that points at nothing is dropped, not stored.
Integrity comes only from what the room recorded. A signal that was not captured is shown as not captured, never as a clean score.
Greenhouse, Lever and Ashby: a stage change invites the candidate; a submission and a decision post the scorecard back, signed.
Against the usual ways
An online judge, a take-home and a panel each answer one question well. Here is what each leaves out, and what Meritello does instead.
| Capability | Meritello | Online judge | Take-home | Human panel |
|---|---|---|---|---|
The candidate is questioned about their own code Follow-ups come from what was written and said in the room, not from a script. | An AI interviewer asks about the code as it changes, and every question must cite something the candidate said or wrote Checked before it is spoken | Hidden tests decide; nobody asks why | Questions come days later, if at all | Yes - by whoever is free that hour |
How you know the work is theirs Signals recorded during the round, shown to the reviewer on a timeline. | Focus, full screen, pasting (refusable), camera and connection are recorded with timestamps; nothing uncaptured is scored Recorded, never assumed | Submission-time heuristics, no session record | None; the work is done unseen | The interviewer's memory |
Kinds of round in one loop What a senior hire actually needs to demonstrate. | Low-level design with running tests, system design on a whiteboard, DSA, technical screen and behavioural 5 kinds | Algorithm problems | One project, usually front-end or CRUD | Whatever each interviewer prefers |
What the reviewer sees behind a score A number is only as good as what it points at. | Each criterion score cites code lines, transcript moments or test runs; overrides need a written reason Cited or dropped | Pass/fail counts | A repository and an opinion | Notes written after, from memory |
How it reaches the ATS Where the hiring team already works. | A stage change in Greenhouse, Lever or Ashby invites the candidate; the scorecard is posted back, signed; rules can move an application on their own Both directions | Usually a score field or an export | Manual | Manual scorecards |
What the candidate gets afterwards Whether the person who did the work learns anything from it. | The full report with cited evidence and practice drills - or only a confirmation, if the hiring team keeps results private. Their choice, per assessment The team decides | A pass or a fail | Usually nothing | Rarely anything specific |
The interviewer
It does not follow a script. Each question comes from what was just said and what was just written, and it has to point at one of those to be spoken at all.
The transcript is the interviewer's memory of the conversation: what was claimed, what was asked, what was answered.
The interviewer sees the code as it changes, where the cursor is, and whether the last run passed or failed.
The criteria and their anchors are written by the hiring team ahead of time; the interviewer works towards them and never reveals them.
One question at a time, in the hiring team's chosen manner. A question that cites nothing the candidate said or wrote is rejected and replaced.
const acquired = await this.redis.setNx(lockKey, "locked", 30);
if (!acquired) throw new DuplicatePaymentError();A lock is taken with a 30-second TTL, and nothing in the file releases it.
The question
“You've acquired the lock with a 30-second TTL. What happens if the payment gateway takes 35 seconds to answer?”
Concurrency and fault tolerance
It asks; it does not answer. Hints, when the hiring team allows them, come one level at a time and only when asked or when the candidate is stuck.
Integrity
The rooms record focus, full screen, pasting, the camera and the connection - with timestamps and durations. A reviewer scrubs to any moment. The score is a sum, not a verdict, and the hiring team chooses how strict the round is.
Webcam and audio recorded, paste events audited, flagged after 3 tab switches.
Pasted 780 characters
{ type: "COPY_PASTE", severity: "low", atMs: 1420000, metadata: { chars: 780 } }
A sum, not a verdict. The reviewer sees every signal with its timestamp and decides. Nothing here accuses anyone.
Two sides of the table
A hiring team and a candidate see the same record of what happened in the room. The team decides how much of it the candidate keeps.
Assessments built from up to five kinds of round, rubrics with written anchors, and a dossier for every candidate where each score cites the moment it came from.
Kinds of round
5
Any of them in one assessment
Blind review
On/off
Names masked while the evidence is read
Score overrides
With a reason
Kept beside the machine’s score
Team notes
Cited
Each one can point at a line or a moment
Resume verification & CS fundamentals
Distributed capacity & architecture
OOP machine coding & live tests
Technical trade-offs & crisis ownership
Five Interview Rounds
Each round runs in its own room - an editor, a canvas or just a conversation - with an interviewer that knows what that round is for.
Object-oriented modelling, extensibility and working code, across several files, with tests.
public class ParkingLotService { // Strategy injected so spot choice can change without touching parking private final SpotAssignmentStrategy assignment; public Ticket park(Vehicle v) { Spot spot = assignment.assignSpot(v, this); return Ticket.open(v, spot, clock.instant()); } }
Interviewer
“You separated the assignment strategy. What happens when two cars reach different gates in the same millisecond and both are offered the last spot?”
Interactive preview
Pick an answer and watch the follow-up change. The real interviewer generates every question from what you say and write - this is a scripted preview of that behaviour.
Feedback for this exchange
Appears after the follow-up: two things that went well and one thing to work on, tied to the answer you gave.
Real Developer Environment
Interviews shouldn't feel like typing into a dumb text area. Meritello provides a full-featured Monaco environment equipped with the tools senior engineers actually rely on.
1package com.meritello.ratelimiter;23public class RateLimiter {4 private final int capacity;5 private final AtomicInteger currentTokens;67 public boolean acquire(int permits) {8 while (true) {9 int current = currentTokens.get();10 if (current < permits) return false;11 if (currentTokens.compareAndSet(current, current - permits)) {12 return true;13 }14 }15 }16}
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.
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.
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
Transparency For Candidates
No vague rejection emails or black-box silence. You receive a structured dossier showing what you demonstrated, where you excelled, and exact moments to practice for next time.
Post-Interview Synthesis Report
“Candidate noted: ‘I will assume only one car parks at a time for now.’ Interviewer followed up on thread safety.”
Line 14 in ParkingLotService.java lacked synchronization lock.
Recommended Next Practice Drill
Practice: “Thread-Safe In-Memory Key-Value Store with TTL” (Targeting Concurrency)
The Continuous Loop
Interviews shouldn't be isolated dead ends. In Meritello, every session generates structured learning signals that feed back into targeted practice, turning past friction into future mastery.
Work on algorithmic invariants, OOP patterns, and system design canvases.
Take a realistic, voice-driven mock session with adaptive follow-ups.
Every utterance, keystroke, and test result is logged into an objective record.
Receive clear, timestamped observations tied to pre-published rubrics.
Turn identified gaps into tailored practice drills in your candidate dashboard.
Return to the arena with measurable progress and renewed confidence.
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.
Privacy & trust
Practising an interview means speaking, sharing a screen and being recorded. These are the rules the product holds itself to.
The system check releases the camera and microphone as soon as it finishes. Consent is per device and the camera is optional in voice rounds.
Video and audio go to private object storage. Playback happens through short-lived signed links issued only to you; nothing is public and nothing is embeddable.
One action removes the transcript, code, report and recorded media for that session. Deleting a behavioral session also removes the stories it created.
Leaving fullscreen or losing focus is recorded as a signal with its timestamp, shown to you in your own report. It never becomes an accusation or a score on its own.
Ratings quote what you said and wrote. Nothing is inferred from your face, your voice or your accent, and reports never contain a hiring verdict.
Email verification to start a session, two-factor authentication for every staff account, and an append-only audit log of every administrative action.
The full detail is in the privacy policy and the terms of service. Ask a question
FAQ
Practice with structure. Hire with evidence.