Why software employees leave and how to understand why
Engineers and product staff leave for many reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead articleA 3D printing business mixes design, machine operation and hand finishing under tight job deadlines. Here is how to run the people side of that mix.

Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.
Share your requirementsA 3D printing company takes a customer's file or idea and turns it into a physical part, through design preparation, printing, cleaning, finishing and dispatch. Customers are product start-ups, engineering teams, architects, dental and medical suppliers, and hobbyists. Work arrives as jobs of very different size, so one week may be a single prototype and the next a batch run. A few people hold the knowledge that matters: how to prepare a file so it prints, how to tune a machine, and how to finish a part to the customer's expectation. Machines often run overnight, and the team is usually small, so the loss of one skilled operator is felt quickly. See also HR for IT and software.
Who does the work
Machine knowledge sits with one or two people
Settings, material handling and fault fixes live in the heads of the senior operators, and their absence stops the floor.
Workload swings with each job
A large batch or an urgent prototype lands on the same people, and overtime follows without a clear way to plan it.
Overnight runs need someone responsible
Machines print through the night, but nobody is clearly assigned to check them, so a failed build is found in the morning.
Finishing is slow hand work
Sanding, support removal and painting are repetitive, are hard to hire for, and decide whether the customer accepts the part.
Design and shop floor do not talk
Designers promise features the machines cannot print well, and operators learn about the problem after the build has started.
Skills are hard to find and easy to lose
Experienced additive manufacturing staff are few, and larger firms or a competitor can hire away someone you trained.
Powders, resins and fumes need care
Materials used in some processes call for handling discipline and protective equipment, and people often learn it by watching.
Write down machine and material know-how
Short job cards for each machine and material covering settings, common faults and fixes, so a second person can run it. The HR documentation process shows how to keep such records current.
Cross-train operators in pairs
Every machine has a named primary and a backup who has run it under supervision, with a simple skills matrix on the wall that shows who can do what.
Name an owner for each overnight run
A person who checks the job before leaving, is reachable if it fails and is covered by a rota and a fair allowance, using the attendance and shift process.
Make design review a joint step
A short check where an operator and a designer look at the file together before quoting, so printability is settled before the job starts.
Build a finishing career path
Grades and pay steps for post-processing technicians, linked to the quality they deliver, so the hand-work team sees a way forward. Role design helps define the levels.
Confirm with a qualified professional. What applies to you depends on your business, your state and your arrangements, and it changes. This page describes practice. It does not state a legal position.
Clear roles and grades for operators, designers and finishers, so each person knows what the job covers.
A skills matrix that shows who can run which machine, and where one departure would stop work.
A fair rota for overnight runs and urgent jobs, with records that feed payroll correctly.
A look at why skilled operators and designers leave, and what it would take to keep the ones who matter.
Every engagement starts by recording where you stand, and every later report compares against that. We do not promise outcomes. Start with a free conversation, or see the paid HR Diagnostic.
From the GullyHR blog: one on HR in information technology and software, and one on each of the topics this page points to.

Engineers and product staff leave for many reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead article
A calendar of courses, a budget spent by March and no record of what any of it changed. What a learning and development process contains when it starts from need rather than from the catalogue.
7 min readRead article
A flat structure works until the founder becomes the only route to a decision. How to tell when you have passed that point, and how to redesign without a reorganisation.
8 min readRead article
How to spot an unmanageable workload before it becomes an exit or an error, what to look at, how to talk about it and what to change, without guessing.
5 min readRead articleMore on the GullyHR blog.
Write the machine and material know-how down, then train a backup under supervision. A visible skills matrix shows where the gaps are and lets you plan cross-training instead of reacting to a resignation.
Name one person for each run, give them a checklist and a way to be reached, and rotate the duty fairly with an allowance. Leaving machines running with no owner is a risk to both the job and the equipment.
The work is repetitive and manual, yet it decides what the customer sees. Clear grades, a quality standard people can meet and a visible path upward help more than a one-off raise.
Track hours per job for a few months, then plan staffing around the pattern you see. Some firms keep a flexible pool of trained people for peaks, which suits better than constant overtime.
They need different role definitions and growth paths, but a shared review step before each job. Pay, appraisal and recognition should reflect both the design quality and the printed result.
We would look at which machines and materials only one person can run, who owns each overnight print, and how designers and operators meet over a live quotation. A sensible first piece of work is writing down machine and material know-how and pairing operators for cross-training. Scope is agreed in writing afterwards, and you decide whether to go ahead.
All 5 business types in information technology and software · Find another business type
See all HR topics for information technology and software, or another industry.
Identify payroll leaks, record gaps and hiring bottlenecks in a free first conversation, and leave knowing what to fix first.
Know what you need? Share your requirements in four short steps.
Want the full picture? See the paid HR Diagnostic.
Prefer a quick message? Chat on WhatsApp