How might Turing (Human Capital Services) enhance its matching algorithm to better pair companies with the most suitable developers for their projects?

Introduction

To enhance Turing's matching algorithm for better pairing companies with suitable developers, we need to dive deep into the current system, user needs, and market dynamics. I'll approach this by examining key stakeholders, analyzing pain points, generating solutions, and proposing metrics for success. Let's begin by clarifying some crucial aspects of the current situation.

Step 1

Clarifying Questions (5 mins)

• Looking at Turing's position in the market, I'm curious about the current success rate of matches. Could you share what percentage of initial matches result in successful project completions?

Why it matters: This helps us understand the baseline performance and set improvement targets. Expected answer: Around 70% of matches lead to successful project completions. Impact on approach: A high success rate might lead us to focus on incremental improvements, while a lower rate would suggest more radical changes.

• Considering the evolving nature of tech skills, I'm wondering about the frequency of updates to the skill assessment process. How often does Turing update its skill evaluation criteria and tests?

Why it matters: Ensures the matching algorithm is based on up-to-date skill assessments. Expected answer: Skill assessments are updated quarterly. Impact on approach: Frequent updates might indicate a need for a more dynamic, real-time skill tracking system.

• Given the global nature of remote work, I'm interested in understanding the geographical distribution of developers and companies. What are the top 3 regions for both developers and hiring companies?

Why it matters: Helps identify any regional biases or opportunities in the matching process. Expected answer: Developers primarily from India, Eastern Europe, and South America; companies mainly from the US, Western Europe, and Australia. Impact on approach: Significant geographical disparities might suggest incorporating cultural fit and time zone compatibility into the algorithm.

• Thinking about the long-term success of matches, I'm curious about the retention rate of developers with companies after the initial project. What percentage of developers continue working with the same company on subsequent projects?

Why it matters: Indicates the quality of matches beyond the initial project. Expected answer: About 40% of developers work on subsequent projects with the same company. Impact on approach: A low retention rate might suggest focusing on long-term compatibility in addition to immediate skill matching.