Writing job posts with live checks

Job posts is where you write a post with your team. As you type, checks flag exclusionary wording, jargon, long requirement lists, a missing pay range and length, and teammates' comments sit beside the text.

Start a post

1. 1.Choose New job post.
2. 2.Pick the Role and, if you like, a Title. The title is what candidates see; leave it empty to use the role title.
3. 3.Choose Create draft.

The draft is written from the role's brief, in sections: about the company, the role, what you'll do, what you're looking for, and pay and benefits. Edit each section in place; each one shows its word count. Start a line with a dash to make it a bullet.

The five checks

The Checks panel reruns as you type and lists warnings first.

Fix a warning

Each warning says what it found and what to do instead. Choose Show in to select the flagged words in the post, or Go to to jump to the section.

• Inclusive language: say what you mean. Describe the work and the pace instead of an age or a type of person, write "fluent in English" instead of "native English speaker", and name the values you hire for instead of "culture fit".
• Clarity: say the concrete thing. "We ship every week" instead of "fast-paced", and the actual responsibilities instead of "wear many hats".
• Requirements: long lists put off people who meet most but not all of them. Keep the 8 or fewer that matter and move the rest to nice-to-haves.
• Pay transparency: add the base range with a currency, such as "$150,000 to $180,000" or "SGD 120k–150k". "Competitive salary" doesn't count. If the role has an approved pay band, the warning shows it.
• Length: under 250 words may not give candidates enough to decide, so aim for 300 to 700 covering the work, the team and how you'll support them. Over 900, cut, starting with the company story.

Comments from your team

Teammates' comments appear under Comments, each tied to the words it's about. Select the quote to find those words in the post. If the text has changed since, the quote is struck through.

Choose Resolve when you've dealt with a comment, or Reopen to bring it back. Resolved comments are hidden until you choose to show them.

Draft, In review, Published

Set the post's Status at the top of the editor:

• Draft while you're writing.
• In review when it's ready for teammates to read and comment.
• Published when it's final. You can also choose Publish.

Checks don't block publishing, but Emoti tells you how many are still open, so fix them first. You can move a post back to Draft at any time. The Job posts list shows each post's status, its warnings or All clear, open comments and when it was last updated.

For why these checks matter, see Fair and responsible hiring with AI.