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 server management company runs and watches servers on behalf of clients. Here is how to manage monitoring engineers, system administrators and on-call staff who hold the keys to other people's systems.

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 server management company takes responsibility for clients' servers, whether in a data centre, in the cloud or in the client's own office. Work includes monitoring, patching, backup checks, security hardening, performance tuning and fixing faults. Staff include system administrators, monitoring engineers, cloud and Linux or Windows specialists, support agents and account managers. Since servers run all day, coverage is needed at night and on weekends. Patching and changes happen in agreed windows, often after hours. Engineers hold high-level access to clients' systems, so trust and records matter. Most work is quiet until something fails, and then it is urgent. See also HR for IT and software.
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.
GullyHR runs talent acquisition for permanent roles in server management companies. For each role we agree the job description with you, find and screen candidates against it, and support the offer through to joining. Tell us the role and the number of people, and we start there.
We recruit permanent employees. We do not supply contract or temporary staff.
Every business interviews, but few have a written process that works the same way for every role and every interviewer. GullyHR designs yours, from the role brief to the offer, trains your managers to run it, and can run it for you on the roles you hand us.
We agree what the role must deliver, the must-have and nice-to-have skills, and how each will be scored.
Screening call, assessment, interview rounds and decision points, sized to the role and the number of people you hire.
Structured questions for each role family and a rating guide, so two interviewers judge the same answer the same way.
A short briefing for your managers on what to ask, what to avoid and how to give a clear yes or no.
Who approves, how the offer is made, and how candidates are kept informed from first call to joining.
Night staff watch screens for long hours, with fatigue and little contact with the day team.
Changes happen at night or weekends, and the same engineers are asked again and again.
Too many alerts, many false, lead to important ones being ignored.
Engineers have admin rights on client systems, and access is not always removed when staff leave.
When all is well, nobody notices the engineers; when something fails, they are blamed.
Each client's server quirks are known by one engineer, so leave and exits cause risk.
At 3 a.m., the night engineer does not know whom to call, or whether they are allowed to make a big change.
Cloud, containers and new operating systems change what the team must know.
Start with the topics that matter most here: Health, Safety and Wellbeing; HR Operations and Governance; Exit and Alumni Management. Then work through the rest. Each topic is written for information technology and software, not in general.
Induction, records, incident reporting and follow-through.
An HR function that runs the same way every month.
Resignation to relieving letter, in a defined order.
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.
Records, attendance, leave and the day-to-day HR that must simply work.
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.
Records that survive people, and approvals that do not queue.
A short monthly pack management actually reads.
The pieces a server management companies business puts in place, in an order that makes each easier. Open any card for the detail.
Rotations, rest after nights, breaks and a link to the day team using the attendance and shift process.
Rotations, rest after nights, breaks and a link to the day team using the attendance and shift process.
A fair rota for change windows, with compensation and recovery time.
A fair rota for change windows, with compensation and recovery time.
A regular review to remove false alerts and set which ones wake people up.
A regular review to remove false alerts and set which ones wake people up.
Role-based access, regular reviews and a clean exit checklist through the exit and offboarding process.
Role-based access, regular reviews and a clean exit checklist through the exit and offboarding process. Have the terms reviewed by a qualified professional.
Short guides for each client's servers and decisions, so more than one engineer can act.
Short guides for each client's servers and decisions, so more than one engineer can act.
A chart of who to call, and which changes an engineer may make alone at night.
A chart of who to call, and which changes an engineer may make alone at night.
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.
Night and change-window rotas with fair allowances and rest, and accurate records.
Prompt removal of access to client systems and transfer of client knowledge.
Fatigue and isolation care for night staff.
Run books, escalation charts and access terms kept current.
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
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 article
A delivery head's plan for the notice period: what to ask the leaver in the first week, how to capture knowledge, when to cut access and how to keep the client informed.
6 min readRead articleMore on the GullyHR blog.
Rotate nights, limit runs, provide rest and keep contact with the day team. Review alert volume, since noise adds fatigue. Take advice on legal duties from a qualified professional.
Share change work across engineers on a rota, pay or compensate fairly and plan recovery time. Record who worked what so it is visible.
Give the least access required, review regularly and remove it on role change or exit. Keep logs, and ensure staff understand their duty.
Alert noise causes fatigue and missed incidents. Cleaning alerts is an engineering task, but HR can make sure staff feel able to raise the problem.
Write run books, pair engineers on each client and rotate responsibilities. Include knowledge sharing in goals.
We would ask about night shift design, change-window fairness, access removal and escalation. A sensible first project is a rota with an exit checklist. Scope goes into writing before you decide.
All 61 business types in information technology and software · 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.