I processed a lot of open data from Stackoverflow, Instagram, H&M, and others. I'm interested in how users return to make their actions: to write posts, to make a purchase, to answer a question.
This data can be valuable for startups to develop their business models as repeat users are the core of any business.
Or at least the JS reference. Or design the questions to fit the role. If it's a frontend role, then ask frontend questions, not some bullshit high school arithmetic.
I wrote most of the 'fizzbuzz' function but couldn't remember the "%" operator. Tests are annoying because it's not how developers work, at least I don't work that way, without any way to verify syntax or look anything up.
I recall an interview from years ago where I was asked to show the code behind my websites and step through it explaining what it did and why I did it. This is better than a test, because you're explaining how the code works and also showing off your work.