Take it one step farther. After a couple of well-publicized bad situations they are likely to find the most desirable users becoming reluctant to check that checkbox. And then the model breaks down, which is not in anyone's interest.
I hope they figure it out before that situation arises. But until I'm confident that they understand that, I won't be comfortable with that service.
Re:Looking for a Job? Let GitHub Help
by sandGorgon on Wednesday November 25, 2009 @04:58AM
(#960915)
A good middle ground is search rankings - users who are "looking for a job" have their ranking bumped-up on search results (shown to employers). Not to the very top mind you (too obvious!) - but enough to come ahead of non-lookers.
This way - the employers get a good result on their search for prospective hires and employees get plausible denaibility.
Re:Looking for a Job? Let GitHub Help
by UncleOxidant on Wednesday November 25, 2009 @04:55PM
(#961897)
Prospective employers (or their agents) often contact people who are not actively looking for work. And sometimes those people end up accepting offers even though they weren't actively looking. I got my current job that way.
The data on skillsets (resume info) is what the prospective employer is looking for. Whether or not the person who posted it is "actively looking" is not so relevant.
Prospective employees pay nothing. They are not the customers of this system. It will serve their interests... when it is reasonably practical to do so without trodding on the toes of the paying customers.
Prospective employers are not worried that prospective employees might find themselves suddenly separated from their previous employer -- indeed, that is sort of the general idea.