A machine vision company takes on two freshers in July. In week three one is sent to a customer's bottling hall to 'help' a senior with a label inspection station. While the senior is in the control room, the newcomer raises the camera gain and widens the region of interest to stop false rejects. Good bottles stop being kicked off. So do bottles with torn labels. The shift supervisor spots them at the palletiser, the camera gets bypassed, and the customer's quality head rings the owner. By September the fresher has joined an IT services firm.
Nobody planned that outcome, which is exactly the trouble. Most automation firms hire freshers and teach them on whatever job is live. Those that build a defined ramp, with named tools, supervised exercises and review dates, reach useful output sooner and lose fewer newcomers in year one.
Signs that freshers are learning by accident
- Nobody can say what a newcomer may do unsupervised, or who decided it.
- Early weeks go on redrawing title blocks or sitting beside a senior's monitor.
- The first real task is on a customer job because no practice work exists.
- Each senior teaches a different habit for tag names, rung comments or ferrule numbering.
- Newcomers travel to site before doing a single I/O check on your own bench.
- Reviews happen only when probation ends, too late to change course.
What learning on live jobs costs
A slip inside a customer's plant costs more than the same slip in your bay, in rework and in goodwill. Seniors lose hours undoing errors a practice drill would have caught. Newcomers lose nerve, especially after a public mistake. And when someone does become capable without a plan, nobody can explain how, so the next intake cannot follow the same route.
Why firms skip the structure
Seniors always have a deadline, so teaching gets squeezed into whatever they are doing that day. Owners see a practice rack and bench hours as spend with no invoice behind them. Many seniors were thrown in at the deep end themselves and assume it works. And writing the exercise list feels like a big job. In practice the list for a first ramp fits on two sides of paper.
Three questions to ask your recent joiners
Ask each engineer who joined as a fresher over the past two years. What was the first task you did unsupervised? When was it? Who said you were ready? Vague answers, or a first solo task on a customer site, mean the ramp needs building. Then add the leaving dates of freshers who quit, and note which stage each had reached.
A ramp in five stages
- 1
Isolation drills and the shop
Electrical isolation, lock-out and tag-out, safe entry to a guarded cell, crimping tools and the firm's drawing conventions. No energised panel work until this is signed.
- 2
Exercises on a practice rack
Wire a star-delta starter from a schematic, ferrule it and megger the circuit. Program a conveyor with a photo-eye, timers and counters. Scale a pressure transmitter's analogue input. Build an HMI faceplate with alarm acknowledgement. Each exercise has a pass check.
- 3
Shadow a factory test
Sit through a FAT beside a senior, run a section of the test script under watch and log punch points. Add bounded jobs such as reconciling the I/O schedule with the wiring diagram.
- 4
Supervised site work
Join a posting with a named senior. Do loop checks and point-to-point checkout with the senior present. No online edits to running logic without the senior's approval.
- 5
Solo on low-risk tasks
The mentor clears named tasks for solo work, such as panel testing or edits on a non-critical HMI screen. The cleared list grows at each review.
Name, joining date, mentor, review dates.
Isolation and cell-entry drill: date cleared, cleared by.
Exercise 1, star-delta wiring and megger test: watched, assisted, solo (dates).
Exercise 2, conveyor logic with photo-eye, timers and counters: watched, assisted, solo.
Exercise 3, analogue scaling and alarm faceplate: watched, assisted, solo.
FAT shadowing: job number, sections run, punch points logged.
Site posting: job number, senior present, checks done under supervision.
Tasks cleared for solo work: each with date and mentor initials.
Focus for next review: two or three items, no more.Choosing and preparing mentors
A good mentor is patient, explains why as well as how, and can watch a newcomer wrestle with a fault for ten minutes before stepping in. Your sharpest programmer may not be that person. Give mentors hours on the loading plan, two newcomers at most, and a short briefing on running a review. Count mentoring in their own appraisal, or it will be dropped the moment a deadline bites.
Holding on to freshers once they are useful
The riskiest moment comes just after a newcomer turns capable, because rival firms can now see the value. Tie the move from trainee to engineer to the final sign-off, with the pay change agreed at joining. Give the newly cleared engineer a first job with a senior as backup, not alone.
GullyHR's learning and development process service designs ramps of this kind. The learning plan for panel builders and its SCADA counterpart show how the stages shift by business type. For fitting newcomers around deadlines, read running trainees alongside live projects. Other recurring pressures are mapped on our automation and robotics hub.
