What makes a good field tech: the hiring signals that actually predict success

What makes a good field tech?

A good field tech is a strong diagnostician who treats customers well, owns his mistakes, and keeps getting better — in that order. Notice what's not on the list: years of experience, a wall of certifications, or interview polish. Those are either entry requirements or noise. The techs who generate revenue, five-star reviews, and zero drama share four observable traits — diagnostic thinking, customer behavior, ownership, and coachability — and every one of them can be screened for before you hire, if you know what to look for. Most bad hires in the trades were screenable; the interview just measured the wrong things.

I'll take the four signals in order of how hard they are to fake, then cover the traditional credentials and what they're actually worth.

Signal 1: Diagnostic thinking — the order matters more than the answer

The core of field work isn't turning wrenches. It's figuring out which wrench to turn. A service call is a fault tree: symptoms in, hypothesis, test, narrow, repeat. The techs who earn their pay work that tree in a disciplined order. The ones who cost you money skip to a guess — and the guess usually ships with a parts invoice and a callback.

You screen for this with a bench scenario, not a quiz. Pull a real failed call from your history — the no-cool with the misleading symptom, the breaker that kept tripping — and give the candidate the setup: here's what the customer reported, here's what the last guy found, what do you check first? Then listen for structure. A real diagnostician thinks out loud in sequence: verify the complaint, check the simple and cheap causes first, explain why each reading rules something in or out. A pretender talks in generalities ("I'd check the system over") or leaps to a component swap.

Two details that separate the great from the good: what they do when they're stuck, and whether they ask questions. A tech who says "at that point I'd call my old lead, because this pattern usually means X or Y" just showed you humility and a working method in one sentence. And a candidate who asks you clarifying questions about the scenario — what was the ambient temp, was this after the storm — is running the tree in real time. That's the hire.

We keep a bank of these in our interview questions for HVAC technicians; the format ports directly to plumbing and electrical.

Signal 2: Customer behavior — the trait that shows up in your reviews

A field tech spends most of his working life alone in customers' homes, unsupervised, representing your company. Whatever he does at that kitchen door — how he explains the problem, how he handles the price conversation, whether he covers his boots — becomes your brand, one house at a time. A brilliant diagnostician who's curt with homeowners quietly bleeds customers you never see leave; they just call someone else next season.

This is harder to screen than technical skill, but it leaks everywhere if you watch for it:

• How they talk about past customers. Ask about the worst customer interaction they've had. Everyone has one. Listen for whether the story ends with contempt ("people are idiots") or with de-escalation and what they'd do differently. The tone they use about past customers is the tone your customers will get.
• How they explain technical things to you. Ask them to explain a repair the way they'd explain it to a homeowner. Good field techs have a translation gear — plain language, honest about options, no jargon-flexing. Techs who can't or won't shift registers create the "he talked down to me" review.
• The small courtesies in the interview itself. On time, returns calls, communicates delays. A candidate who goes quiet for four days mid-process will go quiet on your dispatcher too.

If you run a ride-along or paid working interview — and for final candidates you should — put weight on the doorstep, not just the diagnosis. Your senior tech will see the mechanical skills. Watch how the candidate treats the homeowner, and the office staff, and the apprentice.

Signal 3: Ownership — ask about the callback that was their fault

Every tech generates callbacks. The question is what they do with them. The techs who compound in value treat a callback as information: what did I miss, how do I not miss it again. The ones who plateau treat it as an injustice: bad parts, bad luck, bad customer, previous guy's fault.

The interview question is simple: "Tell me about a callback that was your fault." Then be quiet. You'll get one of three answers. A specific story with a lesson attached — that's your hire. A story where fault mysteriously belongs to someone else — that's a pattern, and you'll be hearing it about your own jobs within a month. Or "I don't really get callbacks" — which from anyone with real field time is either a red flag for self-awareness or just untrue.

Ownership also shows up in the work history when you check references. Skip the generic reference questions and ask two narrow ones: "Would you put him alone in a customer's home?" and "Would you hire him back?" A pause after the second question is an answer. This trait matters more than almost anything on the technical side, because replacing a tech who doesn't work out is brutally expensive — SHRM Foundation research puts total turnover costs at 90–200% of annual salary once you count the recruiting, the ramp, and the lost work. The behavioral misses are what drive most of those exits.

Signal 4: Coachability — trajectory beats tenure

Years of experience is the most over-weighted line on a trades resume. It tells you someone survived in the field, not that they grew there. Plenty of ten-year techs are running year two's habits on repeat, and they interview confidently because they've had lots of practice being sure of themselves.

What you actually want is trajectory: is this person better than they were two years ago, and how did that happen? Ask what they've learned recently — a new system type, a code change, a diagnostic trick from another tech. Ask about a time a lead corrected them and what they changed. A coachable tech answers with specifics and without bristling. An uncoachable one signals it fast: every past shop was run by fools, every correction was unfair.

This is also where the market reality cuts in your favor. With the tech shortage being what it is, the fully-formed senior tech is the scarcest and most expensive candidate on the market. A sharp, coachable three-year tech is far easier to find, costs less, and in eighteen months under a good lead will outperform the plateaued veteran — while being far more likely to stay, because you're the shop that developed him. Screening for coachability is what makes hiring on potential safe. And it pays off past the hire: development is half of why techs stay.

What about certifications and experience?

They're the floor, not the signal. EPA 608 for refrigerant work, the right license for the trade and jurisdiction, insurable driving record — verify all of it early, and treat any missing hard requirement as disqualifying. But past the floor, credentials have flat returns: the difference between a good hire and a bad one almost never lives in the certificate count. Verify the floor fast, then spend your limited evaluation time on the four signals above, where the actual variance is. The step-by-step process for doing that — post, screen, hands-on evaluation, fast offer — is in our guide to hiring HVAC technicians.

You can't screen well under panic

Here's the uncomfortable dependency: everything above assumes you have candidates to screen and time to screen them. The owner with an empty truck in July, three weeks behind on calls, does not run bench scenarios and narrow reference checks. He hires the first candidate with a pulse and a license, and he finds out about signals two through four the expensive way.

That's why we keep coming back to the same thesis at HireAligned: recruiting is a sales function, and the screening only works when it happens before the emergency. A standing pipeline of techs you've already evaluated is what buys you the luxury of being picky about the traits that actually predict success. Know what a good field tech looks like — then build the bench that lets you hold out for one. If you'd rather have the sourcing and screening run for you, that's the service.