3 ms·
"Candidate 1 knows .NET but is new to Oracle" "Candidate 2 has a long track record of .NET and Oracle work" These should be two different JDs with different s
by dheera 5y ago
"Candidate 1 knows .NET but is new to Oracle"
"Candidate 2 has a long track record of .NET and Oracle work"
These should be two different JDs with different stated salaries.
Or explicitly say "+$50K for candidates with a long track record of .NET and Oracle work".
- jjav 5y ago> These should be two different JDs with different stated salaries. But I'm only hiring one person. Ideally, the one with all the perfectly matching experience. But I'm not going to wait around forever for the unicorn to show up, so I may likely settle for someone promising who doesn't quite have the experience. > Or explicitly say "+$50K for candidates with a long track record of .NET and Oracle work". That's the same as giving a range.
- dheera 5y agoNot the same, because giving a range allows you to discriminate on race, gender, and other things. The reality is this actually happens, and that's why this discussion is happening in the first place. If it's an objective function of qualifications that's a lot more clear-cut.
- kempbellt 5y ago> "+$50K for candidates with a long track record of .NET and Oracle work" This also allows discrimination based on "race, gender, and other things" since "long track record" is completely open to interpretation and if the interviewers are already operating in bad faith, they can find any BS reason to try and undermine an interviewee. "$100-$150k DOE" is exactly the same, if not clearer, than "$100k (+$50k if XYZ)" For those operating in good faith, it gives an honest comp range depending on experience. For those who aren't, a format change on job postings isn't going to do anything.