3 ms·
This is like a masterclass in how to answer system design questions. Maybe a bit verbose. They cover requirements, how to answer those requirements, relevant te
by NotAnOtter 5y ago
This is like a masterclass in how to answer system design questions. Maybe a bit verbose.
They cover requirements, how to answer those requirements, relevant tech for the problem, implementation, and techniques for maintenance
- deleted 5y ago[deleted]
- bcrosby95 5y agoAre you saying that one person, without consulting other engineers, or having to do any research, made this decision in less than a day? Because I have some bad news for you. The sentiment you express here is why interviewing is so shit these days.
- golergka 5y agoWell, that's true for any task that you're asked to complete at an interview: you're doing the fast, draft version that is obviously not comparable in quality to what you would do in a real setting. But still, even this draft could be illuminating.
- whymauri 5y agoAre you replying to the right comment?
- imdsm 5y agoThey must be. Totally out of context response.
- NotAnOtter 5y agoNo? But I am saying this is like an extremely articulate, over the top, excessively detailed answer for a system design question. I'm not saying this is what people should aim for, just that it's a good example of the types of things you should discuss during a system design interview. I mean that's what it IS. It's a system design.
- manigandham 5y ago1) Yes, there are people that can do this. 2) But this isn't an interview situation. This was "system design questions" as in how to solve a problem as a company using the whole team (4 backend engineers at that time).