How many of those have you done? It's usually basic JavaScript / CSS / HTML / responsive design, performance, accessibility. You don't hire a plumber by asking him about the make of his hammer.
I've been using this exact analogy the other way around about hiring in IT. First screening is usually some HR drone scanning your resume/cv for buzzwords.
HR: So, I see on your resume you have been building houses for a decade. This is a good foundation for the work we are doing.
Applicant carpenter: Yes, all sorts of houses. Done both interiors and prep for concrete pouring. Fiddled a little bit with wiring on a job where the electrician needed some help.
HR: Uhu. Yes. What vendor did you use for your tools?
AC: Pardon?
HR: Well, we have secured a really good deal on tools from Stanley. Are you familiar with their hammers?
AC: (puzzled) uhn, sure. I'm not too sure what I used on my last site. For me a hammer is a hammer. It has to be a really crappy tool not to do it's work.
HR: Thank you for coming in. I think you should expect a call from us sometime next week. (marks the checkbox, Not familiar with tools)
Coding is usually based around learning the solution we are employing. It's a very boring problem if the solution is known beforehand. It's now knowing the tools that make you effective, it's being able to learn them that is valuable about a knowledge worker.
You don't hire a plumber by asking him about the make of his hammer.
You might if all the nails you have could only be used with a certain make of hammer and if learning how to use a different hammer efficiently could take several month.
Let's not get carried away, but that's the result of your own choice to accept vendor lock-in. Like having to hire only authorised service providers. Most companies I've known are smart enough to avoid that and just hire good generalist developers, and the interviews will be shaped accordingly.
HR: So, I see on your resume you have been building houses for a decade. This is a good foundation for the work we are doing. Applicant carpenter: Yes, all sorts of houses. Done both interiors and prep for concrete pouring. Fiddled a little bit with wiring on a job where the electrician needed some help. HR: Uhu. Yes. What vendor did you use for your tools? AC: Pardon? HR: Well, we have secured a really good deal on tools from Stanley. Are you familiar with their hammers? AC: (puzzled) uhn, sure. I'm not too sure what I used on my last site. For me a hammer is a hammer. It has to be a really crappy tool not to do it's work. HR: Thank you for coming in. I think you should expect a call from us sometime next week. (marks the checkbox, Not familiar with tools)
Coding is usually based around learning the solution we are employing. It's a very boring problem if the solution is known beforehand. It's now knowing the tools that make you effective, it's being able to learn them that is valuable about a knowledge worker.