Hacker News Reader

Comment by jasonjmcghee | Hacker News Reader

I have to ask- you're not interested in candidates if they have experience in certain frameworks?

It was just an example, but yes, I would like to disqualify results that I don't want. It is just a general feature I wish were widely available in many places. If I were looking for jobs, for example, I would not want to waste time on that which is not relevant or outside my level.

If you were looking for jobs and had Typescript experience but not React experience, then sure, you might want to exclude jobs that require React experience.

An employer looking for a candidate has no reason to exclude someone with React experience though. If they want a candidate with Express.js experience, candidates may still have both. They just need the positive search in that case.

I think the belief is that they think that knowing some framework/language/tool etc. is harmful, i.e a candidate not knowing that would be better, has some better habits, and so on. I've saw that come up a few times

> An employer looking for a candidate has no reason to exclude someone with React experience though

I completely disagree and you are focusing on a made up rhetorical example far too much. There is always benefit to more efficiently excluding results you don't want.

i'd like to see an example that actually makes sense. the only one i can come up with is that i might not want to hire people who have more experience with windows than with linux. but even in that example people with less windows experience would be ok.

if you have a realistic use case please describe it.

Yeah, if you're hiring for a senior-level role, 10 years of experience with Linux is 10 years of experience with Linux, even if the person also has experience (perhaps even more than 10 years) with Windows.

> i'd like to see an example

Why? You are clearly missing the point and lack imagination. Another example won't satisfy you the way you think it will.

Reply on news.ycombinator.com