Why we won't tell you you're interview ready
We can see your practice. We can't see your performance.
· 5 min read · Building
There's a green badge we could ship tomorrow. Interview Ready. Users would love it. It's the single most requested thing after the match score, and it's the natural endpoint of every prep flow ever designed — do the work, earn the checkmark.
We don't ship it, and the reasons turned out to be more interesting than we expected.
Ready isn't a property you have
Start with the grammar of the claim. "You are interview ready" describes a state of a person. But readiness isn't a state — it's a relationship between you and one specific conversation that hasn't happened yet.
Ready for the hiring manager who spends forty minutes on system design, or for the one who spends forty minutes on how you handle conflict? Ready on a Tuesday when you slept, or on the morning your kid was up all night? Ready for the panel that liked you in minute one, or the one that had an internal candidate in mind before you joined the call?
Each of those is a different question, and we can't see any of them. A badge asserting readiness is a claim about a future event, made by a system with access only to a past one.
We can see practice. We can't see performance.
What we can genuinely observe is narrow: which questions you attempted, how long your answers ran, whether they contained specifics, whether you said them out loud or only read them.
What decides the interview is none of that. It's what happens when you're nervous, when the question arrives in an unfamiliar shape, when someone interrupts your best story thirty seconds in, when you like the interviewer and start rambling. The gap between rehearsal and performance is the difficult part, and it's precisely the part we have no visibility into.
Any system telling you you're ready is measuring the rehearsal and making a claim about the performance.
Both possible verdicts do damage
This is the argument that settled it.
If we say "ready" and we're wrong, we've caused the outcome. You stopped preparing because a system told you to. And the failure mode is quiet — nobody walks out of a bad interview thinking the app misled me. They think I wasn't good enough. We'd have taken confidence from someone and left them holding the blame for it.
If we say "not ready" and we're wrong, it's worse. We've told a qualified person they're not good enough for a job, on evidence we don't have, at the exact moment they were deciding whether to go for it. Some of them won't apply. We would never find out, and it would be the most harmful thing our product ever did.
A verdict with no ground truth behind it isn't a neutral piece of UI. It's an intervention in someone's career, and we can't justify making it in either direction.
Completion is not competence
There's a quieter version of the same problem: the progress bar.
Fill every section, reach 100%, and the interface has told you something — but what it's told you is that you touched all the steps, not that you can do the thing. Every learning product in existence blurs these two, because completion is trivial to measure and competence isn't.
The failure is invisible from inside. Someone who has read all twelve sections and said nothing aloud will register as complete, and they are the least prepared person using the product.
What we show instead
Observations, and no conclusion.
Which question areas you've attempted and which you haven't. How many you've said out loud rather than read. Where an answer ran four minutes when it should run ninety seconds. Which answers contain no specifics. What you marked as shaky and never came back to.
Each of those is a fact — checkable, stable, not a judgment. Together they're usually enough for the conclusion to be obvious, which is the point. The person who has practised two of nine areas and never spoken one aloud does not need a badge to tell them where they stand. And the person who has done all nine, out loud, twice, doesn't need our permission to feel ready.
The conclusion belongs to you because you hold the information we don't: how much time is left, how much the role matters, how you tend to do under pressure, whether you're the sort of person who sharpens on the day or unravels.
How to judge it yourself
If you want a rough test, these are the questions worth asking — none of which a tool can answer for you:
- Have I said my six or eight core stories out loud, not read them?
- Can I deliver each in under two minutes without losing the thread?
- Does every one contain a number and a clear statement of what I did?
- Do I have a real answer for the gap or weakness I'm hoping won't come up?
- Do I have two questions that only someone who researched this role would ask?
- If the first question lands badly, do I know how I'll recover?
Six honest yeses is as close to "ready" as the concept actually gets.
What it costs us
Am I ready? is the question people most want answered, and declining to answer it is not a satisfying product experience. A badge would improve our demo, our onboarding completion, and probably our retention.
We'd rather be the tool that tells you what you've actually done and lets you decide what it means. Confidence you didn't earn is worth less than uncertainty you can act on — and in an interview, borrowed confidence is audible.
All posts