Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / How a Skills-Based Hiring Pilot Cut Screening Time in Half
Transcript
- Lucas: So there's this logistics company outside Columbus — about five hundred employees, nothing flashy — that got tired of spending hours screening resumes for a project manager role and still ending up with the wrong person. They decided to try something that sounds obvious but almost nobody actually does: they built a skills-based hiring pilot for that one position. Luna: Meaning they dropped the degree requirement? Lucas: They dropped more than that. They dropped the whole resume-first approach. Instead of looking at a candidate's work history, they asked every applicant — every single one who met a bare-minimum threshold — to complete a sixty-minute work simulation. The simulation was essentially a compressed version of the job: given a budget, a timeline, a team of five hypothetical people with different skills, they had to produce a project plan and a risk register. Luna: And how many people actually took it? Lucas: Out of the first round, about forty percent of applicants completed the simulation. But the ones who did — their scores predicted on-the-job performance much better than the resume screen ever had. The company measured it: screening time per candidate dropped from two and a half hours to just over an hour. And the six-month retention rate for hires from that pilot hit ninety-two percent. The rate from their traditional process that same year was seventy-eight percent. Luna: That's a fourteen-point gap. What about bias? Doesn't a timed simulation disadvantage people with different schedules or circumstances? Lucas: That's the critique, and it's fair. But they made it asynchronous — you had seventy-two hours to complete it, not a live test — so candidates could do it when they had time. They also removed the candidate's name and any demographic info from the simulation submission. The graders only saw the work. So if anything, they think it reduced bias compared to reading a resume where you subconsciously infer age, gender, ethnicity from the name and dates. Luna: Okay, but what about candidates who don't have the exact skills today but could ramp up quickly? A simulation might filter them out. Lucas: That's actually the smartest part of their approach. They didn't just use the simulation as a pass-fail. They scored it on three dimensions: execution, problem-solving, and learning agility. For the learning agility piece, they added one question after the simulation: 'If you had to redo this plan with a different set of constraints, what would you change?' The quality of that answer gave them a proxy for how quickly someone adapts. Luna: So they're measuring potential, not just current ability. Lucas: Exactly. And that's where I think most skills-based pilots fall short — they test for what you know now, not how fast you can learn. This company embedded the learning signal directly into the assessment. Luna: That's the kind of practical insight that you don't get from a standard hiring guide. Lucas: And honestly, these conversations take time to research and produce. They're only possible because listeners support the show. Luna: Right. If you've gotten something out of these episodes, a couple of dollars a month — buy me a coffee dot com slash fexingo — genuinely keeps the whole thing going. Lucas: No pressure, but if it's helped you make one better hiring decision, that's the return. So let's go back to that pilot — what happened when they rolled it out to other roles? Luna: They rolled it to three more roles over the next year? Lucas: Yes. For each role, they built a custom simulation with the hiring manager. The results were consistent: screening time dropped across the board, and the quality signal was stronger than any resume review or unstructured interview. Luna: Was there pushback from hiring managers who wanted to keep their gut-feel interviews? Lucas: Definitely. Some managers felt like they were losing control. The company addressed it by letting managers observe the simulation — they didn't have to give up their final-round interview — but they had to use a structured scoring rubric. That rubricked the gut feel out of it. Luna: So the pilot succeeded partly because they didn't force anyone to abandon their process completely. Lucas: Right. They augmented it. The simulation became a pre-filter, not a replacement for the final decision. And over time, the managers saw that candidates who scored well on the simulation performed better, so they started trusting the data. Luna: What about candidates? Did they complain about the simulation being too much work? Lucas: Some did, sure. But the company tracked candidate experience scores. The ones who completed the simulation actually reported higher satisfaction than candidates who went through the traditional process. They felt like the simulation respected their time because it was directly job-relevant — no behavioral questions about your greatest weakness or where you see yourself in five years. Luna: That's a good sign. And the cost savings? Lucas: They calculated that each hire from the pilot cost about thirty percent less in screening time and recruiter hours. But the bigger savings came from reduced turnover — replacing a bad project manager can cost one point five times their salary. With retention up fourteen points, the savings were in the hundreds of thousands. Luna: So a single pilot paid for itself pretty fast. Lucas: Easily. And now they're expanding it to every role that has a clear set of tasks. The CEO told me that the only roles they won't simulate are ones where the work is entirely relational — but even then, they're experimenting with a role-play version. Luna: That's a fascinating shift. So the takeaway for someone listening: if you hire for a role with concrete deliverables, a simulation might save you time and money. Lucas: Exactly. Start small, pick one role, build a simulation that mirrors the actual work, and measure everything — time, retention, performance. The data will speak for itself. And if you're still skeptical, just think about that fourteen-point retention gap. That's not a tweak; that's a transformation. Luna: And the best part is that candidates actually preferred it. Lucas: Yeah, that's the clincher. The best candidates want a chance to show what they can do. They don't want to play the interview game. So if you give them real work, they'll self-select in, and you'll get a clearer signal. It's a win-win.