You've just launched Facebook Jobs, a marketplace for employees and employers.
Job listings are up 20%, but employer response time for applicants is down 20%. How would you approach this?
About this question
Category
Product Execution
Subcategory
Root Cause Analysis
Difficulty
Medium
Est. time
35 min
What this question helps you practice
This question tests whether you can reason through a marketplace metric paradox. A strong response should clarify the metric definition, segment supply and demand, identify funnel bottlenecks, and distinguish healthy growth from operational overload.
How to practice
Clarify definitions
Define job listings, employer response time, applicant volume, active employers, and measurement windows.
Segment the marketplace
Break down by employer type, job category, geography, listing quality, and applicant volume per listing.
Diagnose bottlenecks
Check whether the issue is employer overload, poor matching, low applicant quality, tooling friction, or measurement bias.
Strong answer signals
Explains why more listings can create more applicant volume and slower employer response.
Considers marketplace quality, not just growth in supply.
Proposes segmented metrics such as response rate, qualified applicant rate, and time-to-first-response.
Common mistakes
Assuming more listings are automatically good without checking marketplace liquidity and quality.
Treating employer response time as purely an engineering latency problem.
Ignoring applicant-side changes that may affect employer workload.
Ready to try it?
Practice your answer in the interactive workspace.
Keep practicing
Explore frameworks and related prompts that build the same interview muscle.
Recommended frameworks
5 Whys Analysis: Uncovering Root Causes in Product Execution
Discover the 5 Whys technique—a powerful framework that helps Product Managers peel back the layers of symptoms to pinpoint the exact failure points in a system. More than just repeating "Why," it is the art of causal inquiry to prevent recurring issues.
