Re:So We Might Have Killed the Job Description
by negrit on Wednesday March 04, 2015 @09:06AM
(#9144216)
Not sure why you're getting down voted like this...
EDIT: It doesn't appear that bad anymore, but as soon as this comment was posted it got down voted pretty bad. Something fishy going on...
Re:So We Might Have Killed the Job Description
by lobster_johnson on Wednesday March 04, 2015 @08:58AM
(#9144172)
I don't disagree with your first sentence, but this looks better than a hacky workaround. One of the main problems of finding people is reading through candidates' lists of qualifications and interests. By having a set of quantified metrics I see this being useful in being able to sort applicants by something like K-nn distance.
Re:So We Might Have Killed the Job Description
by marrs on Wednesday March 04, 2015 @09:19AM
(#9144303)
But this about creating the job description, not reading CVs. There are already lots of apps designed to parse CVs and sort them based on keyword relevance.
I didn't really see the point of this tool. From what I can tell, you put in a bunch of metrics and the app tells you what the job title and description are. Surely if you're creating a position in your company, you must know what it's for?
What kind of terrible CTO is that? If you don't know how to describe the tasks and requirements of a job such that a person qualified to take it will understand what the job will be, then you have two options:
1. If your org is big enough, delegate to the team leads closer to the matter, better yet: To the actual people the new hire will be working with.
2. If your org is small: Resign, you're unqualified for your position.
Don't try to fix hiring by ignoring the actual problem and try to jam in a terrible hacky workaround. The only real fix is to be honest about the job.
@lobster_johnson: Fair enough, that would be a valid use.
@workshape: Oh hi, have you come with the downvotes after deleting the first submission on which i made this comment? ( https://news.ycombinator.com/item?id=9143891 )