Hello everyone, I have a product design interview comming up in a couple of weeks for a FAANG company. I have opted to go for a product design variant (instead of system) which has a little bit more focus on api/data structure/functionalities rather than on capacity estimation.

Given that, I was thinking about the best way to approach this interview in terms of topics/lenght per topic:

• General questions (clarify functionalities, target audience, non-functional specifications, etc.): 5 minutes.
• API Design (both URI and design the main methods that will be exposed to a user, such as post and get_newsfeed for a "design facebook" question): 5 minutes.
• Data structure (designing the tables, their relationships, not focusing that much on the technology yet): 5 minutes.
• High level system design (draw a diagram with the components, what they do and how they are connected, talk about api gateway, serverless vs. kubernets/ec2 architecture, etc): 10 minutes.
• Deep dive on a few topics, such as authentication, bottlenecks/single points of failure, HTTP/longpooling/websockets/message queues, internal workings of a particular component, etc): 10 minutes.

Considering that the full interview is supposed to take 45 minutes, and introductions could take up to 5 and so could the conclusion section, that leaves me a total of 35 minutes. This also gives some time in case the interviewer asks for me to clarify something a bit better.

Would you say the order I suggested to tackle the interview, and the time sepparated for each section sounds ok? Any input is appreciated!