Why software employees leave and how to understand why
Engineers and product staff leave for reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 min readRead articleA networking services company sells engineer time on client networks: cabling, switches, firewalls, Wi-Fi and links. The business depends on the right certified person reaching the right site, including at night, and being paid fairly for it.

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 networking service company installs, maintains and fixes client networks. Its people are network engineers, cabling teams, firewall and Wi-Fi specialists and a help desk that takes the first call. Work comes as planned rollouts, annual maintenance contracts and urgent faults, so some weeks are quiet and some run through nights and holidays. Engineers hold vendor certifications that the owner sells to clients, and some work alone at a client site. Rosters, allowances and certifications are where owners feel the pressure first. See also HR for IT and software and HR for IT infrastructure and managed services.
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 networking service 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.
The engineer who knows that client is on leave, and the person on call has never seen the site. The delay is on your name, not theirs.
Willing people get called most, and the rest are never asked. Tired seniors then resign or start making mistakes at client sites.
A client contract asks for a certified engineer by name. If the certificate lapsed last month, a tender or renewal is at risk.
Night visits, travel days, weekend rollouts and standby hours are paid by habit. Engineers compare notes and the difference is noticed.
Three rollouts starting in the same week pull in everyone, and the support desk is left with juniors.
Hours worked at a client site can be known only to the engineer. Disputes arise when the project closes and the hours are totalled.
A newly certified engineer is attractive to rivals and to the client itself, and the cost of the course walks out with them.
Start with the topics that matter most here: Employee Administration; Compensation, Payroll and Benefits; Learning and Development. Then work through the rest. Each topic is written for information technology and software, not in general.
Records, attendance, leave and the day-to-day HR that must simply work.
Salary structure, payroll inputs and a month that closes on time.
Training planned from need rather than from the calendar.
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.
Goals, reviews and ratings that hold up in a conversation.
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.
Induction, records, incident reporting and follow-through.
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.
An HR function that runs the same way every month.
The pieces a networking service companies business puts in place, in an order that makes each easier. Open any card for the detail.
A published roster by week with a named primary and backup per client group, a handover note and a limit on consecutive nights.
A published roster by week with a named primary and backup per client group, a handover note and a limit on consecutive nights. The attendance, shift and leave process defines how it is kept.
One list of every engineer, each vendor certificate, the expiry date and who pays for the renewal, reviewed monthly.
One list of every engineer, each vendor certificate, the expiry date and who pays for the renewal, reviewed monthly. The learning and development process plans the exam calendar.
A short table covering standby, call-outs, night visits, travel days and weekend rollouts, so two engineers in the same situation get the same answer.
A short table covering standby, call-outs, night visits, travel days and weekend rollouts, so two engineers in the same situation get the same answer.
Plain role descriptions from L1 to L3 and project lead, with what each is trusted to do alone at a client site.
Plain role descriptions from L1 to L3 and project lead, with what each is trusted to do alone at a client site. The role design work sets the ladder.
Before accepting a rollout date, check who is free, who is on leave and who is mid-certification, so promised dates are met.
Before accepting a rollout date, check who is free, who is on leave and who is mid-certification, so promised dates are met.
A clear, fair understanding on what happens if an engineer leaves soon after the company pays for a course.
A clear, fair understanding on what happens if an engineer leaves soon after the company pays for a course. Confirm the wording with a qualified professional.
Before changing anything, find out what is true today. Work through the checks using a recent operating period. The time needed depends on the records you hold; note missing evidence and use the findings to choose a priority.
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.
An on-call roster and an hours record that is fair to engineers and clear to clients.
A certification calendar and a skills ladder so exams are planned, not scrambled.
Allowances for standby, night visits and travel written as rules, not favours.
Clear L1 to L3 and project lead roles, so everyone knows what they can do alone at a site.
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 reasons beyond salary. How to run an exit conversation in a software company, read the pattern and act on it.
6 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
Simple variable pay structures for product and engineering teams: four options, why individual metrics backfire, a build plan and a one page outline to adapt.
6 min readRead article
A founder's guide to hiring freshers and running a first-year programme: campus or open drives, a screening round, a training plan by quarter, mentors and checkpoints.
6 min readRead articleMore on the GullyHR blog.
It depends on the number of clients, the number of night-time faults and how far apart the sites are. Count your night calls for a quarter, then size a primary and a backup per client group from that.
That is a business and legal choice. Some firms pay a standby allowance and a separate call-out rate. Decide the rule in advance, write it down and confirm the legal side with a qualified professional.
Pair the course with a visible next grade and pay step, and agree in writing what happens if they leave soon after. Retention comes more from a clear path than from a clause.
One named person, such as the service delivery head or HR, owns the register and checks it on a set schedule. Engineers also need a reminder, but the company should not depend on them alone.
Share a simple check-in routine, the site contact and a way to reach the on-call lead. For specifics on safety duties, confirm the rules with a qualified professional.
We would ask for your last quarter of night calls, your list of engineers and certificates, and your next three rollout dates. A fair on-call roster with a written allowance table is a natural first job, and scope goes into writing for your sign-off.
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 your industry, team size and the issue you want to address. Bring one example of where work gets delayed or ownership is unclear, and the deadline or decision you are working towards.