Why Learning Speed Now Outweighs Résumé Experience in Hiring

A résumé is a record of work that's already finished. The job you're hiring for will look different in twelve months, and some of the tasks may not exist yet. That gap is why I think learning velocity, the speed at which someone goes from confused to competent, is a better predictor of performance than past experience.

Some of the best hires I've made had never done the job before. Their résumés got them in the door, but their ability to learn got them the offer. A résumé reads like a map of where someone has been. Hiring managers tend to treat it like a forecast, and that's the mistake.

I founded BriteCo, an insurtech company, in 2017. In that time the ground has kept moving. Tools our team relied on two years ago have been replaced or rebuilt, sometimes more than once. When I review a candidate, I'm asking two questions: can they learn this job quickly, and can they learn the next version of it even faster?

I've favored potential over experience since the early days of the company, and our hiring has never looked especially conventional. Experience still matters. It's one of the first things I check. But the second factor carries equal weight: how fast someone picks up what they haven't done before.

Résumés have a shelf life, and it's getting shorter

A résumé says, "I mastered these tools, systems, and processes." In a field like ours, a specific skill loses value the moment it's listed. Approaches that counted as advanced a few years ago are now baseline expectations.

This is where over-indexing on pedigree becomes a real problem. You can assemble a team of people who know exactly how the work used to be done, then watch them stall when the work changes. You hired a snapshot of the past, and snapshots don't adapt.

AI is shifting job functions quickly enough that specific skills matter less than the meta-skill of learning how to learn. Credentials describe what someone has done. Learning velocity tells you how they'll handle what comes next. If you have to choose one, I'd bet on the predictive skill.

What learning velocity actually means

Most companies say they hire people who love to learn. Few test for it. Learning velocity measures how quickly someone moves from confusion to competence when the tools change. It covers three things: how fast they absorb something new, how willingly they set aside outdated knowledge, and how quickly they apply the new material to a real problem.

Plenty of smart people can learn. Fewer can learn and apply new knowledge in the same week. That combination is what I'm looking for.

The good news is that this trait can be observed. At BriteCo, much of our interview process is designed to surface it. We'd rather hire people who think on their feet and move quickly than people who simply tick the boxes on a job description.

How we screen for it

Start by changing the questions. Walking a candidate through their experience with prepared examples rewards people who have memorized their own résumé. Ask instead about something they taught themselves recently, without anyone telling them to. How did they start? What did they get wrong? How long did it take before the new skill was useful? You learn more from how someone describes picking up an unfamiliar tool than from any list of past titles.

Next, bring an unfamiliar problem into the interview and watch how the candidate approaches it. Do they ask sharp questions? Are they comfortable not knowing the answer right away? Or do they shut down because they've stepped outside their lane? The response tells you more than the answer does.

Third, use short trial projects built around real work with a real deadline. Keep the scope small enough to finish in a few days, and pay people for their time. I haven't found a better signal than watching someone ramp up. We've hired people whose résumés undersold them, and they went on to outpace better-credentialed peers once our engineering stack changed. They treated the new stack as a puzzle to solve, not a threat to their standing.

Reference calls can test for it too. Ask a former manager what the person picked up on the job that nobody asked them to learn, and how quickly the rest of the team came to rely on it. Pay attention to whether the answer comes without a pause. A quick, specific answer usually means the learning was real.

Where adaptability can backfire

Learning velocity doesn't win every time. In a heavily regulated industry like insurance, some roles depend on deep domain knowledge, and you don't want someone learning the fundamentals on the fly. The fix isn't to swap experience for adaptability. It's to look for people who have both. When you can't find both, decide which one the role requires and be honest about that choice. Write the decision down before you open the search. A strong interview can talk you out of your own criteria, and it's easy to fall for a sharp candidate who happens to lack the one thing the role needs. What a role requires also changes as a company grows. A startup and a growth-stage company need different profiles, so tell candidates which stage they're joining.

Adaptability also backfires when you hire fast learners and then leave them bored. Once they've mastered the current tools, they get restless. If your environment is rigid, with locked-down processes and technology that never changes, you'll lose the people you worked hardest to recruit. Fast-learner hiring only works if the culture rewards relearning. Give them the next hard problem before they go looking for it somewhere else.

I've believed for years that the right person in the wrong environment still fails. Hiring someone who learns quickly is only half the commitment. The other half is giving them room to use what they learn. A year from now, the job may look very different from how it looks today. The people who can keep up with that change are the ones worth building a team around.