How to Hire a Pool Service Technician (From Someone Who's Done It Hundreds of Times)

I own a pool service company in the DFW area. We service around 900 pools a week with 25 people, and getting there meant hiring a lot of pool techs. Some of them are still with me. A lot of them didn't work out. I've made just about every hiring mistake you can make, and I've gotten enough of them right to keep the trucks rolling.

So when I tell you how I hire a pool technician, it's not theory. It's the process I actually run, refined over years of doing it badly and then less badly.

Here's the part nobody tells you when you start a pool company: hiring one good tech is a numbers game, and the numbers are rough. To land a single technician I'm happy with, I'll leave a job posting up until it pulls around 100 applicants. Out of that hundred, a chunk are worth a phone screen, so I start calling. But a phone screen isn't an interview. Between the people who never pick up, the ones who talk themselves out of it on the call, and the ones who won't commit to a time, I have to keep screening until I've got around 10 confirmed interviews on the calendar. Then interview day comes, a few of those no-show anyway, and the ones who do show get me to one good hire. One. From a hundred.

If that sounds brutal, it's because it is, and it's why most pool company owners I know quietly dread hiring season. The work isn't the pools. The work is the funnel. And the widest, most miserable part of that funnel is the top of it: sitting down with a stack of a hundred resumes and trying to figure out which ones are worth your time.

That's the problem this whole guide is really about. Everything below is how I think about separating the worth-calling resumes from the rest, and then the one good hire from everyone you call.

You're not hiring a pool cleaner. You're hiring someone for your customer's backyard.

This is the thing I wish someone had told me early, because it changes every decision that comes after it.

We tell ourselves we're hiring someone to clean pools. We're not. The pool part is the teachable part. A tech who's never touched a pool will get the chemistry, the skimming, and the basic equipment down in about three weeks of in-person training, and then we keep supporting them: quality checks on their work, periodic ride-alongs, phone support when something comes up they haven't seen. But here's what most people miss: in-person training is three weeks, and really learning this job takes a year. They have to see all four seasons, the spring green-up, the summer load, the fall leaf drop, the winter equipment issues, before they've actually seen the whole job. The pool side is teachable, it just takes a while. What I can't teach, on any timeline, is everything around the pool.

The job is this: every week, this person drives to a stranger's home, lets themselves through the side gate, and spends time alone in that family's backyard while the kids' toys are out and the back door is unlocked. Then they do it again the next week, and the week after that, fifty-some times a year, at house after house. The homeowner has to feel completely fine with that. If they don't, it doesn't matter how clean the pool is.

So I stopped thinking of us as a pool company that needs cleaners and started thinking of us as a customer service company that happens to clean pools. Once that clicked, hiring got clearer. I'm not screening for the best pool cleaner. I'm screening for someone I'd trust in my own backyard, who also happens to be teachable on the pool side. That order matters. Trust first, skills second.

Everything in the rest of this guide comes back to that.

The non-negotiables (where I stop reading and move on)

Before I evaluate anything interesting about a candidate, a stack of basic requirements has to clear. These aren't preferences. If a candidate misses one, I stop right there and move to the next resume, no matter how good the rest of it looks. I learned to be ruthless about this because every time I've made an exception "just this once," it's come back to bite me.

Here's what has to be true before I'll even look at the experience:

A valid driver's license. The job is driving a truck to a route of houses. No license, no job. It sounds obvious, but you'd be surprised how far some applicants get before this comes up, so I check it first.

A clean enough background. This person is going to be alone in your customers' backyards every week, with kids and pets and unlocked back doors. I will not put someone with a history of violent, theft, or sexual offenses into that situation. It's a liability and, honestly, it's just the right call. I tell every candidate up front that a background check is a condition of employment, so there are no surprises later.

A reliable way to get to work. Every single morning, on time, no exceptions. If someone's transportation situation is shaky, the route doesn't get done, and the customer doesn't care why.

A schedule with no standing exceptions. This one trips people up, and it's worth explaining. I've had candidates say something like "every other Wednesday I need to leave by one for a family thing." I get it, life happens, but it doesn't work for this job. Customers expect their pool done on their assigned day, and I build routes assuming the tech is available the whole day. The minute there's a standing carve-out in someone's week, I'm scrambling to figure out who covers those pools, and the routes stop making sense. So I screen for people who can commit to a consistent, full-time weekly schedule, full stop.

They have to live close enough. This is the one I feel strongest about, and it's the least obvious. I disqualify anyone whose commute to the shop would run long. Not because of the drive itself, but because of what it predicts. I've watched it happen over and over: the tech with the long commute is the tech who burns out and quits. A short commute on a hot Tuesday in July is an annoyance. A long one is the reason they start looking for a job closer to home. Proximity isn't a nice-to-have, it's one of the strongest retention signals I've got, before they've even started.

One note on that last one, because it connects to how I run trucks: I keep my technicians' trucks at the shop overnight rather than letting them drive home. If you let techs take trucks home, the math changes a little, but the principle holds. Keep the assigned route close to where the tech actually lives, or you'll be hiring for that spot again before long.

None of these requirements are about whether someone is a good person or a hard worker. Plenty of good, hard-working people fail them. They're about whether this specific job can work for this specific person, and whether I can build a reliable route around them. If the answer is no, the kindest thing for both of us is to figure that out before anyone wastes their time.

The signals that actually predict a good hire (and the ones that fool you)

Once a candidate clears the basics, this is where the real judgment starts, and it's where most owners get it backwards. We tend to over-weight the obvious thing (pool experience) and under-weight the things that actually predict whether someone's still on the route a year from now. Here's what I've learned to look for, roughly in order of how much it matters.

Can they hold a job? This is the big one. If I could only know one thing about a candidate before hiring, it would be their job history, not their skills. A resume that shows someone bouncing between jobs every few months is the single most reliable predictor of turnover I've found. It doesn't matter how good they look otherwise. Someone who can't stay anywhere won't stay with me either, and I'll be back to screening a hundred resumes for the same spot in six months. So I reconstruct the timeline: how long at each job, what the gaps look like, whether there's a pattern of leaving the second things get hard. Stability beats almost everything else on the page.

Pool experience helps, but it's not what you think it is. Obviously a candidate who's cleaned pools before ramps up faster, and that's worth something. But here's the trap: prior pool experience does not predict a good long-term fit. I've hired experienced pool guys who washed out in two months and total greenhorns who are still with me years later. Treat experience as a nice-to-have that shortens training, not as the thing that makes the hire. Which leads to the next point.

The right kind of work history matters more than the exact job. I'd rather hire someone who's never touched a pool but spent three years doing hard outdoor work than someone with pool experience and a spotty record. What I'm really screening for is: have they done physical, outdoor, hands-on work and stuck with it? Construction, landscaping, roofing, ranch work, HVAC, plumbing, equipment operation, field service. All of that transfers. Those people already know what it means to work outside in the heat all day and keep showing up. What I'm wary of is the candidate coming straight from an indoor, climate-controlled job (retail, call center, food service, an office) with no history of outdoor labor. Not because those aren't real jobs, but because the first 100-degree afternoon hauling salt bags is a brutal way to find out someone doesn't actually want to work outside.

Watch for overqualification. It's a flight risk, not a bonus. This one's counterintuitive, so it's worth saying plainly. When I see a candidate who's significantly overqualified for a pool tech role (a master's degree, a career in something professional), my guard goes up rather than down. The honest read is that this job is a stopgap for them, and the day a better-fitting offer comes along, they take it, and I'm hiring again. I'm not looking for the most impressive resume. I'm looking for the person for whom this is a good job they'll want to keep.

Can they physically do this, day in and day out? This one I mostly confirm in the interview rather than the resume, but it belongs here. The job is carrying 40-pound salt bags in 100-degree heat at four in the afternoon, every day, all summer. It's genuinely taxing. Someone doesn't need to be an athlete, but they need to be capable of the physical reality of the work, because the route doesn't get lighter in August.

Would your customer be glad to see them? Back to the thesis from earlier: this person represents your company in someone's backyard every week. So I'm paying attention to how they present, and whether they seem to actually get customer service. During the interview I'm fishing for that. Do they look like someone a homeowner would feel comfortable having around their kids and their house? Some things are automatic disqualifiers for me on that front, offensive tattoos for example, not out of judgment, but because my customer didn't sign up to be uncomfortable in their own backyard. And the candidates I get most excited about are the ones who, somewhere in the conversation, show they understand they're in the service business. Those are rare, and they're worth hiring even when something else on the resume is just okay.

If I had to boil this whole section down to one sentence: I'm not hiring the best pool cleaner, I'm hiring the most reliable person who can become a good pool cleaner and who my customers will be happy to see. Skills are teachable. Reliability and temperament mostly aren't.

Where to find techs, and why your job ad is the first filter

Let me start with the ad itself, because most owners treat it as an afterthought and it's actually the first place you either save yourself work or create a mountain of it.

Put the pay in the ad. Always. I know the instinct to leave comp off, to keep your options open or avoid tipping off competitors. Ignore it. Listing the pay is the single easiest filter you have, and it works before anyone even applies. If someone needs to make more than this job pays, they self-select out and never land in your stack. If the pay works for them, they apply already knowing the number, which means you're not spending a phone screen discovering you're miles apart on money. Every applicant the comp filters out is one less resume you have to read. That's free filtering, so use it.

While you're at it, use whatever screener questions the platform gives you. On Indeed I set required qualifications and yes/no screener questions, and anyone who misses them gets filtered before I ever open their resume. It's the same principle as listing pay: push the easy disqualifiers as far upstream as possible, so the only resumes you actually read are from people who already cleared the obvious bars.

Now, where they actually come from. I'll be honest about what works and what doesn't:

The big job boards (Indeed for me) are where the volume is, full stop. That's where the hundred applicants come from. The tradeoff is that volume cuts both ways: you get reach, but you also get every person clicking "apply" on everything, so the screening burden is heaviest here. Most of my hires come through the boards, and so does most of the slog.

Referrals from your existing techs are gold when you can get them. A good tech usually knows other people who can do the work, and someone who comes recommended by an employee you trust has already passed a filter no resume can replicate. The catch is volume: referrals trickle in, they don't fill a route on a deadline. Treat them as a bonus, not a strategy.

The trade-adjacent pipeline is worth a real mention. Some of my best people came from other outdoor trades, not from pool work. When the broader job market shifts and people in construction, landscaping, or oilfield work are looking, that's a pool of candidates who already know hard outdoor labor. Worth keeping an eye on.

And if you're not part of your regional and national pool industry groups, you're missing a channel. Beyond the obvious networking, the relationships you build there turn into referrals, advice, and occasionally a good tech who's moving and needs a new shop. It compounds slowly, but it's real.

The thing to understand across all of these: no single channel solves hiring. The boards give you volume but bury you in screening. Referrals give you quality but not quantity. The trades and industry connections give you the occasional great fit but unpredictably. You end up running all of them, and the boards do the heavy lifting, which brings us back to the real problem.

The part that breaks you: reading the stack

Here's where all of it comes together into one genuinely awful task.

You posted the ad with the pay listed. You set your screener questions. The easy disqualifiers got filtered upstream like they should. And you still come back to a stack of around a hundred resumes, because that's what it takes to find one good tech, and now somebody has to actually read them. That somebody is usually you.

So you sit down with the pile. And for each one, you're running the whole checklist from the last two sections, in your head, one resume at a time. Where do they live, is that a reasonable commute to the shop, or do I cross them off right there? Let me look at the job history. Okay, three jobs in two years, that's a pattern, or wait, is that two jobs and a contract gig, and when exactly did this one end, because if it's been over a year since they worked I'm out. What's this most recent role, is that real outdoor labor or is it a warehouse job that just sounds physical? Have they actually done this kind of work or am I going to be teaching from zero? Master's degree on a pool tech application, why, what's the story there, is this person going to bolt the first chance they get?

Now do that ninety-nine more times.

That's the job. Not the hiring, the screening. And it's brutal for reasons that aren't obvious until you've done it a few dozen times:

It's mind-numbing, which makes it dangerous. By resume forty you are not screening as carefully as you were at resume five. Your standards drift. You start skimming. The exact thing that requires consistency, applying the same bar to every candidate, is the thing your tired brain is worst at after an hour of it. I've absolutely shortlisted people at the bottom of a stack that I'd have rejected at the top, just because I was worn down. That's not a discipline problem, it's a human problem. Nobody applies a hundred judgment calls identically.

It's slow, and it's slow at the worst possible time. You're not screening resumes when business is calm. You're screening because you're short a tech, which means the route is already strained, which means you're doing this at night after a full day, or in stolen pieces between service calls. The hours it eats are hours you do not have.

And it's repetitive in the cruelest way: you do all of it, land a good tech, feel the relief, and then turnover being what it is in this industry, you're back at the bottom of a fresh stack a few months later running the identical gauntlet again. The screening is never done. It's a tax you pay over and over for the privilege of staying fully staffed.

This is the single biggest hidden cost of running a pool company that nobody warns you about. Not the trucks, not the chemicals, not the customers. The quiet, recurring, soul-draining hours of working through a hundred resumes to find enough worth calling, making the calls, and doing it again and again until ten of those calls finally become ten people who show up to interview. Knowing you have to apply the same bar to every resume, and knowing you won't, because you're human and the stack is a hundred deep.

I did this by hand for years. It's the part of the job I hated most.

The phone screen, and the math nobody likes

Say you've done the screening. You've got your shortlist, the resumes that survived the stack. You are not close to done. You're at the start of the second funnel, and this one leaks just as badly as the first.

Here's how it actually goes. You start calling. A good chunk don't pick up, so you leave a voicemail, send a text, drop them a message on the platform, and move to the next name. Some of those never call back, and after a few days of silence you cross them off. Of the ones you do reach, a few talk themselves out of it the moment they hear the real details, the schedule, the pay structure, the fact that the truck stays at the shop, whatever it is. That's fine, better now than after you've hired them, but it's another name gone.

So you do not call ten people and get ten interviews. You call however many it takes, working down the shortlist, until you've got around ten interviews actually confirmed on the calendar. For me that's a real, deliberate process, and it's why the shortlist has to be more than ten deep to begin with. The phone screen is its own attrition layer, and you have to keep feeding it.

Then comes the last gut-punch: interview day arrives, and a few of your ten confirmed don't show. No call, no cancellation, just an empty chair at the time you blocked off. So you build in cushion, you backfill from the shortlist when you can, and you accept that "ten confirmed" really means "however many actually walk through the door," which is always fewer.

A couple of things I've learned to do to keep this from eating me alive:

Make the screen quick and consistent. I'm confirming the same handful of make-or-break things every time before I spend anyone's time on an interview, the basics from earlier: do they actually live close enough, valid license, can they commit to the full-time schedule, are they good with a background check, can they physically do the work. If any of those is a no, the call ends politely right there. A phone screen's whole purpose is to fail people cheaply, before they cost you an hour of interview time.

Over-schedule on purpose. Because you know some confirmed interviews will evaporate, the number you confirm should already account for the no-shows. The owners who get blindsided are the ones who confirm exactly the number they need and then sit in an empty office on interview day with a route still short.

And this is the part to sit with: every layer here, the no-answers, the talk-themselves-out, the no-shows, sits downstream of the resume screening. Which means if the screening at the top was sloppy, if you let weak resumes through because you were worn down at resume forty, you're now spending your scarcest resource, your actual phone and interview time, on people who never should have made the shortlist. A bad screen doesn't just waste the screening hour. It poisons every expensive hour after it.

That's the real reason getting the top of the funnel right matters so much. It's not about the resumes. It's about everything the resumes cost you downstream.

Why this never actually ends

I'll keep this short, because retention is its own beast and not really what this guide is about. But you can't talk honestly about hiring pool techs without saying the quiet part: you are going to do everything above again, and sooner than you'd like.

Turnover in this industry is just high. The work is hard and physical, it's seasonal in a lot of markets, and there's always another shop or another trade willing to dangle a little more money. Some of your best people will leave for reasons that have nothing to do with you. That's the nature of it. The goal isn't zero turnover, which doesn't exist. The goal is to keep it manageable, and to not be caught flat-footed when it happens.

Most of what actually keeps techs is upstream of any retention tactic, and it loops right back to how you hired them. The tech who lives twenty minutes away stays longer than the one driving an hour. The one who genuinely likes outdoor work doesn't burn out the way the one who took the job as a stopgap does. The stable work history that made you comfortable hiring them is the same trait that makes them likely to stick. In other words, a lot of retention is just hiring well in the first place, which is the whole reason to take the screening seriously instead of grabbing the first warm body when you're short.

But even doing all of it right, you'll be back at the top of the funnel a few times a year. That's not failure. That's the business. And once you accept that hiring isn't a thing you finish but a thing you run, continuously, season after season, you start thinking about it differently. You stop treating it as an emergency every time and start treating it as a system you need to be able to run again and again without it wrecking your week.

Which is exactly what I eventually had to figure out.

What I eventually built

For years I did all of this by hand. Then at some point it occurred to me that the screening part, the part I hated most, was actually the most repeatable part. Every time I sat down with a stack of resumes, I was running the same checks in the same order. Where do they live, how's the job history, is this real outdoor work, are they overqualified and likely to bolt. The same logic, every time. The only variable was me, and how tired I was by resume forty.

So I built a tool to run that logic for me. It's called PoolCrew. You hand it the stack of resumes, and it does the first pass the same way I would on my best day, every time, without getting worn down. It separates the people with real pool or trades experience from the ones just clicking apply on everything, it flags the job-hoppers by actually doing the tenure math, it figures out who lives close enough to the shop to make sense, and it hands you back a sorted shortlist. What used to cost me an evening it does in a few minutes.

I want to be straight about what it is and what it isn't, because I'd want the same from another owner. It does not hire anyone for you. It doesn't make the phone calls, it doesn't run the interviews, and it sure doesn't promise you a great tech, because no tool can. There's no substitute for the phone screen and looking someone in the eye. What it does is take the worst, most mind-numbing, most error-prone part of the process, reading a hundred resumes and applying the same bar to every one, and just handles it, so you get to the calls faster and with a cleaner list. It saves you the hours and it keeps the bar from drifting. That's the whole pitch. That's all it needs to be.

There's one more thing it did for me that I didn't expect, and it's actually the biggest one. Once the screening logic lived in the tool instead of in my head, screening stopped being something only I could do. The judgment was fixed and consistent, so I could hand the whole top of the funnel, the screening, the shortlisting, the phone calls, the interview scheduling, to someone else and trust it was being done the way I'd do it. Not someone who understands pools or our culture or fifteen years of my hiring instincts. Anyone who can follow a process. My office could run it. An assistant could run it. The tool makes the one judgment call that used to require me, and everything around it becomes a process somebody else can own. At my size that's given me back something like twenty hours a month, and more than the hours, it's the not-having-to-be-the-bottleneck. The bar doesn't move whether I'm the one screening or not.

I built it for my own company first. It turned out other owners had the exact same stack of resumes ruining their week, so I put it online for them too. If reading the stack is the part of hiring you dread like I did, it's at getpoolcrew.com, and you can come find me there. Either way, whether you ever touch the tool or not, I hope the rest of this was useful. We're all fighting the same fight out here.