How to write a job post candidates actually read

Most job posts read like a list of demands. Here is a structure that tells a candidate what they need to know in the first ten lines.

A candidate gives a job post a few seconds before deciding to read on. Most posts lose them with a paragraph about a "fast-paced environment" and a list of fifteen requirements. The posts that get good applications answer a handful of plain questions early.

Start with the work, not the company

Open with what the person will do and why it matters now. Two or three sentences. The company story can come later, and shorter than you think.

The questions every post should answer

  • What will I work on in the first months?
  • Who will I work with?
  • What is the salary range, and is there equity?
  • Where and when do people work: office, hybrid or remote?
  • What does the hiring process look like and how long does it take?

Cut the requirements in half

Split the list into "you need this on day one" and "nice to have", then delete most of the second list. Long requirement lists do not raise the bar. They make good people who match seven of ten points decide not to apply.

Say the salary

Posts with a salary range get more applications and fewer wasted calls. If you cannot give a range yet, you are not ready to post the job.

I applied because the post told me the salary, the team size and the stage. Nobody else did.

An engineer who joined a twelve-person startup

When the post is ready, publish it on The Hub and share it from your own profiles. People trust a job more when it comes from someone they know.

← All posts