During an interview debrief recently the hiring manager was genuinely frustrated. "I told her the role was skills-based, I asked her directly to walk me through how she's handled a coverage dispute and she just recited her job titles again." The candidate wasn't underqualified. She had the experience. What she didn't have was any idea how to actually answer the question she'd been asked.

This gap between what employers are now asking for and what candidates think they're being evaluated on is one of the most common breakdowns I see in today's hiring process, on both sides of the table. And it's not a small or fringe issue. It's becoming the default way hiring works.

The Shift Is Real, and It's Accelerating

Skills-based hiring isn't a passing trend anymore it's rapidly becoming the standard. Roughly 70 percent of employers now use skills-based hiring practices, up from 65 percent just a year earlier, and other industry surveys put the number closer to 73–75 percent, with more than 40 percent of employers now prioritizing skills over formal degrees entirely. The reasoning is straightforward: employers evaluating candidates on skills rather than titles or credentials see their qualified talent pool expand dramatically in some analyses, by nearly 19 times and report meaningfully better outcomes, including improved retention.

But here's the part that doesn't get talked about enough: candidates haven't caught up to this shift. Research from the National Association of Colleges and Employers found that job seekers are largely unfamiliar with the concept of skills-based hiring, even when they're being explicitly asked to demonstrate their skills in an interview. Employers changed the test. A lot of candidates are still studying for the old one.

Why This Gap Exists

It's worth understanding why this disconnect keeps happening, because it sn't really anyone's fault it's a structural lag.

For decades, candidates were coached to answer interview questions by summarizing their background: "I've spent six years in claims, I've handled X type of file, I worked at Y company." That approach was built for a resume and-credentials hiring model, and for a long time, it worked fine,because that's genuinely what was being evaluated.

Skills-based hiring asks something different. It wants evidence aspecific situation, a specific action, a specific measurable outcome. But most candidates were never taught that distinction, and a lot of interview prep advice still floating around hasn't caught up either. So when a hiring manager asks, "Tell me about a time you identified a coverage gap before it becamea claim," a lot of candidates hear that as a variation on "tell me about your experience" and answer accordingly with a summary instead of astory.

That mismatch is where good candidates get screened out for reasons that have nothing to do with their actual competence.

For Hiring Managers: Design the Interview to Actually Get What You're Asking For

If you've adopted skills-based hiring in name but candidates keep giving you resume summaries in response, the fix usually isn't a better candidate it'sa better-designed process.

Tell candidates explicitly, and early, what kind of answer you're lookingfor. Don't assume they know what "skills-based" means in practice. A short line in the interview invite or the opening minutes  "we're going to ask you to walk us through specific situations, not just describe your background" resets expectations before the first question lands.

Use structured behavioral or situational questions, not open-ended ones. "Tell me about your underwriting experience" invites a summary. "Walk me through a specific file where you had to decide between binding coverage and declining it what did you weigh,and what happened?" invites evidence. The more specific the question, the harder it is to answer with a generic overview.

Build in a real work sample or simulation where possible. For insurance roles particularly, a short scenario reviewing a mock loss run, prioritizing a stack of claims,evaluating a submission reveals far more than a conversation about past experience, and it removes the ambiguity of "am I supposed to be telling a story or listing skills."

Coach your interview panel to probe, not just collect. If a candidate answers with a summary, a well-trained interviewer follows up: "Can you walk me through one specific example of that?" That single follow-up often unlocks exactly the evidence you were looking for, and it's a fairer way to evaluate someone who simply didn't know the expected format, rather than silently marking them down.

Separate skill evaluation from culture and communication evaluation. Candidates who are excellent at the actual job aren't always naturally excellent at real-time story telling under interview pressure. Consider giving candidates the behavioral questions inadvance, or allowing a brief prep moment, so you're evaluating their skills and judgment rather than their ability to improvise a well-structured anecdote on the spot.

For Job Seekers: Learn to Answer the Question You're Actually Being Asked

If you're interviewing for a skills-based role, the single most important adjustment you can make is this: stop summarizing, start narrating.

Prepare specific stories, not general talking points. Before any interview, build a mental(or written) bank of 6–8 specific situations from your career a problem you solved, a mistake you caught, a difficult client you managed, a process you improved. Have real detail ready: what the situation was, what you specifically did, and what the measurable result was.

Use a simple structure to keep your answers evidence-based. A framework like Situation–Task–Action–Result (STAR) works well because it forces you past the summary and into the specifics. State the situation briefly, explain what you needed to do, describe the action you personally took, and close with the outcome.

Listen for the format of the question, not just the topic. If an interviewer asks "tell me about a time when..." or "walk me through how you handled...,"that phrasing is a direct signal they want a specific story, not a career overview. Answering that kind of question with "well, throughout my career I've generally..." is a mismatch candidates make constantly, and it costs them.

Quantify results wherever you honestly can. "I reduced our claims cycle time" is fine. "I reduced our average claims cycle time from 14 days to 9 by restructuring our initial contact process" is the kind of specific, measurable answer that skills-based interviewers are actually trying to surface.

Ask directly, if you're unsure, what kind of answer they're looking for. There's no penalty for asking, "Would it help if I walked through a specific example?" It signals self-awareness, and it often prompts the interviewer to clarify exactly what they're evaluating.

The Bottom Line

Skills-based hiring is not going away if anything, the data suggests it's becoming the default rather than the exception across most industries, including insurance. That's good news for candidates who have real, demonstrable competence but lack traditional credentials, and good news for employers trying to build teams around actual capability rather than pedigree.

But the model only works if both sides understand the new rules. Hiring managers need to design interviews that actually elicit evidence, not just ask for it and hope. Candidates need to learn that "tell me about a time" is a request for a story, not a summary. Closing that gap isn't complicated it just requires both sides to recognize that the interview format changed, even if nobody sent out a formal memo announcing it.

‍