I've seen a lot of disagreement about whether you should 'hire for your stack', i.e. hire narrowly for your team's current work and tools. I briefly ran hiring

I've seen a lot of disagreement about whether you should 'hire for your stack', i.e. hire narrowly for your team's current work and tools. I briefly ran hiring for a team with a core skillset that I thought was pretty general (python/web), but a lot of the python resumes I got turned out to be 'I used it in college', 'haven't used it recently', or django-focused devs who were uncomfortable with anything non-django. I'm not sure what that means other than that I'm bad at sourcing. Seems like 'aiming at my stack' was the wrong way into this, but I'm not sure how else to filter resumes.