Hiring managers still read resumes as if they were forecasts, even though a resume only records what someone has already done. The job you're hiring for next year may look nothing like the one on the posting today, and a list of past titles says little about how a candidate will handle that gap.
I founded BriteCo in 2017, and building an insurtech company has taught me that the ground moves fast. Many of the tools our team relied on two years ago have been replaced or rebuilt. So when I evaluate a candidate, I ask two questions: can they learn this job quickly, and can they learn the next version even faster?
That's been our approach since the early days of the company. Experience matters, and I look at it. But I weigh one other factor just as heavily: how fast someone picks up what they haven't done before.
The resume is a snapshot, and snapshots age quickly
A resume says, "I mastered these tools, systems, and processes." In a field like ours, a specific skill starts losing value the moment it appears on a page. An approach that counted as sharp in 2020 is now the baseline, and the baseline keeps rising.
Over-indexing on pedigree creates a predictable 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. They aren't lacking talent. They're optimized for a process that no longer exists.
That's why I think specific skills matter less than the meta-skill of learning how to learn. Credentials describe the past. Learning velocity tells you how someone will handle what comes next. If you have to choose between the two, choose the predictive one.
What learning velocity actually measures
Almost every company says it hires people who love to learn. Few test for it. Learning velocity is the speed at which someone moves from confused to competent when the tools change. It captures more than raw speed of absorption. It also reflects how willingly a person sets aside outdated knowledge and how quickly they apply new knowledge to a real problem. Plenty of smart people can learn. Fewer can learn something and put it to work in the same week, and that second part is where the value shows up.
The good news is that this trait is observable. At BriteCo, much of our interview process is designed to surface it, because we'd rather hire someone who thinks on their feet than someone who simply checks the boxes on a job description.
Screening for it in practice
Start by changing the questions. Asking candidates to walk through their experience mostly rewards people who have rehearsed their own resume. Ask instead about something they taught themselves recently, with no one assigning it. 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. Pay attention to whether they ask sharp questions. Notice whether they're comfortable not knowing the answer right away, or whether they shut down because they're outside their comfort zone.
Short trial projects are the most useful tool I've found. Use real work with a real deadline, keep the scope small enough to finish in a few days, and pay the candidate for their time. Watching someone ramp up tells you more than any interview answer. We've hired people whose resumes undersold them, and they outpaced better-credentialed peers once our engineering stack changed. They treated the new stack as a puzzle to solve, not a threat to their identity.
Reference calls can test for this as well. 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 back without a pause. A hesitant answer usually tells you something.
Where the bet breaks down
Learning velocity doesn't win every time. In heavily regulated industries such as insurance, some roles depend on deep domain expertise. You don't want someone learning the details of compliance on the fly. The answer isn't to dismiss experience. It's to stop treating experience as a stand-in for adaptability. The best candidates have both, and when you can't find both, you need to decide honestly which one the role requires. Write that decision down before you open the search. A strong interview can talk you out of your own criteria if you haven't committed to them in advance. And what a role needs changes as the company grows. A startup and a growth-stage company need different kinds of people, so be direct with candidates about the stage they're joining.
Adaptability also backfires in a second way. Hire fast learners and then give them nothing new to learn, and they get restless quickly. Once they've mastered the current tools, a rigid environment with locked-down processes and technology that never changes will push out the people you worked hardest to recruit. Velocity hiring only works if the culture rewards people for relearning the job. Give them the next hard problem before they go looking for it somewhere else.
A good hire in the wrong environment still struggles. 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 will likely look different from how it looks today. The teams that handle that shift well will be the ones that hired for the capacity to keep up with it.
