New Zealand engineering and technical businesses compete for staff against Australia, against remote employers offshore, and against each other in a small market. Losing an experienced engineer costs the recruitment fee, months of reduced output, and frequently a client relationship — and the knowledge they took is rarely written down anywhere.
Why technical people actually leave
Exit interviews consistently identify the same drivers, and money is rarely first:
- No visible progression. Technical staff in small firms often see one path upward, occupied by the owner.
- Work that has stopped being interesting. Engineers who spend two years on repetitive variations of the same problem leave for something harder.
- Poor management, usually by someone promoted for technical ability with no preparation for the people part.
- Feeling unable to influence anything — high demands, low control, which is a recognised psychosocial hazard as well as a retention problem.
- Sustained overload, which is frequently celebrated rather than managed.
- Money, which matters, and which is usually the stated reason rather than the real one.
What retention actually requires
A technical progression path. Not everyone wants to manage, and forcing progression through management loses good engineers and creates poor managers. A senior technical track with genuine status, pay and autonomy retains people who would otherwise leave for it elsewhere.
Deliberate variety. Allocating work with development in mind rather than purely by who is fastest at it costs some short-term efficiency and retains people.
Support for chartered registration. CPEng and equivalent registrations matter to technical staff. Firms that fund the process, allocate time for it and provide mentoring signal investment, and the capability stays in the business.
Managers who are trained to manage. Most psychosocial harm and most avoidable turnover is mediated by a direct manager who was promoted for technical competence and given no preparation.
Real flexibility. Remote and hybrid options are now competitive necessities. A firm requiring full-time office presence is competing for a smaller pool against employers who do not.
Knowledge transfer: the harder problem
When an experienced engineer leaves, the drawings remain and the reasoning does not. Why a particular detail was chosen, what was tried and rejected, which client cares about what, where the buried problems are on a long-running project — none of that is in the file.
Approaches that work better than a handover document written in the last fortnight:
- Design decision records. A short note with each significant decision recording what was considered and why. Written contemporaneously it takes minutes; reconstructed later it is impossible.
- Paired working on complex problems. Two people on a hard problem is the most reliable knowledge transfer mechanism there is, and it looks inefficient on a timesheet.
- Structured mentoring with allocated time, not goodwill.
- Internal technical review that is genuinely a discussion rather than a signature. Review is where junior staff learn how senior staff think.
- Client relationship mapping, so no relationship is held by one person only.
- Standard details and internal guidance that capture how your firm does things, maintained rather than written once.
The single point of failure test
Ask, for each significant project and client: if this person left tomorrow, what would we lose and how long would recovery take?
Most firms find several answers uncomfortable. That is the list to work on, and it is a business continuity issue as much as a people one.
Exit well
People leave. How they leave affects whether they come back, whether they refer others, and whether they say anything useful on the way out.
A structured handover with allocated time, a genuine exit conversation conducted by someone other than the person’s manager, and a professional farewell all cost little. Boomerang hires are common in a small market and returning staff arrive with additional experience.
The market context
Engineering New Zealand and the technology sector bodies publish workforce material, and Education Counts publishes tertiary and training pipeline data under an open licence — useful for understanding what is actually coming through rather than assuming.
The structural position is that New Zealand trains fewer engineers than it needs and competes internationally for the rest. That is not solvable by any single employer, which makes retention and knowledge capture the levers you actually control.
