HVAC Interview Questions to Ask Candidates (by Role, With What Good Answers Sound Like)

For contractors hiring technicians. If you are a technician preparing for an interview, this page will still be useful to you, but it is written from the other side of the table.

The problem with most HVAC interview question lists is that they are lists. Twenty-five questions with no indication of what you are listening for turns the interview into a formality, because every candidate has a rehearsed answer and you have no basis for telling a good one from a fluent one.

The format below gives you, for each question, why you are asking it, what a strong answer contains, and what a memorized answer sounds like. Use the ones that match the role you are filling.

First: decide what you're hiring for

A residential service tech, an install tech, and a maintenance tech fail in different ways. Screening all three with the same questions means you are optimizing for a generic technician who does not exist.

Before the interview, pick the role and pick six to eight questions from the relevant sections below. More than that and you run out of time for the candidate to ask you anything, which is its own signal.

Diagnostic questions

“Walk me through a call where the obvious answer turned out to be wrong.”

Why you're asking: Real diagnostic experience produces this story. Every working tech has one.
What a strong answer contains: Specific system, specific initial read, specific reason they doubted it, what they checked next. The doubt is the part you are listening for.
What a memorized answer sounds like: A general statement about being thorough, with no actual call attached.

“You gauge up and suction pressure is low with high superheat. What do you check next?”

Why you're asking: Tests whether they narrow before acting.
What a strong answer contains: Subcooling, and why. 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. Bonus for feeling the liquid line for a temperature drop or looking for frost at the drier. Strong bonus for noting that on a TXV system subcooling is the primary charge indicator anyway, since the valve controls superheat, and that a restriction downstream of the valve can present with normal superheat because the valve compensates.
What a memorized answer sounds like: “Add refrigerant.” Not wrong about the most common cause, and it is also the answer that puts a plugged drier back in service. Also weak: reaching for a dirty filter, since low airflow pulls superheat down rather than up.

“How do you decide whether a compressor has actually failed?”

Why you're asking: Compressor calls are high-dollar and a wrong condemnation is expensive in both directions.
What a strong answer contains: Electrical checks before mechanical conclusions. Confirming power and controls are delivering what they should, checking windings, checking the capacitor and contactor, ruling out what upstream conditions might be causing the symptom.
What a memorized answer sounds like: Jumps to “it's locked up” from the symptom alone.

“A customer says their system was fixed last week by someone else and it's doing the same thing. How do you handle that call?”

Why you're asking: Tests diagnostic humility and customer judgment together.
What a strong answer contains: Verifies the original complaint independently rather than assuming either the previous tech was wrong or right. Explains the finding without trashing the other technician.
What a memorized answer sounds like: Immediate criticism of the previous work. Techs who do this in an interview do it in customers' homes.

“Tell me about a call you couldn't solve.”

Why you're asking: The most useful question in the set. Candidates who claim they solve everything are either inexperienced or not being straight with you.
What a strong answer contains: A specific job, what they tried, what they did next, whether they escalated. Escalating well is a skill.
What a memorized answer sounds like: “I've always figured it out eventually.”

Electrical and controls

“Walk me through how you'd isolate a no-cool call where the outdoor unit isn't running.”

What a strong answer contains: A sequence, not a list of parts. Confirming the call for cooling is getting there, then working from the thermostat through the control circuit, checking the transformer, contactor, and capacitor, then confirming power at the unit.
What a memorized answer sounds like: “Check the capacitor.” It is the most common cause, which is exactly why it produces parts-swappers.

“How comfortable are you reading a wiring diagram on equipment you've never seen?”

What a strong answer contains: Comfortable, with a description of how they orient themselves on unfamiliar equipment. Sequence of operation first.
What a memorized answer sounds like: Confidence with nothing behind it. Follow up by asking them to describe the last unfamiliar unit they worked on.

Airflow

“When do you check static pressure?”

Why you're asking: Separates techs who confirm airflow from techs who condemn components.
What a strong answer contains: Routinely on diagnostic calls, and specifically before concluding a refrigeration problem. A good candidate will connect airflow problems to symptoms they have chased.
What a memorized answer sounds like: “When the customer complains about airflow.” That is the answer that generates comebacks.

