News for hackers. Stuff that matters.
Re:So We Might Have Killed the Job Description by negrit on Wednesday March 04, 2015 @09:03AM (#9144204)
This sounds over complicated and the CTO sounds horrible.

The dev team hiring the engineers should gather together and write some specs. The leader should post the job online and then the team should deliberate on each candidate.

Everything else sounds like a waste of time.

Re:So We Might Have Killed the Job Description by GordyMD on Wednesday March 04, 2015 @09:19AM (#9144298)
CTO of Workshape.io here. My co-founder Hung was painting a rather extreme picture, but the picture he does paint is a reasonable portrayal of a possible reality.

Not all CTOs are good at hiring/writing an effective job description (what is an effective job description?). And it does stand to reason, like with many other things, that people use other job descriptions as inspiration.

Re:So We Might Have Killed the Job Description by jussij on Wednesday March 04, 2015 @09:16AM (#9144284)
I agree. Surely someone in the group looking to hire a new developer has some idea as to what skills would be beneficial.

For example:

Skill Level (pick one): Junior, Mid Level, Senior

Language (pick one or more): C, C++, C#, D, Go, SQL, PHP, Java, Ruby, Perl, Python, Rust

This isn't rocket science!