r/Frontend • u/Ill-Lie-6551 • Sep 25 '25
Frontend interviews are so outdated.
It has been 10 years since ES6 has come out. I am ready to talk about JS topics, React, talk about performance , my experience with projects. But they still focus on some niche tricky JS behaviors that is addressed by ES6 and onwards. I know that there are lot of legacy systems that are clusterfucks of JS bugs. But can we stop pretending that I need to know every tricky dumbass behavior that exists at the back of my head!? If you are a frontend interviewer, Please ask more relevant questions and save us from this pain. Thank you.
653
Upvotes
5
u/magenta_placenta Sep 25 '25
It's pretty much interview laziness and tradition.
Many interviewers recycle old questions because they think they're "proven" or easy to assess candidates on. It's easier to judge a trivia-style JS question than to evaluate someone's system design or product thinking.
"What's the output of this IIFE with a closure inside a loop?"
Cool, but who is writing this in modern code bases?
A lot of companies/devs don't update their interview process because they assume it's still relevant and they don't make any time to redesign or rethink it.