
Back in 2026, I worked with a guy named Chandler who was a Recruitment Process Outsourcing (RPO) Analyst. His job was essentially to map out the entire candidate journey for a medium-sized tech company and find bottlenecks. For example, he noticed that the time-to-hire was dragging because hiring managers were taking an average of 6.7 days to review resumes after the initial screening. He built a simple dashboard to track it, and within two months, that number dropped to 3.2 days. That’s the kind of impact he had. He wasn’t just a coordinator; he was a data-driven problem solver.
Chandler’s role involved four main areas:
One thing I remember clearly: he never just said “we need more candidates.” He would say “if we improve the job description clarity by adding bullet points for must-have skills, we can increase the application-to-screen ratio by 15%.” That level of specificity made him invaluable. His job was less about filling seats and more about optimizing the system so that the recruiters could focus on building relationships. If you’re trying to understand what a role like Chandler’s entails, think of it as the engineering behind the hiring process—not the sales, not the admin, but the design and measurement.

I heard Chandler managed something called the candidate experience score. He ran quarterly surveys and discovered that candidates who waited more than 24 hours for a response after an interview had a 50% lower acceptance rate. So he automated a “thank you, we’ll follow up” message. That small change alone boosted our offer acceptance rate by 12% in 2026. His job was basically turning feedback into actions.

From what I saw, Chandler’s job was salary benchmarking. He pulled data from 15 industry reports and built a table comparing our compensation against market rates for similar roles. When we found that our senior software engineer offers were 8% below the 50th percentile, he recommended a range adjustment. That simple fix cut our negotiation time in half. He was the numbers guy who made sure we didn’t lowball candidates.

I think Chandler focused on skills-based hiring. He argued that requiring a degree for a project manager role eliminated 30% of qualified applicants. So he redesigned the job description to list specific competencies instead of education. The result? A 25% increase in diverse candidates and a faster fill rate by 11 days. His job was challenging outdated requirements and proving it with data. It wasn’t glamorous, but it made recruitment fairer.

For me, Chandler’s job was all about compliance and risk. He reviewed every job posting to ensure they didn’t accidentally include language that could be discriminatory—like “recent graduate” or “digital native.” He


