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 unified communications provider sells voice, video, messaging and contact-centre tools as one service. Here is how to manage engineers, deployment teams and support staff whose customers cannot afford downtime on calls.

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 unified communications provider offers business phone systems, video meetings, chat, call routing and contact-centre software, often as a cloud service, sometimes with desk phones and headsets installed at the customer's site. Staff include voice and network engineers, software developers, deployment consultants who migrate a client's phones, support agents, sales engineers and account managers. Customers use the system all day, so downtime during business hours is felt at once, and migrations are done at night or on weekends. Call quality faults are hard to trace between the customer's network, the carrier and the platform, which causes friction between teams. 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 unified communications providers. 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.
Phone systems are switched over at night or on weekends, and the same engineers are repeatedly used.
Echo, jitter and drops could come from the client, the carrier or the platform, and teams argue.
A failure during working hours brings angry calls and leaves little room for calm diagnosis.
They must know phones, video, chat and routing, and new staff take months to be useful.
The few engineers who understand the core platform are paged often.
Complex integrations are promised without deployment input.
Installing phones and cabling at customer sites involves travel, ladders and tight windows.
Upstream changes force quick work with little notice to the team.
Start with the topics that matter most here: HR Operations and Governance; Onboarding and Probation; Health, Safety and Wellbeing. Then work through the rest. Each topic is written for information technology and software, not in general.
An HR function that runs the same way every month.
A first day that is the same for the fifth joiner as the first.
Induction, records, incident reporting and follow-through.
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.
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.
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 unified communications providers business puts in place, in an order that makes each easier. Open any card for the detail.
A fair schedule for after-hours cutovers, with rest afterwards and records via the attendance and shift process.
A fair schedule for after-hours cutovers, with rest afterwards and records via the attendance and shift process.
A shared method for finding where call quality fails, with joint ownership between network, voice and support.
A shared method for finding where call quality fails, with joint ownership between network, voice and support.
A staged programme from phones to routing to integrations, set up using the employee onboarding process and the learning and development plan.
A staged programme from phones to routing to integrations, set up using the employee onboarding process and the learning and development plan.
Run books and shadowing so more engineers can respond, with an allowance and rest after callouts.
Run books and shadowing so more engineers can respond, with an allowance and rest after callouts.
A review of every integration promise by a deployment person before it is sold.
A review of every integration promise by a deployment person before it is sold.
Checklists, ladders and working-at-height rules for engineers who install on client premises.
Checklists, ladders and working-at-height rules for engineers who install on client premises.
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.
Fair cutover and on-call rotas with accurate pay records.
A structured start for support agents and engineers, to build skill step by step.
Training across phones, video, routing and integrations.
Safe installation work and care for on-call fatigue.
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
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 first-week plan for bringing in an outside specialist: what access to give, how to protect client data, and the confidentiality steps to settle on day one.
7 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 articleMore on the GullyHR blog.
Use a rota, give an allowance and rest the next day, and record who worked. Avoid relying on the same few willing engineers.
Agree a joint tracing method and shared ownership of the ticket until the cause is found. Reviewing cases together reduces blame.
It depends on your product range. Use a staged plan, check skills at each stage and have a mentor. Rushing leads to wrong answers and unhappy clients.
Write run books, pair junior engineers with seniors and let them handle lower-severity alerts first. Pay a fair allowance.
Require a deployment review of complex integrations before a quote. Link some reward to delivered, not only signed, work.
We would ask about cutover rotas, fault-tracing, support training and on-call spread. A sensible first project is a cutover rota with a staged support training plan. 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.