I’m willing to bet that a lot of the advice you’ve read about writing compelling tech job listings came at the exact moment(s) you thought, “Wow, I’m pretty great at this.” The timing of these discoveries can be frustrating, but it’s no secret that developers have strong opinions about the things they see in tech job postings. And if you want to make a great first impression, it’s important to understand what does (and doesn’t) resonate with developers when they read job listings. To shed some light on this mystery, we interviewed a handful of developers to hear their thoughts about what they wish employers included more often when they write a technical job listing.
While it’s important not to rule out a developer because he or she doesn’t know your entire tech stack, it’s perfectly acceptable to have baseline qualifications that are important for all candidates to have. In fact, developers want to know what your minimum requirements are from the get-go. Chris Savage, a software developer at BlueMetal, told us that he appreciated tech job listings that outlined which languages would be required, and which would be nice to have. He adds, “When I was looking for a job, most companies listed all the qualifications they wanted, but the truth was they were more of a 'wish list.’”
The developers that responded to our survey this year made no secret of the fact that interviewing for a new job is one of their least favorite things. Of course, it would be borderline irrational to respond to this by eliminating developer interviews altogether. However, your tech job listings can go a long way in making this part of the job search much easier on developers. Jack Liu, a software engineer at Hearst Digital, tells us that he wishes more job listings would go deeper into the interview process, especially when it comes to the coding test. “Some expect you to write graphing algorithms from scratch in minutes. Others involve writing working heaps and priority queues,” he continues. “I'd wish they would say ‘expect to know a bit of graphing algorithms’ or ‘expect to be able to solve hackrank medium problems for strings.’”
We’ve written quite a bit about the fact that developers are attracted to employers who are willing to share salary information right off the bat. According to Judah Anthony, Technology Director at The Economist, many companies have been slow to catch on. Not only does he use salary ranges to determine whether or not to consider a position, Anthony tells us that employers who are more tight-lipped about compensation also risk rubbing developers the wrong way. “It kind of sends the message that they will be happy to lowball me if they have the chance,” he says. “That is an awful way to start a relationship.”