In this episode, I walk through the context and goals of a systems design and architecture interview. If you're considering working for a tech company, you'll almost certainly be asked to tackle a high-scale systems design problem. This video explains why companies ask this of you, how to prepare for this interview mentally and emotionally, and what success or failure might look like.
A full write-up of this video is available here: [ Ссылка ]
If the background music bugs you, here's a version with no background music: [ Ссылка ]
Contents:
The part about money [ Ссылка ]
Different kinds of interviews [ Ссылка ]
Coding interviews vs. architecture interviews [ Ссылка ]
The structure of an architecture interview [ Ссылка ]
The actual architecture question [ Ссылка ]
How much this question sucks [ Ссылка ]
Life isn't fair [ Ссылка ]
Breaking the problem down [ Ссылка ]
All the stuff I didn't talk about [ Ссылка ]
The goal of the interview [ Ссылка ]
The most important point [ Ссылка ]
Failing this interview [ Ссылка ]
Why these skills might get you fired [ Ссылка ]
Reasons you can succeed [ Ссылка ]
Advantages you can leverage [ Ссылка ]
Getting rejected [ Ссылка ]
![](https://s2.save4k.ru/pic/ZgdS0EUmn70/maxresdefault.jpg)