The old loop tested hidden knowledge
Most campus loops claim to measure fundamentals, but they often measure something narrower: whether a student already knows the rituals of professional interviewing. Candidates who had friends in tech, expensive prep resources, or repeated interview exposure looked polished. Candidates with equal potential but less context looked unready.
That created a noisy funnel. Interviewers confused unfamiliarity with weakness, and candidates spent half the session trying to decode what the company wanted instead of showing how they learn.
The prep packet changed the room
The redesigned loop started before the interview. Candidates received a short packet that described the product surface, the kind of repo they would see, the tools they could use, and the scorecard dimensions. It did not give away the answer. It removed the guessing game.
That small context shift made the interview more rigorous. Students arrived with better questions, interviewers spent less time restating basics, and the session moved faster into the work that mattered: reading code, making a safe change, and explaining the path they chose.
The repo got smaller and more realistic
Campus candidates do not need a giant production codebase to prove they can learn. They need a repo with enough texture to expose habits: a few files, a failing test or bug report, one product constraint, and one or two tempting wrong paths.
A smaller repo also made scoring fairer. Interviewers could compare how candidates approached the same source of ambiguity instead of rewarding whoever happened to recognize a problem pattern from interview prep.
Learning velocity became the signal
The strongest candidates were not always the fastest. They were the ones who formed a hypothesis, checked it against the code, used AI or docs without surrendering control, and improved their answer when the interviewer added a constraint.
That is the signal campus hiring should care about. A new grad will not know your stack on day one. The question is whether they can absorb context, make progress without thrashing, and become useful quickly inside a real engineering team.
Make the early-career bar explicit
Diego can help turn a campus loop into a fairer, sharper hiring system: prep materials, repo exercises, interviewer calibration, and a scorecard that rewards real learning velocity.