Design a Video Streaming for ServiceNow

Last updated: February 16, 2026

Quick Overview

Design a distributed video streaming system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

ServiceNow
System Design
Software Engineer
ServiceNow
February 16, 2026
Software Engineer
System Design Round
System Design
Hard

7

11

955 solved


Design a distributed video streaming system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

This is a common system design question asked during System Design Round at ServiceNow. The interviewer expects you to demonstrate your ability to design large-scale distributed systems, make well-reasoned trade-offs, and communicate your thought process clearly. ServiceNow values engineers who can think about scalability from day one.

What the Interviewer Expects
  • Drive the design discussion proactively with minimal interviewer guidance
  • Perform detailed capacity estimation and use it to inform design decisions
  • Design for global scale with multi-region deployment and data consistency
  • Deep dive into 2-3 critical components with implementation-level detail
  • Address complex trade-offs: CAP theorem, eventual consistency, conflict resolution
  • Discuss operational excellence: deployment strategy, chaos engineering, SLOs/SLIs
  • Propose a phased rollout plan from MVP to full-scale system
Key Topics to Cover
Message queues and async processing
Monitoring, logging, and alerting
Caching strategies (local, distributed, CDN)
Requirements gathering and capacity estimation
Consistency models and replication
Database selection and data modeling
How to Approach This
  1. Start by clarifying functional and non-functional requirements with the interviewer.
  2. Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
  3. Draw a high-level architecture first, then deep dive into 1-2 critical components.
  4. Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
  5. Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
  • How would you handle schema migrations with zero downtime?
  • What monitoring and alerting would you set up on day one?
  • What would the deployment pipeline look like for this system?
  • How would you implement rate limiting to protect the system?
Practice a Similar Problem on Codemia

Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.

Solve on Codemia
Sample Answer
Requirements

Functional Requirements

  1. Video Upload: Users should be able to upload videos with various formats and sizes.
  2. Video Streaming: Users can stream videos in various resolutions (SD, HD, 4...
Capacity Estimation

To estimate the capacity, we assume the following:

  • Concurrent Users: 10 million concurrent users.
  • Average Video Size: 500 MB.
  • Video Length: 10 minutes.
  • Upload Rate: 50,000 uplo...

Submit Your Answer
Markdown supported

Related Questions