This post was updated in November 2017 with new information.
Proud of your current tech job listings? If they're not bogged down by requirements and are getting developers excited to apply, you should be.
But before you start reusing old job listings, think about all the work you did to create them. You probably met with your current developers to make sure they represent your engineering culture well. You probably got feedback from the other recruiters on your team. And you probably edited them along the way.
Even the most exciting job listings need to be reviewed before you reuse them in the future. Every developer job you need to hire for will be unique from the last—and if your listings don't reflect that, you could miss out on your ideal candidates. We'll walk through three other reasons you can't always reuse developer job descriptions, and the impact it can have on your hiring goals.
Even the highest performing engineering teams are subject to change. Some developers might shift their focus. Others might move on to other opportunities. No matter what the case is for you, the reality is that the story you tell in today's tech job listings is much different than it was a year or two ago.
Your developer job descriptions might not need a complete overhaul, but you should make sure they accurately tell your engineering team's story before you relaunch them. What projects are your developers currently working on? What are your company's biggest goals this quarter? If your job listings aren't telling the current story, this might give developer candidates pause about pursuing the opportunity down the road.
If you have trouble keeping up with all of the newer tech languages that developers want to use, don’t worry—you’re not alone. Considering that the developers we surveyed told us that career development opportunities are important to them at work, companies of all sizes have started baking in opportunities to tinker with new languages on the job.
What does that mean for the tech job listings you’ve written in the past? If you included a list of “required” languages in your most recent job descriptions, that section is likely out of date. It might take a little effort to learn more about the languages your tech team is currently using, you’ll ultimately set candidates up to have an outstanding experience throughout the entire developer interview process.
At some point, your organization’s technical needs will change, especially when it launches new initiatives and products. Although that might not necessitate sweeping changes to the structure of your tech team or tech stack, you’ll likely need to recruit developers to support specific projects. If a developer candidate stumbles onto your listing for an opening on your ad server team, only to find out you need an engineer to focus exclusively on marketing initiatives, it will be difficult to overcome that negative first impression of your company.