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 · Embedded Systems Companies
HR for Embedded Systems Companies: Firmware, Hardware Design and Prototype Labs
An embedded systems company designs the hardware and firmware that sit inside other people's products, and often builds the first units too. The hard part is that a few engineers hold the whole design in their heads.
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 embedded systems company designs microcontroller boards, firmware and sometimes the enclosure and test setup for customers who put them inside meters, machines, vehicles or appliances. Work arrives as a customer specification, then moves through schematic, board layout, firmware, bring-up on the lab bench, testing and a pilot batch. Many firms also run a small production or assembly line for the first few hundred units. Teams are small. One firmware lead may know every driver and one hardware engineer may know every board revision. Projects have fixed customer dates, so the last weeks are long. Good engineers are approached by larger product companies all the time. See also HR for manufacturing.
- Plan
- Hire
- Onboard
- Manage
- Develop
- Perform
- Engage
- Retain
- Exit
- Improve
When HR is weak in embedded systems companies, you may see
- One engineer holds the whole design
- Bring-up work has no fixed hours
- Bench skill and desk skill are valued unevenly
- Customer changes arrive late
- Fresh graduates need long ramp-up
- Engineers are poached by product firms
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 embedded systems companies
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.
- Firmware engineers
- Hardware design engineers
- PCB layout designers
- Test and validation engineers
- Bring-up technicians
- Prototype assembly staff
- Project and programme managers
- Field application engineers
Where HR strains in embedded systems companies
One engineer holds the whole design
The firmware lead or board designer often carries undocumented knowledge, and if that person resigns mid-project the customer date is at risk.
Bring-up work has no fixed hours
Boards that do not boot or sensors that misbehave take engineers deep into evenings, and the effort is rarely recognised in how people are rated.
Bench skill and desk skill are valued unevenly
Technicians who debug with a scope and soldering iron are paid and graded below coders, although projects stall without them.
Customer changes arrive late
A specification change after layout sends hardware and firmware teams back to work together, and nobody owns the cost of that rework.
Fresh graduates need long ramp-up
A new engineer takes months to read the codebase and the lab habits, and seniors who mentor lose their own project time.
Engineers are poached by product firms
Larger companies offer fixed roles and brand names, so mid-level engineers compare your project churn with their stability.
HR topics for embedded systems companies
Start with the topics that matter most here: Retention and Attrition Management; Learning and Development; Compensation, Payroll and Benefits. Then work through the rest. Each topic is written for manufacturing, not in general.
Retention and Attrition Management
Who leaves, when, why — and which of them mattered.
Learning and Development
Training planned from need rather than from the calendar.
Compensation, Payroll and Benefits
Salary structure, payroll inputs and a month that closes on time.
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.
Performance Management
Goals, reviews and ratings that hold up in a conversation.
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.
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 embedded systems companies business puts in place, in an order that makes each easier. Open any card for the detail.
Write down who owns each module
A simple ownership sheet for firmware modules, board revisions and test scripts, with a named backup for each.
What this coversHide
Write down who owns each module
A simple ownership sheet for firmware modules, board revisions and test scripts, with a named backup for each.
What this coversHideA simple ownership sheet for firmware modules, board revisions and test scripts, with a named backup for each. See employee information management.
Grade bench and desk skills together
One scale that places bring-up technicians, test engineers and firmware developers by what they can do alone, linked to pay.
What this coversHide
Grade bench and desk skills together
One scale that places bring-up technicians, test engineers and firmware developers by what they can do alone, linked to pay.
What this coversHideOne scale that places bring-up technicians, test engineers and firmware developers by what they can do alone, linked to pay. See compensation benchmarking.
Plan a documented handover before every release
A short review where the engineer explains the design to a second person before the pilot batch, so knowledge is not held by one head.
What this coversHide
Plan a documented handover before every release
A short review where the engineer explains the design to a second person before the pilot batch, so knowledge is not held by one head.
What this coversHideA short review where the engineer explains the design to a second person before the pilot batch, so knowledge is not held by one head.
Give new engineers a staged first project
A small real task, then a bring-up shift beside a senior, then ownership of a module, with a sign-off at each step.
What this coversHide
Give new engineers a staged first project
A small real task, then a bring-up shift beside a senior, then ownership of a module, with a sign-off at each step.
What this coversHideA small real task, then a bring-up shift beside a senior, then ownership of a module, with a sign-off at each step. The learning and development process shapes this.
Hire for the project calendar
A view of which skills each coming project needs, so searches start before the gap.
What this coversHide
Hire for the project calendar
A view of which skills each coming project needs, so searches start before the gap.
What this coversHideA view of which skills each coming project needs, so searches start before the gap. The recruitment process consulting work supports it.
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 the modules and boards only one person understands.
- Ask your firmware lead who could take over if they left next month.
- Count how many evenings the last project's team worked beyond normal hours.
- Check how long your last three engineering hires took to deliver their first independent work.
- Note which technicians are graded lower than engineers although they unblock projects.
- Confirm with a qualified professional the registration, record-keeping and employment obligations that apply to your embedded systems 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.
- Retention and attrition management
Keeps the few engineers who hold your designs, with clear reasons to stay beyond the current project.
- Learning and development process
A staged path that takes a new graduate from reading code to owning a module.
- Compensation benchmarking
Grades that value bench technicians and firmware developers against nearby firms.
- Role design and job descriptions
Clear roles for hardware, firmware and test so ownership is not left to habit.
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
How to recognise and address employee workload problems
How to spot an unmanageable workload before it becomes an exit or an error, what to look at, how to talk about it and what to change, without guessing.
5 min readRead article
HR Process
The training calendar nobody attends: fixing the learning and development process
A calendar of courses, a budget spent by March and no record of what any of it changed. What a learning and development process contains when it starts from need rather than from the catalogue.
7 min readRead article
HR Management
Salary bands for SMEs: building grades when you have never had any
Most salary structures grew one negotiation at a time. How to build grades and bands from what you already pay, without repricing everybody at once.
8 min readRead articleMore on the GullyHR blog.
Questions owners ask
Ask for a module ownership sheet, pair every module with a backup and make a design walkthrough part of each release. Recognise the mentor's time in how you rate their work.
Record the hours and the problem solved, and look at it in ratings. Without a record, the people who stay late on stubborn boards look no different from the rest.
They can share one scale with different tracks. What matters is that debugging and test skills are written down and paid for, so technicians see a path upward.
Agree a change process with the customer, with a note of what each change costs in engineer days. It protects the team and gives you facts for the next quotation.
Be honest about what you offer: wider ownership, faster decisions and design work end to end. Show a clear grade path and keep the interview process quick.
We would look at which modules and boards only one person understands, how many extra evenings the last project took, and how long new engineers took to work alone. A good first piece of work is an ownership sheet plus a skill grade scale for engineers and technicians. Scope is agreed in writing afterwards.
More on HR for manufacturing
All 8 business types in electronics and embedded systems · Find another business type