This seems to be closer to the right approach to interviewing over the leetcode grind, but it's the wrong example. The head tags are trivia and have changed a l

This seems to be closer to the right approach to interviewing over the leetcode grind, but it's the wrong example. The head tags are trivia and have changed a lot over 5-10 years (not to mention Twitter doesn't include the head tag which is just wrong, IMO, though every browser since the '90s is flexible on this and everything else to do with HTML). Many front end devs haven't touched the head tags because that's a separate team. Or it's the lead devs that set that up. It's also the kind of thing you set once and never touch again and every site will use different head tags. A better approach is to drop into some code and ask the candidate to explain it. What's the code doing, why is it doing it. Maybe even show some code with a bug and have the candidate fix the bug. That's like 60% of most jobs right there. Reading code, understanding what it's doing, and figuring out how to make changes to it.