This article provides an overview of practices and areas of focus when navigating a high-level systems design interview. I expect this information will be most helpful to engineers with 1-3 years of experience or those who have never done a systems design interview.
Additionally, this article is expected to be used as a jumping-off point, and readers will likely need to leverage other resources to dig deeper into the referenced concepts and terms.
What You Can Expect
The shape of a system design interview will likely depend heavily on the company with which you are interviewing and the level of the role for which you have applied. For instance, an intern or an associate-level candidate might be asked to diagram how multiple classes or modules in a system would interact with each other. In contrast, a more experienced candidate might be asked to design an entire distributed system.
These interviews are generally conducted in a “whiteboard” style, where the interviewer will ask the candidate to present their answer as a diagram. Before the increased prevalence of remote work, this would be conducted on a physical whiteboard; however, as more of the engineering workforce moves to remote work, these interviews are more commonly being performed with tools like Excalidraw, tldraw, diagrams.net, and similar online whiteboarding tools. Ideally, the employer will let you know which tools they use for their interviews, and I highly recommend familiarizing yourself with the tool ahead of time. If the employer doesn’t let you know which tool they expect you to use, don’t fret: the interviewer shouldn’t be grading your proficiency on using a specific tool.
System design questions are designed to understand a candidate’s ability to think deeply about systems and their requirements. These questions generally require a candidate to talk about a system they’ve already worked in, or more commonly, about a theoretical scenario.
Below are examples of questions that I’ve been asked, others have been asked, or that I have asked:
- Can you describe a system you’ve worked in recently?
- How would you design the backend for a social media app?
- How would you design the system for a parking garage?
- How would you design an e-commerce site?
- How would you design the content management system for a large blog?
For specialized industries, an interviewer might ask you a question specific to the domain they operate in, so it wouldn’t hurt to understand some of the complexities of their industry. However, it is just as likely that an interviewer will ask you a generic question, so try not to deep dive too heavily into specialized solutions during your preparation.
Prepare for the Interview
The systems design interview can and should be something you deliberately prepare for, just like any other interview.
An easy way to practice systems design is to diagram the system you are currently working in and identify the components or areas that are undefined or unknown to you. This exercise should help you identify additional areas of preparation. For instance, your system may use a specific type of database or leverage a cloud provider for block storage. Do you know why the original designers chose a particular database technology? Do you know the benefits and tradeoffs of block storage? Looking into these and related topics more deeply should be part of your interview preparation.
Your Current Work
If the system you are currently working in isn’t very complex or exciting, you may be inexperienced and thus disadvantaged when designing a system from scratch. If this applies to you, it is recommended to spend time answering some of the example questions above, watching mock interviews on platforms like YouTube, and even asking your friends or trusted colleagues to run a mock interview with you.
Seek Out the Customer
A system is only helpful if it serves a customer’s needs.
Identify the Customer
A “customer” is any user of the system. These “customers” could be the actual human being using the mobile app that interacts with your system, or they could be other services inside a company’s microservices architecture. As the system designer, you will need to ask yourself: “Who is my primary customer?” Then, keep the customer in mind as you design the system.
It will be vital that you identify who the primary customer of the system is and what requirements those customers have of the system. If it is not apparent who the customer is during the interview, it is recommended to be direct and ask the interviewer, “Who is the primary customer of this system?” The interviewer should be receptive to these types of questions.
Additionally, you can identify the primary customer by making assumptions based on statements made by the interviewer. For instance, if the interviewer asks you to “design TikTok” (a popular video-sharing app), you could assume that the customers are global users who primarily interact with the system using their smartphones. Once you think you know who the primary customer is, you should validate this assumption with the interviewer: “Is it safe to assume that my primary customer is global users who are using a smartphone application?”
Identify Customer Needs
The “needs” of the customer can generally be defined as either “functional requirements” or “non-functional requirements.” It is imperative to identify and validate requirements (both functional and non-functional) with the interviewer before you start providing your solution.
Generally speaking, you should start by defining the system’s functional requirements, and your interviewer should be receptive to your questions about these requirements. For instance, given the question to “design TikTok,” you might ask your interviewer if the below list of functional requirements satisfies the customer’s needs. The interviewer will likely reply, “Looks great to me!” and if not, you should try to dig in on what functional requirements you might have missed.
- Upload short videos (length <= 3 minutes)
- View a “feed” of videos
- “Like” videos
- Comment on videos
As you dig into your system design, these functional requirements should also expand to include the fundamental ways they will be satisfied. For example, it would be a good idea to list out the various API endpoints needed to satisfy each requirement and maybe even which database structures (tables, documents, etc.) might be required to support those API endpoints. Later on, we’ll touch a bit more on when you should go into detail and also when you should leave things vague.
Along with functional requirements, non-functional requirements should be identified and vetted with the interviewer before you dig into or decide on system architecture and start creating a diagram. These non-functional requirements could include concepts such as:
- High Availability
- Low Latency
- Eventually Consistent (or Strongly Consistent)
When determining which of these are relevant to your system, you should always ask yourself how this requirement would serve or impact your customer (the end-user). For example, in the question to “design TikTok,” you might presume that this system could support an architecture that is “Eventually Consistent.” You could argue that it is more important that users can quickly access videos in their feed than for those videos to be the latest or most up-to-date. This argument would suggest that eventual consistency is sufficient.
When making these arguments or assumptions, you should again validate them with your interviewer. If you fail to validate your assumptions, you may be leaving yourself open to a “curveball” later if the interviewer decides to introduce a constraint contrary to an assumption you made and that your design does not support.
To validate your assumptions, you may pose the question to your interviewer: “Is it safe to assume that it is more important for the video feed to load quickly than it is for the videos to be the most up-to-date?”
Knowing the Appropriate Level of Detail
A common misstep when answering system design questions is when you provide too much or too little detail. Knowing and ascertaining the correct level of detail expected from your interviewer can be vital to answering your question correctly and sufficiently. Remember that interviews are a two-way conversation between the candidate and the interviewer, and becoming comfortable asking these questions will make you more successful. When describing a particular component of the system, take a moment to pause and ask your interviewer: “Is this the level of detail you were expecting, or would you like me to give more or less?”
For example, prematurely giving too much detail can hinder you, especially when digging deep on a particular portion of the system in a sufficiently more detailed way than others. An easy example of this can be when describing databases. The chances are that the system you are designing will require some database or data storage, and you might be eager to blurt out the first database technology that comes to mind, or maybe whichever is your favorite. Unless you’ve established with the interviewer that they are interested in these finer details, try your best to avoid doing this. If you feel the urge to recommend a specific solution, be sure to confirm with the interviewer if they would like those details at that time, but it can also be advantageous to defer that decision.
By avoiding specifics where they aren’t yet necessary, you allow yourself the flexibility to make this decision later when you potentially have more information. You also avoid showing a potential bias towards a solution or technology that may not fit the system’s requirements. If you do go as far as to state that the database will be a NoSQL database, and even worse, will specifically use Cassandra, you’ve made a strong indication that you think these technologies would provide significant value to the system. The interviewer would be well within their rights to go deep on questioning these decisions.
Don’t Show Up With a Solution
You’ve likely worked in a few different architectures, and you might even have a favorite design or pattern that you think works best. Experience and opinions are great, but this can be a trap when answering system design questions. It is best to avoid approaching systems with rigid pre-existing solutions or designs.
For example, suppose you are a big fan of event-driven architectures and are already set on or fantasizing about how you’ll apply this pattern to whichever scenario the interviewer describes. In that case, you’ll quickly fall short when the functional or non-functional requirements of the system don’t lend themselves to the limitations of your predetermined solution.
Rather than showing up with an architecture already in mind, it is best to understand standard components and approaches and where they can be employed to satisfy different requirements of any given scenario. While the list below is not comprehensive, and the best components and approaches will vary heavily based on the system, it is recommended to understand where each offers value and which tradeoffs they present. These topics are likely to be expected knowledge for mid-level and higher backend engineering interviews.
- Vertical vs. Horizontal Scaling
- Monolith vs. Microservices Architecture
- Database Approaches (Relational, NoSQL, Graph)
- Event/Message Queues
- Load Balancers
- Block/Cloud Storage
- Content Delivery Networks (CDN)
I hope this article gave you some insights into what to expect from a systems design interview and strategies for successfully navigating them. As stated at the beginning, this article likely isn’t where your preparation ends but where it has just started. I highly recommend digging deeper into the above concepts via other resources and watching a mock system design interview (or ten) to gain broader exposure to common questions and suitable approaches.
If you landed on this article while preparing for an upcoming interview, or if someone shared it with you, I wish you the best of luck! Please feel free to reach out to me with any questions or comments.