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

Global Metrics Monitoring System

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

Your question is Global Metrics Monitoring 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 large-scale metrics monitoring and alerting system for a global microservices architecture that lets engineers track service health, visualize performance via dashboards, and receive real-time alerts when anomalies occur.

Asked in the Stage 2 stage. Clarify scale, metric types, retention, alert latency, dashboard requirements, and notification channels before sizing the design.

Deliverables

  1. Define functional and non-functional requirements and estimate ingestion, query, and alerting load.
  2. Design metric collection, aggregation, storage, dashboard queries, and alert delivery.
  3. Choose anomaly detection approaches for seasonal, sparse, and high-cardinality metrics.
  4. Explain batch versus streaming processing, model training, evaluation, and deployment.
  5. Address alert deduplication, incident correlation, missing data, feature drift, and training-serving skew.
  6. Describe monitoring, capacity planning, failure handling, and rollback.

Constraints

Support global services, multi-tenant access control, configurable retention, low-latency alerts, cost-aware storage tiers, and graceful degradation during regional or pipeline failures.