A question about system design procedure

There are two common procedures in system design:

  1. clarification --> API definition --> data models --> high level architecture --> deep dive --> further improvements
  2. clarification --> high level architecture --> deep dive --> further improvements

The 2nd procedure leaves the API and data model design into "deep dive" as optional if some interviewers want to ask.

Saw the 2nd one more often in Google interview and the 1st one more often if the interviewers are more product focused.

If we choose a procedure with the wrong interviewer, it often ends as an interview failure. For example the interviewer with 1st procedure will complain you don't provide API design, the interviewer with 2nd procedure will complain you don't have an overview in mind.

Can we ask for this clarification to the interviewer beforehand?

Comments (2)