I guess I'm different in that I care that people understand the pluses and minuses of the various frameworks. I think anyone can pick up a framework or solve a problem. However, can they understand why and when to use x framework to solve a problem and back up why they chose to solve the problem in the way they chose to do it.

Additionally I want someone who can be passionate about the tech stack and frameworks they are using or plan on using. Otherwise, I've got a code monkey who may get things done in the short term but their code and problem solving abilities actually has negative implications in the future when it comes time for maintenance and to add additional features to things.

I don't understand why people label others who care about their craft and the tools they use as junior/midlevel. I think that's lazy. Many times there really is a best way to solve a problem or a best framework for your particular situation or problem. All engineers should care about the tools and what is being used and why it's being used.

I guess its just not enough for me to have an answer so much as to understand why its the answer and under what conditions assumptions can fail. To me that is more valuable when hiring someone who is switching careers than being able to solve a problem in a generic sense.