Software Engineer Handbook
  • 👋Welcome to this handbook
  • Level 0 : Non-technical considerations
    • How to manage your time effectively
    • How to prepare for job interviews #1 : Digital Presence
    • How to prepare for job interviews #2 : At the interview
  • Level 1 : Computer Science
    • Intro: Why computer science is critical
    • Algorithms & Data structures Handbook
      • Algorithms & Data structures Handbook
      • Sorting Algorithms
      • Data Structures ADTs Implementation (In Go)
      • Techniques for Solving Data Structures Problems
    • Computer Organization and Architecture
    • Operating Systems
    • Database systems
  • Level 2 : System Design
    • Step 1 : Analysis
    • Step 2 : Digging deeper into data modeling
    • Step 3 : High-Level component design
    • Step 4: Low-Level / Detailed Design system
      • Clients
      • Application Servers
      • Databases
      • Security
      • Distributed Systems with Microservices
  • Level 4: Productivity Handbook for Software Engineers
    • How I use Fig
    • Command line tools
    • Develop on the cloud
  • Extra
  • Leadership
    • Processes
    • Poeple
    • Delivery
    • Transitioning to a new role
    • Resources I like
Powered by GitBook
On this page
  • Steps ⚡:
  • Examples of asking questions 🔍:
  • ref:
  1. Level 2 : System Design

Step 1 : Analysis

Try to understand the problem and establish the scope

PreviousLevel 2 : System DesignNextStep 2 : Digging deeper into data modeling

Last updated 2 years ago

Steps ⚡:

  1. Gather Requirements

  2. Always ask for clarification. Do not assume your assumption is correct

  3. A solution designed to solve the problems of a young startup is different from that of an established company with millions of users. Make sure you understand the requirements

  4. Ask Questions

Examples of asking questions 🔍:

1. What specific features are we going to build

2. This a mobile app? Or a web app?

3. What are the most important features for the product?

4. How fast does the company anticipate to scale up?

5. What are the anticipated scales in 3 months, 6 months, and a year?

6. What is the company’s technology stack? What existing services you might leverage to simplify the design?

7. How many users does the product have?

Good muck interview to explain how to ask questions to do analysis

ref: