I got such fatigue from scrolling through so very much prologue, introduction, expectation-setting, and general "here is what we are going to say and here is how you may expect we will say it" fluff that I gave up, pages in, before getting to any apparent content.
I like some parts of part 1 too, like this paraphrased quote from a senior FB engineer “I’ve learned more about distributed systems reading the internal interview wiki at FB than anything I ever actually built myself… the actual systems at scale are designed by platform teams and most engineers don’t have to think about the impact of dumping a billion messages on a queue, because the infra team will handle it”.
Goes to show what a ridiculous game we’re all forced to play in tech.
That is why the infra team get paid the big bucks (bigger than normal SWE) and are basically untouchable in layoff rounds. I know FB was still in full hiring mode for infra folks, even in the middle of layoffs / hiring freezes. I assume this is the same at the other FAANG / FAANG-adjacent companies.
Hey, founder of interviewing.io here. We actually did zero thinking about SEO. We had someone look at this guide at the end through an SEO lens, but then we decided that that would make the content not as good and would make the guide less readable.
(As an aside, I think in recent years, the spirit of SEO has become more about just making good stuff and less about hacking...)
Anyway, it wasn't for SEO. It's hard to edit stuff well because we're so passionate about what we wrote here, and we probably should do another pass.
These people don’t have to think about SEO because it’s already been embedded into them. BS corporatespeak at their very core, the perfect type to sell interview gaming.
