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
ExperiencesCoaching
New
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess 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
Get started

Scalable Logs System

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

Your question is Scalable Logs System. 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 a scalable system for harnessing logs for Booking.com's internal infrastructure.

Asked in the onsite stage. Clarify the intended consumers and use cases before proposing the design, such as operational search, anomaly detection, incident investigation, or capacity forecasting.

Address:

  1. Functional and non-functional requirements, including retention, privacy, availability, and freshness.
  2. Log collection, transport, schema management, storage, and replay.
  3. ML processing, including parsing, anomaly detection, incident correlation, or ranking relevant events.
  4. Batch versus online processing and serving architecture.
  5. Offline and online evaluation, monitoring, drift detection, and feedback loops.
  6. Failure modes, backpressure, cost controls, and operational fallbacks.

Do not assume scale, latency, retention, or label availability. State the clarifying questions and show how your design changes based on their answers.