Prep
A maintenance interview is mostly one question asked four ways: can you reason about a machine, and can you say so out loud. This page works from what you already have — the faults in your log, the reasoning the missions teach, and an honest account of what you can use.
Questions technicians actually get asked. There is no model answer here — a good answer is your fault, in your words. What you get instead is what the question is really testing, and which threads your draft has not touched yet.
What they are actually testing
Whether you reason or whether you swap parts until it stops. Almost nobody is testing whether you knew the answer — they are testing whether you can explain how you got there, in order, and whether the order was sensible.
What they are actually testing
Whether you can operate across a boundary you do not own. In a plant, the fault is very often not in the equipment you are responsible for, and the interviewer wants to know what you do when the fix belongs to somebody else.
What they are actually testing
Partly a real inventory check, mostly a check on whether you can talk about your own capability without either undereselling or bluffing. People blank on this question and give a list of hand tools.
What they are actually testing
Honesty, and whether you have a working feedback loop. Everyone has been wrong. The technicians worth hiring can say what the wrong call cost and what they changed because of it.
What they are actually testing
Whether you can hold a technical line under commercial pressure without being obstructive. Both failure modes get people rejected: the technician who folds, and the one who cannot work with production at all.
What they are actually testing
Method under uncertainty. There is no equipment knowledge to fall back on, so the answer is entirely about process — which is exactly why it is asked.