3 ms·
>Secondly, the author believes that senior developers, who likely have 10+ years under their belt if they're senior, need to spend a solid month revising in ord
by fatnoah 6y ago
>Secondly, the author believes that senior developers, who likely have 10+ years under their belt if they're senior, need to spend a solid month revising in order to be successful landing a role there.
FWIW, I joined FB at 20 YOE and spent about 3 hours on Leetcode problems just to get my mind back to being able to handle "stupid computer" tricks. Array manipulation, algorithm cleverness, etc. are things that I hadn't really done since the early days of my career. Aside from that, the only real challenge was a system design interview with a VERY junior engineer where I had a really hard time keeping things at a level they'd understand while not coming across as patronizing.
- permille42 6y agoI had the same experience. They only asked about things I haven't focused on or cared about in over 20 years. The person on the other side of the design interview also seemed very inexperienced and wasn't able to follow things that would be obvious and simple to anyone who has actually done system architecture.
- fatnoah 6y ago>...things that would be obvious and simple to anyone who has actually done system architecture Load balancing web servers was one of those that almost got me in trouble. I just assumed that any sane web infra would balance load.