Campus Hiring Playbook for Indian SMBs: From Drive to Day One

Every placement season, the same story plays out. The big IT services firms and product companies roll into the top campuses with polished decks, alumni panels, and offer volumes that make headlines. Smaller companies watch from the sidelines and conclude that campus hiring is a game for brands with deep pockets.

That conclusion is wrong, and it costs Indian SMBs some of the best early-career talent in the country.

Campus hiring works for smaller companies precisely because it is not a brand contest when done well. It is a process contest. A 40-person startup with a clear role definition, a fair selection process, and a warm pre-joining experience will out-hire a distracted large firm on the same campus more often than you would expect. Students remember who treated them like adults.

This playbook walks through the entire campus recruitment process for an Indian SMB, from deciding how many freshers you actually need to the moment they finish their first 90 days. It is long because the gaps between those steps are where campus hiring usually fails.

Why campus hiring makes sense for smaller companies

There are three reasons founders and HR leads at growing companies keep coming back to fresher hiring, even after a rough first drive.

Cost. Entry-level compensation is lower than lateral compensation for obvious reasons, but the real saving is in sourcing. A single well-run placement drive can produce a shortlist of twenty to fifty candidates in a day. Getting the same volume of mid-career applicants through job boards, agencies, and referrals takes weeks and agency fees that can run into a sizeable percentage of annual CTC per hire.

Culture fit. Freshers arrive without habits from a previous employer. That sounds like a cliché until you have tried to get a lateral hire from a large process-heavy organisation to work comfortably in a place where nobody files a ticket to get a laptop. Early-career talent adapts to your way of working because it is the only way of working they know.

Foundational skill building. If you train a fresher on your product, your codebase, your customers, and your quality standards, you build a person who understands your business from the ground up. In three years that person is a team lead who can train the next batch. Lateral hires can be excellent, but they rarely carry your institutional memory the way someone who grew up in the company does.

Why campus hiring fails when done casually

The failure modes are also predictable.

• A founder decides in a rush to "pick up ten freshers" without a role definition, so interviewers evaluate on gut feel and end up with a batch that does not match any real need.
• The company turns up at one college because someone knew the placement officer, hires whoever seemed sharpest, and never revisits the decision.
• Offers go out in the middle of the academic year, joining is six to eight months away, and nobody talks to the candidates in between. Half of them do not show up on day one.
• The ones who do show up get a laptop, a Slack invite, and a vague instruction to "shadow someone." Three months later, they are bored and looking elsewhere.

Each of these is fixable. None of them requires a big budget. They require a process, and that is what the rest of this article gives you.

Campus hiring vs lateral hiring: a practical comparison

Before committing to a campus recruitment process, it helps to be honest about what freshers are and are not good for. The table below is a working comparison for a typical SMB, not a universal rule.

The takeaway: campus hiring is a bet on the future that pays off only if you invest in the first year. If you cannot commit a mentor, a training plan, and a manager's time, hire laterally instead. Doing campus hiring half-heartedly is more expensive than not doing it at all.

Step 1: Define the fresher role, skill rubric, and headcount

The most common mistake in fresher hiring happens before anyone visits a campus. The company has not decided what it is hiring for.

"Fresher" is not a role. A fresher software engineer, a fresher sales development representative, a fresher accounts executive, and a fresher customer support associate need completely different rubrics, different colleges, and different interview panels.

Start from the workforce plan

Campus headcount should come out of your annual workforce plan, not out of a good mood after a funding round. Ask three questions:

1. Which teams will have work that a trained fresher can do productively by month four?
2. Which of those teams has a manager or senior who can actually mentor, given their existing workload?
3. What is the revenue or delivery trigger that justifies the headcount, and what happens if that trigger slips?

If a team cannot answer question two, it should not get freshers this cycle. A fresher without a mentor is an attrition statistic waiting to happen.

A practical rule for smaller companies: no more than one fresher per experienced team member in the first cycle. Ratios can loosen as your training programme matures and your first batch becomes the next set of mentors.

Build a skill rubric, not a wish list

Most fresher job descriptions are wish lists. They ask for strong fundamentals, excellent communication, leadership qualities, and a passion for learning. None of that is measurable in a 30-minute interview.

