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 modernisation company moves old applications to new platforms for clients who cannot afford to stop. Here is how to hire rare legacy skills, train for new ones and manage cutover weekends and client-site teams.

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 requirementsAn application modernisation and legacy migration company helps clients move from old systems, such as mainframes, COBOL, old Java or .NET stacks, on-premise databases and desktop applications, to cloud, modern frameworks and new data platforms. Its people are architects, analysts who read old code with no documentation, developers, database specialists, testers, project managers and cutover leads. The old systems are critical to banks, insurers, manufacturers and government bodies, so mistakes are costly. Skills on the old side are rare and ageing, and often held by clients' own retiring staff. Teams read code written decades ago, reconstruct business rules, then rebuild and test it on new platforms. Delivery is organised in phases, with cutover weekends and parallel runs that need long shifts. Work is often on client sites or under client security rules. Engineers worry about their own skills going stale if they work only on old technology. See also HR for IT and software companies.
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 modernisation and migration 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.
Few engineers know the old language and system, and the company competes for them with clients and rivals.
A developer who spends two years on old code worries about being unemployable elsewhere and leaves for modern work.
The only people who understand the business rules are near retirement at the client, and handover may be missed.
Teams work through nights to switch systems, and a failure means rollback, blame and exhaustion.
Staff work under client policies, with restricted devices, limited access and different cultures, making supervision harder.
Veterans of old systems and young cloud engineers misunderstand each other, and respect is uneven.
Estimates assume code is simple, then hidden complexity appears and the team is asked to catch up through overtime.
Engineers wait between migrations, and the company must decide whether to train, redeploy or let them go.
Start with the topics that matter most here: Recruitment and Talent Acquisition; Learning and Development; Retention and Attrition Management. Then work through the rest. Each topic is written for information technology and software, not in general.
Requisition to joining, the same way every time.
Training planned from need rather than from the calendar.
Who leaves, when, why — and which of them mattered.
How many people, in which roles, by when — and what they will cost.
Structure, reporting lines and who is allowed to decide what.
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.
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.
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 modernisation and migration companies business puts in place, in an order that makes each easier. Open any card for the detail.
A map of legacy skills needed and a mix of hiring, retired experts as advisers and internal training.
A map of legacy skills needed and a mix of hiring, retired experts as advisers and internal training. The recruitment process can support it.
Rotation between old and new work, certifications and recognition so engineers see growth.
Rotation between old and new work, certifications and recognition so engineers see growth. The learning and development process helps.
Interviews, recorded walkthroughs and shadowing before key client people retire, with a named owner.
Interviews, recorded walkthroughs and shadowing before key client people retire, with a named owner.
Shift plans, rest before and after, food and travel arrangements and a decision point to roll back.
Shift plans, rest before and after, food and travel arrangements and a decision point to roll back. See the attendance, shift and leave process.
Briefings on client rules, a company contact and regular check-ins for staff placed at client sites.
Briefings on client rules, a company contact and regular check-ins for staff placed at client sites. Confirm contract details with a qualified professional.
A learning list, internal tools to build and clear rules on how long a person can wait between projects.
A learning list, internal tools to build and clear rules on how long a person can wait between projects.
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.
Hiring for scarce legacy skills, including advisers and returnees.
Skill paths that keep legacy engineers employable.
Cutover rotas with rest and fair compensation.
Briefing for staff placed at client sites.
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
How a D2C founder can test a performance marketing hire on real work, ignore weak signals such as dashboard screenshots, and run a fair process.
7 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 article
What really keeps mobile app and web developers in a small firm: stay conversations, growth paths, fair release rules and a risk sheet an owner can use this month.
6 min readRead articleMore on the GullyHR blog.
Look at career-switchers, retirees as advisers and trainable engineers, and offer clear learning and project variety.
Rotate them between old and new work, fund certifications and show a visible path to modern roles.
A written plan with shifts, rest, meals, travel and decision points, and time off after the event.
Start capturing it early through interviews, recordings and shadowing, and agree a handover plan with the client.
Use a bench plan with training, internal work and clear communication. Avoid long unplanned waits.
We would ask which skills are scarce, how cutover weekends are staffed and how engineers see their careers. A sensible first piece of work is a scarce-skills hiring plan, a cutover rota and a skills path. Scope and fees are agreed in writing afterwards.
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.