I mean we all know those things are stupid and an employer who puts stock in them is defo not someone you'd wanna work for, cus they are building teams on stupid principles and clearly dont have a clue about making software.
I'd say spend your time building something you always wanted to. That will really show off your skills.
I guess it comes down to the kinda work you want to be doing. I myself love building products and product features and I've never really needed any leetcode knowledge for that (I don't work on products with a massive user base). I suppose if I had a problem that required a specialised algo, I'd just consult a few AI tools.
Good luck finding that motivation though.
I was recently chatting with the ChatGPT about it and it come up with a solid list:
#1, #3, #217, #347 - foundations
#33, #56, #76, #239 - efficiency patterns
#102, #104, #110, #200 - recursion + structure
#207, #133, #323 - graphs
#215, #23, #621, #146, #692 - heaps & scheduling
#295, #355, #460 - system simulation
What I - more or less - asked for:
"Would you say that being good at leetcode style problems is a crucial/important skill for a web software developer who wants to work on the most complex software? Why yes, why not? If so, give me a good LeetCode numbers to tackle for practice in this context"
stitch4143•32m ago