A skill rubric replaces adjectives with observable behaviours. Split it into three buckets:

• Must-have foundations. Skills the person needs on day one to benefit from training. For a developer, this could be basic problem decomposition and familiarity with one programming language. For a sales role, it could be clear spoken communication and comfort with rejection.
• Trainable skills. Things you will teach in the first 90 days. Your product, your tools, your process. Do not screen for these.
• Signals of trajectory. Evidence that the person learns fast and takes ownership. Projects, internships, competitions, side work, or even a well-explained failure.

Sample role scorecard: Associate Software Engineer (fresher)

A role scorecard is a one-page document that every interviewer reads before the drive. Here is a sample for a technology role at a product SMB.

Scorecards like this do two things. They align interviewers so that a candidate is not rejected by one panel for lacking a skill that another panel considered trainable. And they give the eventual hire a clear picture of what "good" looks like, which matters enormously for fresher onboarding.

Write one for every fresher role. It takes an hour and saves weeks.

Step 2: Choose colleges with a tier strategy

Once you know what you are hiring for, the question is where to find it. This is where smaller companies most often copy the large firms and get burned.

Why tier-1 campuses are usually the wrong first bet

Top-tier engineering and management institutes have placement processes designed around slot allocation. Companies are typically ranked by past offers and compensation, and the earlier slots go to the biggest brands. A first-time SMB recruiter often lands a late slot after the best candidates have already accepted offers.

That does not mean tier-1 is off the table. It means it should not be your only bet, and probably not your first.

The case for tier-2 and tier-3 institutes

Colleges outside the top bracket are where smaller companies win. Several things work in your favour:

• Placement cells are actively looking for reliable recruiters and will give you attention that a large firm's campus team would never get.
• Students are hungry, often the first in their families to enter a professional career, and less likely to treat your offer as a fallback.
• Compensation expectations are aligned with what an SMB can reasonably pay.
• Renege rates tend to be lower because the candidate has fewer competing offers, though you should still manage this actively (more on that in Step 5).

The trade-off is that skill levels vary more widely, so your selection process needs to do more work. That is fine. A good test and a good interview are cheaper than a bad hire.

Polytechnics and non-engineering streams

If your roles do not need a four-year engineering degree, do not restrict yourself to engineering colleges.

• Polytechnics and diploma institutes produce candidates with hands-on technical exposure, often at lower compensation expectations, and are a strong fit for support engineering, QA, field service, and operations roles.
• Commerce and BBA programmes are a natural pool for finance, accounts, operations, and sales roles.
• Arts, science, and mass communication streams supply content, customer success, marketing, and research roles and are often ignored by recruiters, which means less competition for you.
• MCA, BCA, and BSc computer science programmes are frequently overlooked by product companies that fixate on BTech and yet produce plenty of capable developers.

Match the stream to the role scorecard, not to habit.

Building relationships with placement cells

Placement officers are the gatekeepers of campus recruitment, and they remember how companies behave. A few principles:

1. Show up before you need them. Visit or call the placement cell months before the season with a clear description of your company, the roles, and your rough headcount. Ask what their process looks like rather than dictating yours.
2. Be honest about compensation and role. Placement cells lose credibility with students when a company misrepresents the job. They will not invite you back.
3. Give feedback after the drive. Tell them which candidates were shortlisted and, in general terms, where the batch was strong or weak. Very few recruiters do this and it builds goodwill fast.
4. Honour every offer. Withdrawing offers after a placement drive is the single fastest way to be blacklisted from a campus. Do not hire more than you can absorb.
5. Keep one owner. A single named person at your company should manage each college relationship so the placement officer is not passed between three different people.

Timing the placement season

Placement calendars vary by institution, course, and region. In general terms, campuses tend to run a main placement window in the academic year before graduation and may run additional windows for students who remain unplaced. Internship hiring typically happens earlier than full-time hiring.

Because this varies so much, treat it as a research task. Ask each placement cell for their calendar, and build your own campus hiring calendar around those dates. Plan backwards: if you want joiners in a particular month, count back the offer-to-join gap, the selection window, the college outreach period, and the internal preparation. For most SMBs that means planning starts well over half a year before the joining date.

A simple spreadsheet or a shared calendar in your HRMS is enough. What matters is that the dates exist somewhere other than in one recruiter's head.

