What approach framework do you follow in an LLD interview?
basicClarify requirements, identify entities and their relationships, define interfaces and behaviours, pick patterns only where variation exists, then code the core flow and discuss concurrency and extensions.
- Requirements: functional scope, what is out of scope, scale (single JVM vs distributed).
- Entities: nouns become classes, verbs become methods; draw ownership (has-a) and inheritance (is-a).
- Contracts: interfaces for the parts that vary (pricing, strategy, state).
- Core flow: write the happy path end to end, then edge cases.
- Concurrency and extensibility: where is shared mutable state, what changes next.
- Should you start coding immediately? No, 5-8 minutes of requirements and a class sketch prevent rewrites.
- Do you need a pattern in every design? No, forcing patterns is a common negative signal.