Power systems: You have personally designed a multi-rail battery-powered architecture — not reviewed someone else's. You can size a protection circuit, choose a regulator topology for a given load profile, and explain the inrush and brownout behavior you encountered on first power-on. You can read a schematic and find a problem.
Sensor synchronization: You have solved the problem of aligning data from multiple sensors with mismatched sample rates and variable bus latencies. You know what a time-stamping strategy looks like at the firmware level, and you know what misalignment actually looks like in a captured dataset — not in theory, in your own data.
Firmware and embedded Linux: You have personally brought up a SoM or SBC platform under real workload. You can read and follow firmware written by someone else well enough to identify a timing bug, interrupt priority issue, or buffer overrun using a logic analyzer or serial log. You do not need to write production firmware, but you must be able to debug it.
Mechanical judgment: You will not own CAD in this role, but you must review, critique, and push back on mechanical designs with engineering justification. You understand load paths, tolerance stack-up, strain relief, and what "designed for the lab" looks like vs. designed for a person wearing it for eight hours.
- You have shipped at least one hardware product from first prototype to real users. "Shipped" means it was used by someone who was not an engineer
- You have operated as a staff, principal, or founding engineer — not solely as an engineering manager
- You have worked with distributed teams across time zones and can maintain engineering quality without being in the room every day
- 6-10+ years of hardware engineering experience with a track record in wearable hardware, robotics, motion capture, or field-deployed devices