Industries
Why manufacturing employees leave and how to understand why
Operators, technicians and supervisors leave for reasons that sit in shifts, skills and supervision. How to ask, read the pattern by shift and act on it.
6 min readRead article
Electronics and Embedded Systems · IoT Device Makers
HR for IoT Device Makers: Connected Hardware, Firmware and Cloud Teams
An IoT device maker sells hardware that talks to the cloud, so electronics, firmware, app and support teams must work as one. The people strain comes from mixed skills, field failures and fast-moving product plans.
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 IoT device maker builds products that sense, connect and report, such as trackers, smart meters, home devices or industrial gateways. The company needs hardware designers, firmware developers, cloud and mobile app engineers, testers and a small production or contract assembly team. A device may be in the field for years, so over-the-air updates, support calls and returns keep teams busy after launch. Roadmaps change with customer feedback and funding. Founders often manage all of this with a young team, and the risk is that hardware and software people work to different calendars, pay and expectations. See also HR for manufacturing.
- Plan
- Hire
- Onboard
- Manage
- Develop
- Perform
- Engage
- Retain
- Exit
- Improve
When HR is weak in IoT device makers, you may see
- Hardware and software teams keep different clocks
- Field failures pull engineers off roadmap work
- Pay and growth differ across disciplines
- Product plans change with every funding or customer turn
- Support work has no clear owner
- Early joiners carry too much
These are the places the people side of this kind of business tends to give way. The rest of this page works through them.
Who does the work in IoT device makers
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.
- Hardware engineers
- Firmware engineers
- Cloud and backend developers
- Mobile app developers
- Test and quality engineers
- Field support engineers
- Product managers
- Production and logistics coordinators
Where HR strains in IoT device makers
Hardware and software teams keep different clocks
Software ships often while hardware waits for boards and certificates, and each side feels the other is slow.
Field failures pull engineers off roadmap work
A batch problem at a customer site sends firmware and support people to firefight, and planned features slip.
Pay and growth differ across disciplines
App developers can easily move to software firms for higher pay, while hardware engineers are rare and slow to replace.
Product plans change with every funding or customer turn
Teams rebuild work they just finished, and motivation drops when priorities shift without explanation.
Support work has no clear owner
Customer complaints reach engineers directly, and nobody tracks which issues recur or who solves them.
Early joiners carry too much
The first engineers hold design, hiring and support together and burn out before the company can add a second line of managers.
HR topics for IoT device makers
Start with the topics that matter most here: HR Strategy and Workforce Planning; Organisation Design; Recruitment and Talent Acquisition. Then work through the rest. Each topic is written for manufacturing, not in general.
HR Strategy and Workforce Planning
How many people, in which roles, by when — and what they will cost.
Organisation Design
Structure, reporting lines and who is allowed to decide what.
Recruitment and Talent Acquisition
Requisition to joining, the same way every time.
Onboarding and Probation
A first day that is the same for the fifth joiner as the first.
Employee Administration
Records, attendance, leave and the day-to-day HR that must simply work.
Compensation, Payroll and Benefits
Salary structure, payroll inputs and a month that closes on time.
Performance Management
Goals, reviews and ratings that hold up in a conversation.
Learning and Development
Training planned from need rather than from the calendar.
Career and Succession Management
Named backups for the roles that cannot be vacant.
Employee Engagement and Experience
Communication, recognition and the conditions people actually work in.
Employee Relations
Two routes — one for complaints, one for conduct — kept separate.
Policies, Compliance and Governance
Policies a manager can apply, and obligations with owners and dates.
Health, Safety and Wellbeing
Induction, records, incident reporting and follow-through.
Retention and Attrition Management
Who leaves, when, why — and which of them mattered.
Exit and Alumni Management
Resignation to relieving letter, in a defined order.
HR Technology and Automation
Records that survive people, and approvals that do not queue.
HR Analytics and Management Reporting
A short monthly pack management actually reads.
HR Operations and Governance
An HR function that runs the same way every month.
What a working HR set-up looks like
The pieces a IoT device makers business puts in place, in an order that makes each easier. Open any card for the detail.
Set common planning rhythms
A shared calendar of hardware milestones, firmware releases and app updates so each team sees the others' constraints.
What this coversHide
Set common planning rhythms
A shared calendar of hardware milestones, firmware releases and app updates so each team sees the others' constraints.
What this coversHideA shared calendar of hardware milestones, firmware releases and app updates so each team sees the others' constraints. The hr strategy and workforce planning work covers this.
Make roles and grades clear across disciplines
Role descriptions for hardware, firmware, cloud and support with a transparent path.
What this coversHide
Make roles and grades clear across disciplines
Role descriptions for hardware, firmware, cloud and support with a transparent path.
What this coversHideRole descriptions for hardware, firmware, cloud and support with a transparent path. See role design and job descriptions.
Separate support from engineering
A named support rotation with a log of field issues and a weekly review of the repeats.
What this coversHide
Separate support from engineering
A named support rotation with a log of field issues and a weekly review of the repeats.
What this coversHideA named support rotation with a log of field issues and a weekly review of the repeats.
Explain priority changes to the team
A short note on why the plan changed and what it means for each person, before the first rumour.
What this coversHide
Explain priority changes to the team
A short note on why the plan changed and what it means for each person, before the first rumour.
What this coversHideA short note on why the plan changed and what it means for each person, before the first rumour.
Plan hiring by skill rarity
Start searches for hardware and embedded roles early and keep software roles steady.
What this coversHide
Plan hiring by skill rarity
Start searches for hardware and embedded roles early and keep software roles steady.
What this coversHideStart searches for hardware and embedded roles early and keep software roles steady. See recruitment process consulting.
Start by checking where you stand
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 requirements- List which teams depend on which others for the next release.
- Count how many engineering hours went to field support last month.
- Check the pay gap between your software and hardware engineers for similar experience.
- Ask each team lead what priority change hurt them most this quarter.
- Note how many roles in your team have no written description.
- Confirm with a qualified professional the registration, record-keeping and employment obligations that apply to your IoT device 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.
How GullyHR helps
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.
- Role design and job descriptions
Clear roles across hardware, firmware, cloud and support in a small company.
- Recruitment process consulting
A hiring routine that handles rare hardware skills and quick software searches.
- Workforce planning
Hiring and team structure planned against the product roadmap.
- Retention and attrition management
Reasons to stay for early engineers who carry design and support together.
Start with a free conversation, or see the paid HR Diagnostic.
Our HR transformation approach
- 1
Assess
Understand the business, its workforce, current processes and HR challenges.
- 2
Identify gaps
Find the missing, weak, inconsistent or person-dependent processes.
- 3
Design
Create the structure, processes, policies, SOPs, dashboards and systems needed.
- 4
Implement
Help HR and department managers actually adopt the new system.
- 5
Automate
Digitise repetitive and approval-based workflows where it is worth doing.
- 6
Measure
Track hiring, attendance, employee cost, performance, training and attrition.
- 7
Improve
Strengthen the people-management system continuously, not once.
Blogs worth reading first
From the GullyHR blog: one on HR in manufacturing, and one on each of the topics this page points to.
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 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 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
Share one planning calendar, hold a short joint review each week and name a single owner for each release. Make constraints visible so neither team feels ignored.
You can use one structure with different market ranges. Compare each role to its own market and write down the reasons so people see the logic.
Run a support rotation, log issues and review repeats weekly. Engineers on rotation are protected from other work.
Explain the reason, show what is paused and what is not and ask the team for concerns. Constant change without explanation costs trust.
Define the real work first, then hire for it. Short interviews with a practical task work well for firmware and app roles.
We would look at how hardware and software calendars connect, how many hours went to field support last month and which roles have no written description. A good first piece of work is a cross-discipline role and grade structure. Scope is agreed in writing afterwards.
More on HR for manufacturing
All 8 business types in electronics and embedded systems · Find another business type
Embedded Systems CompaniesPCB ManufacturersPCB Assembly UnitsElectronic Manufacturing Services ProvidersIndustrial Electronics MakersElectronic Product ManufacturersHR Strategy and Workforce Planning in manufacturingOrganisation Design in manufacturingRecruitment and Talent Acquisition in manufacturing