# How to write a job ad developers actually apply to

> Developers self-select out of vague ads. Say what the job is, what it pays, and how remote it really is.

_Category: For employers · Updated: 2026-10-15 · 2 min read_

Developers self-select out of vague ads. Say what the job is, what it pays, and how remote it really is.

## Lead with the work

The first paragraph should describe what the person will build and why it matters. Not the company origin story, the actual job. The best candidates decide in the first ten lines.

## Say the salary

Advertised pay is not a concession; it is a filter that saves you time. It also signals that you are serious. Our own [salary guidance](/guides/what-are-you-worth-researching-developer-salaries) is the same data your candidates are using.

## Be precise about remote

"Remote" alone is useless. Say the countries, the timezone overlap, and whether it is [remote-first or remote-friendly](/guides/remote-first-vs-remote-friendly-vs-hybrid). Vague remote ads attract thousands of ineligible applications and frustrate everyone. See [why your remote role isn't getting applicants](/guides/why-your-remote-role-isnt-getting-applicants).

## Write requirements honestly

Separate the two or three things that genuinely matter from the wishlist. Every requirement you add removes qualified people; read [how candidates read your ad](/guides/how-to-read-a-job-listing-like-a-recruiter) to see it from their side.

## Make the process visible

State the number of interview stages, whether there is a [take-home](/guides/beating-the-take-home-without-burning-your-weekend), and the expected timeline. Transparency is the single cheapest way to win trust.