Keep tech job descriptions to three sentences: mission statement plus 30/60/90-day expectations. Split requirements into must-haves and nice-to-haves, skip learnable frameworks. This approach got the highest candidate response rates on a twelve-person recruiting team.
Chapters
Must-haves and nice-to-haves to job descriptions. Also, I think job descriptions should be short. We don't need ColdFusion next to jQuery next to React. Maybe, maybe give a little bit about what this role is going to do 30, 60, 90 days, right? Hey, when we have you come on, this is the problem we're having you solve. Here's where we want you to be in the next 60 days, 90 days. That would be pretty cool. 3 sentences. I'm not looking for a lot. Then the next thing is must-haves. Do they really need to have 6 JavaScript frameworks that can all be learned on the job? I consistently had the best candidate responses across my recruiting team of 12 individuals time and time again. And so we did a deep dive on why. I made it really, really short. I cut out all the fluff. All I put is a little summary, like the mission, and then I put exactly what I just said— nice-to-haves, must-haves— and sent it out. The job description literally on the— it was like that long. And I got the best response rates.