Whiteboard to Blueprint: HLD & LLD
Translating fuzzy requirements into buildable designs — architecture reviews, design documents, and the path from a stated need to implementable detail.
Start reading →01Chapter 1: What HLD and LLD Are, and How They Differ02Chapter 2: Gathering and Clarifying Requirements Before Designing Anything03Chapter 3: HLD Deliverables: Architecture, Components, Technology Choices, Data Flow04Chapter 4: LLD Deliverables: Class Diagrams and Sequence Diagrams05Chapter 5: LLD Deliverables: Database Schema and API Contracts06Chapter 6: Documenting Decisions: ADRs and Communicating Trade-offs to Stakeholders07Chapter 7: Moving Cleanly from HLD to LLD Without Losing Intent08Chapter 8: Common Mistakes: Over-Designing, Under-Specifying, and Skipping Non-Functional Requirements09Chapter 9: When LLD Contradicts Its Own HLD10Chapter 10: HLD and LLD in Design Reviews: What Reviewers Actually Look For11Chapter 11: Worked Example: Ride-Sharing Dispatch — Requirements Through HLD to LLD12Chapter 12: Worked Example: Hotel Booking — Requirements Through HLD to LLD13Chapter 13: Worked Example: Food Delivery — Requirements Through HLD to LLD14Chapter 14: How HLD and LLD Show Up in Interviews and Design Reviews15Chapter 15: Common Interview Questions About HLD and LLD
Other tracks
Python DSA — CoursePython DSA — Interview PrepPython DSA — BeginnerPython Syntax & DSA ReferenceGit MasteryCognitive Skills & Mental ToolsCode Optimization RulesObjects First: OOP FundamentalsPatterns of Good DesignUnder the Hood: Operating SystemsHow the Bytes Travel: NetworkingData at Rest, Data in Motion: DatabasesSharing Time: Concurrency & MultithreadingClean by Default: Coding StandardsThe Review: Code ReviewFrom Idea to Production: the SDLCDesigning at Scale: System DesignBuilt to Last: Reliability & ScalingTell Me About a Time: Behavioral Interviews