That's fair. If you're on job search, prepare for the interview at hand!
I'm not saying people shouldn't learn about paradigms, frameworks and tools. Or that they should overly focus on understanding their internals.
But there's _leverage_ here that some (including younger me) might miss:
If I'm getting asked how to use a specific tool, and I understand the principles behind it, then the surface usage becomes much easier to understand as well. Often you can _infer_ specifics or at least make a good argument of what you expect how something works and how you would go about in general.
In the absolute worst case you make assumptions based on conceptual knowledge and apply "wishful thinking" (SICP).
YMMV but I personally find it very impressive and fun when someone applies problem solving skills and conceptual knowledge with a dash of curiosity.
These qualities combined with a strong grounding in concepts, standards, protocols and so on, will help you understand and adopt the surface level things quicker and with more confidence.
As a (mostly) self-taught programmer, I was somewhat trapped in black box understanding for a while. My technical preferences and decisions where largely based on cultural things instead of technical grounding. From that perspective everything seemed so different and idiosyncratic. But after gaining more fundamental knowledge, trying out different approaches and talking to veterans, I started to see that they're all surface level re-inventions of the same stuff.
