A design house wins a contract for a brushless motor controller. Two weeks after kick-off, the firmware engineer who scoped it accepts an offer from a consumer products company. His replacement arrives three months later and spends two more learning the register map and the build scripts. The customer's pilot run slips. The owner wonders why last year's raise did not hold him.
Our electronics and embedded systems page puts this first among the patterns in the group: engineers are scarce, and they know it. The answer is rarely a fatter offer letter. It is a handful of steady changes to how engineers are hired, handed work and shown a future.
Signs in the design team
- Shortlisted candidates vanish between the technical round and the offer because a rival moved faster.
- Resignations cluster just after customer releases, almost never mid-project.
- Counter-offers have become routine, and each one quietly resets what the rest of the team expects.
- Juniors cannot be trusted alone with a JTAG debugger because the seniors who coach them keep leaving.
- One or two people absorb every nasty bring-up, and those are exactly the names recruiters call.
The bill for a lost engineer
The visible part is a vacancy open for months, a recruiter's fee and perhaps a joining bonus. The heavier part arrives later. A release stalls because nobody else understands the bootloader. Schematic reviews thin out to one reviewer. The newcomer burns weeks on the test jigs, the toolchain and old design notes before shipping useful code. And the senior who mentors them loses hours from their own board.
There is a social cost too. Each visible exit tells the remaining engineers that moving on is normal, and it hands recruiters a fresh list of colleagues to ring.
Why salary matching never settles it
Most firms in this group benchmark only on pay. Engineers benchmark on more. Will the next project teach me something? Is there time to pick up a new microcontroller family, Zephyr or embedded Linux? Can I become a principal engineer without managing people?
Allocation is often the buried cause. Projects go to whoever happens to be free, so a strong engineer can spend a year patching an ageing data logger. Late nights at the oscilloscope are expected but invisible at appraisal. Interview loops crawl across a month because the one engineer able to run the technical round is firefighting a field issue.
Six steps, starting with your own records
- 1
Read the last twelve months first
List every engineer who resigned and every candidate who declined. Note the stage, the stated reason and the project each was on. Timing patterns show up fast.
- 2
Price the skill, not the title
An engineer who ports an RTOS and writes peripheral drivers sits in a different market from one who maintains application code. Compare like with like before moving any number.
- 3
Allocate on purpose
Before each project, decide who leads, who learns and who backs up. Rotate maintenance builds so they do not settle permanently on the same desks.
- 4
Write the technical ladder down
Engineer, senior, lead and principal, each defined by what it owns: a module, a board, a product, an architecture. Strong engineers can climb without taking on a team.
- 5
Ring-fence learning hours
A fixed slot each month for a new chip, a tool or a conference talk, tied to the roadmap so nobody mistakes it for leisure.
- 6
Compress the hiring loop
Name two engineers who can run the technical round, fix one practical exercise and aim to decide within a week of first contact.
Pricing skills is covered in our pay benchmarking notes for embedded design firms. The hiring guide for IoT device makers walks through a loop for roles that straddle hardware and software.
Selling the work honestly at interview
Scarce engineers interview the firm as hard as it interviews them. Show the bench. Name the parts on the current boards, the RTOS or bare-metal choice and the radios involved. Admit the messy bits too, such as late customer changes or the occasional night at a customer's plant. Candidates who join knowing the real picture stay longer than those sold a glossy one.
Let a working engineer, not only HR, take the candidate through a recent bring-up story. Hearing how a stubborn clock issue or a brown-out reset was traced tells a good candidate more about the team than any brochure. It also shows whether your engineers enjoy the craft, which is the strongest pitch a small firm has.
Questions to put to yourself on Monday
- Which engineers have sat on maintenance work for two quarters or longer?
- Who has never been asked about their next project since joining?
- How many days did the last three technical hires take from first call to offer?
- Where does your pay sit for the skills each engineer actually uses?
- Does any role above senior engineer exist on paper?
If the hiring loop is where you lose people, our recruitment process consulting is the natural starting point. You can also share your requirements in a few short steps.
