Then I'm happy to prepare for the interview in the sense that I try to learn as much as possible about the company and the people I'm going to meet.
Then I'm happy to prepare for the interview in the sense that I try to learn as much as possible about the company and the people I'm going to meet.
The rampup at FAANG can be brutal and you'd be doing lots of learning even after getting in. The leetcode style interviews are designed to select people capable of studying and materialising broad problems in depth and scope under time constraints. They are also objective and can't really be faked nor you can talk your way in like in most banking/finance IT jobs. I was of similar opinion at some point but these realisations made me change my mind and I've come to like leetcode interviews. But I also think they only make sense in FAANG scoped companies where all the stack is proprietary. Small companies or companies using opensource tools don't really have this rampup and are doing such interviews mostly because others (FAANG) do it.
I’m very happy to be in a position where I can do most learning during company time, and then spend my free time with my wife and kids.
Edit: Anecdote time. The best interview I ever had was for my current job. It was a hour long where they gave me 1 design problem to solve. It was an open problem but the interviewer kept introducing new information. "Lets say the speed of stage cannot exceed x", "what if the wafer cannot take the stresses you will generate?", etc. I think that showed both my design thinking and the ability to assimilate new information in my mental model.
Leetcode is a memorization/trivia exercise, not a reflection of someone's deep understanding of proper coding practices, software architecture, and ability optimize in real world cases (since in the real world you can use google and use whatever libraries you want).