Campus hiring that assesses every applicant, not the top of an aptitude ranking

Four thousand applications and sixty seats is a coordination problem. The students that filter misses are the ones you most wanted to find.

Four thousand applications, sixty seats, three weeks

Campus season is a coordination problem long before it is a judgement problem. The usual process tests aptitude on a form, interviews the top two or three hundred, and quietly accepts that everyone else was ranked by a multiple-choice score nobody would defend to the student who was rejected.

The people that filter misses are predictable: strong engineers from regional-medium colleges who are hesitant in an English aptitude test, and late bloomers whose CV has nothing on it yet because they have not had the internship that signals competence.

What a campus campaign looks like

• 1

  One link per campus, or one for all of them

  Filter and compare by campaign later. Placement cells can share the link directly; there is nothing to install and students need only a phone and a connection.

• 2

  Voice interview plus a coding round

  Both generated from the job description. The coding task runs in the browser alongside the conversation, and the two results are blended into the final rating - the interview at 75%, the coding round at 25%.

• 3

  Every student gets an answer

  With a reason. This is the part that almost never happens at campus scale today, and it is the part placement cells remember when they decide who to invite back next year.

• 4

  A ranked shortlist your panel can defend

  Each score cites the timestamp in the interview that produced it, so a panel debate is about evidence rather than about whose gut to trust.

Fairness, and being able to show it

Campus hiring is the most scrutinised hiring most companies do, and the one most likely to be challenged. Every assessment here carries its evidence, integrity signals are shown as signals rather than acted on automatically, and the consent a student gave is stored verbatim with its timestamp. If a placement cell or a regulator asks how a decision was reached, there is a record - see security and data protection and the privacy policy.

Hiring at volume outside campus? See bulk hiring. Ramping a contact centre? See BPO hiring.

Common questions

How is this different from an online aptitude test?

An aptitude test ranks people on a multiple-choice score. This is a conversation: it hears the answer and asks the next question because of it, then scores against a rubric with the moment that earned each score attached. You can defend the outcome to a student who asks why.

Can it assess coding as well as communication?

Yes. A coding task is generated for the role and run in the browser, scored separately on logic and correctness, code quality, efficiency, problem-solving and edge case handling - so someone who writes working-but-slow code is not confused with someone who cannot write it at all.

Does it work for tier-2 and tier-3 campuses?

That is where it helps most. Candidates answer in the language they think in and still get a CEFR English level on the report, so a strong engineer from a regional-medium college is not marked down for hesitancy in a second language.

How long does a campus season take?

The interviews themselves are not the constraint any more, because they all happen in parallel. One IT services intake assessed four thousand applicants instead of three hundred, in the same calendar window.

What does it cost for a campus intake?

CV scoring is 25 credits per CV and a twenty-minute interview is 800, where a credit is a rupee. There are no per-seat licences, so inviting every panel member and placement coordinator to view reports costs nothing.