I think jQuery gets a bad name because of it's historical context. Newer devs in the field view it as outdated and seasoned devs have seen the mess it can lead

I think jQuery gets a bad name because of it's historical context. Newer devs in the field view it as outdated and seasoned devs have seen the mess it can lead to when just sprinkled in here and there for this and that reason; and as frontend work became increasingly more programmatic and complex, this sort of approach becomes pretty hard to maintain. Because frameworks/libraries like Angular and React were largely adopted due to this issue, people who have had success with them (or just need to justify the switch), have come to see these as part of the solution and jQuery as part of the problem. If you're an interviewer who only sees jQuery on an application, you can use this as a chance to get to see what the candidate thinks about the evolution of web development. See if they can have a reasonable discussion about trade-offs made on choosing one over the other. This will expose their critical thinking skills and values as a developer and you may even get a new perspective yourself. To be honest, I'd rather work with someone who could have this discussion rather than just blindly adopt what everyone else is using ... well ... just because.