I'd strongly dispute this point - these tags need to (usually) be written once per organization, occasionally you need to come in and fiddle with it, but the contents of your page header should occupy no brainspace. Additionally I think this interview question might be testing a depth of knowledge, but not one that's actually relevant for your position. I've worked on backend systems for most of my life (that and databases) and I can definitely name the purpose of most of these tags since, back before node, I'd just be popping them out in some PHP file somewhere - again, once written and then mostly forgotten about. If the job responsibilities are going to involve a modern front-end framework/language suite and your interview isn't even touching on that topic then you're not effectively interviewing for the position - you're querying about some corollary information that most people in the space will sort of know but, if I was their manager, I'd be happy as a clam if they popped over to the MDN and copy-pasted a big chunk of this as a starting point... assuming they ever actually needed to interact with it.