Step 3: Employer branding on a budget

Students choose between companies based on what they know. If they know nothing about you, they default to the bigger name. The fix is not an advertising budget. It is presence.

Guest lectures and workshops

Placement cells and department heads are usually happy to host a practitioner who can talk about something real. A senior engineer walking through how your team debugs production incidents, or a sales lead explaining how B2B deals actually close, is more interesting to a final-year student than any recruiting video.

Keep it practical, keep it under an hour, and leave time for questions. Do not pitch the company in the lecture. Students see through that immediately. Let the placement cell mention that you are hiring.

Hackathons, case competitions, and problem statements

A small hackathon or a case competition costs little more than a few prizes and a weekend of your team's time. It gives you something more valuable than resumes: you watch candidates work.

You can also sponsor a problem statement in an existing college event rather than running your own. Offer a real, scoped-down version of something your team actually deals with. The students who take it seriously are your shortlist.

Internships as a pipeline

Internships are the most reliable employer branding tool an SMB has, because they convert directly into pre-placement offers.

A structured internship of a few months, with a real project, a mentor, and a proper evaluation at the end, does three things:

• It lets you assess a candidate over weeks instead of thirty minutes.
• It lets the candidate assess you, which reduces renege risk when you make an offer.
• It creates a group of students back on campus who talk about your company to their peers.

Pay interns fairly, give them real work, and end every internship with a written evaluation and a conversation about whether a full-time offer is on the table. Interns who are not offered should still leave with a reference and a clear reason.

Alumni and early joiners

If you already have employees from a particular campus, they are your best recruiters. Send them along on the drive, let them run the pre-placement talk, and give them a few minutes to answer honest questions without HR in the room.

Students trust someone who sat in the same classroom two years ago far more than they trust a recruiter.

Low-cost digital presence

You do not need a careers page that rivals a large tech company. You need a page that answers what students actually ask: what the work is, who they will report to, what the training looks like, and what people who joined as freshers are doing now. Short, honest write-ups from your first batch of campus hires will do more than any polished production.

Step 4: Design the selection process

Selection is where fairness and speed meet. A placement drive compresses what would normally take weeks into a day or two, so the design has to be tight.

The typical funnel

A placement drive for an SMB usually looks like this:

1. Pre-placement talk. Fifteen to thirty minutes on the company, the role, the compensation, and the growth path. Take questions.
2. Screening test. Aptitude, skill, or both. Filters the pool to a manageable number.
3. Skill round. Coding test, case study, writing task, or role-play depending on the role.
4. Structured interview. Usually one or two rounds.
5. Final decision and offer communication. Ideally within a day or two; placement cells prefer same-day results where possible.

Aptitude and skill tests

Aptitude tests are useful as a coarse filter when you have hundreds of applicants, but they are a poor predictor of job performance on their own. Use them to shrink the pool, not to rank finalists.

Skill tests are more valuable. For technical roles, a short coding exercise that resembles real work beats trick puzzles. For business roles, a written case, a mock email to a customer, or a short data interpretation task tells you far more than a general aptitude score.

Whatever you use, make sure it is:

• Relevant to the role scorecard from Step 1.
• Timed reasonably, so that it tests competence rather than speed under stress.
• Scored consistently, ideally with an answer key or rubric prepared in advance.
• Free of questions that require knowledge of your specific tools or domain, which you agreed were trainable.

Group discussions vs structured interviews

Group discussions are a campus tradition. They are also one of the most bias-prone selection tools in common use. They reward the loudest voice, penalise candidates who are thoughtful but reserved, and tell you almost nothing about how someone works when the job is not a debate.

If you must use a group activity, make it a collaborative task with a shared outcome, where the evaluation focuses on listening, building on others' ideas, and contribution quality rather than airtime.

Structured interviews are better in almost every case. "Structured" means every candidate is asked the same core questions, interviewers know in advance what a strong and weak answer looks like, and each answer is scored independently before the panel discusses.

A structured fresher interview for most roles can be built around four question types:

• Walk me through a project. Tests depth of ownership. Push on the details: what did you personally do, what broke, what would you do differently.
• Solve this small problem aloud. Tests reasoning and communication under mild pressure.
• Tell me about a time you received difficult feedback. Tests coachability, which is the single most important trait in a fresher.
• What do you want to learn in your first year? Tests motivation and whether their expectations match the role.

