Roles by discipline
Firmware roles where the hardware is still moving
There is a version of this job where the board is final and you write the code that makes it a product, and a version where the board changes every month and you write the code that finds out why it broke. Both are called embedded engineer. Both list the same microcontroller. What separates them is whether the hardware team has frozen a revision, whether the bench has the equipment to see the fault, and whether firmware gets a say in the next board. None of that is in the ad, so we ask.
What we ask before we post one
The questions the ad never answers.
- Which board revision is in the field, which is on the bench, and who decides when one is frozen?
- What does the test bench have, and what did the team wish it had during the last hard bug?
- Is there a hardware abstraction layer, or does every board bring a rewrite?
- How does firmware get a requirement into the next board, and when did that last happen?
- What is the release path from a build on your machine to a device in the field?
- Which part of the codebase does nobody want to touch?
What we will not post
We do not post a firmware role that hides the days on site behind the word hybrid.
Hardware roles here are on site or hybrid. The ad says which, and how many days.
For hiring teams
Hiring for this discipline?
We work through the role and hiring criteria with your team as part of embedded recruitment. Talk to Jonathan about what you need to hire.