Should WorkIndia prioritize expanding its job listing database or improving the accuracy of its job matching algorithm?

Introduction

The trade-off between expanding WorkIndia's job listing database and improving the accuracy of its job matching algorithm is a critical decision that could significantly impact the platform's growth and user satisfaction. This scenario touches on the core functionality of WorkIndia's service and requires careful consideration of both short-term gains and long-term sustainability. I'll analyze this trade-off by examining the current product landscape, potential impacts, and key metrics, before proposing an experiment to guide our decision-making process.

Step 1

Clarifying Questions (3 minutes)

• Based on WorkIndia's current market position, I'm thinking user acquisition might be a priority. Could you share our current user growth rate and how it compares to our targets?

Why it matters: Helps determine if we should focus on attracting more users or improving experience for existing ones. Expected answer: Growth is below target, need to accelerate user acquisition. Impact on approach: Would lean towards expanding job listings to attract more users.

• Considering our revenue model, I assume we charge employers for job postings. Is this correct, and what's our current conversion rate from free to paid listings?

Why it matters: Informs whether we should prioritize quantity or quality of job matches. Expected answer: Yes, with a 15% conversion rate from free to paid listings. Impact on approach: Low conversion might suggest focusing on improving match accuracy.

• Looking at user behavior, what's our current job application to interview ratio? This could indicate the effectiveness of our current matching.

Why it matters: Helps gauge the current accuracy of our job matching algorithm. Expected answer: 10% of applications result in interviews. Impact on approach: Low ratio would suggest prioritizing algorithm improvement.

• From a technical standpoint, how scalable is our current database infrastructure? Can it handle a significant increase in job listings?

Why it matters: Determines if expanding the database is feasible without major tech investments. Expected answer: Current infrastructure can handle 3x growth without significant changes. Impact on approach: High scalability would make database expansion more attractive.

• Regarding our team capacity, do we have more resources in data science for algorithm improvement or in business development for expanding job listings?

Why it matters: Helps align our strategy with current team strengths and capabilities. Expected answer: Stronger data science team, limited BD resources. Impact on approach: Might lean towards algorithm improvement if data science team is stronger.