Well, being a good engineer is about more than knowing all the leetcode algo ins and outs. If you're bound and determined to work someplace that interviews prim

Well, being a good engineer is about more than knowing all the leetcode algo ins and outs. If you're bound and determined to work someplace that interviews primarily on that basis, treat the leetcode like an entrance exam- cram cram cram and you won't need the leetisms very much after you pass. Do you understand how to set up testing for the right things, how to design for testability? Do you understand the ins and outs of HTTP and object API design? How to review code for the right characteristics per PR? How to distribute and scale computations, how to build for economical operation as well as CPU and memory performance? How to write a spec or an onboarding doc? Leetcode is a do-it-the-way-prominent-companies-did-it meme. It's not wrong on its own, but it's one dimension out of many, and the best leetcode problem solver I ever interviewed was a terrible senior engineer.