Roles by discipline
Electronics roles where you find out who owns the schematic
An electronics engineer inherits a schematic the way a backend engineer inherits an architecture. Somebody chose the power tree, picked the parts that are now on allocation, and decided how many layers the board would have. What makes the job worth doing is not the board. It is whether you can change it, how many spins the budget allows, and whether the person who has to approve the change still works there. A component list answers none of that, so we ask.
What we ask before we post one
The questions the ad never answers.
- How many board spins did the last product take, and how many were planned?
- Who reviews a schematic before it goes to layout, and who can say no?
- Which parts are on allocation, and who owns the second-source decision?
- What EDA tooling is in use, and is layout done in house or outside?
- What compliance testing is required, and where was the last failure?
- Which board does nobody want to open?
What we will not post
We do not post an electronics role that wants analog, digital, firmware and layout from a single person and calls it senior.
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.