Sample interview scorecard

Interviewers score each dimension on a one-to-five scale with anchored definitions, before any discussion. Here is a sample for the Associate Software Engineer role from Step 1.

Two rules that make this work:

• Score before you discuss. Panel discussions drift towards whoever speaks first. Independent scores protect against that.
• Evidence, not impressions. Every score should have a note about what the candidate actually said or did. "Seemed sharp" is not evidence. "Identified the off-by-one error before running the code" is.

Avoiding bias in fresher selection

Freshers have thin resumes, which makes it tempting to lean on proxies: college name, marks, English fluency, or how confident they seemed. All of these correlate with background more than with ability.

Some safeguards:

• Do not use academic percentage cut-offs beyond the minimum the placement cell requires. Marks reflect many things, not just competence.
• Evaluate spoken communication for clarity, not accent or vocabulary. A candidate who explains a solution simply in plain words is communicating well.
• Mix interview panels. Two interviewers with different backgrounds catch each other's blind spots.
• Train interviewers, even briefly. A thirty-minute session on the scorecard and common biases before the drive is enough to change behaviour.
• Track shortlist and selection rates by college, stream, and gender, and look at them after the season. If something looks skewed, ask why.

Using an ATS during the drive

Placement drives generate a lot of paper: resumes, test scores, interview scorecards, decisions. Managing this in spreadsheets works for one college. By the third college in a week, it falls apart.

An applicant tracking system lets you create a requisition per role, upload candidates in bulk from the placement cell's list, attach test scores, record scorecards from each interviewer, and move candidates through stages. The payoff comes later: when you need to know your offer-to-join ratio by college, or which interviewer's scores predicted 90-day performance, the data is already there.

CozyHR's ATS is built with this kind of batch hiring in mind, so drives do not become a spreadsheet-reconciliation exercise afterwards.

Step 5: Offers for freshers

The offer stage is where campus hiring diverges most sharply from lateral hiring. You are making a commitment to someone who may not join for many months, and who has never held a job. Every detail matters more than it would with an experienced hire.

Pre-placement offers

A pre-placement offer (PPO) is a full-time offer extended to an intern or a competition winner before or outside the regular placement drive. For SMBs, PPOs are the most valuable offer type available because:

• You have seen the person work over weeks, not minutes.
• The candidate knows your company and has already decided they like it enough to consider staying.
• Many colleges allow students with a PPO to opt out of or restrict further placement participation, which reduces competing offers.

Set a clear PPO policy before internships begin: what the evaluation criteria are, when the decision is communicated, and what the offer will contain. Interns should know from the first week that a PPO is possible and what it depends on.

Offer letters for freshers

A fresher offer letter should be clearer and more complete than a lateral one, because the recipient has no frame of reference. At minimum it should state:

• Role title, department, and reporting manager.
• Location and work arrangement.
• Compensation, broken out by component, with a plain-language summary of what monthly take-home will roughly look like.
• Joining date, or the expected joining window and how the final date will be communicated.
• Probation period and what confirmation depends on.
• Any conditions: degree completion, minimum marks if applicable, background verification, document submission.
• Acceptance deadline and how to accept.
• A named contact for questions.

Have the letter reviewed by someone with legal or compliance expertise. Fresher offers sometimes contain conditions that are unclear or difficult to enforce, and it is better to know that before a dispute.

CTC structure for entry-level roles

Freshers and their families read offer letters closely and often do not understand cost-to-company arithmetic. A CTC figure that includes employer contributions, variable pay, and one-time benefits can look much larger than the monthly take-home, and that gap causes resentment on the first payday.

Some practical guidance:

• Stipend vs salary. If a candidate joins before graduation as an intern or trainee, they may be on a stipend rather than a salary. Be explicit about which applies, for how long, and when the transition to full salary happens.
• Keep the fixed component dominant. Freshers cannot influence company performance much. A large variable component feels like a bait-and-switch.
• Show the monthly number. Include a simple illustration of the approximate monthly credit after statutory deductions, with a note that actual figures depend on tax declarations and applicable rules.
• Probation. State the duration and what a successful confirmation looks like. Tie it to the 90-day plan from Step 7 so the expectation is concrete.
• Training bonds. Some companies ask freshers to sign a bond committing to a minimum tenure or to repay training costs if they leave early. These are contentious, they affect employer brand on campus, and their enforceability depends on how they are drafted and on the facts of each case. If you are considering one, get proper legal advice first and think hard about whether a good onboarding experience would retain people more effectively than a bond.

