Interview questions for HVAC technicians: 18 questions and what to listen for

What should you ask when interviewing an HVAC technician?

Ask questions that force the candidate to narrate real work: how they diagnose, what they do when they're stuck, how they handle an angry homeowner, and what they did after their last callback. Certifications and years are on the resume already; the interview is for what a resume can't show — reasoning, honesty, and how they'll represent your company in someone's kitchen. Below are 18 questions grouped by what they test, with what a good answer sounds like and what should worry you.

A bad hire in a truck is expensive — SHRM puts average cost per hire around $4,700, and replacing a departed employee runs 90–200% of salary all-in. We break that down in the cost of a bad hire in the trades. The hour you spend interviewing well is the cheapest quality control you'll ever buy.

Technical skill

1. "Walk me through the last diagnostic you were genuinely proud of."

Good answer: A specific story with a system, a symptom, and a sequence — "intermittent no-cool, two techs had already replaced the capacitor, I found a chafed low-voltage wire shorting on the cabinet edge." Pride in finding root cause, not in swapping parts.

Red flag: Nothing comes to mind, or the story is about a big install rather than a diagnosis. A service tech with no diagnostic war story hasn't been doing much diagnosing.

2. "What do your gauge readings and superheat/subcooling numbers actually tell you about a system?"

Good answer: They connect numbers to conditions — low subcooling suggesting undercharge, high superheat pointing to restriction — and they check airflow before touching refrigerant.

Red flag: "I just top it off until the pressures look right." That tech fixes symptoms by adding refrigerant: bad practice, and done carelessly, a legal problem.

3. "Which systems are you weakest on?"

Good answer: A real answer — "I've barely touched boilers" or "mini-split inverter boards still slow me down" — plus what they do about it. Honesty here predicts honesty on a job site.

Red flag: "I can fix anything." Nobody can, and a tech who won't admit a gap in an interview won't admit one in a customer's attic. The most predictive question on the list.

4. "What certifications do you hold, and when did you get your EPA 608?"

Good answer: Straightforward: 608 Universal (or Type II for residential), maybe NATE, and they can tell you when and where. Verify the card — it's required by federal law for refrigerant work, not a nice-to-have.

Red flag: Vagueness about whether the 608 is current or "in progress" from someone claiming years of service experience.

Diagnostic reasoning

5. "A homeowner says the AC is short-cycling. Walk me through your first ten minutes on site."

Good answer: An ordered process that starts simple: talk to the homeowner, check the thermostat and filter, then air handler, coil, condenser. Cheap and likely causes first.

Red flag: Jumping straight to "probably the board" or "needs refrigerant." Guessing a part before gathering evidence is how callbacks happen.

6. "You've checked everything you know to check and the system still isn't right. What now?"

Good answer: Re-read the symptoms, consult the manual or tech support line, call a senior tech, and be straight with the customer about needing more time. Knowing when to ask for help is a skill.

Red flag: "That doesn't really happen to me," or worse, replacing parts until something works — on the customer's dime.

7. "Tell me about a callback that was your fault. What did you change afterward?"

Good answer: They own one, specifically, and describe the process change — "I missed a failing contactor because I didn't check it under load; now it's on my checklist every call."

Red flag: "I don't really get callbacks." Every working tech has caused one. This answer means they hide mistakes or don't track them, and both are worse than the mistake.

8. "Two plausible causes, one expensive and one cheap. How do you decide what to tell the homeowner?"

Good answer: Test until the evidence separates them; if genuine uncertainty remains, present both honestly with the cheap fix first. The diagnosis is something to prove, not to sell.

Red flag: Defaulting to the expensive fix "to be safe," or whatever maximizes the ticket. You're hearing how they'll treat your customers when nobody's watching.

Customer-facing judgment

9. "A homeowner is angry before you even open your bag — the last visit didn't fix it. What do you do?"

Good answer: Let them vent, stay off the defensive, don't throw the previous tech under the bus, then redirect: "let me start fresh and find out what's actually going on." Calm is the skill being tested.

