If you've hired even five people in field service, you already know the problem. The interview goes great. The first day is fine. Then by week two, the new guy is texting "running late" three days a week, missing Saturdays, and disappearing without notice. By month two, he's gone — and you're back on Indeed.
Showing up is the bare minimum of any job. In field service, it's also the hardest thing to actually find. The pool of available workers is smaller. The wages aren't competitive with desk jobs. The work is physical. And reliability has somehow become a rare and valuable trait.
This post is about how to fix that. Not by lowering your standards. By hiring smarter.
Why field service hiring is so broken right now
You're not imagining it. Hiring is harder than it used to be, and it's specifically hard in field service for a few real reasons:
1. The pool of "willing to do physical work" workers is smaller every year.
An entire generation has been pushed toward office work, college degrees, and remote jobs. Trade schools have been gutted. The cultural narrative about field work — that it's a fallback, not a career — has done real damage to recruitment.
2. You're competing with gig work.
Doordash. Uber. Instacart. Amazon Flex. Every one of those gives a worker total schedule control with zero accountability. If your competition is "drive whenever I feel like it for $18/hour," your structured shifts at $20/hour aren't as appealing as you think.
3. Your job posting probably looks like everyone else's.
"Field service technician needed. Pressure washing experience preferred. Must have valid driver's license. Pay DOE." That posting is invisible. It's identical to twelve other postings on the same job board. The good workers — the ones with options — scroll right past it.
4. The interview process selects for the wrong things.
Most field service owners interview for likability. Did the guy seem nice? Did the conversation flow? Did he say the right things? But likability is uncorrelated with reliability. Some of the most likable guys you'll ever meet are also the worst at showing up.
The traits that actually predict who will show up
Forget the resume. Forget the personality. Here's what I've learned actually predicts whether someone will show up reliably:
Stable housing
Not "owns a home." Stable housing. Lived at the same address for at least 12 months. If someone's bounced through 4 apartments in 18 months, that instability often correlates with attendance issues. Not always. But often enough to ask about.
Reliable transportation
Not "has a car." A reliable car. Ask: "If your car breaks down on a Tuesday, what's your backup plan to get to work?" The answer "I'd have to figure something out" is a yellow flag. The answer "My mom's car / my brother / I have a backup plan with X" is green.
Job tenure pattern
Look at their resume. Have they ever held a job for more than 18 months? If their longest tenure is 8 months and they're 32 years old, you're not going to be the magical exception. They job-hop. That's their pattern.
Counterintuitively, someone with one 5-year stint at a previous job — even if it ended badly — is more reliable than someone with six 6-month stints.
Specific reasons for leaving past jobs
Vague reasons are red flags. "It just wasn't a fit." "We had a falling out." "They were really disorganized."
Specific reasons are green flags. "My boss promised promotion that didn't materialize after two years and I needed more income." "I moved 40 minutes away when my wife took a new job and the commute became unworkable."
Specifics show self-awareness. Vagueness usually hides something.
Skin in the game
Single guys with no responsibilities are flight risks. Not always — but more often. Married guys with kids and a mortgage tend to show up. Their consequences for not showing up are higher than yours are.
I'm not saying don't hire single guys. I'm saying weight the screening differently. The single 24-year-old needs more reference checks and a tighter probationary period than the 38-year-old with three kids and a mortgage payment.
How to write a job posting that attracts the right people
Most field service job postings repel good workers because they're written by owners who are trying to sound professional. Stop sounding professional. Start sounding human.
Bad posting:
"Field service technician needed. Must have 2+ years experience. Valid driver's license required. Reliable transportation. Background check. Pay DOE."
Better posting:
"We're hiring a field tech. The job is hard physical work outdoors in Florida heat. You'll be on your feet 8 hours a day. Most days you'll work with one other person. We pay $X/hour starting, with raises based on performance — not seniority. We have crew members making $XX/hour after 18 months because they earned it. If you show up every day, do clean work, and don't make me chase you for updates, you'll thrive here. If you need to be reminded to clock in, this isn't the job."
The difference: the second posting is honest about the work. It signals what you actually value (reliability, quality, ownership). It pre-screens out people who can't handle physical work or don't want accountability. And it attracts the people who are tired of working for owners who reward seniority over performance.
Honest postings get fewer applicants. They also get better applicants. That's a trade you want.
The best field service workers actually want a job description that's honest about how hard the work is. Sugar-coating attracts people who'll quit when reality hits. Being upfront attracts people who already know what physical work feels like and aren't running from it.
Interview questions that predict reliability
Skip the standard questions. Use these instead:
"Walk me through your morning routine on a workday."
You're listening for: structured routine, realistic wake-up time, factoring in commute, eating breakfast or having coffee. People who don't have a real morning routine struggle to show up consistently.
"What's the longest you've worked anywhere? Why did that job end?"
You're listening for: tenure (longer is better) and specificity in why they left. Someone who can articulate a clear, blame-free reason for leaving has self-awareness.
"Tell me about a time you really didn't want to go to work but went anyway."
You're listening for: ANY answer. People who can recall a specific instance where they pushed through have demonstrated the actual skill you're hiring for. People who say "I always want to go to work" are lying or have never had a hard job.
"Describe your relationship with your last boss."
You're listening for: balance. "He was great, I learned a lot" + "He was tough sometimes, especially on quality" is a healthy answer. "He was awful, micromanaged everything, never let me do my job" is a flight risk. So is "He was perfect, never had any issues at all."
"If your car broke down at 6 AM on a Tuesday, what would you do?"
You're listening for: a real answer. Backup plans, names of family members, ride-sharing apps, whatever. Someone who has clearly never thought about this is going to ghost you the first time their car has trouble.
"What does someone need to do, in your view, to lose this job?"
You're listening for: alignment. If their definition of fireable is wildly different from yours, you have a problem. "I guess if I never showed up?" is concerning. "Stealing, lying, or repeatedly being late and not communicating about it" is much more aligned with how a good owner thinks.
The first 30 days are make-or-break
You'll know whether someone will be reliable inside the first 30 days. Maybe sooner. Watch for these:
- Day 1-3: Did they show up early? On time? Late? Late on day one is the strongest predictor of late forever.
- Week 1: Did they ask intelligent questions about the work? Or did they just nod and stay quiet?
- Week 2: Did they call out sick? "First two-week sick day" is a warning sign, especially with no documented illness.
- Week 3: Have they made any suggestions, observations, or improvements? Engaged workers offer ideas. Disengaged ones do the minimum.
- Week 4: What does their attendance look like? Have they been late even once? How did they communicate it?
If you're seeing any orange flags by day 30, don't hope they go away. They don't. The behavior in the first 30 days is the behavior you'll deal with for as long as you employ them.
Either coach it out fast — explicitly, in writing — or let them go before they cost you more.
Why pay matters less than you think
"I just need to pay more and people will show up."
Sometimes. Usually not.
I've watched owners raise wages from $18 to $22 and still have the same no-call-no-show problems. I've also watched owners pay below market and have crews who never miss a day. The difference isn't the money. It's the people.
What pay does is widen your candidate pool. More applicants. But more applicants doesn't mean better applicants — it means more screening work for you. If your screening process is bad, paying more just gives you a bigger pool of bad-fit hires to choose from.
Pay should be competitive. After that, your screening process is what matters. The reliable workers are out there at every wage range. Finding them is about how you hire, not how much you pay.
The bottom line
You can't fix the labor market. You can fix your hiring process.
Stop hiring under pressure. Stop interviewing for likability. Stop accepting vague reasons for leaving past jobs. Start asking concrete questions. Start writing job postings that filter out the wrong people. Start using the first 30 days as a real evaluation period — not just a "settling in" period.
And once they're hired, start measuring whether they're actually showing up to do the work. Not just clock-in time — actual output. Quality. Reliability. The metrics that matter.
The reliable workers exist. They're applying for jobs every day. The trick is making sure your hiring process is filtering for them, not against them.
Most field service owners think their hiring problem is a "no good workers exist anymore" problem. It's not. It's a "I'm not running a process designed to find them" problem. That's actually good news, because the second problem is one you can fix.