How do I keep good embedded engineers?

The short answer: pay fairly, hand out varied and absorbing projects, defend time for learning, and show a route to lead roles that does not force anyone into people management. Then talk with each engineer regularly about what they want next, so you hear the trouble before a competitor's recruiter gets the chance.

That is the reply given on our electronics hub. Below, each part gets unpacked, a hypothetical design house shows it working, and the questions owners tend to ask next get answered.

Embedded engineers compare offers from product companies, chip vendors, automotive electronics teams and other design houses. Benchmark against those, not against general manufacturing. Look at what each engineer actually does rather than the label on their card. Someone who brings up new silicon, writes DMA drivers and tunes low-power modes commands a different price from a colleague who mostly edits application logic. Close big gaps quickly. Small gaps matter less when the rest of this list is in place. The salary comparison method for embedded teams sets out how.

Engineers often resign straight after a release, when the next assignment is vague or dull. Plan each engineer's next board before the current one ships. Rotate sustaining builds, customer escalations and fixes on ageing products across the team. Give each senior engineer something to own outright: a board, a stack, a customer relationship. Ownership is a strong anchor, as long as it does not turn into the single-owner trap.

Engineers who stop learning start browsing job boards. Reserve a block every month for a new microcontroller family, a trace tool, embedded Linux or secure boot. Link it to the roadmap so its value is obvious. Let engineers present what they learned at a lunchtime tech talk. Buy the evaluation board or the conference pass where it fits the product, and do not cancel learning time for every customer escalation.

• Engineer: delivers modules under review.
• Senior engineer: owns a module or board, reviews colleagues' work and mentors juniors.
• Lead engineer: sets a product's technical direction and chairs its design reviews.
• Principal engineer: shapes architecture across products and speaks for the firm technically with customers.
• Engineering manager: a separate track for those who want to lead people, with its own training.

Write down what each level owns and how promotion is decided. Without that, promotion means managing people, which many engineers never wanted.

1. 1

   Thirty minutes, every quarter

   The engineering head or founder meets each engineer. Keep appraisal topics out of it and talk about the work and the future.

2. 2

   Ask about the next six months

   Which product would you like next? Which tool or chip do you want to learn? What is grinding you down?

3. 3

   Agree one action

   A project choice, a course or a change in escalation duty, written down with a date.

4. 4

   Open the next talk with it

   Each new conversation starts with last quarter's promise: done, late or dropped?

Sometimes, if your benchmark shows a real gap and pay is the engineer's main reason. If the reason is project interest or growth, a match buys months rather than years. Ask before deciding. Remember too that every match quietly resets expectations across the team.

Often more than a product company can. Customer work brings fresh chips, sensors and puzzles. The danger is that strong engineers always land on the most urgent project rather than the most interesting one. Make allocation a planned decision and let engineers state a preference.

Bring-up and hardware debugging need the bench, but code reviews, documentation and design work can often happen at home. A clear pattern, such as lab days for bring-up and flexible days otherwise, is valued by many engineers. Agree it project by project rather than as a blanket rule.

Few small firms can. Close the gaps that are large, then compete where you are stronger. A product company may keep an engineer on one codebase for years; you can offer three chip families in two years. You can put an engineer in front of the customer's chief engineer, which a large firm rarely allows a junior. You can decide quickly. Say all of this out loud, because engineers do not always notice it unprompted.

Set up an escalation rota so one engineer each week handles customer fires, with the others left to finish roadmap work. Pair a junior with the rota engineer to spread the debugging skill. Log every escalation, and after a quarter look for recurring faults that a fix in the design or the test jig would remove for good.

Our page on keeping engineers at design-led embedded firms goes further, and why your strongest people get the most calls explains the poaching pressure.