The 400-Hire Problem: Why Large-Scale Recruiting Starts With Operations
- Jeramy Johnson
- Aug 2
- 4 min read
A hiring target is not a talent acquisition strategy. It is a business-capacity decision with recruiting consequences.
In one of my prior operating roles, the business set out to hire 400 field-service technicians in a year. The previous high was 156.
It would be easy to tell that story as a recruiting campaign. The sourcing work mattered. The employer message mattered. Recruiter capacity mattered. But none of those were the real starting point.
The starting point was the operation. The business had customer demand, backlog, revenue opportunity, safety requirements, regional capacity constraints, and an eight-month time to productivity for new hires. If we treated 400 as a requisition target, we could have filled roles and still failed the business. A hiring target is not a recruiting strategy. It is a business-capacity decision with recruiting consequences.
The number had to come from demand
The workforce plan was built from several sources, not from a single top-down headcount request. We considered backlog, prior-year hiring, expected sales demand by offer, time to revenue, current utilization by service district, and work that had been moved because emergency service took priority over planned work.
We also incorporated the realities that can make a hiring plan look better on paper than it performs in practice. New employees required technical training and could not immediately carry a full workload. Safety requirements limited how quickly people could be deployed. Some hires would resign early. Some would experience delayed training. The plan included an 8% hedge for those risks and 80 expected backfills.
This work changed the conversation. Instead of asking how quickly recruiting could fill 400 openings, the leadership team could see when capacity would become available, where it was most needed, and which assumptions could put the plan at risk.
Recruiting was one part of a larger system
Once the demand was clear, the organization had to be prepared to absorb the hires. That required coordinated work across HR, operations, finance, training, marketing, IT, fleet, and frontline leadership.
We had to answer basic questions that become difficult at scale:
Could the training organization handle the volume without weakening safety or quality?
Would managers have enough capacity to onboard and coach new employees?
Could laptops, tools, vehicles, uniforms, and system access be ready on time?
Were compensation levels competitive in the locations and skill markets that mattered?
Could recruiting explain the work honestly and attract people who were likely to stay?
Would the business have productive work available as employees completed training?
These are not secondary details. They determine whether a hire becomes productive capacity or an expensive delay.
The talent message had to be specific
The campaign could not rely on generic language about joining a great company. We developed employee personas with recruiting and marketing, then built a message around what actually made the role different: technical growth, meaningful customer work, career opportunity, safety, and the experience of serving critical infrastructure.
The campaign used professional video, targeted digital advertising, search, radio, job platforms, and geographic skill data. We monitored which sources generated applicants, qualified candidates, offers, and hires. That distinction mattered. A channel that creates high application volume is not necessarily creating productive employees.
The message also had to match the reality. Employer branding is useful only when the job experience supports the promise.
Compensation and retention were part of the hiring strategy
Recruiting cannot solve a market-position problem by working harder. The workforce analysis helped support a $6 million investment in technician compensation. That work improved the company’s ability to hire and retain the skills the growth plan required.
We also tracked retention of campaign hires, not just starts. Offer acceptance reached 95%, and new-hire retention remained 97% across the first 18 months. Every retained employee completed training and moved into deployment.
Those measures were more useful than celebrating application volume. The goal was not to create a large funnel. The goal was to create safe, productive, retained capacity.
The dashboard had to connect recruiting to operations
The reporting included demand versus actual starts, pipeline volume and conversion, source effectiveness, geographic and role-level progress, offer activity, candidate experience, time to productivity, and retention.
The executive view was simpler. It focused on progress against plan, capacity risk, investment decisions, and business impact. Recruiting needed the operating detail. Leadership needed to know whether the workforce plan was on track and where intervention was required.
By October, the organization had delivered 400 hires. That result mattered, but the operating system behind it mattered more. Without demand planning, training capacity, compensation, onboarding, equipment, and management readiness, the same number could have created disruption instead of growth.
What I would carry into another large-scale hiring effort
Build the target from business demand, not from a round number.
Separate starts from productive capacity and account for time to proficiency.
Plan the full employee system, including training, managers, equipment, access, and work availability.
Measure source quality through qualified candidates, hires, productivity, and retention.
Treat compensation and employee experience as part of the recruiting strategy.
Give leaders a business dashboard, not a list of recruiting activities.
Large-scale hiring is often assigned to Talent Acquisition because recruiting owns the visible funnel. The best results come when the business treats it as an enterprise capacity program. That requires HR to move beyond filling jobs and help the organization understand what it will take for those hires to create value.
The Practical Takeaway: Plan for productive, retained capacity. A start date alone does not deliver revenue, service, safety, or customer outcomes.