A senior controls engineer at a special-purpose machine builder walks into the owner's cabin holding a rival's offer letter. The owner matches it that evening. Within a fortnight the story has done the rounds of the assembly bay. Two engineers at the same grade ask for the same, and a third, who taught the senior servo tuning years ago, discovers he now earns less than his former pupil. By the next increment letters, pay talk in the firm happens only through outside offers.
Automation skills are in demand, and one competing letter can crack a team's sense of fairness. Matching faster does not fix that. A pay structure with clear grades, tested against the market, gives a manager something to explain without opening the owner's chequebook.
Signs your bands have slipped
- Experienced robot programmers turn down your offers on money, not on travel or city.
- A wireman hired last spring takes home more than the panel tester who checks his work.
- Most raises arrive as matches to rival letters rather than through increment letters.
- Nobody can say what separates an engineer from a senior, so every raise is argued afresh.
- Site allowances have quietly swollen to plug a gap in fixed pay.
- Leavers mention pay alongside the phrase 'they value weld programming there'.
Where the market splits hardest
Skills where the market tends to split most sharply include the following. Pay for these moves faster than for general controls work.
- Teaching weld seams and setting seam tracking on body-shop robot lines.
- Palletiser pattern programming and conveyor tracking for end-of-line cells.
- Safety relay and safety PLC logic for guarded cells and light curtains.
- Multi-axis servo gantries, electronic cams and flying shears.
- Lens, lighting and threshold choices for shiny or transparent parts on vision stations.
- Historian, alarm rationalisation and redundant servers for water and power SCADA.
What trailing bands cost
The obvious cost is lost people and slower hiring. Every declined offer for a palletising or welding cell programmer pushes back a kickoff. The quieter cost is the matching habit. Matches are made in a hurry, with no reference to peers, so each one seeds the next request. Inversion sours the engineers who stayed and trained others. And allowances stretched to cover fixed pay become impossible to trim when site patterns change.
Why bands fall behind in this trade
Many integrators set their ranges once, when the firm had a dozen people, and have moved them only by yearly percentages since. The market for certain skills moves in jumps instead. When a rival lands a large body-shop welding order, it may need three robot programmers within a month and pay whatever closes the gap. A multinational's service arm opening a regional office does the same to SCADA engineers. New joiners then enter at that rate while the old guard stays on yesterday's track. With no written grades there is no fixed reference, so each manager fights for their own people and the structure drifts further.
Start with one sorted sheet
List every engineer and technician with role, grade if any, years served and fixed monthly pay. Sort within each role by pay. Highlight anyone who joined in the past eighteen months. Look for two warning signs. First, recent joiners sitting above long-servers doing the same work. Second, people whose pay sits far from grade-mates for no reason anyone can name. Then add the offers you lost on money over the same stretch. That sheet usually shows where to begin.
Building a tested pay structure
- 1
Define grades by what people deliver unaided
Trainee. Engineer who programs and tests to someone else's functional description. Senior who runs a FAT and a site alone. Lead who architects the control system and checks others' logic. Add two or three observable markers to each.
- 2
Gather market evidence
Use letters your candidates hold, offers you lost, leavers' accounts and recruiter feedback. Our guide to benchmarking automation pay without a survey explains the method.
- 3
Set a range for every grade
A floor, a midpoint and a ceiling for fixed pay, with neighbouring grades overlapping slightly, letting a strong engineer grow without a title change.
- 4
Add premiums only where the market clearly splits
Offline robot programming, safety PLC design or vision application work may justify a named premium. Record the test that proves the skill and the date the premium lapses unless renewed.
- 5
Slot everyone in and list the gaps
Each person goes into a grade. Anyone under the floor, every inversion and anyone far over the ceiling goes on a list, each with a cause and a planned fix.
- 6
Correct in stages
Fix inversions and scarce-skill gaps first, inside the increment round where possible, and the remainder over one or two rounds.
- 7
Write a counter-offer rule
A match is considered only when the person's range trails the market, and any correction extends to grade-mates too.
Grade name, plus the two or three things someone at this grade delivers unaided.
Fixed pay range: floor, midpoint, ceiling (monthly).
Site allowance rule: kept on a separate sheet, outside this range.
Skill premium: which skill, how it is verified, amount, review date.
Evidence used: letters held, offers lost, recruiter notes, date gathered.
Headcount in this grade: below midpoint, near midpoint, above midpoint.
Next review date and who owns it.Talking about pay with the team
Publish the grades and their markers so engineers know what moves them up. Publishing ranges is a separate decision; many firms show a person their own range and the next one. Individual pay stays private. Explain the counter-offer rule openly, so nobody believes a rival letter is the quickest road to a raise.
GullyHR's pay and rewards design service builds structures like this one, and our downloadable band worksheet is a format you can fill in today. Machine builders can compare with the benchmarking notes for automation equipment makers. Recurring people patterns across the trade are listed on our controls and robotics hub.
