Most graduate hiring in India is run as an annual event. The teams that get consistently better results run it as a continuous pipeline with an annual peak — a different thing entirely.
This is the operating model, quarter by quarter.
Q1 — decide the batch and the shape
Start by fixing which graduating batch you are building for and what the cohort should look like: how many, which functions, which locations, what the conversion target is. Do this before touching a campus calendar, because the calendar should follow the requirement rather than define it.
The most common failure here is inheriting last year's numbers. Ask instead what the business will need eighteen months out, which is when these hires become productive.
Q2 — map supply before committing spend
Find out where the talent you have specified actually sits, by city, institution and skill, before booking anything. This is the step most campus programmes skip, and it is the one that determines whether the rest of the year is efficient.
Expect the map to disagree with your calendar. Two or three institutions on it will be places you have never visited, and two or three on your calendar will not appear on it at all.
Q3 — engage early, concretely
Engagement that works is specific: a project challenge, a mentored sprint, a short paid engagement, a technical talk with a follow-up. Engagement that does not work is a talent community that collects registrations and then goes quiet.
The test is simple. If a student who engaged with you in Q3 cannot describe what they got out of it, you did not run a programme, you ran a mailing list.
Q4 — run the process fast
Compress the decision cycle as far as your governance allows. Every additional week between final interview and offer measurably reduces acceptance, and in the scarce categories it reduces it a lot.
Pre-clear the approvals before the process starts rather than during it. The most common cause of slow early-career offers is not the hiring team but an approval chain nobody warned in advance.
Continuous — measure the two numbers that matter
Offer-acceptance by institution, and twelve-month retention by sourcing channel. Aggregate metrics hide everything useful; these two tell you which relationships and which channels to keep funding.
Add a third if you run pre-final-year engagement: the proportion of students engaged last year who are still reachable this year. It is the only honest measure of whether early engagement worked.
Key takeaways
- Fix the cohort requirement before the campus calendar — the calendar should follow the requirement.
- Map where your specified talent actually sits before committing campus spend.
- Early engagement must be concrete; a quiet talent community is a mailing list, not a programme.
- Compress the offer cycle and pre-clear approvals — latency costs acceptance in scarce categories.
- Measure offer-acceptance by institution, retention by channel, and year-on-year re-engagement rate.
Questions
How far ahead should we build pipeline?+
Twelve to eighteen months for internship-to-full-time conversion models. Shorter than that and you are competing at peak season with everyone else; longer and the business requirement you planned against will have changed.
What size team does this need?+
Less than most people assume, if the sourcing is done against a pool rather than through volume campus travel. The binding constraint is usually interviewer availability, not recruiter headcount.
How do we justify pre-final-year spend internally?+
With the re-engagement metric. A cohort you can still reach a year later, at a fraction of peak-season cost-per-hire, is the argument — and it is measurable from year two onwards.