Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / Why Hiring for Potential Beats Hiring for Experience
Transcript
- Lucas: There's a number I keep coming back to. A 2024 study from the National Bureau of Economic Research tracked nearly 10,000 hires across a dozen companies and found that employees hired primarily for potential — measured by cognitive ability, curiosity, and learning agility — outperformed those hired for direct industry experience by roughly 18 percent after two years on the job. Luna: Eighteen percent is a big gap. But I'm guessing the 'potential hires' looked riskier on paper at the start? Lucas: Exactly. They often had less directly relevant experience, maybe a career pivot or a non-traditional background. But the study suggests that traditional resume screening — where you filter by years of industry experience first — systematically weeds out people who could become your best performers. Luna: It makes intuitive sense. Someone who's done the same role at a competitor for five years might be competent, but they're also set in their ways. A person who's constantly adapted to new domains might bring fresh thinking. Lucas: Right. The researchers called it 'experience bias.' And it's pervasive. I spoke to a talent leader at a big tech firm who told me their internal data showed that hires with less than two years in the industry had a 40 percent higher promotion rate after three years than hires with more than a decade of experience. Luna: So the experienced hires plateau faster. They're playing the hits. The potential hires are still learning. Lucas: Yeah. But the trick is: how do you actually assess potential in an interview? You can't just look at a resume and guess. One method that's gaining traction is what I call the 'learning project' question. Ask the candidate: 'Tell me about something you learned from scratch in the last six months — not for a course, but on your own.' Luna: I like that. It reveals intrinsic curiosity and the ability to structure your own learning. Not just what they know, but how they learn. Lucas: And you can probe deeper: 'What was the hardest part? How did you know you understood it well enough? Did you teach it to anyone else?' Those follow-ups tell you way more than a list of job duties. Luna: Bridgewater Associates — the hedge fund — is famous for this. They hire almost entirely for cognitive ability and values alignment, not for finance experience. Their founder Ray Dalio used to say he'd rather hire a smart person with no finance background than a finance expert who can't think critically. Lucas: Right. And Bridgewater has consistently outperformed. But it's not just about hedge funds. I think of a software engineer I once read about — she spent seven years as a journalist covering local news, then taught herself to code in a year. She got hired at a mid-size SaaS company on the strength of a coding project she built, not her resume. Within two years, she was leading their data pipeline team. Luna: That's a powerful anecdote. But I do want to push back a little. Hiring purely for potential has risks. If you need someone to step into a complex regulatory role on day one, you probably can't afford a six-month ramp-up. Lucas: No, that's fair. The study found the 18 percent outperformance held for roles where learning was critical — product management, engineering, marketing — but for roles like compliance or specialized accounting, experience still mattered more. So it's not a one-size-fits-all. Luna: So the question becomes: how do you weigh the two? Do you set a minimum experience floor and then bias for potential above that? Lucas: I think that's a smart approach. Set a reasonable threshold — say, two years in a related function — then evaluate potential more heavily beyond that. One company I know uses a 'potential score' alongside their skills assessment. The score includes things like: number of distinct domains they've worked in, evidence of self-taught skills, and a structured interview rubric for learning agility. Luna: And you mentioned learning agility — how do they test for that in an interview? I've seen some terrible proxy questions, like 'How many golf balls fit in a Boeing 747?' which tests nothing. Lucas: That's a classic example of a fake smart question. A better approach is to give them a short, unfamiliar scenario — say, a business problem in an industry they don't know — and ask them to reason through it out loud. You're not looking for the right answer; you're looking for how they structure their thinking, how they ask clarifying questions, and whether they can adapt when you push back. Luna: I used a variant of that when I was hiring a junior analyst. I gave them a dataset with missing values and asked how they'd clean it. The candidate who just said 'I'd drop missing rows' was less interesting than the one who said 'I'd check if the missingness is random or systematic, and decide based on that.' Lucas: Exactly. That second candidate is showing potential — they're applying a framework, not a rote step. And that kind of thinking can be developed. Experience is what you've done; potential is what you could become. Luna: You know, if today's discussion has given you a practical way to rethink your own hiring process — maybe a new question to ask or a way to weigh potential differently — that's exactly the kind of takeaway this show aims for. Lucas: And we're able to keep these conversations ad-free because of listeners who chip in. If you find value here, you can support the show at buy me a coffee dot com slash fexingo. That's all lowercase. It helps us keep doing these deep dives without any sponsor interruptions. Luna: Yeah, it really does. And we appreciate every bit of support. So back to potential versus experience — I think one final caution is about confirmation bias. If you're excited about a candidate's potential, you might overlook red flags. Lucas: That's a real danger. The same study found that hiring for potential only worked when the interviews were structured — using the same questions and scoring rubric for every candidate. Unstructured 'I liked their vibe' interviews actually led to worse outcomes than just hiring based on experience. Luna: So structure is the guardrail. You can bias for potential, but you need a consistent way to evaluate it. Lucas: Exactly. And that's the takeaway I'd leave you with: don't just ask 'what have you done?' Ask 'how do you learn? How do you think? How do you adapt?' The answers might surprise you — and your next star hire might not look like you expected. Luna: I'm sold. Next time I'm hiring, I'm going to try that learning project question. Lucas: Let us know how it goes. That's all for today on Hiring & Firing. We'll be back with another episode soon.