Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Evaluate New Ad-Ranking Model

HardA/B Testing & Experimentation00:00
Practice interviewer
In session
5 left
00:00

Your question is Evaluate New Ad-Ranking Model. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Context

AdSphere runs sponsored listings in a large marketplace app. The ads team has trained a new ad-ranking model that is expected to improve ad quality and monetization, and wants a rigorous online experiment before launch.

Hypothesis Seed

The new model uses richer user-context and conversion features, and the team believes it will increase revenue per 1,000 ad impressions by showing more relevant ads. However, leadership is concerned that a model optimized too aggressively for revenue could hurt user engagement, advertiser fairness, or system latency.

Constraints

  • Eligible traffic: 12 million ad impressions/day across homepage, search, and feed surfaces
  • Average baseline click-through rate (CTR): 1.8%
  • Average baseline revenue per 1,000 impressions (RPM): $24.00, with impression-level standard deviation approximately $120 when expressed on a per-1,000-impression normalized basis
  • Maximum experiment duration: 14 days
  • Randomization must be chosen to avoid users seeing inconsistent ad ordering within a session
  • False positives are expensive because a bad launch can reduce marketplace trust and advertiser ROI; false negatives are acceptable but should be minimized

Deliverables

  1. Define the experiment hypothesis, including the primary metric, 2-4 guardrails, and a clear minimum detectable effect (MDE).
  2. Compute the required sample size and estimate whether the test can be completed within the 14-day traffic budget.
  3. Choose the unit of randomization, allocation, and duration; explain trade-offs such as user-level consistency, interference, and variance.
  4. Pre-register an analysis plan: statistical test, treatment of multiple metrics, peeking policy, and how you will check for sample ratio mismatch.
  5. State a clear ship / don’t ship / iterate rule that respects both the primary metric and guardrails.

Assume you may use asymptotic approximations, but your design should be robust enough for production decision-making. Be explicit about how you would handle pitfalls such as novelty effects, network interference from advertisers adapting bids, and any mismatch between unit of randomization and unit of analysis.