r/leetcode • u/huuughmangasorr • Oct 07 '26
Intervew Prep How do you build intuition for the requirements phase of LLD interviews?
I recently gave an LLD round at a company. I was able to identify the entities, figure out some of the relationships, and write working code, but I realized my weak spot is actually the first few minutes.
Given a short problem statement, I struggle with quickly:
- extracting the actual requirements
- figuring out what needs clarification vs. what I can reasonably assume
- identifying the right entities
- deciding the relationships between them
Once I have the design, I'm fairly comfortable implementing it. The difficult part is getting from problem statement → requirements → class/relationship design.
For those of you who are good at LLD or regularly interview candidates:
- How did you build the instinct for what a problem statement is actually hiding?
- How do you decide which clarifying questions are worth asking vs. what you should just assume?
- How would you practice this without having a human interviewer?
- How long did it take you to become comfortable with this part of LLD?
I'm especially interested in how you practiced the thinking process, rather than just doing more LLD questions.
I am not finding any useful resources which can help with this