Hiring freshers through campus drives: shortlisting on skills, not just CGPA

For a company hiring freshers, campus drives are efficient in one way and wasteful in another. A college brings a batch of candidates together in one place, on one day. But the usual shortlisting method, a CGPA cutoff followed by a generic aptitude test, filters out capable people and lets through some who cannot do the work. The interviews then carry the whole burden of finding out who can.

This guide is for the recruiters and engineering managers who hire from campuses: how to set criteria, how to test, and how to work with the placement cell so the drive finds the people you are looking for.

Criteria: use the cutoff, but know what it costs

A CGPA cutoff is not wrong. It is quick, it is easy to explain, and it correlates with some of what you care about, such as consistency. But it measures university exams, which are not the job, and a cutoff that is higher than the role needs removes candidates you would have hired. Set it at the level the role genuinely requires, say so in the notice, and let the test do the rest of the sorting.

Test the job, not the trivia

The most useful thing a campus test can do is look like the work. For a software role, that means a coding problem the candidate has not seen, marked by running their code against hidden test cases, in a language they choose. Puzzle-style problems that turn on one well-known trick mostly test whether the candidate has seen that trick.

• Write problems around realistic scenarios rather than famous puzzles, so preparation cannot substitute for skill
• Mark on hidden test cases, including edge cases, so partial understanding shows as partial marks
• Keep aptitude sections if the role needs them, but weight them to the role, not by habit
• Ask a candidate to explain their approach in the interview, since a candidate who cannot explain code they submitted did not write it with understanding

The best campus test is one a candidate cannot prepare for except by getting good at the job.

Fairness across colleges

If you hire from several colleges, you want to compare candidates across all of them. That only works if every candidate sits the same paper under the same conditions and is marked the same way. A test run on different platforms, or proctored differently at each campus, gives you scores that cannot be compared.

On Assessly, every applicant takes the same proctored test in a locked-down desktop app with an ID check, whichever college they are at, and faculty review every flag. You see how each candidate did, question by question, with one paper and one way of grading across every college.

Working with the placement cell

The placement cell is your partner in the drive, not a mailbox. Give them the criteria and the test pattern early, in writing. Agree the schedule, the rooms and the interview slots before the day. Share results as a shortlist the same day, and tell them who received offers so they can close the loop with students. Colleges remember the companies that ran a clean drive, and send them their best candidates next year.

The short version

Set a CGPA cutoff only as high as the role needs. Test on unseen problems that look like the work, marked on hidden tests. Give every college the same paper under the same rules. Treat the placement cell as a partner and close the loop with them. Assessly for companies runs campus drives this way, and your first drive is free.