We can use API gateway to request throttling, rate limiting. The APIs can be abstracted behind the API gateway which will throttle and route the requests.
The interviewer played his role well, that's how interviewers behave usually - kinda reserved, not following exactly the train of thought or direction of the interviewee, asking a lot of follow up questions in the middle of something! This is legit stuff! Typically on other videos from this channel, the interviewer is either missing or too nice. I noticed that Jacob was a bit underperforming, compared to the stellar designs in other videos. I think it is mostly because of how the interviewer leads the interview. Keep that in mind, interviewees! Most of the interviews will be something like that. I usually want to draw some boxes, talk about concrete implementation and it's kinda sad that most interviews have really strong timelines and leave me unfullfilled.
Love the idea behind this video, it's very timely. Thank you so much!! Want to see more of it. Also, more in depth discussion would be helpful. Also for the interview, using "tsk" sound often can be distracting.
@@tryexponent Thank you so much for responding so quickly! Totally surprised, and really grateful. Next video request: How would you design Dropbox API? How would the client request data on the document from the server, especially as the document gets large enough that you wouldn’t want to download it in a single request? How would you handle loss of internet connectivity in the middle of download/upload? How would you add new features without breaking older clients?
10:46 clear explaining. I like how you set up explaination by saying goign heads up on it's prior to request sent( to creating token or obtain token then send it WITH the request). Great thorough explainations with a clear structure, and specific implementation details on how the authentication works The simple way to explain would've just been "we use tokens"
Hey, Thank you for doing this. Very concise and systematic approach. Very seamless flow of discussion. Do you have a video that goes into depth that you referred in the end. I would like to learn about approach or details on the architecture and implementation side. Especially how much details are expected and how to balance between keeping it abstract enough while covering important part for that section.
14:05 was it a good idea to basically justify why interviewer asked about rate limiting? Usually they don't really care about these signals, although you might show them your depth of the topic and friendliness, but aren't you wasting time potentially when they just care about the solution to the problem given?
Hey DiklahC! This video is more technical than most PM interviews will go, but some of these concepts are certainly fair game for the interview. I'd recommend checking our our technical PM mock interview to get a better sense: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-3MsWDQJmYOE.html
This seems like a quiz on technical jargons (What is REST, 4xx status codes, OAUTH). Too elementary for an actually system design interview. Remember that you won't even be given a system design interview if you're applying for an entry level position.
@@tryexponent Thanks appreciate :-) I have a Technical Product Manager interview at Israel and I am looking for an example of Technical Product Manager questions, you wrote that this is a Technical Program (and not product) Manager interview- why?
@@barakhazan26 System design interviews often don't occur in product manager interviews. However, it's definitely possible! We'd recommend asking your recruiter about what types of questions to expect, and preparing as such.
@@tryexponent Do you think I can ask HR what questions to expect? Is it legitimate to ask that kind of question? I am not familiar withe the VP products person, the person from the HR talk with me to about the interview.
That’s not a good solution 😇 Wrong HTTP Verbs in REST, what about backend for Frontend pattern? Or ask about what clients are there to also choose between REST BFF or GraphQL. What about real time interaction or push notifications / subscriptions …
