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

Genius Flag tiniest to Bronze/Silver/Gold Tiering

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

Your question is Genius Flag tiniest to Bronze/Silver/Gold Tiering. 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 computing, storing and serving a near-real-time 'Genius' flag for 1B Booking.com customers (at least 2 completed bookings in last 2 years), re-evaluated after 2 years; later extend to Bronze/Silver/Gold tiers with upgrades and downgrades.

Asked in the system design stage. Reported follow-up: move from a boolean flag to a tier-based system.

Address:

  1. Clarifying questions and scale estimates.
  2. Event ingestion, eligibility computation, storage, and serving.
  3. Near-real-time updates and two-year expiry handling.
  4. A backward-compatible design for tier upgrades and downgrades.
  5. Consistency, replay, privacy, monitoring, and failure recovery.

No fixed QPS, latency, or freshness target is provided. State the assumptions you need and explain how the design changes if those targets are stricter.