product sense · standard
Design a product connecting handymen with consumers
Design a product that connects handymen with consumers.
Most candidates describe a booking app and call it a strategy. The interviewer is checking whether you can reason about marketplace liquidity, supply-side recruitment, and why Meta specifically should build this rather than a startup.
What the interviewer is actually evaluating
The US home services market is $97 billion and growing at 7.2% annually. The handyman sub-market is $1.65 billion growing at 10% annually. Less than 1% of total home services spend flows through digital platforms. The gap is not a feature problem; it is a trust and supply-recruitment problem. An interviewer at Meta wants to know if you can see that distinction.
The competitive landscape matters too. Angi’s lead-spam model eroded trust on both sides. TaskRabbit, now owned by IKEA, is constrained in scope. Thumbtack acquired Angi’s home services division in 2025, becoming the largest US marketplace by bookings, and by October 2025 was embedded inside ChatGPT for home services booking. A candidate who proposes “build a matching UI” in 2026 is proposing the feature Thumbtack already ships inside the world’s most-used AI assistant. Name this context or leave an obvious gap on the table.
Meta’s product sense framework is Understand, Identify, Execute. Align your answer to that structure explicitly.
Structure a strong answer
strong
"Before I propose anything: when you say Meta, do you mean we're building on Facebook and Marketplace infrastructure using the social graph? Or is this a standalone product? I'll assume Facebook Marketplace context, because that changes the entire strategy. I'll also focus on planned jobs rather than urgent reactive work. Discovery and trust matter most for planned projects, and that's where Meta has structural advantages no startup can replicate."
Understand: Connecting people through local commerce is core to Marketplace, and home services is the largest category of local spend Marketplace doesn't currently capture well. The risk is becoming another lead-gen site. The strategic bet worth making is identity-verified trust: Meta's social graph is the one moat Angi, Thumbtack, and a hundred startups cannot copy.
Identify: Three distinct user segments exist. First, the anxious first-time homeowner, 28-35, just bought, has no contractor relationships, paralyzed by fear of being ripped off. Second, the time-poor dual-income couple, 35-50, willing to pay a premium but stuck in a 3-hour search-and-vet loop every time work comes up. Third, the repeat renovator, 45-60, who has a few contractors but wants competition on price for new job types. I'll focus on segment two: highest willingness to pay, clearest pain, most likely to form a habit on platform.
The pain points, with real texture. (a) Vetting cost: reading 40 reviews across three platforms while texting friends for referrals takes 3-4 hours. The root problem is not a lack of information; it is the cost of synthesis. (b) Scheduling friction: handymen don't respond to quote requests within 48 hours, and no-shows happen on roughly 30% of first appointments. Root problem: asymmetric urgency. The consumer is ready; the handyman is juggling five other jobs. (c) Scope creep anxiety: consumers don't know enough to write a clear brief, so jobs balloon in cost after the fact. Root problem: information asymmetry at job definition.
Execute: Three meaningfully different solutions.
One: Social graph trust score. Instead of raw star ratings, surface a "people in your network have hired this person" signal. If three second-degree connections hired Marcus the plumber, that one signal is worth more than 200 anonymous 4.8-star reviews. This solves pain point (a) by replacing synthesis work with trusted signal. It is the one thing no competitor can replicate without Meta's identity infrastructure.
Two: Job Brief AI assistant. A short conversational intake before posting: photos of the space, a scope checklist, a realistic price range based on similar local jobs. Handymen then respond to a real brief instead of a vague message. This solves pain point (c) and reduces quote variance. Services with higher average ratings see 20% higher booking frequency; better briefs drive better ratings.
Three: Reliability bond. Handymen who opt in post a small commitment deposit (say, $50) released on confirmed job start. Consumers see a "Reliability Guaranteed" badge. This solves pain point (b) by creating skin-in-the-game for supply, without classifying workers as employees.
MVP: ship the Job Brief AI assistant and the social graph trust signal only. Leave the reliability bond for the next iteration; it requires payment infrastructure and supply-side legal review. The north star metric at launch is job completion rate within five days of posting. This captures both sides working. GMV is the wrong primary metric at launch because price variance across job types distorts the signal entirely.
On the supply side, and this is what most answers skip entirely: there is a real chicken-and-egg problem. No consumers post if there are no handymen; no handymen join if there are no leads. Seed supply by identifying the 50-100 licensed contractors already advertising in local Facebook Groups or on Marketplace in a given metro. They are on platform already, just unstructured. Offer zero commission and free lead-gen for the first six months in exchange for a structured profile and response SLA commitment. This costs Meta very little and solves the cold-start problem in a way a standalone startup cannot, because the supply already lives on Facebook."
weak
"I would design an app where homeowners post a job and handymen bid on it, with ratings and reviews so consumers can trust the results." This describes TaskRabbit circa 2012. It fails for several compounding reasons: no clarifying question about Meta context, so the social graph is never mentioned; "homeowners" is too vague a segment to drive a single real product decision; "trust via reviews" is a solution stated without identifying why Angi, Yelp, and Google reviews don't already solve it; the supply side is completely absent; there is no north star metric; and no MVP tradeoff appears, only a feature list. The interviewer's internal note: "This person can describe a marketplace but cannot reason about one."
The cold-start problem nobody names
The chicken-and-egg problem is the most reliable interviewer signal in this question. Candidates who name it without being prompted demonstrate marketplace reasoning. Candidates who wait for a prompt have revealed the limit of their thinking.
The seeding mechanism matters as much as the problem statement. Thumbtack’s early playbook was manual outreach to local contractors in one city. Angi’s was acquiring lead-gen sites. Meta’s structural advantage is that the supply already exists on platform, inside Groups and Marketplace, with real identity, real reviews from neighbors, and existing community trust. The product’s first job is to make that latent supply legible, not to recruit new supply from scratch.
The 2026 reframe
In 2026, building a two-sided booking marketplace takes weeks with AI-assisted development. Feasibility is essentially free. The real scarce resource is supply-side trust: what gives a handyman a reason to give Meta their schedule and commit to SLAs when Thumbtack already pays them leads inside ChatGPT?
Thumbtack is now embedded in an agentic workflow. A consumer asks ChatGPT to find someone to fix their fence and Thumbtack closes the booking in the background. The question “build a matching UI” has already been answered. The question worth asking in 2026 is where the matching layer lives in an agentic world, and whether Meta’s social graph signals can travel into that layer as the trust primitive that other platforms cannot supply.
The viable argument for Meta building this, rather than a startup: sub-1% digital penetration of a $97 billion market means no saturation problem. The only barriers are trust and supply recruitment, and Meta is structurally positioned to solve both better than any standalone player. That is the argument worth making in the room.
For more on Meta’s interview structure, see the Meta interview process. On the viable/lovable lens that applies across all product sense questions, see feasibility is free and lovable, not just usable.
Framework
Asked at
Related
- "Design a jobs product for Facebook" product-sense
- How would you measure the success of Facebook Marketplace? execution
- "How would you improve Facebook Groups?" (Meta product sense) product-sense