Interview questions and skills tests for technicians

Why structure beats a good conversation

Most technician interviews are a friendly chat in the shop followed by a gut decision. Friendly chats reward candidates who talk well, not techs who fix things well, and they make it hard to compare people fairly. A structured interview uses the same questions, the same skills test and the same scoring sheet for every candidate at the same level. It takes no longer than a chat, and it produces notes you can compare weeks later when the owner asks why one candidate got the job.

The cost of a bad hire is high in service work. A tech who misdiagnoses, upsets customers or skips safety steps costs callbacks, refunds and reviews before you even notice. Customers are already struggling to find good help: on average 53% of surveyed US homeowners reported difficulty finding pros in 2025, and 70% of millennial homeowners did^[5]. Each good hire protects the reputation that brings those customers to you.

Build the interview in three parts

1. 01

   Phone screen (10 minutes)

   Confirm pay range, schedule, on-call, driver’s license and required credentials. Ask one troubleshooting question to hear how they think.

2. 02

   Structured interview (30 to 45 minutes)

   Behavioral and technical questions, the same for every candidate at this level, scored right after.

3. 03

   Hands-on skills test (30 to 60 minutes)

   A set task on a training board or unit in the shop, scored on a checklist. For longer working interviews on real jobs, pay the candidate.

Behavioral questions

Behavioral questions ask about real past situations. They reveal how a tech handles customers, mistakes and pressure, which matters as much as technical skill. Ask for a specific example and follow up with "what did you do next?" until you have the full story.

1. Tell me about a call where the homeowner was upset before you arrived. What did you say first, and how did it end?
2. Describe a time you could not find the problem on the first visit. What did you do?
3. Tell me about a time you made a mistake on a job. How did you find out and what did you do about it?
4. Walk me through how you explain repair and replacement options to a homeowner who is worried about cost.
5. Tell me about a time you disagreed with a dispatcher or manager about how to handle a job.
6. What do you do when you finish a call early and have time before the next one?

Listen for ownership, honesty and respect for the customer. Red flags include blaming every problem on someone else, describing customers with contempt, or never having made a mistake.

Technical questions by trade

Ask the candidate to talk through their process rather than give one-word answers. A tech who checks the simple things first, explains why, and knows when to stop and ask for help is usually better on real calls than one who jumps to the most expensive part.

The hands-on skills test

A skills test shows what a candidate can actually do. Set up a training board or a unit in the shop with a known fault, give the candidate the tools they would carry and a time limit, and score them on a checklist. Use the same fault for every candidate at the same level so scores are comparable.

• Safety first: did they verify power is off and use the right protective equipment before starting?
• Process: did they test before replacing anything, and in a sensible order?
• Tools and meters: did they use them correctly and read them accurately?
• Diagnosis: did they find the actual fault within the time limit?
• Communication: could they explain the problem and the fix in plain words, as if to a homeowner?
• Clean-up: did they leave the work area tidy?

Paid working interviews

Some companies ask candidates to ride along for a day or run supervised calls before deciding. That is a good test, but once the candidate is doing productive work for your business, pay them for that time. Put them on payroll for the day, keep them with a lead tech at all times, and make sure they are covered under your insurance. A short skills test in the shop is different from a day on real customer jobs; keep the two clearly separate in your process.

Credentials and checks

Verify every credential the job requires before an offer. For HVAC roles, the EPA requires nearly all technicians to be certified in proper refrigerant handling^[3]. Most states require electricians to be licensed^[4], and state laws require pest control workers to be licensed, usually after training and an exam^[6]. Check licenses on the state board’s website and ask to see refrigerant certification cards.

If you run a background check or driving record check through a consumer reporting company, federal law sets the steps. You must tell the applicant in writing, in a stand-alone document, that you may use the report and get their written permission; before rejecting someone based on the report you must give them a copy of it and a summary of their rights; and after the decision you must give a notice of the adverse action^[2]. States and cities can add limits on criminal history questions, so check local rules.

Questions to avoid

Federal guidance says information requested before hiring should be limited to what is essential for judging qualifications, and that questions about race, sex, national origin, age and religion are irrelevant to that decision^[1]. Employers are explicitly prohibited from making pre-offer inquiries about disability^[1]. You can describe the physical demands of the job, such as climbing ladders, working in attics and lifting equipment, and ask whether the candidate can perform those duties with or without accommodation.

• Avoid: age, year of graduation, marital status, children, pregnancy, religion, national origin, health conditions and medications.
• Instead: ask about availability for the actual schedule, ability to perform the listed duties and legal authorization to work.
• Keep notes about answers, not about the person’s appearance or background.

Reference checks that tell you something

Most reference calls produce polite, empty answers because the questions are vague. Ask former supervisors specific questions instead: how often the candidate had callbacks, how they handled a difficult customer, whether they showed up on time in peak season and whether the supervisor would hire them again for the same role. Listen for hesitation. A reference who answers the rehire question slowly or with conditions is telling you something. Always ask the candidate for a supervisor, not only a co-worker, and call at least two references for every tech you plan to hire.

Score, decide and follow up

Score each part on a simple scale immediately after the interview, before talking to anyone else about the candidate. Add the scores, then discuss. If two interviewers disagree strongly, go back to the notes and the skills test checklist. Call the candidates you want within a day, because good techs get other offers quickly, and send a short, polite message to the ones you do not. The hire is only the start: see technician onboarding for the first 90 days and, for writing the ad that brought them in, technician job ads. Ranges discussed in the interview should match your posted pay; see pay transparency laws.