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 mobile application company builds for phones that its clients and their customers hold in their hands. Release dates, store reviews and device differences set a rhythm that makes scarce specialists hard to hire and easy to lose.

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 mobile application company builds software for phones and tablets, either for clients or for products of its own. The team has Android and iOS developers, designers who think in small screens, back-end developers for the services behind the screens, testers with a shelf of devices, and a product or project lead. Work moves in release cycles. A build goes to the store for review, a rejection or a crash after launch needs a fix at once, and new phone versions force updates. Strong mobile developers are in short supply and know it. The wider IT and software page covers what the sector shares.
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 mobile application 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.
A build submitted late on Friday, a store rejection on Saturday and a crash report on Sunday turn a release into a weekend for the whole team.
Good mobile developers are scarce, so offers fly and a single resignation can stall a client's release.
One platform's developer cannot cover the other, so leave or exits leave a gap.
Testers check dozens of phones and versions by hand, and the work is seen only when something is missed.
New system versions force changes to released products, and the effort rarely appears in a plan or a quote.
What looks right in a design file behaves differently on a phone, and the discussion repeats on every project.
Developers in other cities join calls but feel outside the group, and growth conversations are sparse.
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 mobile application companies business puts in place, in an order that makes each easier. Open any card for the detail.
A shared view of store submissions, rollouts and holidays so leave and cover are set early.
A shared view of store submissions, rollouts and holidays so leave and cover are set early. The attendance and leave process can use it.
Pair Android and iOS developers on small tasks so cover exists.
Pair Android and iOS developers on small tasks so cover exists. The learning and development process can plan it.
A list of devices, an owner and a way to rotate testing duty so it is shared and recognised.
A list of devices, an owner and a way to rotate testing duty so it is shared and recognised.
Reserve time each quarter for system changes and tell clients in contracts.
Reserve time each quarter for system changes and tell clients in contracts. Hours then stop vanishing.
A short joint session on real devices before build begins, to settle behaviour questions.
A short joint session on real devices before build begins, to settle behaviour questions.
Monthly one to ones with remote developers and visible chances to lead.
Monthly one to ones with remote developers and visible chances to lead.
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.
Cross-platform pairing and skills growth for scarce specialists.
A route to find and assess hard-to-hire mobile developers.
Simple measures of release load, attrition and time to hire.
Pay for scarce mobile skills set against nearby offers.
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
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.
Start early, assess with a short practical task, move quickly and offer growth as well as pay. Keep contact with past candidates, and consider training capable developers from a nearby platform.
Plan the release calendar early, rotate who is on call and give time back. Fix the causes too, such as late builds and unclear testing, that make weekends necessary.
Yes for basics and reviews. You will not turn an iOS specialist into an Android one overnight, but pairing builds cover for emergencies and makes people more valuable.
Treat device testing as a skill, share the load, show the defects they caught and give a path toward lead or automation roles. Their work is easily invisible.
Schedule regular one to ones, include them in planning and give them leading tasks. Meet in person now and then if budgets allow.
First we would count weekend releases, list platform skills held by single people and compare your pay with nearby offers. A learning plan for cross-cover and a release calendar are a natural first job, with scope agreed in writing.
All 6 business types in software development companies · 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.