This page is written for the technician going into the interview. We also publish the version written for employers, which lays out what a service manager is told to listen for. Reading both is not cheating. It is preparation.
The useful thing to understand before any of the specific questions: a technical interview is not testing whether you know the answer. It is testing whether you narrow before you act. Service managers have all hired the tech who replaces parts until the symptom goes away, and most of them are screening for that specifically.
Which means the structure of your answer matters as much as its content.
The pattern that makes an answer land
Almost every diagnostic question has the same strong shape:
- What you would check first, and why that check. The “why” is the part most people skip and the part being graded.
- What each result would tell you. This is where you show you are narrowing rather than guessing.
- What you would do about it.
Compare these two answers to the same question.
“I'd check the subcooling.”
“I'd check subcooling, because low suction with high superheat tells me the evaporator's starved but not why. If subcooling's low too, I'm looking at an undercharge. If subcooling's high, refrigerant's stacking up in the condenser and I've got a restriction, so I'd feel down the liquid line for a temperature drop and check the drier.”
Same knowledge. The second one gets the job.
Diagnostic questions
“Walk me through a call where the obvious answer turned out to be wrong.”
Have this story ready before you walk in. It comes up constantly and improvising it goes badly.
What makes it work: a specific system, what you initially thought, the thing that made you doubt it, and what you found. The doubt is the whole point of the question. Pick a call where you almost got it wrong and caught it.
“You gauge up, suction pressure is low and superheat is high. What next?”
Go to subcooling, and say why, as in the example above. Low subcooling with high superheat points toward undercharge. High subcooling with high superheat points toward a restriction, because liquid stacks up in the condenser and cools further than it should: a plugged drier, a restricted liquid line, an underfeeding TXV.
Two things that will put you above most candidates. On a TXV system, superheat is a weak charge indicator in the first place because the valve exists to control superheat, which makes subcooling the primary measurement there. And a restriction downstream of the valve, at the distributor or a feeder tube, can show normal superheat because the valve compensates, so a normal reading does not clear a restriction.
The answer to avoid: “I'd add refrigerant.” It is the most common cause and it is also how you hand back a system with a plugged drier and get the callback.
Also avoid reaching for a dirty filter. Low airflow pulls superheat down, not up, and jumping there shows you read one number instead of two.
“How do you decide a compressor is actually bad?”
Electrical before mechanical. Confirm the controls and power are delivering what they should, check windings, check capacitor and contactor, rule out upstream causes. Condemning a compressor from the symptom alone is expensive in both directions and interviewers know it.
“Tell me about a call you couldn't solve.”
Do not say it has never happened. Every experienced tech has one, and claiming otherwise reads as either inexperience or evasion.
Give the specific job, what you tried, and how you escalated. Escalating well is a skill and managers are listening for it. The answer that works: here is where I got stuck, here is who I called, here is what I learned from how it got solved.
Electrical questions
“Walk me through a no-cool call where the condenser isn't running.”
Give a sequence, not a part. Confirm the call for cooling is arriving, work from the thermostat through the control circuit, transformer, contactor, capacitor, then confirm power at the unit.
Saying “check the capacitor” first is technically the highest-probability answer and it is exactly what a parts-swapper says. Mention it inside a sequence instead of in place of one.
“How are you on equipment you've never seen?”
The answer that works is a method: sequence of operation first, then the diagram. Then name the last unfamiliar unit you worked on. Confidence with a concrete example behind it is worth far more than confidence alone.
Airflow
“When do you check static pressure?”
Say: routinely on diagnostics, and specifically before concluding anything is wrong with the refrigeration side. Then connect it to something you have actually chased.
This question exists to separate techs who confirm airflow from techs who condemn components. “When the customer complains about airflow” is the wrong answer.
Safety
“Tell me about a time you stopped work for a safety reason.”
Have one ready, and pick one where stopping cost money or time. That is what makes it credible.
“What do you do if you find a cracked heat exchanger and the customer doesn't want to deal with it?”
This is a values question dressed as a technical one. Document it, explain the hazard plainly, follow the red-tag procedure. Any answer ending with leaving it running because the customer asked is disqualifying at most shops, and should be.
Customer questions
“How do you handle repair versus replace?”
Most service tech hires fail here rather than on refrigeration, which means this question carries more weight than its position in the interview suggests.
Show that you give the customer real information and real options, that you have a recommendation, and that you do not manufacture urgency. Know which kind of shop you are interviewing at: some want a tech who sells, some want a tech who diagnoses and hands it to the office. Ask which, if it is not clear. Asking is a good look.
“A customer is already angry when you arrive.”
Let them finish, do not defend the company reflexively, separate the emotional problem from the technical one. Do not start by explaining why they are wrong.
Questions to ask them
You will be asked if you have questions. Having none is a bad signal, and generic ones are nearly as bad. These are real and they tell you something:
- How are calls dispatched, and who decides what I get?
- What is the callback rate, and how is it handled when it is mine?
- Who do I call when I'm stuck at 6pm?
- What does the truck stock look like, and how fast do I get a part I don't have?
- How does pay work on a call where the right answer is a cheap repair?
That last one tells you more about the shop than anything on the job posting.
What interviews cannot tell them
Here is the honest limit of all of this: an interview measures how well you talk about the work. If you are a strong tech who is quiet, or if you get nervous, the interview underrates you, and there is not much advice that fixes that.
That is the actual reason skills assessments exist, and why more shops are using them. A score is a way for a good technician who interviews badly to get a fair read.
See where you land before anyone asks.
Free, 10 to 15 minutes, and the breakdown tells you which of the areas above is your weak one. The shop you work for never sees it, and hiring employers only see you if you turn that on yourself.
Take the free assessmentIt also puts you in the network we are building, the largest network of verified skilled technicians in the trades. Job opportunities get posted to it over time, and the techs who are scored early are the ones in it when they do. If you are also working on certification, start with EPA 608 prep.
Frequently asked questions
What should I bring to an HVAC interview?
Your 608 card and any other certifications, a list of equipment you have worked on, and two stories: the call you almost got wrong, and the one you could not solve.
Should I admit I don't know something?
Yes. "I don't know, here's how I'd find out" is a stronger answer than a confident guess, and experienced interviewers specifically listen for it. The guess is what gets you screened out.
How technical does it actually get?
Depends who is in the room. If a service manager or lead tech is interviewing, expect real diagnostic questions. If it is an owner or a recruiter, expect more about reliability and customer handling.
They want me to do a ride-along. Is that normal?
Yes, and it is usually a good sign. It also means the technical evaluation is happening in the truck rather than in the room, so the interview itself may be lighter than you prepared for.
Raising the bar for the trades.