Ask a solar inverter maker why a gate-driver was changed on the last model, and you often get a name, not an answer. Ask the senior hardware man. Ask the firmware-lead. Ask whoever drew the board. When that person resigns, the reason leaves with him. The next model then carries a risk nobody can see, and the first sign of it is a bad batch.
That is the leading strain listed on our inverter makers page. Below: how the know-how ends up with two or three people, what an exit costs the bench, and the habits that get it written down and shared with a second engineer. For neighbouring trades, see the wider hub for renewables hardware.
What sits in those heads
- Why a schematic uses one MOSFET or IGBT over another, and what failed when a cheaper part was tried.
- How the MPPT tracking behaves on a cloudy-morning, and which firmware lines were tuned for it.
- Which magnetics vendor delivers consistent inductors and which batch needs a second check.
- How heat-sink sizing and derating decisions were reached, and what a field-return taught the team.
- Which test-jig step catches a marginal board and which only looks thorough.
None of it is hidden on purpose. It was never written, because the engineers were busy shipping the next model.
How the risk shows up on the floor
The technicians at the bench see it first. A new board-revision arrives with no release-notes. A fault in burn-in has no known cause. A service-engineer on the phone with a customer cannot find the change-log. The bench stops, the technician looks for the one engineer, and that engineer is in a design-review or on leave.
The loss shows later too. A new hire in firmware needs months to learn the codebase. A rival offers the lead engineer a better title. A bench-technician who was shown a trick by one engineer carries a skill that is gone when he moves on.
Seven habits that move the knowledge
- 1
Keep a change-log for every board and firmware release
One line per change: what, why, who and which unit it was tested on. The engineer owns it, but a technician reads it at the bench.
- 2
Hold a design-review with a second-engineer present
Even a small one. The second-engineer asks why, and the answer gets written down.
- 3
Write release-notes in plain language
A bench-technician or a service-engineer should understand them. If they cannot, the notes are not done.
- 4
Pair each key engineer with a shadow
One designer per shadow. The shadow sits in reviews, reads the schematic and takes a small change end to end.
- 5
Run a monthly field-failure session
Service brings the returns. Engineers explain the cause. Technicians say what they saw on the bench. Write the lesson on one page.
- 6
Rotate test-jig ownership
A technician owns each jig for a quarter and documents what it catches. The owner trains the next.
- 7
Reward the writing
Count change-logs and shadow sign-offs in the review. If nobody is credited for writing it down, nobody will.
Pay and retention for a small, wanted group
Design-engineers are courted by firms that pay more and offer larger scope. A raise alone does not hold them. Offer a visible technical ladder: engineer, senior engineer, principal, each with its own pay band and a written list of what is expected. Offer ownership of a model-line. Our succession planning notes for inverter makers show how to name a successor without frightening the incumbent. Our engineer pay comparison lines the bands up against nearby firms.
Hiring with the gap in mind
If your firmware-lead is the only one, your next hire is not a general engineer. It is a person who can read his code, challenge his choices and learn the product line. Write the role around that, with a first-ninety-day task: take over a named release, with the lead as reviewer. The recruitment process notes for inverter makers cover how to structure the interview.
What to track
- Releases in the last quarter with a complete change-log.
- Reviews held with a second-engineer present.
- Shadows and the models each can now take on.
- Service returns reviewed and written up.
A note on bench and service staff
Technicians and service engineers hold knowledge of their own. The senior bench-technician knows which board lots solder badly and which capacitor lots run warm in burn-in. The service-engineer knows which site installs trip on grid spikes. Ask each of them to keep a short fault-log in a shared notebook, with the serial, the symptom and the fix. Engineers then have field evidence at the monthly session, not hearsay. The log also becomes a training aid for the next hire.
A first month
Pick the latest model. Ask the engineers to write a one-page change-log for the last three revisions. Seat a second-engineer at the next design-review. Name one shadow. To work out the first habits with us, describe your team in the requirements wizard.
