Internal Interview Questions for a Senior Technician Promotion

Senior technician is the promotion companies most often get wrong in the same direction: they promote the person with the deepest technical skill and are surprised when the team gets no better.

The role is not "the best technician with a new title." It is the person whose judgment other people rely on, who teaches what they know rather than hoarding it, and who can push back on a timeline or a diagnosis without being difficult about it. Deep skill is the entry requirement, not the differentiator.

So the interview tests three things: whether they can transfer what they know, whether they will say no to an unrealistic commitment, and whether their judgment holds when the diagnosis is uncertain.

1. "A junior tech misdiagnosed something and you caught it. Walk me through what you say to them."

Strong: asks how they reached the diagnosis before correcting, so the correction lands on the reasoning rather than the answer.
Weak: just gives the right answer, or fixes it themselves without telling the junior tech. The second one is common and it guarantees the same error recurs.

2. "You are asked to commit to a timeline you think is unrealistic. What do you do?"

Strong: says so directly, offers what is achievable, and makes the tradeoff visible rather than silently absorbing it.
Weak: agrees and plans to explain later. This is the single most expensive habit in a senior technical role.

3. "You do not know what is causing a problem. What do you do next?"

Strong: describes a structured narrowing process and a point at which they escalate or bring in help.
Weak: describes persistence without method, or never escalating. Both burn hours.

4. "How would you get someone on the team to the point where they could handle what only you can handle now?"

Strong: a specific approach involving graduated exposure and being available rather than doing it for them.
Weak: vague willingness to help if asked. Or reluctance, which usually signals the person sees their expertise as their job security.

5. "A customer or another department is pushing for a shortcut you think is a bad idea. What do you say?"

Strong: explains the consequence in their language, offers the real alternative, and escalates if overruled on something that matters.
Weak: does it under protest, or refuses without explaining why in terms the other person can act on.

6. "Tell me about a call you got wrong."

Strong: a real example, what they learned, and what they changed. Comfortable being wrong in front of you.
Weak: cannot produce one, or produces one where the real cause was someone else.

7. "What would you standardize, and what should stay to individual judgment?"

Strong: distinguishes the two sensibly and has an opinion about where the current gaps are.
Weak: wants everything documented, or nothing. Both suggest they have not thought about the team as a system.

8. "You will still be carrying your own workload. How do you make time to help others?"

Strong: acknowledges the tension honestly and has a concrete answer, usually about protecting specific time or accepting reduced personal throughput.
Weak: says it will not be a problem. It always is, and the ones who say this are the ones who quietly stop helping in month two.

• Knowledge transfer. Do they teach the reasoning or hand over the answer. Questions 1 and 4.
• Willingness to push back. Will they say a timeline is wrong before agreeing to it. Questions 2 and 5.
• Method under uncertainty. Structured narrowing, and a point where they get help. Question 3.
• Comfort being wrong. Question 6. A senior tech who cannot be wrong in front of you cannot be corrected by anyone.
• Systems thinking. Do they see the team's capability as part of their job. Questions 7 and 8.

Knowledge transfer is the dimension that justifies the promotion existing at all. If the strongest candidate scores low there, you are paying a premium for the same output you already had.

Technical candidates frequently assume this interview will be a technical assessment, and prepare accordingly. Tell them explicitly that technical depth is assumed and the interview is about judgment, teaching, and communication. Otherwise you will get a candidate who prepared for the wrong test and you will read that as a weak performance.

Give every candidate the competencies, the format, and a week. Then run the same questions in the same order.

This runner-up conversation carries a particular risk: a technically excellent person who does not get a senior title often concludes the company does not value technical skill, and technically excellent people have options.

Be explicit that the technical bar was met, and name the actual gap. "Your diagnostic work is the strongest on the team and that was not in question. The gap was on knowledge transfer, specifically the answer about bringing someone else up to your level." Then give the condition and the date, and give them something real to practice on, like owning the onboarding of the next hire.

If your company has no senior individual-contributor path that is distinct from a leadership path, this conversation is the moment you will discover that gap. Worth thinking about before you are in the room.