01
Bench time is normal
Measurement is part of design, not a separate verification phase someone else performs.
T · [CLIENT TO PROVIDE] E · [CLIENT TO PROVIDE]
The work
Engineers here follow a product rather than a ticket. The person who chose the regulator is usually in the room when the rail misbehaves at temperature, and the person who wrote the driver is the one reading the scope trace.
That has a cost: you cannot hide behind a discipline boundary. It also has a reward, which is that you find out whether your decisions were right, on real hardware, while you can still do something about it.
Practice
The habits that shape how a working week actually looks.
01
Measurement is part of design, not a separate verification phase someone else performs.
02
Designs are reviewed against constraints and evidence, not against opinion or seniority.
03
Design intent, test procedures and handover documentation are written by the engineers who did the work.
04
A problem raised in week two is engineering. The same problem raised in week twelve is a programme risk.
05
We do not force a toolchain onto a programme that would be better served by another.
06
Buildability is considered by the whole team, not delegated to whoever runs the handover.
Development
Progression is about the range of decisions you are trusted with, not a title on an org chart.
Become genuinely reliable in one discipline, with evidence behind your judgements.
Work on the other side of the hardware–software join until you can predict it.
Carry a part of a product from requirement to validated behaviour.
Hold the architecture, the constraints and the client relationship for a whole product.
Bring new engineers into the practice and keep the standard of evidence high.
Disciplines
Roles are described by the engineering, not by a ladder position.
Analog and digital circuit design, power conversion, board architecture and bring-up.
Stack-up, placement, routing, signal and power integrity, manufacturing data.
Drivers, RTOS and Linux platforms, communication stacks, bootloaders and updates.
Verification strategy, environmental and reliability testing, production test design.
Tell us what you have designed, what went wrong and what you did about it. That is more useful to us than a list of tools.