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 robotics company builds machines from mechanical parts, firmware and vision software, so people with very different habits must ship one product. Here is how to organise them.

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 robotics company designs machines that sense, move and decide, for factories, warehouses, hospitals, farms or homes. One product needs mechanical designers, electronics and embedded engineers, software and vision developers, and technicians who assemble and test each unit. After sale, field engineers install the robot and keep it running at the customer's site. Robotics firms are young, small and funded in rounds, and move from a lab prototype to a small production batch quickly. The result is a team with very different working styles that must still ship on one date. For the wider sector picture, read 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 robotics 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 mechanical freeze takes weeks and a firmware build takes days, and each team blames the other when a release slips.
People who thrived building one-off arms struggle with repeatable build sheets, test records and revision control.
Engineers with motion control, ROS or machine vision experience are few, and each hire takes long enough to delay a product.
Service engineers fly out to customer sites at short notice, work long days away and are hard to supervise or appraise.
Technicians who wire, calibrate and test each unit are paid like helpers, though shipped quality depends on them.
Early employees who did everything resist a narrower role, and newer joiners do not know who owns what.
Hiring surges after a round and freezes before the next, which leaves teams uneven and morale unsettled.
Start with the topics that matter most here: Organisation Design; HR Strategy and Workforce Planning; Recruitment and Talent Acquisition. Then work through the rest. Each topic is written for information technology and software, not in general.
Structure, reporting lines and who is allowed to decide what.
How many people, in which roles, by when, and what they will cost.
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.
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.
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 robotics companies business puts in place, in an order that makes each easier. Open any card for the detail.
Who owns the design, who signs off a release and who settles a trade-off between hardware and software.
Who owns the design, who signs off a release and who settles a trade-off between hardware and software. The organisation design work sets this out.
A rolling view of the skills each milestone needs, so hiring is steady and not a rush after a round.
A rolling view of the skills each milestone needs, so hiring is steady and not a rush after a round. The workforce planning approach supports it.
Grades for wiring, calibration and test staff with clear skills at each step, so the people who build the robot can grow with the company.
Grades for wiring, calibration and test staff with clear skills at each step, so the people who build the robot can grow with the company.
Trip planning, rest after long site days, allowances and a regular check-in with a manager, recorded through the attendance process.
Trip planning, rest after long site days, allowances and a regular check-in with a manager, recorded through the attendance process.
Simple build and test procedures that new staff follow, so quality does not depend on whoever built the prototype.
Simple build and test procedures that new staff follow, so quality does not depend on whoever built the prototype. See HR documentation.
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.
Clear structure and ownership across mechanical, electronics and software teams.
Hiring planned against the product roadmap and funding rounds, not in bursts.
Roles and grades that fit a growing firm, including assembly, test and field staff.
Safe routines for workshops, test cells and customer sites where moving arms and drives are used.
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
A founder's guide to building job grades, titles and billing levels for a growing IT services firm, with a step-by-step method and a grade description outline.
6 min readRead article
How a D2C founder can decide which digital marketing work to hire for, which to buy from an agency, and which to split, with a worksheet and a five step plan.
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 articleMore on the GullyHR blog.
Give them shared milestones, one owner for the product and regular joint reviews. Separate plans and separate bosses are the usual cause of friction.
When roles overlap and nobody is sure who decides, when you hire more than a few people a quarter, or when the first production batch is planned. Basic roles, pay logic and records pay off early.
Plan early, be specific about the skills you need, and consider people from adjacent fields who can learn. Let the hiring process show the work. The [talent acquisition service](/talent-acquisition-services) can support the search.
Plan trips ahead, agree allowances and rest rules, keep a regular call with a manager and review their work through customer feedback and records, not only observation.
Be honest about how roles will change, give a defined scope and growth path, and recognise what they built. Some leave because the role shrinks without discussion.
We would map who owns what across mechanics, firmware and software, which skills the next milestones need, and how assembly and test staff feel they are treated. A sensible first job is a short role and decision-rights note that each discipline agrees. Scope and next steps are then written out for you to review.
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 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.