Safety and code

“Tell me about a time you had to stop work for a safety reason.”

What a strong answer contains: A specific situation and what they did, including how they explained it to the customer or the office. Bonus for a story where stopping cost money.
What a memorized answer sounds like: Generic safety commitment with no instance.

“What's your process before you work on anything energized?”

What a strong answer contains: Lockout/tagout described as practice, not policy. Verifying de-energization rather than assuming.
What a memorized answer sounds like: Recites a policy without describing what they actually do.

“What do you do if you find a gas leak or a cracked heat exchanger and the customer doesn't want to deal with it?”

Why you're asking: This is a values question wearing technical clothes.
What a strong answer contains: Documents it, communicates the hazard plainly, follows the shop's red-tag procedure, does not let the customer's preference override the safety call.
What a memorized answer sounds like: Anything that ends with leaving it running because the customer asked.

Customer-facing judgment

“How do you explain a repair-versus-replace decision to a customer?”

Why you're asking: Most service tech hires that fail, fail here rather than on refrigeration.
What a strong answer contains: Presents the actual condition and the options with real numbers, gives the customer the information to decide, has a view but does not manufacture urgency.
What a memorized answer sounds like: Either a sales pitch or an abdication. “I just tell them what's wrong and let the office handle it” is a tech who will not sell, which may be fine depending on your model.

“A customer is upset before you've said a word. What do you do?”

What a strong answer contains: Lets them finish, does not defend the company reflexively, separates the emotional problem from the technical one.
What a memorized answer sounds like: Anything that starts with explaining why the customer is wrong.

The interview tells you how they talk. This tells you what they know.

Pair the conversation with a role-specific HVAC assessment scored the same way for every applicant. Free trial, no card required.

Start Free Trial

Questions about their last shop

“Why are you leaving?” and “What would have kept you?” The second question is the one people forget to ask, and it is more revealing than the first. It tells you what this technician actually needs, and whether you can provide it.

“Describe how your last shop dispatched you.”

Why you're asking: Reveals what they are used to and whether your operation will feel like a downgrade to them. A tech coming from a well-run dispatch operation into a chaotic one leaves within a year.

“What's the ratio of your work that was maintenance versus service versus install?”

Why you're asking: Resumes flatten this. The answer often reveals the candidate is applying for a role they have not actually done.

Questions worth skipping

“Where do you see yourself in five years?” In a trade with this much mobility, the honest answer is unknowable and the rehearsed answer is worthless.

“What's your greatest weakness?” You will get a prepared answer. The “tell me about a call you couldn't solve” question above gets you the real version.

Pure definition questions. “What is superheat” tells you a candidate watched a video last night. Ask them to use it instead.

What the interview can't tell you

Interviews measure how well someone talks about their work. That correlates with skill, and it correlates more with confidence and communication, which is why articulate mediocre technicians interview well and quiet excellent ones interview badly.

The fix is not a better interview. It is pairing the interview with something that measures capability directly, whether that is a ride-along, a hands-on test, or a structured skills assessment. Use the interview for judgment, communication, and fit, and use something else for whether they can actually diagnose. While you are at it, verify their EPA 608 certification rather than taking the card at face value.

Free interview scorecard

A one-page scorecard with these questions grouped by role and space to rate each answer. Print it or save it as a PDF from your browser. No email required.

Open the scorecard

Frequently asked questions

How many questions should I ask?

Six to eight technical questions plus the last-shop questions fits a 45-minute interview and leaves the candidate time to ask you things. What they ask you is a data point.

Should I ask the same questions of every candidate?

For a given role, yes. Consistency is what makes candidates comparable, and it matters for defensibility if a hiring decision is ever challenged.

Should the technical interview be done by a technician?

If you can. A service manager or lead tech will hear the difference between a real answer and a fluent one in a way a recruiter cannot.

What if a candidate doesn't know an answer?

How they handle it is the answer. "I don't know, here's how I'd find out" is a stronger response than a confident guess, and it predicts field behavior directly.

HVAC Interview Questions to Ask Candidates