Managing offer-to-join ratio and renege risk

The offer-to-join ratio is the share of accepted offers that actually turn into joiners. For campus hiring it is often the most painful number an SMB tracks, because the gap between offer and joining can stretch across months and a candidate's circumstances change.

Common reasons freshers renege:

• A competing offer with a bigger brand or higher pay arrives later in the season.
• Family pressure to take a job in a particular city or a "safer" employer.
• Higher studies admission comes through.
• Silence from the employer during the gap, leading the candidate to assume the offer is not serious.
• Degree completion issues.

You cannot control the first three. You can control the last two, and you can reduce the impact of the first three by making the candidate feel genuinely connected to the company.

Practical measures:

1. Over-offer deliberately, within limits. Based on your past joining ratio (or a conservative assumption in year one), extend more offers than your headcount. Be careful: over-offering too aggressively and then withdrawing offers is far worse than a few no-shows.
2. Get acceptances in writing, fast. A short acceptance window with a clear process signals seriousness.
3. Make the gap short where you can. If a candidate can join as a trainee or intern before graduation without violating college rules, offer that option.
4. Run a keep-warm plan. This is the single biggest lever, and it deserves its own step.

The keep-warm plan between offer and joining

A keep-warm plan is a scheduled set of touchpoints between offer acceptance and joining. It does not need to be elaborate. It needs to be consistent.

The goals are simple: the candidate should never go more than a few weeks without hearing from you, should have a named human they can message, and should arrive on day one already knowing some faces, some context, and what the first week will look like.

The next section lays out a month-by-month version.

Step 6: Pre-joining engagement plan

Below is a sample timeline for a candidate who accepts an offer roughly six months before joining. Compress or stretch it to match your actual gap. The important part is that every month has an owner and an action.

A few notes on execution:

• Use one channel and keep it alive. A pre-joiner community that goes silent for weeks is worse than no community at all.
• Have a human respond. Automated emails are fine for logistics, but questions about the role, the city, or the team should get a personal reply from someone on the team.
• Watch for silence. A candidate who stops responding in month three or four is signalling something. Reach out directly and ask.
• Track it. Log every touchpoint against the candidate record in your ATS or HRMS. When a candidate does renege, you will want to know whether the plan was followed.

Step 7: Fresher onboarding and training

The offer-to-join ratio gets attention because it is visible. Early attrition gets less attention because it happens quietly, one resignation at a time, six to nine months in. It is usually a symptom of onboarding that stopped at the laptop handover.

The 90-day structured learning path

A fresher's first 90 days should be a designed programme, not a series of improvised assignments. Break it into three phases.

Days 1 to 30: Foundations.

• Company, product, customers, and how the team fits into the whole.
• Tools, access, and workflows.
• Foundational skills specific to the role, delivered through a mix of short sessions and hands-on practice.
• First small, low-risk deliverable by the end of the month, reviewed by the mentor.

Days 31 to 60: Guided contribution.

• Real work, scoped to be achievable with support.
• Pairing with a senior on at least one meaningful piece of work.
• Weekly review of what was learned and what was hard.
• Exposure to at least one customer interaction, incident, or cross-team meeting so the work has context.

Days 61 to 90: Independent contribution with a safety net.

• Ownership of a small, well-defined piece of work end to end.
• Reduced check-in frequency, but a clear escalation path.
• A formal review at day 90 against the scorecard from Step 1, feeding into the probation confirmation decision.

Write the plan down, share it with the fresher on day one, and update it as your training programme improves. A fresher who can see the whole path is far less anxious than one who is waiting to be told what comes next.

The buddy system

A buddy is not a manager and not a mentor. A buddy is a peer, ideally someone who joined as a fresher one or two years earlier, whose job is to answer the questions a new joiner is embarrassed to ask anyone else.

