![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
World of interview madness
Jan. 6th, 2019 00:35I've been reading few subreddits related to CS careers, general programming stuff and similar things on Hacker News for quite long time and it's pretty obvious that process of interview in US is way different from anything one could find on our side of the pond.
How it is complicated amazes me every time, but it is other people's business to do all these strange things to be hired by Google/FB/etc.
Grinding leetcode, studying long months, preparing yourself for stressful days of interviews on bunch of imaginable and unimaginable problems - you name it.
And below there is one more bizarre examplar of such activities, detailed overview of system design of Uber-like company. If it would be some solution architects stuff - I would be totally fine with it, because somebody needs to be that smart to keep such high-level and simultaneously high-detailed platform map in his/her mind on constant basis and direct others.
However, this is system design overview answer on interview question for some software engineer role, not architect's one. And this is crazy, simply because the person that would be hired after reproducing this overview would be doing same boring routine programming stuff, I guarantee that. Or, more likely, a lot of described stuff would be outsourced to our side of the pond =]
How it is complicated amazes me every time, but it is other people's business to do all these strange things to be hired by Google/FB/etc.
Grinding leetcode, studying long months, preparing yourself for stressful days of interviews on bunch of imaginable and unimaginable problems - you name it.
And below there is one more bizarre examplar of such activities, detailed overview of system design of Uber-like company. If it would be some solution architects stuff - I would be totally fine with it, because somebody needs to be that smart to keep such high-level and simultaneously high-detailed platform map in his/her mind on constant basis and direct others.
However, this is system design overview answer on interview question for some software engineer role, not architect's one. And this is crazy, simply because the person that would be hired after reproducing this overview would be doing same boring routine programming stuff, I guarantee that. Or, more likely, a lot of described stuff would be outsourced to our side of the pond =]