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

Design Intelligent Mobile Image Loading

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

Whenever you're ready, walk me through how you'd approach this.

You need to log in / sign up to chat or submit.

Problem

Scenario

You are designing an image loading system for a mobile social app with image-heavy surfaces such as feed, stories, profiles, and marketplace listings. Instead of using fixed caching rules, your team wants an ML system that predicts which images should stay in memory, which should be persisted on disk, and which can be evicted, with the goal of improving scroll smoothness and reducing network usage. The system must adapt to user behavior, device constraints, and network quality while avoiding crashes, stale content, and wasted storage. This is a core client performance problem because image fetch latency directly affects engagement on the app's highest-traffic surfaces.

Scale

SignalValue
DAU180M
Peak image requests2.2M QPS
Avg images viewed per DAU per day320
Distinct image URLs/day3.5B
On-device memory cache budget32-128 MB depending on device tier
On-device disk cache budget200 MB-2 GB depending on free storage
Per-image load latency target (p95)< 80 ms if cached, < 300 ms if network fetch
Model decision latency budget on device< 5 ms

Question

How would you design this end-to-end ML system so the mobile client can decide when to use memory caching versus disk caching for images at scale? Explain the architecture, model choices, online and offline components, evaluation approach, and how you would handle drift, skew, and operational failures.