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 data centre provider runs buildings that customers expect never to go down. Round-the-clock shifts, strict access rules and a small number of trained facility staff make people planning a matter of uptime.

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 data centre provider hosts customers' servers in a building with power, cooling, fire protection and tight access control. The people include electrical and mechanical technicians, network and server operations engineers, security staff, customer support and a small management layer. Shifts run day and night every day of the year, and the work alternates between long calm watches and urgent response. Mistakes in the hall can take down a customer. Staff must follow strict procedures for entry, change and handover, and the quality of each shift handover decides much of the uptime. The wider IT and software hub and the infrastructure and managed services hub cover what these firms share.
These are the places the people side of this kind of business tends to give way. The rest of this page works through them.
HR here has to work for each of these groups, not only the office. The set-up below is written with all of them in mind.
Hours of quiet monitoring, followed by a sudden alarm, test alertness and the shift pattern decides who is awake for it.
A verbal note at the gate loses the open fault, the half-done change and the customer who is nervous.
A power or cooling specialist is trained over years, and a vacancy leaves the night shift without a key skill.
A change request, a visitor entry or a test is rushed, and the near miss is not written down.
A technician is asked by a customer to do something outside the ticket, and the line between help and risk is unclear.
Few want permanent nights, and rosters fall back on the same volunteers.
Planned work is set at quiet hours, so the same people give up weekends and rest.
Start with the topics that matter most here: Health, Safety and Wellbeing; Employee Administration; HR Operations and Governance. Then work through the rest. Each topic is written for information technology and software, not in general.
Induction, records, incident reporting and follow-through.
Records, attendance, leave and the day-to-day HR that must simply work.
An HR function that runs the same way every month.
How many people, in which roles, by when — and what they will cost.
Structure, reporting lines and who is allowed to decide what.
Requisition to joining, the same way every time.
A first day that is the same for the fifth joiner as the first.
Salary structure, payroll inputs and a month that closes on time.
Goals, reviews and ratings that hold up in a conversation.
Training planned from need rather than from the calendar.
Named backups for the roles that cannot be vacant.
Communication, recognition and the conditions people actually work in.
Two routes — one for complaints, one for conduct — kept separate.
Policies a manager can apply, and obligations with owners and dates.
Who leaves, when, why — and which of them mattered.
Resignation to relieving letter, in a defined order.
Records that survive people, and approvals that do not queue.
A short monthly pack management actually reads.
The pieces a data centre providers business puts in place, in an order that makes each easier. Open any card for the detail.
Rotation, rest and break rules that protect alertness, with a fair spread of nights.
What this coversHideRotation, rest and break rules that protect alertness, with a fair spread of nights. See the attendance and shift process.
A short, fixed form for open faults, changes in progress, customer notes and next actions, signed by both shifts.
What this coversHideA short, fixed form for open faults, changes in progress, customer notes and next actions, signed by both shifts.
For every critical skill, train two people so a vacancy or leave does not leave a shift uncovered.
What this coversHideFor every critical skill, train two people so a vacancy or leave does not leave a shift uncovered.
Walk-throughs of entry, change and test steps, with a way to record near misses without blame.
What this coversHideWalk-throughs of entry, change and test steps, with a way to record near misses without blame. The health and safety work covers routines.
A written list of what technicians may do for a customer, who approves anything else and how it is recorded.
What this coversHideA written list of what technicians may do for a customer, who approves anything else and how it is recorded.
Plan the windows ahead and rotate who works them, with time off in return.
What this coversHidePlan the windows ahead and rotate who works them, with time off in return.
Before changing anything, find out what is true today. These checks take an afternoon and tell you which of the topics above to start with.
Share your requirementsConfirm 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.
The services below fit this kind of business best. Each starts by recording where you stand, and every later report compares against that. We do not promise outcomes.
Safety training, near-miss habits and shift wellbeing for people working around power and cooling.
Training records, authorisations and handover forms kept so each person's right to act is clear.
A hiring route for technicians and operations engineers who can work disciplined night shifts.
A fair way to handle procedure breaches and complaints in a setting where rules matter.
Start with a free conversation, or see the paid HR Diagnostic.
Understand the business, its workforce, current processes and HR challenges.
Find the missing, weak, inconsistent or person-dependent processes.
Create the structure, processes, policies, SOPs, dashboards and systems needed.
Help HR and department managers actually adopt the new system.
Digitise repetitive and approval-based workflows where it is worth doing.
Track hiring, attendance, employee cost, performance, training and attrition.
Strengthen the people-management system continuously, not once.
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 shift, weekly and monthly safety routine for rubber plants that names who checks platen guards, mill trip bars, autoclave doors, burst-test cages and slings, and who acts on near misses.
7 min readRead article
Payroll says one joining date, the personal file says another and the manager remembers a third. How to establish a single trustworthy employee record and keep it that way.
7 min readRead article
Every growing company reaches a point where the founder approving everything stops being speed and starts being the bottleneck. Twelve signs it has happened, and what to fix first.
9 min readRead articleMore on the GullyHR blog.
Use a short fixed form, a face-to-face overlap of fifteen minutes and a signature from both sides. Review a sample of handovers weekly. Reliable handover reduces repeat faults and improves customer trust.
Entry and change procedure, fire and safety drills, communication with customers and writing a clear incident note. Keep a record of who has been trained and authorised for what task.
Find out why first: pressure, unclear steps or habit. Coach and fix the process where it is weak, and use formal steps where the breach is serious or repeated. Treat the outcome consistently.
Yes, by a fair rotation, a known allowance and rest rules. Build a pool of people willing to work nights for a period. Rotate those who prefer days into nights now and then.
Explain politely that it needs a ticket and approval, offer to raise it at once and note the request. A written list of what is permitted helps technicians say no without argument.
We would read a week of handover notes, list skills held by one person and ask night staff about rest. A handover form with a cross-training plan is a natural first job, with scope written for your approval.
All 5 business types in IT infrastructure & managed services · Find another business type
See all HR topics for information technology and software, or another industry.
Tell us what is slowing your team down. We’ll help you find a practical way forward, starting with a conversation.