Rethinking Hiring: Skills Over Degrees in Engineering

We implemented a skills-based hiring approach, eliminating traditional filters like degrees and years of experience, leading to more qualified candidates.

A Slack Thread That Changed Our Hiring Approach

One afternoon, during a routine Slack discussion about our hiring process, a message from one of our recruiters caught our attention. “We’re rejecting too many qualified candidates because they don’t have a degree or a specific number of years in the industry.” This sparked a deeper conversation about the validity of our hiring filters, igniting a realization that could reshape our approach to recruitment.

The Importance of the Issue

Our hiring process had long relied on traditional metrics like degrees and years of experience. This practice not only limited our candidate pool but also led to missed opportunities with talented individuals who had the skills but lacked formal credentials. We felt the pressure to adapt; our product relied on a diverse range of ideas and perspectives. As we aimed to build a more inclusive engineering team, the stakes were high—if we continued down the same path, we risked stagnating our innovation and growth.

Breaking Down the Problem

The crux of the issue lay in the disconnect between traditional hiring metrics and actual job performance. For instance, one candidate we considered had extensive experience with relevant technologies and a proven track record of successful projects but did not hold a formal degree. We ultimately passed on this candidate, prioritizing the degree over demonstrated skills. This scenario exemplified how we were missing out on top talent simply because our filters were outdated.

Initial Attempts at Change

In our eagerness to address these concerns, we initially tried to tweak our existing filters. We adjusted the years of experience requirements and attempted to develop a scoring system based on interview performance. However, these efforts fell flat. Candidates still felt discouraged, and we didn't see any meaningful improvement in our hire quality. We realized that merely adjusting the numbers wouldn’t suffice; we needed a fundamental shift in our approach.

Implementing a Skills-Based Framework

After several discussions and brainstorming sessions, we decided to adopt a skills-based hiring methodology. This involved creating a comprehensive skill taxonomy that mapped out the specific competencies required for each role. We gathered evidence of candidates' skills through practical assessments and project portfolios instead of relying solely on resumes.

# Example of skill assessment criteria
skills = {
    'programming_languages': ['Python', 'JavaScript'],
    'frameworks': ['React', 'Django'],
    'tools': ['Git', 'Docker']
}

We implemented this framework across our hiring process, allowing us to focus on real-life skills instead of proxy indicators.

Observable Changes in Our Hiring Process

The transition to a skills-based hiring framework led to significant changes in our recruiting outcomes. We began to see a more diverse array of candidates applying for positions. The quality of our hires improved, as we were now selecting candidates based on their abilities to solve problems and complete tasks relevant to the job. This shift not only enhanced the team’s capabilities but also positively impacted our product development cycle, leading to faster iterations and more innovative solutions. Candidates were more engaged with the process, and our application metrics reflected this change, with increased applications through our /jobs portal.

Key Takeaways from the Experience

  • Focus on Skills: Prioritizing skills over degrees opened up our candidate pool significantly.
  • Evidence Matters: Real-world evidence of skills provides a better predictor of success than traditional metrics.
  • Candidate Experience: A more transparent and skills-focused process led to higher candidate engagement.
  • Continuous Learning: We learned that hiring is an evolving process requiring regular adjustments based on outcomes.

Implications for Candidates

For candidates, this new approach means that your skills and experiences will take center stage in the hiring process. Instead of worrying about formal qualifications, you can focus on showcasing your actual work, projects, and the skills you've acquired. This opens up the opportunity for a diverse range of applicants—from self-taught developers to those who have taken unconventional paths in their careers.

Implications for Recruiters

For recruiters, this shift signifies a move towards a more inclusive and effective hiring process. It allows for a broader evaluation of talent, promoting diversity and innovation. Recruiters can focus on identifying skills that align more closely with job requirements, ensuring better matches and ultimately leading to higher retention rates.

Looking Ahead

While we've made significant strides in implementing skills-based hiring, our journey doesn't end here. We're closely monitoring the performance of our new hires to ensure that this approach continues to yield positive results. Future challenges include refining our assessment methods and ensuring consistency across teams. If we had to undo any part of this process, it would be the initial hesitation to fully embrace skills over degrees. Moving forward, we remain committed to evolving our hiring practices to ensure we attract the best talent without the constraints of outdated filters.

Related materials

  • Architecture diagram planned — Skills Taxonomy Structure
    A visual representation of our skills taxonomy used in hiring.
  • Chart planned — Hiring Metrics Before and After
    Comparative metrics showcasing the impact of skills-based hiring.

Also on Fitlane AI

Topics: skills based hiring, skills first hiring, skills based recruitment, skill taxonomy, evidence gathering, /jobs, /for-companies