Runs on your machine Single binary No account

Mock technical interviews that actually push back.

Practise the SRE, platform or engineering manager loop you have booked. One question at a time, follow-ups on what you actually said, and a rubric you never see. Then a second model grades the transcript out of 100 and quotes your answers back to you.

In private beta.

Static Go binary macOS · Linux · Windows Runs against local models In private beta
mockterview start --role sre --type incident-scenario
Site Reliability Engineer · senior · Incident Scenario, question 3/8

Q: It's 02:14. Checkout p99 latency has gone from 180ms to 4.2s over the
last eight minutes and the error rate is at 6%. Payments and search look
normal. You're on call and you've just opened the laptop, what do you do
first, and what are you looking at?

│ First I'd declare a Sev-2 and page the checkout owner, then check
│ whether this correlates with a deploy. I'd look at the deploy
│ timeline before touching anything. Impact first: what fraction of
│ checkouts are failing, and is it all regions or one?
│
│

ctrl+d submit · ctrl+c quit
2 models
One interviews, one grades, separately
9 presets
3 roles × 3 seniorities, plus your own
100-point rubric
Weighted criteria, hidden during the interview
0 bytes
Leave your network when pointed at a local model
Why not just use a chatbot

A chat window tells you that was a great answer. A rubric tells you it was a 6.

Practising in a general-purpose chat has two failure modes: it is relentlessly encouraging, and it forgets what it was assessing. mockterview is built the way a real loop is, brief, rubric, panel, debrief, and keeps the assessment hidden until the end.

01

The rubric stays hidden

The interviewer is briefed with weighted criteria it is told never to reveal. You cannot write to the test, because you cannot see the test, exactly like the real thing.

02

Two models, two jobs

A higher-quality model runs the conversation at temperature 0.7. A separate, cheaper grader scores the finished transcript at 0.2. The grader is never the model you were talking to.

03

Scores with the evidence attached

Every criterion comes back with a score out of ten, its weight, and a comment that quotes your own words, so the feedback can be argued with.

What you get on day one

No account to make, and nothing that stops working when the Wi-Fi does. Beta members get the binary, every bundled role and rubric, and the updates as they land. Every feature, in detail.

◆

Adaptive interviewer

Asks one question at a time, follows up on vague answers, and escalates depth for mid, senior, and staff candidates.

◆

Live incident simulation

Role-plays the production system: symptoms only appear when you go looking, and a complication lands partway through.

◆

Weighted grading

Per-criterion scores out of ten, normalised into one weighted result out of 100, with written feedback per criterion.

◆

Progress tracking

Every session is stored locally. history shows your average per interview type and the delta from your first run to your latest.

◆

Editable YAML roles & rubrics

Drop in a new role or interview format as a YAML file. No code, no rebuild, no waiting on a vendor roadmap.

◆

Bring your own model

Talks to any OpenAI-compatible endpoint. Point it at a local runtime and the whole thing works offline.

◆

Single static binary

No CGO, no runtime, no daemon, no container required. Copy one file onto the machine and run it.

◆

Local SQLite history

Transcripts and scores live in one file you own. Back it up, inspect it with any SQLite client, or delete it in one command.

◆

No telemetry, no accounts

Nothing phones home. The only secrets involved are your own endpoint URL and key, kept in a local .env.

How it works

Four steps, about twenty minutes

Choose the loop

Pick a role, a seniority, and an interview format, or pass them as flags and skip straight in.

Sit the interview

Up to eight questions, multi-line answers, Ctrl+D to submit. The interviewer follows the thread you actually opened.

Get graded

The grader scores the transcript against the hidden rubric and writes feedback that cites what you said.

Track the delta

Re-run the same format next week and watch the per-type average move.

Screenshots

Real output, not a mockup

Every panel below is verbatim output from the tool, the picker, a live incident interview, the graded result, and the history commands.

mockterview start
Select a role

> Engineering Manager
  Platform Engineer
  Site Reliability Engineer

↑/↓ move · enter select · ctrl+c quit

Role, then seniority, then format, or pass --role, --seniority and --type and go straight to question one.

Your loop, your rubric

Encode how your company interviews

