I take it this wasn’t for a front-end developer position? I can’t understand the point of memorizing the QuickSort algorithm itself, given it’s been implemented a dozen times. Maybe memorizing its Big O notation in comparison to other algorithms… But even Chrome V8 uses TimSort, which is a bit complicated to memorize beyond just conceptually. So why memorize QuickSort beyond its pros-cons? I don’t understand the benefit as far as the interview in the least. I’d think a pair programming exercise (on a real codebase) or an “implement this business objective” live coding task using your preferred or the company’s preferred framework would be better.

Thanks for sharing your experience Gourab Sarkar !!!

🤓 The physical therapist who writes JavaScript 💪 Web Developer 😎 Mentor 🧠 DPT 😄 SEO Expert 😁 React 😆 Jamstack 💬 Ask me anything 👉 DoctorDerek.com 👈

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store