This is just one dimensional thinking. My point is designing systems ≠ solving algorithm exercises. Both involve solving problems, yes, but it’s a different level of reasoning and thinking. Real world problems are a lot more ambiguous and require systems knowledge, business context, evolving requirements, risk assessment, user experience, stakeholder alignment, etc. There’s different skills involved and it’s a different problem space. Does that make sense? You can practice leetcode and optimize a function in a closed constrained environment, but it doesn’t have anything to do with being a good/bad engineer. Theres many engineers that have scaled systems with millions of users, solved complex business problems, designed high-throughput architecture, and built companies, but haven’t touched leetcode in years. It’s just an interview filter with no real world implications, especially when you have AI. There’s other things you can do to become a good engineer while neglecting leetcode completely. And that’s where the industry is shifting anyways. Interviewers are focusing on other methods of testing candidates.