PracHub
QuestionsPremiumLearningGuidesInterview PrepNEWCoaches
|Home/Analytics & Experimentation/Thumbtack

Design a robust pro-ranking A/B test

Last updated: Mar 29, 2026

Quick Overview

It evaluates experimental design and causal inference competencies for two-sided marketplaces, focusing on metric definition and guardrails, randomization to limit interference, power and sample-size estimation, bias controls, monitoring and sequential stopping, and attribution of uplift versus cannibalization.

  • hard
  • Thumbtack
  • Analytics & Experimentation
  • Data Scientist

Design a robust pro-ranking A/B test

Company: Thumbtack

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: hard

Interview Round: Onsite

Thumbtack plans to change the pro ranking algorithm in search results for customer requests. Design an experiment to evaluate the new ranker while minimizing marketplace interference and supply cannibalization. Provide: 1) Primary outcome and guardrails: Define a single primary metric (e.g., booking conversion per request) and at least four guardrails (e.g., time-to-first-quote, cancellation rate, average pro response latency, pro earnings dispersion/fairness) with exact formulas and acceptable threshold deltas. 2) Randomization unit and design: Choose between request-level, customer-level, geography-level cluster, or switchback by region-hour. Justify to reduce cross-unit interference when pros can serve multiple requests. Describe how you’ll prevent pros from systematically over-serving one arm. 3) Power and duration: Given baseline booking conversion = 12%, target relative lift = 5%, alpha = 0.05 (two-sided), power = 90%, and an average of 50,000 eligible requests/day, estimate required sample size per arm and the runtime in days under 1:1 allocation. Show formulas/assumptions (e.g., pooled variance for two-proportion z-test). State how clustering or switchback inflates variance (design effect) and incorporate a plausible ICC to revise the runtime. 4) Bias controls: Specify pre-experiment checks (covariate balance), and variance reduction (e.g., CUPED using pre-period request conversion or stratification by category/region). Explain handling of repeated customers and daylight saving/time-of-day effects. 5) Monitoring and stopping: Propose a sequential monitoring plan (e.g., O’Brien–Fleming or alpha spending) and anomaly triggers. Define what happens if a guardrail breaches but primary improves. 6) Readout: Detail the difference-in-means estimator, heterogeneity by category/region/traffic source, and how you would attribute uplift vs. cannibalization across supply-limited segments.

Quick Answer: It evaluates experimental design and causal inference competencies for two-sided marketplaces, focusing on metric definition and guardrails, randomization to limit interference, power and sample-size estimation, bias controls, monitoring and sequential stopping, and attribution of uplift versus cannibalization.

Related Interview Questions

  • Explain power drivers and resolve unexpected A/B results - Thumbtack (medium)
  • Define success metrics for Instant Book - Thumbtack (hard)
  • Design and evaluate an A/B test for launch - Thumbtack (hard)
Thumbtack logo
Thumbtack
Oct 13, 2025, 9:49 PM
Data Scientist
Onsite
Analytics & Experimentation
3
0

Experiment Design: Evaluating a New Pro Ranking Algorithm (Ranker) in a Two‑Sided Marketplace

You are designing an experiment to evaluate a new pro ranking algorithm in search results for customer requests, while minimizing marketplace interference and supply cannibalization.

Provide the following:

  1. Primary outcome and guardrails
    • Define one primary metric (e.g., booking conversion per request), with a clear measurement window.
    • Specify at least four guardrail metrics (e.g., time-to-first-quote, cancellation rate, average pro response latency, pro earnings dispersion/fairness).
    • For each metric, provide an exact formula and acceptable threshold delta (absolute or relative).
  2. Randomization unit and design
    • Choose a randomization unit: request-level, customer-level, geography-level cluster, or switchback by region-hour.
    • Justify your choice to reduce cross-unit interference, given that pros can serve multiple requests.
    • Describe controls to prevent pros from systematically over-serving one arm.
  3. Power and duration
    • Given: baseline booking conversion = 12%, target relative lift = 5%, alpha = 0.05 (two-sided), power = 90%, and 50,000 eligible requests/day.
    • Estimate required sample size per arm and runtime in days under 1:1 allocation.
    • Show formulas/assumptions (e.g., pooled variance for a two-proportion z-test).
    • Explain how clustering or switchback inflates variance (design effect), state a plausible ICC, and revise runtime accordingly.
  4. Bias controls
    • Specify pre-experiment checks (e.g., covariate balance with standardized differences).
    • Propose variance reduction strategies (e.g., CUPED using pre-period request conversion, stratification by category/region).
    • Explain how you will handle repeated customers and daylight saving/time-of-day effects.
  5. Monitoring and stopping
    • Propose a sequential monitoring plan (e.g., O’Brien–Fleming or alpha spending) and anomaly triggers.
    • Define the decision rule if the primary metric improves but a guardrail breaches.
  6. Readout
    • Define the difference-in-means estimator and standard error approach.
    • Describe heterogeneity analyses by category/region/traffic source.
    • Explain how you will attribute uplift vs. cannibalization across supply-limited segments.

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More Analytics & Experimentation•More Thumbtack•More Data Scientist•Thumbtack Data Scientist•Thumbtack Analytics & Experimentation•Data Scientist Analytics & Experimentation
PracHub

Master your tech interviews with 7,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.