Build tools: when I interview candidates I ask them to explain what things like Webpack do. I don't care if they can write a config for it (but it's nice). Run

Build tools: when I interview candidates I ask them to explain what things like Webpack do. I don't care if they can write a config for it (but it's nice). Runtimes: a lot of frontend JS engineers don't know what these are. Being able to explain them (and the difference between Node and Deno for ex) is a good answer. For backend jobs this is a hard requirement, but when I see "Node" in a frontend job listing I assume it means "can install packages from Node." Frameworks: (like Next) it depends. If I'm hiring for an app already built in one, maybe. A general answer like "SSR is a problem with React" and "this framework solves that problem this way" is useful.