I think it depends on the question and what you do with the response. If I were interviewing for an entry position and I asked "how is a GET request structured

I think it depends on the question and what you do with the response. If I were interviewing for an entry position and I asked "how is a GET request structured?" And they don't know, I'd like the answer to be "I don't know." Because then you can try and work through the problem space to go from "what trivia do they know" to "how accountable are they for what they know/don't know and how much do we need to devote in resources to get this person productive on our stack" All that said this stuff is just useful for a technical screen to filter into "entry level" to "junior" to "little experience but lots of knowledge junior" and can be gauged to estimate the success of the person in the business. Ultimately it's all about balancing risk. Some of the people coming out of boot camps are really risky hires because they don't have the tools to thrive in certain businesses, particularly smaller ones without much time to devote senior staff to mentorship. That doesn't mean they can't or won't, it's just about estimating if the risk outweighs the payoff once they're flying. I've been through this myself for even senior roles. I interviewed at a fintech where they asked me in the first call stuff like "how do you access a server from your dev machine" and "how do you edit a file from the command line on Linux" and "how do you kill a process on Linux." Very basic stuff, but it's not insulting. There are devs out there that can't answer those questions and they needed to be filtered out for that particular role. It happens.