PracHub
QuestionsCoachesLearningGuidesInterview Prep
|Home/ML System Design/Runway

Design a scalable video search system

Last updated: Jun 2, 2026

Quick Overview

This interview question evaluates ML product requirements, data/labeling, modeling, serving architecture, evaluation, monitoring, and trade-offs in a realistic interview setting. A strong answer for Design a scalable video search system states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

  • hard
  • Runway
  • ML System Design
  • Machine Learning Engineer

Design a scalable video search system

Company: Runway

Role: Machine Learning Engineer

Category: ML System Design

Difficulty: hard

Interview Round: Technical Screen

Design an end-to-end video search system that supports text-to-video and video-to-video retrieval. Specify the model architecture (e.g., dual encoders for video frames/clips and text, temporal aggregation strategies, pretraining/fine-tuning objectives, negative sampling, handling long videos via clip sampling), the shared embedding space, and relevance scoring. For infrastructure, describe the offline/online feature extraction pipeline, ingestion, metadata enrichment, indexing in a vector store (e.g., HNSW/IVF, sharding and replication), storage layout for thumbnails/clips, query routing, latency/cost targets, caching, and scalability for billions of clips. Include monitoring, abuse/content safety, and evaluation via offline metrics and online A/B tests; discuss relevance feedback and incremental model updates.

Quick Answer: This interview question evaluates ML product requirements, data/labeling, modeling, serving architecture, evaluation, monitoring, and trade-offs in a realistic interview setting. A strong answer for Design a scalable video search system states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

|Home/ML System Design/Runway

Design a scalable video search system

Runway logo
Runway
Aug 8, 2025, 12:00 AM
hardMachine Learning EngineerTechnical ScreenML System Design
8
0

Design a scalable video search system

Design a Text-to-Video and Video-to-Video Search System

Context

You are tasked with designing an end-to-end multimodal retrieval system that supports both:

  • Text-to-video search (user enters a query, returns the most relevant video segments)
  • Video-to-video search (user provides a reference video, returns visually/semantically similar segments)

Assume a catalog that grows to billions of video clips/segments, with global users and strict latency, cost, and safety requirements.

Requirements

  1. Model architecture
    • Encoders for text and video frames/clips (e.g., dual encoders)
    • Temporal aggregation for video (frame-to-clip, clip-to-video)
    • Shared embedding space, similarity function, and scoring
    • Pretraining/fine-tuning objectives (contrastive, multi-task), negative sampling strategies
    • Handling long videos (clip sampling, segment-level indexing)
    • Optional cross-encoder re-ranking for top-K
  2. Infrastructure
    • Offline/online feature extraction pipelines
    • Ingestion and metadata enrichment (e.g., ASR, OCR, tags)
    • Indexing in a vector store (HNSW/IVF, PQ/OPQ, sharding, replication)
    • Storage layout for thumbnails and short preview clips
    • Query routing and aggregation across shards
    • Latency and cost targets; caching strategies
    • Scalability to billions of clips/segments
  3. Monitoring, safety, and evaluation
    • System and model monitoring (SLOs, drift, recall)
    • Abuse/content safety (NSFW, spam, PII)
    • Evaluation via offline metrics and online A/B tests
    • Relevance feedback and incremental model updates

Constraints & Assumptions

  • Preserve the scope, facts, inputs, and requested outputs from the prompt above.
  • If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.
  • Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask

  • Clarify users, core use cases, read/write patterns, scale, latency, availability, and data retention.
  • State explicit assumptions before making sizing or architecture decisions.
  • Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers

  • A scoped requirements summary with concrete non-goals and success metrics.
  • ML-specific data, model, evaluation, serving, and monitoring choices.
  • Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.
  • A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions

  • What breaks first at 10x traffic or data volume?
  • How would you degrade gracefully during dependency failures?
  • What metrics and alerts would prove the design is healthy after launch?

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More ML System Design•More Runway•More Machine Learning Engineer•Runway Machine Learning Engineer•Runway ML System Design•Machine Learning Engineer ML System Design

Your design canvas — auto-saved

PracHub

Master your tech interviews with 8,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • AI Coding Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.