Skills-Based Hiring for Mid-Sized Companies: Turning a Buzzword into a Working Process

Moritz Steinbach

Moritz SteinbachCo-Founder & CEO of Talentigo

·

Capability-focused hiring promises wider talent pools and better fit. In practice, it often fails because teams keep working from long wish lists and then still favour familiar employers or titles on a CV.

In mid-sized companies the problem is often sharper: limited HR capacity and hiring managers making decisions alongside day-to-day work. Without a fixed role profile and shared scorecard, selection quickly falls back on the familiar – same industry, similar employers, known titles. Skills-based hiring helps here not as a buzzword, but as simplification: fewer requirements, tested more clearly.

What skills-based hiring actually means

Start with a simple question: which observable capabilities does someone need to be effective in this role in their first twelve months? Degrees, industries and titles can be useful signals. They do not replace the question.

Four steps to a reliable role profile

  1. Define outcomes: which three to five results should this person achieve?
  2. Prioritise skills: which are essential and which can be developed?
  3. Plan evidence: how will each capability be observed?
  4. Calibrate scoring: discuss examples of strong and weak evidence before interviewing.

The sequence deliberately happens before the first interview. When the business defines expected outcomes and recruiting defines observable signals together, interviewers do not need to improvise what a strong answer should look like later on.

The scorecard as a shared language

A short scorecard does not eliminate every poor decision and cannot replace experience. It does ensure that a team discusses the same observations. For each capability, one behavioural question, a clear standard and space for evidence are often enough.

  • Must-have: the core task is unrealistic without it.
  • Developable: relevant but learnable during onboarding.
  • Signal: an indication in a profile to test in conversation.
  • Not decisive: useful, but never an exclusion criterion.

Structured profile analysis can support consistent pre-screening. The critical step remains that recruiting and the business define the criteria together and test them in conversation.

Short example: customer success role

Instead of “3 years B2B SaaS, degree, Salesforce,” the team defines: Must-have: onboard customers in the first 90 days, resolve escalations in a structured way. Developable: deep CRM administration. Signal: industry switch from consulting. The interview includes a behavioural question for each must-have – not just a general “tell us about yourself” round.

Takeaway: A good role profile answers not “who do we already know?” but “what observable performance do we need in the first months?”
Do I need to drop degrees and industry experience entirely?

No. They can be useful signals – what matters is whether verifiable capabilities take centre stage in conversation. The scorecard defines what is essential and what is only a signal to test.

What is the difference between must-have and signal?

Must-have: the core task is unrealistic without this capability. Signal: an indication in a profile to test in conversation – but not an automatic exclusion criterion.

Related: assessing AI applications in interviews (AI-generated applications) and widening the pool through active sourcing.

Conclusion

Skills-based hiring becomes practical when teams spend less time debating perfect CVs and more time discussing evidence for relevant capabilities.

Improve recruiting where it matters?

If you want to know whether active sourcing and AI-assisted profile analysis make sense for your roles, book a no-obligation demo – we’ll focus on your specific case.