SKILLS-FIRST HIRING

Look beyond the title. Find the capability.

A practical guide to finding overlooked talent through relevant skills, work samples and structured human judgement.

The resume is a starting point, not the whole assessment

A degree, employer name or job title can provide context. None tells you, on its own, how well someone can perform your particular role. Skills-first hiring begins with the capabilities needed for the work, then asks candidates to demonstrate them. It does not mean discarding resumes, ignoring relevant education or replacing every conversation with a test.

Changing the advert is only the beginning

Research published by the Burning Glass Institute and Harvard Business School in 2024 found that removing degree requirements did not consistently translate into sustained changes in hiring. The research concerns US employers; it should not be treated as a forecast for every market. Its practical lesson is useful: the shortlist, assessment and final decision must change alongside the wording of the advert.

Define what successful work looks like

Before searching, agree a small set of observable outcomes with the hiring manager. Separate capabilities needed on entry from those the team can teach. Keep qualifications where they are genuinely necessary for the responsibilities, rather than treating every credential as either essential or irrelevant.

  • Outcome: diagnose and resolve production API failures, rather than simply hold a Senior Developer title.
  • Essential capability: explain debugging choices, testing and operational trade-offs.
  • Trainable requirement: familiarity with an internal framework or deployment convention.
  • Evidence: a relevant project discussion, a short realistic exercise and consistent interview questions.

Find capability beyond familiar titles

Search for the problems people have solved, the environments they worked in and their individual contribution. A different title may hide relevant experience, while an identical title may describe a very different job. Adjacent skills are a reason to investigate, not proof of readiness.

  • A support engineer who automates incident diagnosis may have relevant scripting and reliability experience.
  • A developer who owns deployment pipelines may bring useful platform engineering capability.
  • A designer from another sector may demonstrate strong systems thinking through a well-explained portfolio.
  • Ask what transfers, what remains unproven and what support would be needed after joining.

Use a work sample that resembles the work

The US Office of Personnel Management describes work samples as tasks that mirror job activities and notes their suitability for capabilities expected on entry. Our recommendation is to keep the exercise focused and proportionate. A long unpaid assignment can lose good candidates and reward spare time more than relevant capability.

  • For an engineer: review a small fictional service and explain a fault, tests and a safe fix.
  • For a product manager: prioritise a short fictional backlog and explain assumptions and trade-offs.
  • For a designer: discuss an existing portfolio case and clarify the candidate’s own decisions.
  • Use synthetic information, explain the time commitment and avoid asking candidates to deliver usable client work.

Agree the scoring before seeing the candidate

A practical test becomes another subjective filter if reviewers improvise the standard afterwards. Define what evidence would meet each criterion, use the same core brief and ask reviewers to record reasons independently before discussion. A sample rubric might assess problem framing, technical reasoning, quality checks and communication. Set weights and thresholds for the actual role; no universal scoring formula makes a decision objective.

Make the process workable for candidates

Explain the stages, timing, tools and assessment criteria in advance. Agree how AI assistance is handled: if it is allowed, ask candidates to explain and verify the output; if independent work is needed, make that expectation explicit. Offer an appropriate route to request adjustments. Lack of a public portfolio should not automatically exclude someone whose previous work is confidential.

Use AI to organise evidence, then verify it

AI may help reviewers organise stated projects and skills against an agreed brief. It should not turn a missing keyword into an assumed lack of ability or infer competence from a polished summary. Verify material claims with the candidate and keep a route back to the original evidence. Technology can suggest a question; it cannot establish that a candidate has demonstrated the answer.

Pilot one role and review the result

Start with a recurring role where the work and assessment criteria are clear. Compare the process with your previous approach, while recognising that small samples and changing role requirements limit conclusions. Look beyond the number of applicants.

  • Are relevant candidates reaching the shortlist from a wider range of backgrounds?
  • Where are candidates dropping out, and how much time does the assessment require?
  • Do reviewers agree, and can they explain their decisions using evidence?
  • After joining, do observed performance and support needs match the assessment?
  • What needs changing before extending the approach to another role?

A clearer brief. A broader search. A considered decision.

For ULTISOURCE, the useful starting point is a conversation about the work your next hire must deliver. Define the essential capabilities, identify credible evidence and agree the assessment responsibilities with your team. UrHires and HARD GATE can support recruitment coordination and structured resume review; neither replaces an appropriate assessment of demonstrated capability. The aim is to find people who can do the work, including those a narrow title-based search might overlook.

FURTHER READING

References & further reading

This guide offers practical evaluation questions. The sources below provide the underlying risk-management and assessment principles; they do not endorse ULTISOURCE or its products.

Discuss a skills-first hiring approach.

Start a conversation
YOUR NEXT CHAPTER

What are you
building next?

Let’s start a conversation

YOUR PRIVACY

We currently use only storage needed for website security and administration. No optional analytics or advertising cookies are enabled, so there are no optional cookies to accept or reject.

Necessary security and administrationAdministrator sign-in uses a secure session cookie lasting up to eight hours. Cloudflare Turnstile checks help protect our forms against spam.Always active
Analytics and marketingNo analytics or advertising services are currently connected.Not used

If we introduce optional cookies, we will ask for your choice before enabling them.

Read our cookie policy