These ChatGPT prompts for system design interview prep take you from calibrating the round to your level, through building blocks and estimates, to critiquing and defending your own designs. There are 13, for practice and review, and they work in ChatGPT, Gemini, Claude and Microsoft Copilot.
For a full timed mock with an interviewer script and a rubric by level, see our system design mock interview guide. The prompts here cover the preparation around it.
Before you start
- Paste your target level, the company's product area, your design written as text (components, data flow, storage, APIs) and your estimates.
- Describe your diagram in words. List the boxes and the arrows between them. Writing it out also tests whether the design hangs together.
- Leave out your employer's internal architecture, real capacity figures and anything else you couldn't say in an interview.
Use the chatbot as a reviewer, not an architect: design first, then ask it to find the holes. That is the core of our guide on how to use AI for interview prep. If the format itself is new to you, start with what a system design interview is.
Calibrate and research
1. Calibrate to your level
I'm preparing for a system design round at [level] at a [type of company]. In a table, compare what is usually expected at my level and one level below: how much I should drive the conversation, how deep the deep dive goes, how many trade-offs I discuss and whether operations and cost come up. Mark anything that varies by company so I can ask my recruiter.
Level changes what a good answer looks like. Treat the table as a starting point and confirm the details with your recruiter.
2. Questions from the company's domain
The company builds [product or domain]. List eight design questions an interviewer there might plausibly ask, from closest to its domain to generic, and the core challenge each one tests, such as fan-out, consistency, real-time delivery or large-scale storage.
Practicing problems near the company's domain makes the round feel familiar. You still need the generic classics; this just puts them in order.
Building blocks, estimates and requirements
3. Building-block quiz
Quiz me on these building blocks one at a time: caching, message queues, sharding, replication, CDNs, rate limiting and consistent hashing. For each, ask when I'd use it, what it costs and one way it fails. Correct me briefly and move on.
Deep dives are built from these pieces, and 'what it costs' is where most answers are thin. Our building blocks walkthroughs cover each one.
4. Check my back-of-envelope estimate
Here's my capacity estimate for [system], with every assumption: [paste]. Check each step's arithmetic and units, flag any assumption that looks unrealistic, and tell me which number actually changes the design. Don't redo the estimate in full.
Interviewers care less about the exact figure than whether it drives a decision. Recalculate anything it flags yourself; chatbots slip on arithmetic too.
5. Interrogate the requirements
Give me a one-line design prompt. Then act as a product manager: answer my clarifying questions about users, scale, latency, consistency and features, briefly and realistically, without volunteering anything. When I say 'done', list the requirements I never asked about and whether they'd have changed the design.
Skipped requirements are the most common early mistake. This shows the gaps after five minutes instead of forty.
Critique and defend your design
6. Find the weak point in my design
Here's my design in text: [components, data flow, storage, APIs]. Identify the single point of failure, the first bottleneck at 10 times today's traffic and one data consistency risk. Ask me how I'd fix each, one at a time. Don't propose fixes first.
Asking before suggesting keeps the reasoning yours. Compare your fixes with a reference walkthrough afterwards.
7. Defend three choices
Push back on three of my design choices the way a skeptical staff engineer would, for example 'Why not a relational database here?'. One at a time. After each reply, tell me whether I named a real cost of my choice or just restated it.
Trade-off discussion is where much of the senior-level signal sits. A defense that names a cost sounds like judgment; one that doesn't sounds like habit.
8. Pick the deep dive
From my design above, choose the component an interviewer would most likely drill into, explain why in one line, then ask me five questions about it that get progressively harder.
You usually get one deep dive and rarely choose it. Practicing the likely one prepares you for its follow-ups.
9. Same system, new constraint
We've designed [system]. Now change one thing: [global users, strict ordering, 100 times more writes or a tight cost budget]. Ask me what changes in my design and why, then tell me what I missed.
Interviewers often add a constraint late in the round. Practicing the pivot shows you can adapt without starting over.
Rehearse and review
10. An eight-minute walkthrough with one interruption
I'll walk you through my design as if presenting to an interviewer, in under eight minutes, with the diagram described in text. Interrupt me once with a question about scale or failure, then let me continue. Afterwards, tell me whether my walkthrough followed a clear order.
Plenty of candidates have a good design and a confusing explanation. Say it out loud with a timer; typing it is a different skill.
11. A written debrief
Write the interviewer's debrief for this session as if for a hiring committee: signals for, signals against, a level estimate and a one-line recommendation. Base every point on what I actually said in this chat, and quote it.
It shows what an interviewer could actually write down about you. Treat the level estimate as a rough read, not a verdict.
12. My first-ten-minutes checklist
Based on the mistakes I made in this chat, write a short checklist for the first ten minutes of any design round: what to clarify, which numbers to estimate and when to move to the high-level design.
A checklist built from your own misses beats a generic one. Read it before each practice session.
13. Recall a real round
Here's what I remember from my real design round: [paste]. Where did I most likely lose points, and what would you study before another round? Five bullets at most.
Write your notes the same day, while you still remember the follow-ups. It turns one round into preparation for the next.
Limits to plan around
| Limit | Why it matters | What to add |
|---|---|---|
| No whiteboard or drawing tool | Drawing while talking is part of the round | Practice on paper or a drawing tool with a timer |
| No clock | A 45-minute round drifts past an hour in chat | Time each phase yourself |
| Plausible but wrong facts | Numbers and guarantees can be misstated | Check against trusted material; see our system design resources |
| Generic designs | A textbook answer ignores your requirements | Ask: what in this design depends on my requirements? |
| No real interviewer | Pushback, silence and hints feel different live | Run a few sessions with a peer |
A real design round is a conversation with a person, and your reasoning is what's assessed. Use these prompts before and after, and follow your employer's rules on the day.
Where CoPilot Interview fits
Design reasoning only counts if you can explain it clearly out loud. CoPilot Interview is an AI interview helper whose AI mock interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Paid plans are Standard at $24.99 a month and Pro at $39.99 a month.
The app runs on Windows 10 and 11 and macOS 12 or later, with a free iPhone and iPad companion. Its live help, with captions and a structured answer in about two seconds, is for situations where the employer allows it.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
Can ChatGPT help with system design interview prep?
Yes, as a reviewer and sparring partner: quizzing building blocks, checking estimates, playing a product manager for requirements and pushing back on your choices. It is weaker as a timekeeper and has no whiteboard, so add timed, spoken practice.
How do I show ChatGPT my system design diagram?
Describe it in text: list each component, what it stores or does, and the arrows between them. Writing it out is useful practice, because you'll narrate the same thing in the interview.
Which system design questions should I practice first?
Start with two or three classics that cover different challenges, such as a URL shortener, a news feed and a chat system, then add questions close to the company's product. Prompt 2 orders them for you.
Is ChatGPT's feedback on system design reliable?
It's good at spotting missing components and unasked requirements, less reliable on numbers and level judgments. Verify facts, recalculate estimates and treat its level estimate as a rough read.
Rehearse it out loud before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview