How to Hire and Manage a High-Performing OSP Team

Most of the OSP engineering firms we talk to aren't short on work. Between BEAD deployments and utility modernization programs, the pipeline is full and clients want it delivered yesterday. What they're short on is people: field technicians who bring home defensible pole data, designers who turn that data into make ready and pole loading deliverables a pole owner will approve, and a project manager keeping the two connected. Experienced hands are scarce in all three seats, and hiring in a rush usually buys poor fits, miscommunication, and rework that eats the margin the new contract was supposed to bring in.

We've written before about how we hire field technicians and how we hire OSP designers. This guide pulls those together with the project management habits that keep the pipeline moving, written for the manager at an engineering firm or broadband provider who is building that team right now.

Two hiring non-negotiables, whatever the seat

The principle doesn't change between a truck and a desk: the right person, in the right seat. If you can't commit to getting both right, subcontracting is a more honest answer than a rushed hire, since the wrong person can do lasting damage to a small team's culture even when the seat fits. The right person is defined by your core values, which aren't aspirational adjectives or permission-to-play traits like honesty. They're the qualities already present in your most successful and culturally influential people, and they're what you hire, fire, promote, and celebrate on. Say them out loud to candidates; someone who doesn't share them will find your team exhausting, and it's kinder to both sides to learn that in an interview. The right seat is whether the person understands the job, wants it, and has the capacity to do it well, and that's where the two roles diverge.

How to hire great field technicians

The way you collect data decides who can do the job. Our field workflow runs on photo documentation and two-person teams, so a technician doesn't need years of pole survey experience to bring home data a designer can trust. The Hastings stick, the height photos, and the measurement work back in the office replace the old model where one field hero memorized a hundred pole tags before lunch and estimated make ready costs from the driver's seat. Moving the engineering judgment into the office is what lets you hire technicians who live near the work and share your values instead of whoever has the longest résumé and is willing to travel. Our data collection page covers how that workflow runs in Katapult Pro.

What to screen for in a field technician

A field technician résumé rarely tells you what matters. The job means working alongside a partner, driving long distances, hiking for hours, taking consistent photos, and staying level with a suspicious homeowner. Simple questions cover the basics (comfort with the outdoors, with phones and cameras, with being on their feet all day), and the subtler traits predict data quality:

• Works peacefully and constructively in close quarters with a partner for a full week
• Has a clean driving record, since driving is the biggest safety exposure in the job
• Shows good judgment and communication with angry property owners
• Can grind through a repetitive task for hours without letting quality slide
• Isn't scared of bugs, briars, or traffic, so none of them become a reason to skip a pole
• Pays attention to framing, since a height photo taken too close or off center becomes a measurement problem in the office

Put a stick and a phone in their hands

Questions only get you so far. If you can, add a short practical exercise to the final round: a mock equipment setup, a pole or streetlight in the parking lot, and a request to shoot a height photo and a few pole photos to your spec. Measurement accuracy isn't the point in a parking lot; what you can see is whether they center the subject, hold the phone in portrait, keep space above and below the pole, and ask what you need before they start shooting. Those are the habits our photo feedback warnings in Katapult Pro flag after the fact, and a candidate who already has them will need far less coaching.

Keep them once you've got them

Field roles turn over faster than office roles for structural reasons: long drives, long days, and weather that ignores the schedule. Four things have helped us hold onto good people.

• Partial weeks. Frontload two to four strong field days so the design team has what it needs, then give the crew office time or an early finish.

• Summer internships. Work ramps up in April and May, interns are hungry for overtime, and both sides get to evaluate each other before a full-time offer.

• Hybrid roles. A day or two in the field is a welcome break for some designers, and fielders who spend a day in the office watching their photos become designs come back collecting better data. Three field days and one office day is one structure that works.

• Culture first. Hire technicians who resonate with your core values and make room to celebrate those things with them in the office, however infrequently they're around.

The growth path is what turns the job into a career. Field technician to field lead is the obvious step; the less obvious one runs through office processing, because the more time a fielder spends annotating their own data, the faster they become a designer or a project manager who understands both ends of the pipeline. Our post on field team health goes deeper on that structure.

How to hire great OSP designers

Sometimes it makes sense to hire an expert. Experts are also expensive, scarce whenever the industry is busy, and they arrive with habits from other workflows and cultures, some good and some not. Our default has been to find people who can handle the day-to-day demands of design work even if they've never looked at a utility pole, then grow the expertise deliberately. That approach has turned former blacksmiths, biologists, camp staff, and landscapers into expert OSP designers.

The traits under the competencies

The competencies a job posting lists are real: make ready engineering, pole loading analysis, GIS and CAD fluency, and local permitting requirements. An experienced candidate who brings them will be productive sooner. They're also teachable inside a structured workflow, while the traits underneath them are much harder to teach:

• Very comfortable with technology, especially desktop and Windows environments
• Doesn't mind looking at screens for eight or more hours a day (a love of TV, movies, or video games is a surprisingly reliable signal)
• Performs repetitive tasks for long stretches without checking out
• Detail-oriented and safety-conscious, because every clearance call is a safety call
• Communicates clearly and expects clear communication from others
• Hungry to follow up on mistakes and not intimidated by regular feedback

That last trait carries the most weight. Calling make ready is often more art than formula, there frequently isn't a single right answer, and a designer who gets defensive about redlines will plateau early.

The field-first advantage

