# AWS Identity call

\[April 11, 2022, 6:09 PM] Choudhury, Zafar: On System Design, the interviewers are not always looking for people to finish the system design part of the question but they want to know how you are thinking about failure scenarios, latency issues, scaling, availability, etc. because at the end of the day there are four pieces that you have to put together. If you focus too much on one piece or it seems like you are not able to speak about all the other areas, then that may be a concern for them.

System Design Primer: <https://github.com/donnemartin/system-design-primer&#x20>;

System Design: <https://www.youtube.com/channel/UC9vLsnF6QPYuH51njmIooCQ&#x20>;

Grokking the System Design Interview: <https://www.educative.io&#x20>;

Grokking the Object Oriented Design Interview: <https://github.com/tssovi/grokking-the-object-oriented-design-interview/blob/master/object-oriented-design-case-studies/design-chess.md> \[April 11, 2022, 6:09 PM] Choudhury, Zafar: Problem Solving Methodology:

1. Clarify the Question - ask clarifying questions to make sure you understand all the variables and address any ambiguity – Ideal time - 2 minutes
2. Rephrase the Question - Repeat the question back in your own words so the interviewer knows you understand the problem, highlight the signature, the inputs you are given and what type of method or function you will be using – Ideal time 1 minute
3. Layout the Algorithm - In order to save time and optimize communication write down your algorithm either before or as you review it with your interviewer. Make sure you state time complexity and have your interviewer agree – Ideal time 3 - 4 minutes
4. Write your code — I have found it is hard to talk and code so for best performance let the interviewer know you are going to focus on Coding for the next 10-15 minutes.
5. Review your code - Optimize, validate, identify edge cases, fix any bugs, test your code and discuss where future enhancements might arise with your interviewer. Ideal time – 5 minutes
