You can go that way. I find it very unlikely the person interviewing you would "see the errors in his ways" and go "ok you are right, dumb question". It is a

You can go that way. I find it very unlikely the person interviewing you would "see the errors in his ways" and go "ok you are right, dumb question". It is a human flaw that when we interview, we project. If we are really good at X, we want to deep dive on that topic. Perhaps it is important for the job. Perhaps we are just trying to show off to a candidate. Who knows. I know I am a fullstack guy, but light on React. If the interview before me was a webdev and asked you a bunch of React questions, I could not add anything of value there. So I would poke around algos and linux and testing and CD and all of the other things I know about, to see where you fall. Not really to show off how leet my algos knowledge is... but I personally would rather hire a guy who knows big O, all things else equal. I do doubt most jobs are so specialized you only need 1-2 frameworks, and nothing else. Knowing what memory is isn't a terrible thing to understand for any programming job...