Hiring for Skills

Recruiting has long leaned on pedigree: years of experience, degrees, job titles, the schools candidates attended. A conversation among talent acquisition leaders lays out why that approach misses qualified people and what to do instead.

The discussion moves through concrete examples of skills-based hiring in practice:

• An actuarial team widened its candidate pool and improved diversity by recruiting math majors rather than only actuarial science graduates, betting on demonstrated aptitude over degree title.
• An aerospace engineering team filled hard-to-source roles by identifying engineers from the automotive brake industry, whose experience with vibration control translated directly to jet engine requirements.
• Recruiters partner with hiring managers to reverse-engineer what a role actually requires, then decide which requirements are essential and which can be trained after hire.
• Labor market data on job openings, candidate demographics, and educational background gets used to build a business case with hiring managers before sourcing even starts.
• Interview questions probe what a candidate is genuinely passionate about and where they want to grow, then match that against real internal career paths so motivation and opportunity line up.
• Coding exercises and screen-share assessments supplement résumé review on technical roles, while recruiters are encouraged to ask hiring managers tough questions about which requirements are truly non-negotiable.

A recurring point: hiring for skills is not a substitute for evaluating the whole person. It is a way of correcting for pedigree bias that has historically caused capable candidates with non-traditional backgrounds to be screened out. A candidate lacking two of five listed requirements but bringing three unexpected strengths can end up adding more value to a team than one who checks every box.

The conversation also touches on how automation and algorithmic screening are reshaping this work, and why recruiters who understand the actual competencies behind a job description are better positioned to source creatively rather than repeat searches that keep turning up the same limited pool.

You might be getting a two-for-one with a candidate because you were willing to go outside the cookie-cutter description and see what they actually bring to the team.