Hiring techs who stay

Pay isn't the whole story

Pay matters. If you're well under the local market, fix that first, because nothing else in this article will overcome it. But once pay is competitive, it stops being the reason good techs leave. They leave because the work is chaotic, the training never happened, nobody told them how they were doing, or they couldn't see where the job was going.

Turnover is expensive in ways that don't show up on a payroll report. Every departure means another round of recruiting, another stretch of training, jobs rescheduled or covered by overtime, and customers meeting a new face again. Getting the hire right the first time is one of the highest-return things an owner can do.

That's good news, because those are things you control. Retention starts before the offer, with who you hire and what you tell them, and it's mostly decided in the first month.

Know what you're hiring for

Before posting a job, write down what a good tech in this role does in a normal week, and what they'll be doing in a year if things go well. Be specific about the work, the schedule, on-call expectations, and the vehicle and tool situation.

Put those details in the posting. Candidates who would hate the on-call rotation or the drive times will self-select out, which saves you from hiring someone who leaves the first time reality doesn't match the pitch.

Separate the skills you need on day one from the ones you're willing to teach. A shop that can train well can hire for attitude and reliability and teach the rest. A shop that can't train needs to be honest about that and hire for experience.

Interview questions that reveal fit

Most interviews test whether a candidate can talk about the work. Better questions ask about specific past situations, because how someone handled a real problem predicts how they'll handle the next one. Listen for detail. Vague answers to specific questions usually mean the story didn't happen the way it's being told.

• Tell me about a job that went wrong. What happened, and what did you do about it?
• Walk me through how you document a job before you leave the site.
• Describe a time a customer was unhappy with you. How did it end?
• What did you learn in your last role that you didn't know when you started?
• Why are you leaving, and what would make you stay somewhere for years?
• What does a good first month at a new company look like to you?

Reading the answers

Techs who stay tend to talk about learning, about doing the job right, and about the people they worked with. Techs already looking for the next move tend to talk only about pay rates and hours, or describe every past employer as the problem.

A ride-along or a paid working interview is worth more than any question. Watch how the candidate treats the customer, how they handle the paperwork side, and whether they ask questions when they don't know something. Asking is a good sign. Guessing is not.

Call references, and ask specific questions. Would you hire them again? What did they need more support with? A pause before the answer tells you as much as the answer.

A first-month plan

New techs decide quickly whether a company has its act together. A written plan for the first month tells them you do, and gives you both a way to measure progress.

Assign one person to own the new hire's first month, usually a senior tech or field lead, and give them time in the schedule to do it. Onboarding that happens in the gaps between jobs usually doesn't happen at all.

1. 1Before day one: have the vehicle, tools, phone, accounts, and uniform ready. Missing equipment on the first morning sends the wrong message.
2. 2Week one: orientation, safety, how jobs are dispatched and documented, and ride-alongs with a strong senior tech. No solo work yet.
3. 3Week two: the new tech leads simpler jobs with the senior tech present. Review each job's documentation together at the end of the day.
4. 4Week three: solo work on job types they've already done with supervision, with a scheduled check-in call each day.
5. 5Week four: a sit-down review. What's going well, what needs work, and what the next three months look like, including any certifications or skills you'll help them build.

After the first month

Keep the check-ins going, less often but on a schedule. Give feedback when it's earned, both good and bad, instead of saving it for an annual review. Make the path forward concrete: what skills, certifications, or responsibilities lead to the next pay step, and when you'll revisit it.

Pay attention to the quiet signals. A tech who stops asking questions, starts arriving late, or goes vague in check-ins is often already looking. A direct, private conversation at that point is more useful than a counteroffer later.

A 30-day onboarding plan you can adapt is available in the Field service docs.