Note: This Post was originally published on Hackernoon.
Over the last two years, I've helped 100+ engineers prepare for interviews in tech compani...
For further actions, you may consider blocking this person and/or reporting abuse
It'd be nice to use more inclusive gender-neutral language, or at least alternate she/he pronouns and avoid phrases like "Don’t be that Guy." Perhaps "Don't be that Candidate" or "Don't be that Person" or "Don't be that Engineer."
April, this is really good feedback. I went ahead and made changes to the post. Thanks a lot.
Really good article with solid tips. Structure, in-depth understanding of the topics and timing are really crucial for those type of interviews. I have also created System Design Template which is generic enough to be used for any interview but also FAANG companies.
Last time we research which storage technology we can use it it took us more than 1 week, researching and gathering all the factors (prices, bottle necks, open source or not, managed or not, libraries, pros and cons ...) so to answer in 10s at an interview is ... superficial. But then the interviewer knows this so ... there is no right answer, right? but there are wrong answers :)
For me, I approach these answers by identifying and focusing on what technical needs the system requires, rather that the technology (at first). You don't want to get stuck trying to defend your choice for Microservice A data storage when you haven't begun to talk about the goals and responsibilities of Microservice D.
This was really enlightening. Thanks for the information. I'll be sure to carry it to my next DevOps interview.