How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a medium difficulty System Design question, commonly asked during Technical Screen rounds at Adobe.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Adobe during technical interviews.

Analyze web request latency causes | Adobe Interview Question

Quick Overview

This question evaluates a candidate's competency in analyzing and optimizing end-to-end web request latency, covering client-side rendering, network/CDN behavior (HTTP/2 or HTTP/3, TLS, caching), server processing, datastore interactions, and observability for p95 TTFB targets.

System Design: End-to-End Web Request Latency

Context

You are designing a user-facing web experience that fetches HTML/JSON from an origin and additional static assets from a CDN. Users are global (desktop and mobile). The goal is to reduce end-to-end latency (from user action to usable content), with a target of p95 TTFB < 300 ms for the primary HTML/JSON endpoint and a fast, stable render.

Task

Analyze a single web request end-to-end and do the following:

Break down latency into client-side, network, and server-side components.
Identify likely bottlenecks and how you would measure them.
Propose concrete optimizations for each layer (client, network/CDN, server, data store), including expected impact.
Provide a small numeric example that computes the current latency and demonstrates how your optimizations reduce it.
Outline an instrumentation and rollout plan (validation, guardrails, and success criteria).

Assume HTTP/2 or HTTP/3 is available, TLS is required, and the primary response is cacheable for 60 seconds. Keep your analysis focused and practical for a technical phone screen.

Quick Overview

Context

Task

Analyze a single web request end-to-end and do the following:

Break down latency into client-side, network, and server-side components.

Identify likely bottlenecks and how you would measure them.

Propose concrete optimizations for each layer (client, network/CDN, server, data store), including expected impact.

Provide a small numeric example that computes the current latency and demonstrates how your optimizations reduce it.

Outline an instrumentation and rollout plan (validation, guardrails, and success criteria).

Assume HTTP/2 or HTTP/3 is available, TLS is required, and the primary response is cacheable for 60 seconds. Keep your analysis focused and practical for a technical phone screen.

Analyze web request latency causes

Quick Overview

System Design: End-to-End Web Request Latency

Context

Task

Solution

Comments (0)

Analyze web request latency causes

Quick Overview

System Design: End-to-End Web Request Latency

Context

Task

Solution

Comments (0)