Your credit score tells you where you stand financially without looking at every transaction. A hireability score does the same for your interview readiness: it's a single persistent number - on a 300-850 scale - that reflects how well you'd actually perform in interviews for a specific role archetype, built up from every practice session you complete.
Unlike the pass/fail grade you get after one interview, a hireability score is cumulative. It accounts for how consistently you perform, how hard the practice rounds you've cleared were, and how you compare to a benchmark for your target role. The goal is a number that means something beyond a single session - something you can track, improve, and eventually show to people who need to know you're serious.
Key takeaways
- A hireability score is a 300-850 standing for a specific role archetype (e.g. Software Engineer - Coding, Behavioral, Product Manager).
- It's computed across all your scored practice sessions, not just the latest one.
- Four components drive the score: performance, consistency, difficulty adjustment, and pool percentile.
- The score drifts downward if you stop practicing - which is the design; it reflects current readiness.
- The single highest-leverage action to move your score is always surfaced alongside the number.
How a hireability score is calculated
The score is built from four components, each weighted differently.
Performance (40%)
The largest driver. This is a recency-weighted average of your rubric scores across all sessions in an archetype - the same criteria your interviewer would evaluate (communication, problem-solving, technical depth, etc.). Sessions from the past month count roughly twice as much as older sessions, so fresh practice matters more than a strong run you did six months ago.
Consistency (20%)
A strong average with wild variation is weaker than a slightly lower average with tight variance. This component rewards candidates who reliably perform at a level, not those who ace one session and bomb the next. Low variance across sessions scores higher; high variance drives this component down.
Difficulty adjustment (25%)
Not all practice sessions are equal. A senior-level panel-grilling round is harder than a junior warmup, and beating a hard round should count more. This component applies a multiplier based on the intensity (warmup / standard / panel-grilling) and seniority level (junior / mid / senior / staff) of each session. A steady diet of easy rounds doesn't build the score as quickly as clearing genuinely hard ones.
Pool percentile (15%)
The final component puts your score in context: where do you sit relative to other candidates practicing the same archetype? Early on, while the platform builds its distribution of real sessions, this leans on benchmark data. It's labeled "provisional" in the UI so you know - once enough real session data exists for your archetype, the benchmark is replaced by actual peer data.
The 300-850 scale
The four components combine into a 0-100 quality score, then remap onto the 300-850 credit-score scale - deliberately chosen because it makes the number feel like a standing you build, not a percentage you pass or fail.
| Band | Score range | What it means |
|---|---|---|
| Building | 300-549 | Early reps; the number is moving, not settled |
| Competitive | 550-649 | Strong enough for most screening stages |
| Strong | 650-749 | Confident in this archetype; clearing hard rounds |
| Standout | 750-850 | Top-tier performance, consistent at high difficulty |
Why the score decays
A score you stop defending drifts back toward the floor - by design. If you aced behavioral interviews six months ago and haven't practiced since, your readiness today is genuinely lower. The decay kicks in after a two-week grace period from your last session; it can erode at most 40% of your headroom above the minimum. The fix is simple: keep doing reps.
How to improve your hireability score
1. Do more sessions - but make them count
Volume matters, but difficulty matters more. A warmup session at junior level moves the score much less than a panel-grilling session at senior level. Push into harder intensity settings faster than feels comfortable. The difficulty-adjustment component (25% of the score) specifically rewards this.
2. Focus on consistency, not peaks
One perfect session doesn't build a high score as quickly as six good ones. The consistency component (20%) punishes variance. If you're swinging between 90 and 50, tighten your floor: identify what breaks in your weak sessions and fix that first, rather than chasing a higher peak.
3. Act on the top mover
Every score comes with a "top mover" - the single highest-leverage criterion holding your score down, pulled from your weakest recent session, with an estimated score gain attached. The platform does the triage for you. If complexity analysis is flagging, that's the one to drill. If structured communication keeps landing below the rubric, that's where the reps go.
4. Practice across archetypes
Your score is tracked separately per role archetype: Software Engineer - Coding, System Design, Behavioral, Product Manager, Recruiter Screen. Each archetype builds an independent standing. If your target role requires both coding and behavioral loops, both scores matter. Building a strong standing in multiple archetypes gives you a more complete profile of interview readiness.
5. Don't let it stale
The decay mechanism exists for a reason. A hireability score is a current readiness signal, not a historical achievement. The candidates who maintain high scores do regular, short maintenance reps - not a frantic burst before an application, but steady sessions that keep the number from slipping.
What your score tells a recruiter
A hireability score doesn't replace an interview. What it does is give you - and eventually anyone you choose to share it with - a data-backed picture of your preparation. A Standout score in System Design at staff-level difficulty is a different signal than a Building score in the same archetype. It quantifies something that was previously a gut feel.
More importantly, it tells you where you are honestly, before it matters. Most candidates don't know how ready they actually are until they're in a real interview, at which point the feedback loop is too slow. The score shortens that loop.