Front-end lead here, building large desktop apps for my company&#x27;s internal use.<p>I&#x27;ve never had a web-app that failed due to performance. I can&#x27;t recall any that ever have, except Facebooks&#x27; attempt to use HTML on mobile.<p>UI performance has little to do with algorithms, and only occasionally requires opening the profiler to hit 60fps with some tweaks to bone-headed nested loops. Or maybe reconsider your use of Angular!<p>Front-end apps fail because long-lived mutable state is a powerful engine of complexity, and algorithms do not solve complexity. I am constantly telling my team (CS back-enders prepare yourself!) to <i>ignore</i> performance concerns. O-whatever has zero-impact on delivering simple, extensible, bug-free web apps that please its users.<p>But admittedly, crafting good software isn&#x27;t as objectively clear as implementing a mathematical function that makes your server code perform. The proliferation of front-end frameworks and compile-to-js languages indicates that writing FE software that <i>works</i> remains a far greater challenge than writing FE software that hums.<p>To that point, maintaining a popular github repo for a library or app that demonstrates your ability to write, maintain, and extend FE software is still the best sign that you know what you&#x27;re doing, and that you <i>like</i> what you&#x27;re doing. Conversely, knowing a lot of algorithms as a FE candidate tells me nothing about whether your first PR will be your last.<p>On a happy note, Netflix didn&#x27;t ask me a single question regarding algorithms! Their interview&#x27;s focus on OOP made sense, even if it didn&#x27;t fit with my own focus on ClojureScript and FP.