Where is lunch, how do I book leave, is it okay to message the CTO directly, what does this acronym mean. These questions seem trivial, but the accumulated friction of not knowing is a major reason freshers feel like outsiders for months.

Set clear expectations for buddies: a short daily check-in in week one, a couple of times a week for the first month, and availability thereafter. Recognise buddies for the effort. It is real work.

Foundational learning: "paying dues" done right

There is an old idea that freshers should "pay their dues" by doing grunt work for a year before they are trusted with anything interesting. There is a useful version of this idea and a harmful one.

The harmful version uses freshers as cheap labour for tasks nobody else wants, with no learning attached. It produces bored, disengaged people who leave the moment a better offer comes.

The useful version recognises that foundational work is where deep understanding comes from. Fixing bugs teaches the codebase faster than building features. Handling support tickets teaches the customer faster than reading a persona document. Reconciling accounts teaches the business faster than a strategy session.

The difference is intent and framing. If the foundational work is chosen because it teaches something, is explained as such, is time-boxed, and is paired with feedback, it is training. If it is assigned because someone has to do it, it is exploitation. Freshers can tell the difference.

Early feedback loops

Freshers need more feedback, more often, than experienced hires. They do not yet have an internal sense of what good looks like in your context, so they cannot self-correct.

Some feedback practices that work well:

• Weekly one-on-ones in the first 90 days, even if short. Ask what was confusing, what they enjoyed, and what they would change.
• Feedback on every deliverable, in writing where possible, so it can be revisited.
• Two-way feedback. Ask freshers what is not working in the training programme. They are your best source of information about its gaps.
• A 30-day and 60-day pulse, a few questions in a form or in your HRMS, to spot early disengagement before it turns into a resignation.

If your HRMS supports onboarding checklists, task assignments, and check-in reminders, use it. Tracking that the day-30 one-on-one actually happened is more useful than it sounds.

Step 8: Metrics that tell you whether campus hiring is working

Campus hiring should be evaluated on a small number of metrics, tracked per cycle and per college, so that next year's decisions are based on evidence rather than memory.

Core metrics

Tracking in ATS and HRMS

The reason to run campus hiring through an ATS rather than spreadsheets is that these metrics require data from multiple stages to be linked to the same person. You need to know that the candidate who scored a four on coachability in the interview is the one who was confirmed at day 90 and is still employed at month twelve.

A practical setup:

• Tag every candidate with the college, stream, drive date, and source (drive, internship, hackathon, referral).
• Record test scores and interview scorecards against the candidate record.
• Record offer date, acceptance date, and joining date so the gaps are computed automatically.
• When the candidate joins, ensure the ATS record flows into the HRMS employee record rather than being re-keyed.
• Log onboarding milestones, probation outcome, and exit date (if any) in the HRMS.

Once this is in place, a season-end review becomes a report rather than an archaeology project. You can see which colleges produced joiners who stayed, which interview dimensions predicted performance, and which touchpoints in the keep-warm plan were skipped for the candidates who reneged.

CozyHR connects the ATS and onboarding modules so this flow happens without re-entry, which is the difference between metrics you look at once a year and metrics you actually use.

Compliance touchpoints for fresher hiring

Fresher hiring involves a handful of compliance steps that are easy to miss because the candidates have never been through them before and do not know what to ask. This section is general guidance. Rules change, thresholds vary, and your obligations depend on your company's registration, size, and location, so verify each item with a qualified professional.

Documentation

Collect and verify the standard set before or at joining:

• Identity and address proof.
• Educational certificates, including the final degree or provisional certificate once available. Many freshers join before the final certificate is issued, so define an acceptable interim document and a deadline for the final one.
• Bank account details for salary credit.
• Any declarations your payroll process requires.
• Signed offer acceptance and appointment letter.

Give freshers a clear checklist well before the joining date. Most delays come from candidates not knowing what to bring, not from unwillingness.

PF and ESI enrolment

Provident fund and employee state insurance enrolment are usually the first statutory interactions a fresher has with the formal economy. Whether these apply depends on your establishment's coverage and the employee's wage levels, and the specifics should be confirmed with your payroll or compliance advisor.

Practically:

