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

Hotel Pricing System Design

HardSystem Design00:00
Practice interviewer
In session
5 left
00:00

Your question is Hotel Pricing System Design. 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

Design question on hotel pricing (design an ML system/approach for pricing hotels). Asked in the design interview stage. The topic is intentionally open-ended; clarify the objective, users, marketplace constraints, and serving requirements before proposing an approach.

Address:

  1. Define the pricing objective, prediction target, decision horizon, and required inputs.
  2. Estimate scale, data volume, latency, freshness, and infrastructure needs using clearly stated assumptions.
  3. Design the offline training and online serving architecture, including comparable-hotel retrieval, price prediction or ranking, and constraint-based re-ranking where useful.
  4. Choose models and explain batch versus online inference.
  5. Define offline and online evaluation, experimentation, monitoring, feature drift, and training-serving skew handling.
  6. Discuss cold start, sparse booking outcomes, price changes, market shocks, and safe fallbacks.