Red flag: Arguing the customer down, or eagerly agreeing that the last guy (maybe your other employee) botched it.

10. "How do you explain a $2,000 repair to someone who expected a $200 one?"

Good answer: Show, don't lecture — photos of the failed part, plain language, real options including repair vs. replace, no pressure. They understand trust closes more work than pressure does.

Red flag: Scripted closing tactics, or visible contempt for customers who "don't get it." That contempt leaks into every kitchen conversation.

11. "A customer asks you to do something off-book — skip the permit, bypass a safety, 'just make it work for the summer.' What do you say?"

Good answer: A polite, firm no with an explanation of why the safety exists, plus an offer of the legitimate options. Bonus points if they'd flag it to the office.

Red flag: Any hedging. A tech who'll bypass a safety to please a customer is a liability you're insuring.

12. "What do you do in the truck before you ring the doorbell?"

Good answer: Anything intentional — review the call notes and service history, check for likely parts, straighten up. Small answer, big signal about professionalism.

Red flag: A blank look. Not disqualifying alone, but it usually travels with sloppy paperwork and sloppy trucks.

Reliability and work habits

13. "Why are you leaving your current shop, and why did you leave the one before that?"

Good answer: Concrete, non-bitter reasons — pay ceiling, all-installs when they want service, an hour commute. Speaking respectfully about a shop they're leaving is how they'll one day speak about yours.

Red flag: Every previous employer was terrible, or the story keeps shifting. Short stints with vague exits is the pattern to probe hardest; it's the pattern that makes turnover so expensive on your side of the table.

14. "How do you feel about on-call rotations, honestly?"

Good answer: Honest ambivalence plus professionalism: "nobody loves 2am calls, but it's part of service work — I just want a fair rotation and real on-call pay." State your actual rotation plainly here too.

Red flag: Either "I love it!" (they don't) or visible resentment at the concept. Mismatched on-call expectations are a top quiet reason service techs quit at month three.

15. "Tell me about a time you were running late or double-booked. What did you do?"

Good answer: They communicated early — called dispatch, called the customer, reset expectations — rather than going dark and hoping. Reliability isn't never slipping; it's what they do when they slip.

Red flag: "I'm never late." See question 7.

16. "What does your truck look like at the end of a week?"

Good answer: Sheepish honesty is fine, but there's a system: restock day, organized bins, tools accounted for. The truck is a proxy for how they'll treat everything you issue them.

Red flag: Treating the question as beneath them.

Culture and fit

17. "What would make this job a place you stay five years, not eighteen months?"

Good answer: Specifics you can act on — a path to lead tech, paid training, fair dispatching, a boss who backs their techs. This question screens them and tells you exactly how to retain them if you hire them.

Red flag: "Just a paycheck." Fine as a fragment, worrying as the whole answer — that tech leaves for fifty cents an hour.

18. "What questions do you have for me?"

Good answer: Real ones: how calls get dispatched, what the callback policy is, who pays for training, what happened to the last tech in this seat. A candidate interviewing you back is a candidate taking the decision seriously.

Red flag: None at all — often a sign they're collecting offers, not choosing a shop.

How to actually run this interview

Don't ask all 18. Pick ten or so across the five groups, ask them the same way every time so you can compare candidates, and spend the saved time following up on the stories — "what happened next?" is the best interview question ever written. Write your notes down within the hour, before the answers blur.

Two more things matter as much as the questions. First, speed: in a market with about 40,100 HVAC openings a year and 8% projected growth through 2034, good techs are interviewing at multiple shops, and the one that moves first usually wins — the logic of speed to lead in recruiting. Interview within days of application, not weeks. Second, the interview starts before the interview: if the posting didn't attract the right candidates, no question list saves the conversation. Fix the top of the funnel with our HVAC technician job description template, and see how to hire HVAC technicians for the whole process in order.

This is roughly the playbook we run at HireAligned for our HVAC and plumbing customers — a screening guide per role with the listen-fors written down, phone screens before candidates reach the owner, and a pre-screened bench so the next opening doesn't start from zero. If you'd rather have that handled, here's how done-for-you works.