• Explain to freshers what the deductions are and why they appear on the payslip. A fresher who sees an unexpected deduction on the first payday and has no explanation assumes something is wrong.
• Complete enrolment promptly after joining, and make sure the fresher knows how to access their account details.
• If your HRMS handles payroll, ensure the statutory settings are configured before the batch joins, not after the first payroll run.

Apprenticeship schemes as an option

Government-supported apprenticeship frameworks exist in India and can be a structured route for bringing in early-career talent, sometimes with financial support for the employer. The eligibility criteria, obligations, stipend norms, and the nature of the relationship differ from regular employment.

For some SMBs, especially in manufacturing, services, and technical trades, this route is worth exploring. For others, the administrative requirements may outweigh the benefit. Investigate the current rules and consult an advisor before deciding, and be transparent with candidates about the nature of the engagement.

Probation and confirmation

Have a written probation policy that states the duration, the evaluation criteria, how extension or non-confirmation is communicated, and what notice terms apply during probation. Freshers should see this in the offer letter and again during onboarding.

Interns and stipends

If you bring in interns, document the arrangement, the stipend, the duration, and the nature of work. The treatment of interns for statutory purposes can differ from regular employees and depends on the structure of the engagement. Get advice rather than assuming.

Common mistakes in campus hiring

Most campus hiring failures at smaller companies trace back to one of these.

1. Hiring freshers without a mentor available. The role scorecard says "under guidance." If no guide exists, the fresher flounders and leaves.
2. Treating the drive as the whole process. The drive is a day. The programme is a year. Companies that invest in the drive and neglect the rest lose the investment.
3. Chasing tier-1 campuses for prestige. Late slots, competing offers, and renege rates make this expensive for SMBs. Build depth at colleges where you can win.
4. Over-relying on group discussions and aptitude scores. Both are convenient and both are weak predictors. Structured interviews with scorecards take more preparation and are worth it.
5. Silence between offer and joining. The single most fixable cause of a poor offer-to-join ratio.
6. CTC surprises on the first payday. Explain the structure and the take-home before the offer is accepted.
7. Withdrawing offers. This damages your reputation at the campus for years. Hire conservatively.
8. "Shadowing" as an onboarding plan. Shadowing without structure is watching someone else work. Design the 90 days.
9. Using freshers as cheap labour. They notice, they talk to their batchmates, and your next drive suffers.
10. Not tracking outcomes. Without retention and productivity data by college and by interview dimension, every cycle starts from scratch.
11. Ignoring non-engineering streams. Roles in sales, support, finance, content, and operations do not need a BTech, and the competition for candidates in other streams is lighter.
12. Skipping legal review of bonds and conditions. What seems like a reasonable clause may be unenforceable or reputationally costly.

Campus hiring checklist

Use this as a working checklist for each cycle.

Planning

• Fresher headcount derived from workforce plan, with a named mentor per fresher
• Role scorecard written for every fresher role
• Compensation band and CTC structure approved, with take-home illustration
• Campus hiring calendar built backwards from target joining month
• Budget approved: travel, tests, prizes, tools, team time

College selection and outreach

• Target list of colleges across tiers and streams matched to roles
• Placement cell contact established and calendar obtained for each college
• One internal owner assigned per college relationship
• Employer branding activities scheduled: lectures, hackathons, internships

Selection

• Screening test finalised, relevant to role, with scoring key
• Skill round designed and piloted internally
• Structured interview questions and scorecard prepared
• Interviewers briefed on scorecard and bias safeguards
• ATS requisition created; bulk candidate import tested
• Decision turnaround committed to placement cell

Offers

• Offer letter template reviewed by legal or compliance
• PPO policy defined and communicated to interns
• Acceptance window and process defined
• Over-offer buffer decided based on expected joining ratio
• Keep-warm plan drafted with owners and dates

Pre-joining

• Welcome kit and pre-joiner channel ready
• Buddies assigned and briefed
• Optional pre-learning path prepared and clearly labelled as optional
• Documentation checklist and timeline sent to candidates
• Mid-gap check-in calls scheduled

Onboarding

• 90-day learning path documented per role
• Day-one schedule and workspace prepared
• Weekly one-on-ones scheduled for the first 90 days
• 30-day and 60-day pulse checks set up
• Probation review at day 90 scheduled against the scorecard

Compliance