Roles and rubrics are plain YAML. Copy one, change the weights to match your own scorecard, and every interview you sit is graded against it. The file's id is what you pass to --role and --type.

  • Weights are yours. Move the numbers to match what your own scorecard rewards.
  • New formats in one file. Code review, data modelling, security design, drop a rubric in.
  • Seniority bands. Mid, senior and staff expectations tune how demanding the interviewer is.
  • Custom rubrics, built with you. During the beta we build the first one from your scorecard, then it is yours to edit.
config/rubrics/system-design.yaml
id: system-design
name: "System Design"

# Short brief the interviewer uses to open and steer.
# It never reveals the criteria or scores below.
interviewer_brief: >
  Open with a deliberately ambiguous, realistic design
  prompt appropriate to the candidate's role and
  seniority. Ask ONE question at a time. Follow up on
  vague answers by asking for specifics. Do not
  lecture; do not reveal how you are assessing them.

# Hidden rubric. Consumed by the grader only.
criteria:
  - id: requirements
    name: "Requirements & scoping"
    weight: 15
  - id: architecture
    name: "High-level architecture"
    weight: 25
  - id: tradeoffs
    name: "Trade-offs & bottlenecks"
    weight: 25
Use cases

Who practises with it

You, with a loop booked

Prepare for the real thing

Run the same format three times in a week before an SRE or platform interview and watch the score move. It does not go easy on you because you sound confident, and it will not tell you an answer was great when it was a six.

You, going up a level

Find out if you read as staff yet

Staff expectations are written into the role files, more scope, more ambiguity, second-order effects. Sit the staff-band version of your own discipline and read the rubric comments on where you still sounded senior.

You, rusty or switching track

Get reps without burning a real interview

Coming back after a break, or moving from dev into SRE, the first two interviews are where you learn what you forgot. Spend those here, at 3pm on a Tuesday, instead of on the company you actually wanted.

Coaches & bootcamps

Give a cohort unlimited practice

Every learner gets their own history file showing progress across the course, and you get rubrics that match what you actually teach. Nobody counts the sessions, in week one or week six.

Hiring panels

Sit the loop before you run it

Encode your real scorecard as a rubric file and have each interviewer take the loop they are about to give. Disagreements surface against something written down rather than in the debrief.

Anyone who would rather not be logged

Your worst answers stay yours

Practice means being bad at it first. Point it at a model on your own machine and no account, no vendor and no future employer ever sees the session, the transcript is a local file you can delete in one command.

Beta

In private beta

mockterview is in private beta. Request access and you will hear when there is a seat.

Request access

Questions before you apply

Is mockterview open source?

No. Beta members get it as a binary. The role and rubric files ship as editable YAML, so you can change how it interviews without access to the source.

What do I need to run it?

One machine and an OpenAI-compatible model endpoint. That can be a local runtime on your laptop, a model server inside your network, or a hosted provider behind a proxy, the endpoint URL and key live in a local .env file.

Do my answers leave my machine?

Transcripts are written to a local SQLite file and are sent only to the model endpoint you configure. Point that at a model inside your own perimeter and nothing leaves it. mockterview itself has no telemetry and no accounts; we cannot see your sessions, in the beta or after it.

Can I use my own scorecard or interview format?

Yes; that is the point of the YAML rubrics. Criteria, weights and the interviewer brief are all editable, and a new interview format is a new file rather than a code change. That applies whether "our" means your company or just the kind of loop you keep failing.

Can we use this to assess real candidates?

No, and the licence does not permit it. mockterview is built for a person to practise on themselves, or for an interviewer to sit a loop before they run it. It is not built, tested or offered as a tool for screening, ranking or selecting job applicants, and its scores must not inform a hiring decision about anyone other than the person who sat the interview. Using it that way would put you in scope of the EU AI Act's rules for high-risk employment systems, as the deployer.

Is the interviewer a person?

No. Both the interviewer and the grader are AI systems: two separate language models, as described above. Every question, score and comment you receive is generated, not written by a human reviewer.

What happens after I apply?

Your application goes on the beta list. When your place opens you get the binary, the install steps and every bundled role and rubric by email.

Request access

Tell us the loop you are preparing for. Beta members get the binary, the install steps and every bundled role and rubric.

No newsletter.