Prompt

Practice system design interviews with Claude's structured approach and detailed feedback.

<system_design_interview>
**System to Design:** {DESCRIBE THE SYSTEM - e.g., "Design Twitter", "Design Uber", etc.}

<interview_structure>
Please guide me through this system design interview:

1. **Requirements Gathering:**
   <requirements_clarification>
   - Functional requirements
   - Non-functional requirements  
   - Scale assumptions
   - User base size
   - Geographic distribution
   - Performance SLAs
   </requirements_clarification>

2. **Capacity Estimation:**
   <calculations>
   - Daily active users
   - Requests per second
   - Storage requirements
   - Bandwidth needs
   - Cache sizing
   - Server count estimates
   </calculations>

3. **High-Level Design:**
   <architecture_components>
   - Major system components
   - Data flow diagrams
   - API design
   - Protocol choices
   - Client-server interaction
   </architecture_components>

4. **Detailed Design:**
   <deep_dive_areas>
   - Database schema
   - Algorithm choices
   - Data partitioning strategy
   - Caching layers
   - Message queue design
   - Microservices breakdown
   </deep_dive_areas>

5. **Scale and Performance:**
   <optimization_strategies>
   - Bottleneck identification
   - Horizontal scaling approach
   - Load balancing strategy
   - CDN utilization
   - Database optimization
   - Asynchronous processing
   </optimization_strategies>

6. **Reliability and Operations:**
   <operational_excellence>
   - Failure scenarios
   - Monitoring and alerting
   - Deployment strategy
   - Rollback procedures
   - Disaster recovery
   - SLA maintenance
   </operational_excellence>
</interview_structure>

<feedback_request>
After each section, please:
- Point out what I did well
- Identify missed considerations
- Suggest improvements
- Ask follow-up questions an interviewer might ask
- Rate my answer (1-10) with justification
</feedback_request>
</system_design_interview>