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.Read More
Even the most experienced writers can be intimidated by a blank page. And hey, sometimes that’s not a bad thing. When you’re trying to create a tech job listing, it’s natural to put a lot of pressure on yourself to say exactly the right things that will make developers want to apply. However, employers often take an aggressive approach to writing job listings that stand out amongst the competition—and the results are not always pretty. To help you avoid some surprisingly common job listing mistakes, here are a few things to avoid.Read More
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.Read More
Anyone who has written a technical job description has probably gotten a lot of advice on how to do it well. You know they shouldn’t be wordy, but you have so much to say about why candidates should want to work for your company. You want to use an inviting tone, but you also want to avoid using too many buzzwords. Those tips probably sound straightforward at first, but applying them to how you write a technical job description is much more complicated. To help you make sense of all the knowledge you’ve gathered, here are a few things that the most effective technical job descriptions all have in common.Read More
When it comes down to it, recruiting is an awful lot like marketing. So if marketers are constantly A/B testing their landing pages or calls-to-action, shouldn’t recruiters be doing the same for their job listings?Read More
Let’s face it – searching for a job isn’t exactly “fun.” This rings especially true for developers, who often have to go through a longer and more intensive interview process (*cough* whiteboard exercises) than other candidates. And while this declaration isn’t exactly breaking news, the topic of the broken developer interview process is still popping up on blogs, forums, and our annual survey.
Here’s a snapshot of what respondents thought were the most annoying aspects of the developer job search (and what you can do to fix that).Read More
A well-written job description can make or break the technical hiring process. Since it’s typically the first thing an applicant sees in the hiring process, it’s crucial to make it the best it can be. I’ve read my fair share of technical job listings and noticed a few common mistakes coming up again and again. Here are my three of the common flaws of developer job descriptions.Read More
There are two types of people in this world: those who care about job titles and those who don’t. All joking aside, what you refer to your potential and current employees as can make a difference. For example, if you’re writing a job posting for an open role on your team, the job title is a huge factor in who applies. The terms “developer”, “programmer”, and “engineer” are often used interchangeably to describe the same type of employee, but do they really all mean the same thing?
We asked programmers around the world what they thought about developer job titles through our annual user survey. 72% preferred the term Developer, followed by 60% favoring Programmer and 42% calling themselves an Engineer. (Respondents were allowed to pick more than one response.)
Additionally, we asked a handful of Developers/Programmers/Engineers (see what we did there?) to offer their personal opinions on the matter.Read More
You’ve typed up your job description, formatted it perfectly, and posted in on all the relevant websites. Now you sit back and wait as the Android Developer applications roll in. Except only a very few are coming in and you’re left wondering what you did wrong. There likely isn’t just one mistake you’ve made that’s causing fewer developers to apply to your job – it’s likely a combination of things that add up to a poor candidate experience. Here are a few of the common gripes technical candidates face when applying for a job.Read More
If you’ve applied for a job in the past decade, you’re familiar with reading job listings. Whether they’re on a niche job board or a company’s website, they typically all look the same – a title, some text, and an apply button at the end. It could be assumed that tech candidates see more job listings than the average worker, as they are bombarded with new opportunities multiple times a week. So what can you do to make your job stand out from the rest? Here are a few ways developers read your tech job listings.