Two senior engineers at a robot integrator receive similar letters in one month. One resigns. The other stays. Asked later, the stayer gives three reasons. He had just been made custodian of the firm's gripper and motion code, so his routines ran inside every cell shipped. He got first crack at a newly signed robot make. And when a customer's plant head swore at him over a missed cycle time, his manager drove down overnight and took over the argument.
Money was close across all three options and did not decide it. In integrators, panel shops and machine builders, staying is mostly about the work itself, the rungs above and how the firm treats people out on the road.
Levers that differ seat by seat
- Robot programmers: first crack at an unfamiliar robot make and a seat on the offline simulation licence. A cell they can demonstrate on the company's exhibition stand helps too.
- SCADA and telemetry engineers: a named backup on every utility so leave is genuinely leave, rest after midnight alarm call-outs, and the next historian migration as a stretch project.
- Vision application engineers: a small lab bench stocked with lenses, ring lights and backlights for experiments, plus written retuning scope so free callbacks do not swallow every week.
- Panel wiremen: a graded route from wiring to testing, credit for panels that pass without snags, and good crimpers, strippers and bench lighting of their own.
- Fitters at machine builders: recognition when a one-off machine clears its trial, and a visible path toward trial or commissioning engineer.
- Calibration and test technicians at sensor makers: rotation between benches to rest the eyes, and praise for clean records rather than only for throughput. Bench clearances help too, like those in the sensor makers' competency notes.
- Field service engineers: a fair call-out roster, remote diagnosis tools that save pointless journeys, and someone senior who backs their judgement on chargeable visits.
Levers that cut across every seat
Some things matter almost everywhere in this hub. A voice before sales commits a scope and date. Postings rotated, with rest after long stays and an occasional job near home. A manager who confronts an abusive customer rather than apologising for the engineer. And credit at go-live: the engineer named in the closing mail to the customer, and thanked inside the firm when the acceptance certificate lands. These cost little, which is why their absence feels like a statement.
A specialist ladder beside the management one
Many firms only promote upward into managing people. Strong programmers then face a choice between stagnating and supervising, and some leave instead. A parallel rung, such as principal engineer, rewards depth: owning the standard code base, reviewing others' logic, leading the hardest commissioning, advising on quotations. Pay steps and titles on that rung should be as real as on the management side.
Where pay fits
Pay still counts. An engineer far below the market will go however absorbing the work. The aim is to hold pay inside a fair range, checked yearly against real evidence, so that money stops being the tiebreaker. Our method for pricing automation skills from your own hiring records explains the check. Past that point, extra rupees buy less loyalty than the levers above.
A retention plan built around project milestones
- 1
List the few you cannot lose
From the skill grid: anyone who alone holds a platform, a utility customer or a machine design the firm sells repeatedly. Keep the list short and private.
- 2
Talk at natural milestones
After go-live on a hard job, after a long posting, after increment letters. Ask what energised them, what drained them, and which kit or customer they want next. The stay interview prompts can be adapted.
- 3
Agree a dated growth item each
An unfamiliar platform, custody of a library, a customer training role, or a junior to bring up. Put a month on it.
- 4
Rebalance road time
Scan the travel register for the listed names. Anyone carrying far more postings than peers gets relief before the next big job.
- 5
Make credit visible
Name the engineer in the handover mail, mention them when the owner reviews the month, and pass on the customer's thanks.
- 6
Check pay once a year
Against evidence, never against panic. Fix real gaps in the increment round rather than after a rival letter appears.
- 7
Revisit the list quarterly
Check each name, each promise and each outcome. Broken promises do more damage than none.
Habits that quietly undo retention
- Leaning on lump-sum retention bonuses, which postpone exits rather than prevent them.
- Promising every senior a manager's chair the organisation chart does not contain.
- Overlooking the engineers just under the top tier, who become the next targets.
- Matching rival letters without looking at peers, which seeds resentment across the bay.
- Holding milestone talks and then changing nothing anyone can see.
Who owns it
The owner holds the short list. Technical heads own growth items and road fairness. HR runs the milestone talks, tracks promises and feeds exit evidence back. Mixed design, build and service firms can see how the pieces fit on our attrition notes for controls integrators. Exit evidence is gathered as described in why people quit controls and robotics firms. GullyHR's retention service builds the plan with you, while the automation and robotics sector hub maps the trade's other patterns.
