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 analytics firm turns client data into reports, dashboards and forecasts. Here is how to manage analysts, data engineers and consultants whose work depends on clean data, careful checks and clients who change their questions.

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 analytics company collects, cleans and studies data for clients, then presents the findings as reports, dashboards or models. Teams include data engineers who build pipelines, analysts who explore and explain the numbers, business intelligence developers who build dashboards, data scientists and consultants who meet clients. Much of the time goes into cleaning poor data and rerunning work when the client changes the question. Staff hold sensitive client information, so confidentiality and access control matter every day. Quality depends on checking and peer review, which tight deadlines squeeze. Analysts are in demand, so good ones leave for in-house roles at clients or larger firms. 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 data analytics 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.
Analysts expected to find insight spend weeks fixing client files, and feel their skill is wasted.
Clients rewrite the brief after seeing early results, and the team redoes work with no change in deadline.
Deadlines push reports out unreviewed, and one wrong figure damages client trust.
Staff copy files to personal devices or share extracts casually, creating real exposure for the firm.
They deliver a report and never learn whether the client acted on it, so motivation fades.
Clients offer jobs to the analysts they have worked with, and the firm loses the people who know the account.
Pipelines get built without the analyst's needs in mind, and each side blames the other for delays.
Billable hours are watched closely, leaving little time for new tools and methods.
Start with the topics that matter most here: Performance Management; Learning and Development; Policies, Compliance and Governance. Then work through the rest. Each topic is written for information technology and software, not in general.
Goals, reviews and ratings that hold up in a conversation.
Training planned from need rather than from the calendar.
Policies a manager can apply, and obligations with owners and dates.
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.
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.
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 data analytics companies business puts in place, in an order that makes each easier. Open any card for the detail.
Each path has its own levels and expectations.
Each path has its own levels and expectations. Compensation benchmarking helps place pay for each.
Every client deliverable is checked by a second named person before release, and time for it sits in the plan.
Every client deliverable is checked by a second named person before release, and time for it sits in the plan.
A short, signed data-handling rule, access that ends when a project ends, and an exit checklist through the exit and offboarding process.
A short, signed data-handling rule, access that ends when a project ends, and an exit checklist through the exit and offboarding process. Have the wording checked by a qualified professional.
When a client changes the question, the project manager records the effect on time and cost before work restarts.
When a client changes the question, the project manager records the effect on time and cost before work restarts.
A set share of time for new tools and methods, planned with the learning and development process.
A set share of time for new tools and methods, planned with the learning and development process.
A follow-up conversation after delivery so analysts hear how the work was used.
A follow-up conversation after delivery so analysts hear how the work was used.
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.
Pay structures for analysts, engineers and consultants, set against the market for scarce data skills.
Planned time for tools and methods, so skills keep pace with client needs.
A clean closing of data access, files and project knowledge when staff leave or projects end.
Appraisal that rewards accuracy and insight, not only billable hours.
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 practical design for an IT services appraisal cycle: when to run it, how to rate fairly across projects, and how to explain hikes so they hold.
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
How an India head can sort a global parent's HR policies into apply, adapt or replace, write an India addendum with advisers, and keep headquarters on side.
7 min readRead articleMore on the GullyHR blog.
Make a second reviewer a fixed step and plan time for it. Keep a checklist of common errors. Leaders must accept that a short delay is better than a published mistake.
Use a simple change record that states the extra effort and cost. This is a project management step, but HR can support it by recognising the extra load in workload and appraisal.
Offer growth, interesting problems and a way to see the impact of their work. Some firms add a non-solicitation clause with clients; take advice on this from a qualified professional.
Give access only for the project, record who has it and remove it at the end. Train staff on what not to copy or share, and review it every quarter.
It shows workload but not quality. Use it alongside review scores, client feedback and learning time. Pure utilisation targets push people to rush.
We would ask about review practice, data handling, scope changes and how analysts, engineers and consultants are graded. A sensible first project is a review rule with clear role ladders. 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.