• Document collection and verification process defined
• PF, ESI, and payroll settings configured in HRMS before joining
• Probation policy documented and included in offer
• Bonds, conditions, and apprenticeship options reviewed with an advisor

Measurement

• Metrics defined: cost per hire, acceptance, joining ratio, time-to-productivity, 6- and 12-month retention
• ATS to HRMS data flow verified
• Season-end review scheduled with hiring managers and placement cell feedback

FAQ

How many colleges should a small company visit in its first campus hiring season?

Fewer than you think. Two to four colleges, chosen carefully, is enough for a first cycle. The goal in year one is to learn what works: which tests predict performance, which colleges produce joiners who stay, and where your process breaks. Depth at a few campuses builds relationships and data; breadth across many campuses dilutes both. Expand in year two based on what the metrics tell you.

Is a pre-placement offer better than hiring through a placement drive?

For most SMBs, yes. A pre-placement offer follows an internship or a competition where you have observed the candidate working over time, which is far more reliable than a single interview. The candidate has also seen your company from the inside, which lowers renege risk. The trade-off is lead time: an internship pipeline takes a year or more to produce full-time hires, so most companies run both routes in parallel.

What is a reasonable offer-to-join ratio for campus hiring?

It varies by college tier, industry, and how long the gap is between offer and joining, so there is no single benchmark worth quoting. What matters is tracking your own ratio per college and per cycle, and watching it improve as your keep-warm plan matures. If your ratio is poor and you are not running a structured pre-joining engagement plan, start there before changing anything else.

Should freshers be asked to sign a training bond?

This is a judgement call with legal and reputational dimensions. Bonds are common in some sectors and resented in others. Their enforceability depends on how they are drafted and on the specific facts. Before introducing one, get legal advice, and weigh whether the same retention outcome could be achieved through good onboarding, clear growth paths, and fair pay. A strong first-year experience usually retains people better than a contract clause, and it does not cost you goodwill on campus.

How do we compete with big brands on compensation?

Usually you cannot match them on headline CTC, and you should not try. What SMBs can offer that large firms often cannot is scope, visibility, and speed of growth. A fresher at a small company may ship real features, talk to real customers, and take ownership of something meaningful within months. Make that concrete in your pre-placement talk, back it with stories from your existing early-career hires, and be honest about the pay. Candidates who value growth over brand will self-select, and those are the ones you want.

What should a fresher's first week look like?

Structured, welcoming, and light on paperwork. Documents should be collected before joining wherever possible. The first week should cover company context, team introductions, tool setup, and the first small task, with the buddy checking in daily. The fresher should leave the first week knowing what the next 90 days look like, who to ask for help, and what success means for the role. If day one is spent filling forms and waiting for laptop access, you have already lost momentum.

Do we need an ATS for campus hiring, or will spreadsheets do?

Spreadsheets work for a single drive at a single college. Beyond that, they break down: multiple interviewers, multiple colleges, test scores, scorecards, offers, and pre-joining touchpoints become impossible to reconcile. An ATS keeps every candidate's record in one place and, if it connects to your HRMS, lets you follow that record through onboarding and retention. That end-to-end view is what makes campus hiring improvable rather than repeatable.

How early should planning start for a placement season?

Well over half a year before the target joining month, and closer to a full year if you want an internship pipeline feeding pre-placement offers. Count backwards from joining: the offer-to-join gap, the selection window, the college outreach period, and your internal preparation. Placement calendars vary by institution, so get the actual dates from each placement cell and build your plan around them.

Conclusion

Campus hiring is not a brand contest. It is a process contest, and process is something a small company can do better than a large one, because a small company can care about every candidate individually.

The playbook is straightforward: know what you are hiring for, choose campuses where you can win, show up before you need to, select fairly with scorecards, make clear offers, stay in touch through the gap, onboard with a designed 90-day path, and measure what happened so next year is better.

None of it requires a large budget. All of it requires that someone owns it end to end and that the data does not get lost between the drive and day one.

If you want that end-to-end view without stitching together spreadsheets, CozyHR's ATS and onboarding modules are built for exactly this: bulk candidate intake for placement drives, structured scorecards, offer tracking, pre-joining engagement, and a seamless flow into onboarding checklists and payroll once the fresher walks in. Try it on your next campus cycle and see how much of this playbook runs itself.