How to Screen Field Service Technicians: 9 Questions and What to Listen For Screening Interview Template

What equipment did you actually service, down to the manufacturers and model families? What did a normal day look like: how many calls, how big was the territory, and were you running your own van? Roughly what was the split between new installs or startups and service calls?

What this assesses: This is the fit calibration question and almost nobody volunteers the numbers. Strong answers name specific manufacturers and platforms rather than a category, describe a real day (four to six calls inside a sixty-mile radius, dispatched through a field app, own van stocked to a list), and give an honest install-versus-service split, because those are different skills. A tech who spent three years on new installs has clean wiring habits and may have never diagnosed an intermittent fault on ten-year-old equipment. Be cautious with a candidate who has only worked on a bench or in a depot and is describing shop repair as field work, since the road job is mostly the parts a bench never tests: driving, customers, weather, no lift, no second meter, and whatever is on the van. Also be cautious with a resume that lists a dozen equipment lines with no depth in any of them.

Tell me about the hardest fault you diagnosed in the field with nobody to call. What were the symptoms, how did you narrow it down, and how long did it take?

What this assesses: This is the parts-changer test and it is the single most predictive question on the list. Strong answers walk a sequence: what the customer reported, what they observed themselves, what they measured, and specifically what each result ruled out. They mention the wrong turns, because real diagnosis has them. They usually land on something unglamorous, a chafed harness, a loose neutral, a failed sensor reading in range but not tracking, a fault that only appeared once the unit warmed up. Be cautious with an answer that jumps from symptom to replaced part with nothing in between, and be very cautious with a story where the fix was replacing the control board, since that is the default guess of a tech who does not measure. Ask a follow-up if they say they swapped a part: how did you know it was that part before you put it in.

Walk me through how you use a multimeter, or your primary diagnostic tool, to isolate a fault. What do you check first and why? How comfortable are you reading a wiring or ladder diagram and working from error codes?

What this assesses: Fundamentals, and they are easy to fake on a resume and hard to fake in a written answer. Strong answers describe verifying supply before condemning a load, confirming voltage is present at the input of a component before deciding the component is bad, doing continuity and resistance checks with power removed, and using the diagram taped inside the panel rather than working from memory. They treat error codes as a starting point that narrows the search, not as an answer, and they know a code can point at a sensor when the real problem is what the sensor is measuring. Be cautious with a candidate whose entire meter use is the continuity beeper, who cannot say what they measure first, or who describes reading a diagram as something the office does. The specific tool matters less than whether the candidate has a repeatable method.

Have you ever had to go back on a call you already closed out? What happened, and what do you do differently now?

What this assesses: First-time fix rate is the metric this role is actually judged on, and this question is as much an honesty check as a skill check. Strong answers produce a real repeat call, name the cause without softening it (treated a symptom, missed a second failure caused by the first, did not run the unit long enough to confirm the fix), and describe a concrete habit that came out of it, usually cycling the equipment through a full run before leaving or checking the thing that failed the part in the first place. Be cautious with a candidate who says they have never had a callback. Either they have not run enough volume to know, or they are managing you rather than answering. Be equally cautious with a story where every callback was the customer's fault or the parts department's fault.

A customer's equipment has been down since this morning, the part you need is two days out, and the site manager is angry at you personally. What do you actually say, and what do you do before you leave?

What this assesses: You are hiring the person who owns your customer relationship on the worst day of it. Strong answers give the customer a straight timeline instead of a hopeful one, look hard for a partial fix or a workaround that gets the customer running at reduced capacity, check whether another branch or a local supply house has the part, escalate to dispatch or the account manager while still on site rather than after, and document what was found and what is on order so the next person is not starting over. They stay on the customer's side of the problem without promising anything they do not control. Be cautious with a candidate who blames the parts department or the office in front of the customer, who commits to a delivery date to end the conversation, or who describes leaving without telling anyone the site is still down. One of those turns a bad day into a lost account.

How was your van or truck stocked, and who decided what was on it? Walk me through exactly what you do at the end of a call before you drive to the next one.

What this assesses: This is the boring question that separates a technician from an expensive one. Strong answers describe par levels for common failure parts, replenishing on a set cadence rather than when something runs out, and knowing what they carry because they have watched which parts fail on their equipment. On close-out, strong answers finish the work order at the site or in the driveway: parts used, labor time, model and serial, readings taken, photos, customer signature, and a note that means something to the next tech. Be cautious with a candidate who saves paperwork for Friday, because unbilled labor, unclaimed warranty parts, and a service history nobody can reconstruct all trace back to that habit. Be cautious too with a tech who has never had input into van stock, since it usually means the parts decision was always someone else's.

Where does this work put you when the job is not at ground level: ladders, roofs, lifts, live panels, confined spaces, hot work? Tell me about the last time you stopped a job because it was not safe to do the way it was set up.

What this assesses: A field tech makes safety decisions with nobody watching, which is the whole risk. Strong answers describe verifying zero energy before touching anything, applying their own lock and tag rather than trusting that someone else did (OSHA requires an energy control program at 29 CFR 1910.147), owning and using their PPE, and knowing which jobs they will not do alone. The stop-work story is usually small and specific: a ladder that could not be footed properly, a roof access nobody would open, a panel that should have been de-energized and was not, a customer pushing to keep the line running during the repair. They called dispatch and rescheduled. Be cautious with a candidate who has never stopped a job, and be more cautious with one who takes pride in working things hot to save a trip. Field techs get hurt alone, and you find out hours later.

You arrive at a site and it is a piece of equipment you have never worked on. No senior tech available. What do you do in the first thirty minutes?

What this assesses: Territory work means meeting unfamiliar equipment regularly, and the honest answer is a process, not confidence. Strong answers pull the service manual or bulletin on a phone or tablet, read the diagram inside the panel, check the fault table against whatever code is displayed, get the model and serial and call the manufacturer's tech support line, and ask the site's own operator what changed and what it sounded like before it stopped, which is often the fastest lead available. They are explicit that they will not start replacing parts to find out. Be cautious with a candidate who says they would figure it out as they go, which usually means guessing on your parts budget, and be cautious with one whose only plan is to wait for a senior tech, because in this job there is not one. Wanting a phone-a-friend is fine. Needing one on every unfamiliar call is not.

Tell me about your driver's license and driving record. Any accidents, violations, or suspensions in the last three to five years? This role runs a one-week-in-four on-call rotation and a few overnight trips a month. Does that work, and what hourly rate or salary are you targeting?

What this assesses: This is where field service offers die after acceptance, so put it in the screen rather than in week three. The driving record is a hard gate, not a preference, because the candidate has to be insurable under your fleet policy and a recent at-fault accident or a suspension can disqualify them no matter how good the rest of the screen looks. Verify through a motor vehicle record check with a compliant disclosure and authorization process rather than taking the answer on faith, and note that if your service truck is over 10,001 pounds and crosses state lines you are in DOT territory with a medical certificate requirement attached. Strong answers are specific and unhurried about the record, treat on-call as a normal part of the job and can say how often they carried the phone before, give a real number on overnight travel they can sustain, and name a rate that lines up with your posted range. Be cautious with a vague reference to a couple of tickets, with someone who has never carried an on-call phone and is agreeing to it sight unseen, and with anyone whose rate expectation is above your band, since that gap does not close later. Score every applicant against the same [interview scorecard](/glossary/interview-scorecard) rather than reading answers in isolation, and see [structured interview](/glossary/structured-interview) and [asynchronous screening](/glossary/asynchronous-screening) for running this as a written first round instead of a week of phone tag with techs who are on a roof.