PracHub
QuestionsPremiumLearningGuidesCheatsheetNEWCoaches
|Home/System Design/Uber

Design A URL Shortener

Last updated: May 14, 2026

Quick Overview

This question evaluates skills in large-scale system design, covering distributed systems, API design, data modeling and storage, caching, short-code generation, redirect flows, analytics collection, scalability, availability, durability, and abuse prevention.

  • medium
  • Uber
  • System Design
  • Software Engineer

Design A URL Shortener

Company: Uber

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Onsite

Design a URL shortening service. Users submit a long URL and receive a short URL. When someone visits the short URL, the service redirects them to the original long URL. Discuss: - Functional requirements, such as creating short links, redirecting users, optional custom aliases, expiration, and basic analytics. - Non-functional requirements, such as low redirect latency, high availability, scalability, durability, and abuse prevention. - API design. - Data model and storage choices. - Short-code generation strategy. - Caching and database scaling. - Redirect flow and analytics collection. - Tradeoffs such as `301` vs `302` redirects and random vs sequential short codes.

Quick Answer: This question evaluates skills in large-scale system design, covering distributed systems, API design, data modeling and storage, caching, short-code generation, redirect flows, analytics collection, scalability, availability, durability, and abuse prevention.

Related Interview Questions

  • Design an Uber Eats Cart Service - Uber (medium)
  • Design Restaurant Search and Monitoring - Uber (hard)
  • Design Nearby Restaurant Search - Uber
  • Design a Food Delivery Cart - Uber (medium)
  • Design a Daily Puzzle Platform - Uber (medium)
Uber logo
Uber
May 4, 2026, 12:00 AM
Software Engineer
Onsite
System Design
0
0

Design a URL shortening service.

Users submit a long URL and receive a short URL. When someone visits the short URL, the service redirects them to the original long URL.

Discuss:

  • Functional requirements, such as creating short links, redirecting users, optional custom aliases, expiration, and basic analytics.
  • Non-functional requirements, such as low redirect latency, high availability, scalability, durability, and abuse prevention.
  • API design.
  • Data model and storage choices.
  • Short-code generation strategy.
  • Caching and database scaling.
  • Redirect flow and analytics collection.
  • Tradeoffs such as 301 vs 302 redirects and random vs sequential short codes.

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Uber•More Software Engineer•Uber Software Engineer•Uber System Design•Software Engineer System Design
PracHub

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

Product

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

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL 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.