What a placement-readiness score actually measures

Most training programmes tell you that you are "job ready" on the day you finish. The date you become ready is the date the course ends, which is a remarkable coincidence.

We do it differently. Every learner has a placement-readiness score out of 100, visible to them from early in the programme, recalculated as they work. It is the single number our placement team looks at before putting anyone in front of an employer.

The interesting part is not the score. It is the formula, and specifically what we refused to put in it.

Why publish the weights at all

A hidden score is a rating of you by people whose reasoning you cannot inspect. That is uncomfortable enough in a credit bureau; in a training programme, where the whole point is to help you improve, it is actively counterproductive. If you do not know what moves the number, you cannot act on it, and the score stops being feedback and becomes a verdict.

So the weights are published in the portal, next to your score. You can see exactly which behaviour raises it. That is not generosity — a score you can act on is the only kind that does the job we built it for.

It also disciplines us. Once the weights are public, we have to defend them. Anything in there for our convenience rather than your employability becomes visible immediately, to you and to any employer who asks.

What goes in

The score is weighted across the things that actually predict whether someone will do well in a junior interview:

Course progress. Have you covered the material? This is the floor, not the ceiling — completion alone is not readiness, and it is weighted accordingly.

Graded assignments. The 23 mentor-marked projects, and how you did on them. This carries real weight because it is the closest thing we have to the actual job: build something, submit it, receive criticism, fix it.

Quiz performance. Cheap to measure, useful as a check on whether the concepts landed, weighted modestly because recognising a right answer is easier than producing one.

Attendance and consistency. Live classes attended, streaks maintained. This is a proxy for something employers ask about constantly and no CV can show: whether you keep going when it stops being novel.

Mentor assessment. A human judgement from the person who has read your work all year. Weighted, structured, and never the whole picture — but excluding it would mean pretending that the one person who knows you best has nothing to add.

Portfolio and deployed work. Whether there is something an employer can open. A junior candidate with a working deployed project is in a different category from one with a list of technologies.

What we deliberately left out

AI mock interviews. The portal has an AI interview practice tool. It is genuinely useful — you can rehearse at midnight, as many times as you like, without wasting anyone's afternoon or your own nerve.

It contributes nothing to your readiness score, on purpose.

The reason is simple. Anything you can repeat unlimited times against a machine that learns nothing about you between attempts is a measure of persistence, not of ability. If it counted, the rational strategy would be to grind the mock interviewer until the number went up, and we would have built a system that rewards practising against a machine over building things for people. The score would rise and the readiness would not, which is the exact failure mode we built the score to prevent.

So: practise as much as you want, and it will help you at a real interview. It will not move your score. Those are two different claims and both are true.

Payment status. Whether your fees are up to date has nothing to do with whether you can do the work. It is not in the formula.

Time enrolled. Sitting in a programme for longer is not evidence of anything. Only what you did in that time counts.

What the score is for

Two things, and it is worth being precise because a score can quietly acquire uses nobody intended.

For you, it is a map. Low on assignments but high on progress means you are consuming material without producing work — a common and fixable pattern, and the most useful thing a system can tell you in month three. The score exists to make that visible while there is still time to act on it.

For our placement team, it is a threshold. We do not send someone to an employer before they are ready. That is not gatekeeping for its own sake: a junior who interviews badly at 60 and would have interviewed well at 80 has burned a relationship that was theirs, and employers stop taking our calls. Waiting six weeks is better for everyone in that situation.

What the score is not is a ranking to be published, or a number an employer sees instead of your work. Employers see your readiness band alongside your actual projects, your certificates and your portfolio — the score is context for evidence, never a substitute for it.

The honest limitation

A readiness score predicts interview performance. It does not predict hiring, which depends on the market, the role, the other candidates, and a dozen things no formula sees. Someone at 85 can go through six interviews without an offer in a slow quarter. Someone at 70 can be hired next week by a company that liked their deployed project.

We publish the weights so you can improve the number. We are telling you its limits in the same paragraph so that improving it does not become the goal in place of becoming employable. The score is instrumentation. The work is the work.

If you want to see the formula in full, it is in the portal from your first week — or ask on a free demo call and we will walk you through it before you enrol.