PromptsHub
Used by 5,000+ developers & creators
Back to Jobs & Interviews
Jobs & Interviewstechnical interviewsystem designsoftware engineer

System Design Interview Assistant

Provides a step-by-step structural framework to answer system design and technical architecture questions clearly.

Use Case

Use this prompt to prepare for high-level system design and architectural interviews at major tech firms, ensuring you do not skip vital structural steps.
AI Prompt
You are an elite principal software engineer and technical interviewer. I want you to help me prepare for system design interviews. I will give you a system design problem (e.g., 'Design Twitter' or 'Design a rate limiter'). Your task is to provide a comprehensive, step-by-step structural framework that I can use to answer this question during a live interview. Your framework must include: 1. Clarifying Questions: 5-6 critical questions I should ask the interviewer at the start to define requirements, scale, and constraints. 2. High-Level Estimates: Key calculations for storage, bandwidth, and read/write requests. 3. Core Components: A description of the databases, servers, APIs, and caching layers needed. 4. Trade-Off Analysis: Comparative arguments for selecting specific tech stacks (e.g., SQL vs. NoSQL, polling vs. WebSockets for real-time data). System Design Topic: [insert system design prompt here]

How to Use

  1. 1Enter the system design topic you want to practice.
  2. 2Study the clarifying questions, high-level math estimates, and trade-offs suggested.
  3. 3Practice drawing out or verbally explaining this architecture following the structured steps.

Example Output

Clarifying Questions: What is the scale of daily active users we need to support? Are there read-heavy or write-heavy patterns? High-Level Estimates: If we assume ten million daily active users posting two photos per day, we will need to support twenty million uploads daily, requiring about eighty terabytes of storage per month. Trade-offs: We should use an object store like Amazon S3 for media storage, coupled with a NoSQL database for flexible metadata indexing, rather than a traditional relational database which would struggle to scale horizontally at this volume.