Fresher hiring and a first-year training programme for a small IT services company

A founder of a forty-person IT services company signs up nine freshers from three colleges after a campus drive. In week one the laptops are late, the team lead is on a client call and nobody knows what the freshers should do. By month three two have left and four are idle on the bench. The founder blames the colleges.

The trouble was not the batch. It was the missing plan. This guide shows how a small firm can hire freshers and run a first-year programme with modest effort and no big learning budget.

A fresher costs senior time for the first six months. Be honest about whether you have that time. If your seniors are fully loaded on client work, hire fewer freshers or wait. A cohort of three with real mentoring beats a cohort of nine with none.

• A named mentor for each fresher, with time set aside weekly.
• A first project that is real but low risk, such as an internal tool or test automation.
• A training room, laptops and access ready before day one.
• A client who accepts that part of the work is done by a learner under review.

Campus drives, open walk-in days, college faculty referrals and your own employees' juniors all work. Pick one or two and do them well. Our software development industry page shows how firms of different kinds plan hiring across levels.

For screening, test how a person learns. A short written round with logic and basic programming, a small coding task in a language the candidate chooses, and a conversation about a college project is usually enough. Ask what went wrong in their project and what they did next. Candidates who have built something, even small, tend to answer well.

1. 1

   Weeks one to four: orientation and basics

   Company, tools, version control, coding standards, how a client project runs, and a short assessment at the end. Keep the days half teaching and half doing.

2. 2

   Months two to three: guided practice

   Small tasks on a live codebase with code reviews from the mentor. Each fresher writes a weekly note of what they learned and what blocked them.

3. 3

   Months four to six: shared delivery

   The fresher takes a defined part of a real project, with reviews and a demo to the team. A senior signs off on a checkpoint at the end of this stage.

4. 4

   Months seven to twelve: ownership

   Increasing independence, one cross-skill exposure such as testing or deployment, and a first formal review with the mentor, the delivery head and the HR contact.

A mentor is not just a name on a list. Set aside an hour a week for each fresher and tell the mentor's own manager that this time counts. Give the mentor a short guide: how to set tasks, how to give review comments, and what to do if the fresher is struggling. A mentor with four freshers is a trainer, not a mentor, so keep the ratio low.

Name, mentor and date.
Technical skills shown since last checkpoint, with an example.
Tasks finished on time and tasks that needed rework.
Communication with the team and with the client, if any.
Learning habit: asks questions, reads documentation, tries before asking.
Support needed from the mentor or the firm.
Decision: continue as planned, add support or adjust the plan.
Signatures of the mentor and the reviewer.

Many small firms ask freshers to sign a service agreement tied to training. Whether such terms are fair or enforceable depends on the facts and on your jurisdiction. Do not copy another firm's bond. The company's decision should rest on the real cost of training and on what you can defend.

Treat day one as part of the programme. Have laptops, email, repository access and a seat ready. Give each fresher a one-page plan for the first week with a morning session, a small task and a meeting with the mentor. Introduce them to the delivery head, the HR contact and one person from a different team.

Pair freshers on the first task. Two learners working together ask more questions and feel less alone. By the end of the first month, ask each of them to present what they built to the team in ten minutes. This builds confidence and shows you who needs more support.

Keep a short record of each fresher's progress from the start. A shared sheet with the checkpoint dates, the mentor's remarks and any extra support given is enough. When the first formal review arrives, you will have evidence in place of impressions, and the fresher will see that the programme is taken seriously.

• Putting every fresher on the bench until a project opens, which kills motivation.
• Training on a tool that the firm will not use in the next year.
• Giving no feedback for the first two months.
• Moving a fresher to a client project too early, then blaming them for the result.
• Skipping the checkpoint at the end of month six.

Freshers leave when they feel unseen, when the work is dull or when they hear of a better offer from a friend. A clear plan, regular feedback and a visible next step answer most of this. Plan the first appraisal with care. The appraisal cycle design post explains how to time the first review, and the post on attrition after appraisal season shows what to watch after it.

If you want help building the programme itself, our learning and development process work covers curriculum outlines, mentor guides and checkpoint forms.