Designers who can read raw field data produce cleaner first drafts, and in our experience they send fewer questions back to the field. Some of that comes from time in the field, which is one more reason hybrid roles pay off. Most of it comes from the workflow: a designer working from the photo record instead of a spreadsheet of typed heights can see whether an attachment is bolted or hooked, whether the midspan crossing was captured, and whether a height photo was framed well enough to trust. That visibility is the premise our engineering design tools are built on.

Vet with a sample, then onboard in sequence

A short design-sample exercise tells you more than an hour of questions. Give the candidate a small set of pole photos and existing-conditions data, then ask them to annotate what they see, flag anything wrong or missing, and explain what they'd send back to the field. For someone new to the industry, run the same exercise with more coaching and watch how they take feedback. Once they're hired, the order of onboarding matters more than the pace:

• Start with the basics. Safety, the software, and the fundamentals of overhead OSP fill the first few days.

• Pair them with a master. New designers do best working closely with experienced staff who review their work and answer questions when they get stuck.

• Begin with existing conditions. Annotation teaches the poles and midspans your team actually collected, and it's easy for a reviewer to check.

• Graduate to pole loading analysis. The designer builds a model that matches conditions they've already annotated. In Katapult Pro, integrated pole loading covers most scenarios and exports to SPIDAcalc, O-Calc Pro, or PoleForeman when a client mandates one.

• Finish with make ready engineering. The platform highlights clearance violations, which makes calling make ready more attainable for a newer designer, but it's still the part of the job that takes longest to master.

Managing the work: keep field, office, and client on one record

Good hires still struggle inside a process that lets field and design drift apart. Most OSP project management comes down to keeping three feedback loops short: field to design, design to client, and everyone to the calendar.

Shorten the loop between field and design

Build photo review into office processing so the designer annotating a job flags framing problems, a missing midspan, or a stick placed too close to the pole while the technician can still remember the day. We don't like calling these things user error, because the people making them are working long hours in brutal conditions to improve the grid. We'd rather build mistake-proofing into the workflow, and the photo warnings in Katapult Pro do part of that. The coaching conversation is still yours to have, and it's the most effective thing a project manager can do for data quality.

Feedback that arrives a month after collection is history; the same habit has already been repeated on two hundred poles. Review photos while the technician can still remember the day.

The design-to-client loop is the same problem at a different scale. Early miscommunication about what the deliverable needs to contain is how a team ends up months into a project with a workflow optimized for the wrong thing. We've written about two projects that failed for exactly that reason, one because the process was too thin for the scope and one because it was too heavy. Hear what the client expects, then agree on a sample deliverable before the first job is fielded.

Track the handoffs

Poles collected per week is the number everyone watches, and it's the least diagnostic. The metrics that catch a bottleneck early live at the handoffs:

• Field-to-design turnaround: days between collection and completed annotation. A widening gap means the office is the constraint, and more field hires will make it worse.
• Rework rate: how often a job goes back to the field, grouped by reason, since a framing problem and a missed midspan have different fixes.
• Redlines per submission from the pole owner or client, by designer and by project, which is your training signal.
• Application cycle time and first-pass approval rate. Review windows are governed by shot clocks and the pole owner's workload, so the lever you hold is the completeness of what you submit.
• Hours per pole by stage, which is the number a per-pole price is ultimately built on.

You don't need a separate dashboard product to start. Attribute history and action tracking in Katapult Pro record who did what and when on every location, which is enough to pull these numbers by job and by person.

Build the margin in before you need it

Teams overestimate their own productivity and underestimate delays. That's a well-documented human tendency, and this industry gives it room to operate. Field days get cut short by weather. A cluster of messy poles can stall a designer for an afternoon. Pole owner review runs on its own clock, and while FCC shot clocks put bounds on it, those calendar days still belong to someone else. When the plan has no margin for any of that, the team either grinds to stay on track or submits change orders, and repeated change orders erode trust faster than an honest schedule ever would.

Batching permit applications saves the office an afternoon and costs the project calendar days. When shot clocks are running, submit each job as it's ready.

A few habits that have kept our projects on course:

• Listen to the client's expectations early, confirm they're understood rather than just heard, and write the deliverable down.
• Hold margin for redlines and recollection, because some rework shows up on every project and a plan with no room for it is already behind.
• Check in on fatigue. If more throughput is needed and the team has been sprinting for months, timely feedback and workflow fixes will do more than a longer week.
• Match the workflow to the scope. A make ready process built for back-office engineering is overkill for a few dozen pole replacement locations a week, and a lightweight field form is too thin for 2,000 poles a week of joint use engineering. Be sensitive to what the client needs and agnostic about which workflow gets them there.
• Name scope creep the week it appears. When a request falls outside the agreement, say so and price it, because the alternative is absorbing it until the schedule breaks and then explaining a change order nobody saw coming.

Where the three pieces meet

A high-performing OSP operation is skilled collectors feeding accurate data to sharp designers, run by project managers who keep the loops short and the schedule honest. This is how our own engineering services crews are staffed and run, on the same platform we offer customers, which is why the workflow is built to make a new hire valuable in their first weeks rather than assuming everyone arrives an expert.

If you're staffing up for a BEAD build or a joint use program and want to talk through what the field-to-design workflow would look like for your team, book a call with our team. If training is the more immediate need, the OSP Field Bootcamp covers field collection and our post on Katapult Pro training covers onboarding for established teams taking on new scope.