To expand. I guess it depends on the company, as well. I have no idea what engineers at faang do. I can tell you what I have been doing the last decade: - dec

To expand. I guess it depends on the company, as well. I have no idea what engineers at faang do. I can tell you what I have been doing the last decade: - decide what kind of db we should use for our next product. Usually a relational one is good enough, although sometimes document or graph ones are needed - DDD. Or at least I try. Our engineers are able to understand the business and relate terms of the problem domain with ones in the solution domain - identify race conditions. Phantom reads? Those suck, but I keep them out of my codebases - maintenance of public APIs. From authN, to authZ, and keeping backwards compatibility as much as possible - observability, monitoring, slas, slos, slis - debugging distributed systems and distributed monoliths - splitting monoliths into microservices because “why not”, and later regret and start with monoliths again for fresh products - decoupling services by using tools like kafka and debezium - mentoring and couching - helping PMs, POs and business people to build products on time - a large etc You know what I have never done? Invert a binary tree. I have read the Cormen book; it’s just that if the company I’m going to work on is all about the things I have mentioned above, then asking leetcode questions is a red flag.