The tag interview-questions seems to be useless - should it be burninated?
It's rather a meta tag (like homework) but I find it interesting to see what's going on interviews.
Furthermore it helps to distinguish homework questions from interview questions which are sometimes very similar to each other.
So, I would not delete it.
interview-questions is a meaningless tag. Whether a question is an interview question or not is completely irrelevant: it doesn't change the nature of the question or the expertise required to answer the question. It isn't useful to categorize the question or to make it more visible to its intended audience. It is a meta tag and should be deleted.
interview-questions might still pop up from migrations from Stack Overflow, where it is being phased out but still present on some old questions.
I don't think interview-questions is a particularly useful tag.
Well, ideally, if the questioneer specifies what particular problem the interviewer had with the code, we can put ourselves in the mindset of a hiring company, think about what we'd expect to see in a candidate, think about why we were asking this particular question, and then try to answer how we might respond to receiving this code in an interview.
But... is this happening? Most of the interview-questions questions I see don't specify any specific problem the interviewer had with the code. Those that do specify extraordinarily vague reasons (to the point where it's not helpful). And even when the questioneer is asked directly in comments, they often say "they didn't tell me", or something of the like.
So, what good does the interview-questions tag do? Best case scenario, someone preparing for a job interview could search through the tag in an effort to prepare for an interview. That's the only benefit I can see to the tag.
It doesn't add any useful information to the question.
Moreover, one of the reasons that has been mentioned in the past that you must be the owner (and now we allow maintainers) of the code submitted for review is because we don't want to allow reviews posted to Code Review be the basis for hiring/firing decisions.
While some (most/all) may be using the interview-questions tag in good faith and truly trying to just gain a better understanding of what was wrong with their code so they can do better in the next interview, it's not inconceivable to imagine a user who sees this tag and decide to use it to post code submitted as part of an interview (to help an interviewer make a hiring decision) or for a user to attempt using a set of mostly positive reviews to their code as an effort to suggest to a company that their assessment of the user's interview code submission was wrong.
I don't know how likely those described scenarios are, but with these possibly scenarios combined with the previously mentioned problems with the tag, I think it's certainly worth considering eliminating the tag.