Industries
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 article
Information Technology and Software
HR for Robotics Companies: Engineers, Technicians and Field Teams
A robotics company builds machines from hardware, software and electronics, so it needs very different people to work as one team. 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 requirementsHow the work is organised
A robotics company designs and builds machines that sense, move and make decisions, for factories, warehouses, hospitals, farms or homes. A product needs mechanical designers, electronics and embedded engineers, software and AI developers, and the technicians who assemble and test the machine. Once a robot is sold, field engineers install it and keep it running at the customer's site. Many robotics firms are young, small and funded in stages, and move from prototype to small-batch production quickly. The result is a team with very different working styles who must still ship the same product on time. See also HR for IT and software.
Who does the work
- Mechanical design engineers
- Electronics and embedded engineers
- Software and AI engineers
- Assembly and test technicians
- Quality and validation engineers
- Field installation and service engineers
- Product and project managers
- Supply chain and procurement staff
Where HR strains in robotics companies
Different disciplines pull in different directions
Hardware and software teams plan at different speeds and blame each other when a release slips.
Prototype habits meet production needs
People who thrived building one-off machines struggle with repeatable processes, documentation and quality records.
Specialist talent is scarce
Engineers with robotics, control or vision experience are few, and each hire takes long enough to delay a product.
Field work is lonely and unplanned
Service engineers travel to customer sites at short notice, work long days away and are hard to supervise or appraise.
Assembly and test teams are under-recognised
Technicians who build and test the product are paid and treated as support staff, though quality depends on them.
Roles stretch as the company grows
Early employees who did everything resist a narrower role, and newer joiners do not know who owns what.
Funding cycles drive hiring stops and starts
Hiring surges after a round and freezes before one, which leaves teams uneven and morale unsettled.
What a working HR set-up looks like
- 01
Define roles and decision rights across disciplines
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.
- 02
Plan hiring to the product roadmap
A rolling view of the skills needed per milestone, so hiring is steady rather than a rush. The workforce planning approach supports it.
- 03
Create a technician and test career path
Grades for assembly and test staff with clear skills at each step, so the people who build the product can grow with the company.
- 04
Set rules for field travel and site work
Planning of trips, rest after long site days, allowances and a regular check-in with a manager, recorded through the attendance process.
- 05
Document the way a robot is built and tested
Simple build and test procedures that new staff follow, so quality does not depend on the person who built the prototype. See HR documentation.
What to put in place first
- Draw who owns what across hardware, firmware and software, and check whether people agree.
- List the next six months of roadmap milestones and the skills each one needs.
- Ask assembly and test staff what they would change about how they are treated.
- Count nights field engineers spent away last quarter and how rest and allowances were handled.
- Check whether the way your product is built is written down anywhere other than one person's head.
- Confirm with a qualified professional the employment, travel and workplace-safety obligations that apply to your robotics business.
Confirm 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.
Where GullyHR helps
- Organisation design
Clear structure and ownership across mechanical, electronics and software teams.
- HR strategy and workforce planning
Hiring planned against the product roadmap and funding, instead of in bursts.
- Role design and job descriptions
Roles and grades that fit a growing firm, including assembly, test and field staff.
- Workplace health, safety and wellbeing
Safe working routines for workshops, test areas and customer sites where moving machines are used.
Every engagement starts by recording where you stand, and every later report compares against that. We do not promise outcomes. Start with a free conversation, or see the paid HR Diagnostic.
Blogs worth reading first
From the GullyHR blog: one on HR in information technology and software, and one on each of the topics this page points to.
HR Management
Everyone reports to the founder: when and how to redesign the structure
A flat structure works until the founder becomes the only route to a decision. How to tell when you have passed that point, and how to redesign without a reorganisation.
8 min readRead article
HR Management
"We need two more people": the headcount plan nobody wrote
Hiring decisions made one request at a time, in the month the pain is worst. What a workforce plan contains and why a twelve-month view changes what you hire.
7 min readRead article
HR Process
Why new hires don't turn up on day one, and what to do between offer and joining
Candidates who accept and never arrive are usually lost in the silence between offer and joining. What actually causes it, and a contact plan that closes the gap.
8 min readRead articleMore on the GullyHR blog.
Questions owners ask
Give them shared milestones, a single 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 start hiring 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. Treat the hiring process itself as a way to 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 through observation.
Be honest about how roles will change, give them a defined scope and growth path, and recognise what they built. Many leave because the role shrinks without discussion.
The conversation would map who owns what across hardware, firmware and software, which skills the next roadmap milestones need, and how assembly and test staff feel they are treated. A sensible first piece of work is a short role and decision-rights document that the disciplines agree on. Afterwards we would write down scope and next steps for you to review.
More on HR for information technology and software
All 5 business types in information technology and software · Find another business type
3D printing companiesCloud computing companiesComputer repair shopsCybersecurity firmsOrganisation Design in information technology and softwareHR Strategy and Workforce Planning in information technology and softwareRecruitment and Talent Acquisition in information technology and software
See all HR topics for information technology and software, or another industry.