Placement readiness
A résumé made of proof
A student picks the role they are aiming at and the work lines up behind it. Everything they finish is judged, certified and attached to a repository, so the résumé is assembled from evidence rather than written from memory.
What students build, and what the job needs
Not a comment on how anyone teaches. It is what a typical portfolio holds on the day a recruiter opens it, set against what a first role actually asks for.
What students build today
A to-do app from a tutorial
Followed step by step, identical to ten thousand others, with nothing in it the student had to decide.
A group project with one real contributor
Four names on the slide, one name in the commit log, and no way for a reader to tell which.
A certificate that proves attendance
It says a course was completed. It cannot say what was built, or whether it worked.
What the job needs
Something wired into an unfamiliar SDK
Under a deadline, against documentation nobody simplified for them, and working at the end of it.
Work an individual can be held to
Commit by commit, with the reasoning visible, so a reviewer knows exactly who did what.
A body of work someone can inspect
Repositories a recruiter can open, scores they can question, and evidence for every claim on the page.
01 · PICK A ROLE
The target comes first, so the work points somewhere
Choose what you are aiming at
Forward-deployed engineer, full-stack, AI integration. The role decides which labs, challenges and hackathons count toward it.
Follow a roadmap, not a syllabus
A sequence of real assignments and projects rather than a certificate course. Each step is something built, not something watched.
See the gap while there is time to close it
The score moves with results, so a student in second year can tell how far they are from the bar for the role they picked.
02 · BUILD THE RECORD
Every finished piece leaves something a stranger can verify
A certificate with the evidence behind it
Not a participation slip. It points at the judged work, the criteria it was scored against, and the rank it earned.
The code stays attached
Every line of the résumé links to the repository it came from, so a recruiter reads the work instead of taking the claim.
One profile, four years
Labs from second year and hackathons from final year land in the same place, so nothing is reconstructed in placement season.
Judging Score
0/ 100
Judging Criteria
Technical
28/30
Innovation
24/25
Track Fit
25/25
Execution
15/20
Impact
22/25
Loops HouseClaude × Loops
Gold Certified Builder
This certificate recognizes outstanding achievement in building and shipping high-quality projects.
03 · HAND IT OVER
A shortlist the office does not have to personally vouch for
Ranked on what they built
The overall builder score orders a cohort on judged, cited work rather than on aggregate marks or on who interviews confidently.
Every name carries its evidence
Hand it over without vouching for it personally: the repos, the scores and the reasoning travel with the list.
Exportable, like everything else
The same workbook export the department uses for evaluation carries the shortlist to whoever needs it next.
Placement readiness
Start with one cohort
Run a semester and look at what the record holds at the end of it, before anyone commits to a programme.