Writing a posting that gets published

Every posting is read by a person before it goes live. This is what that person is looking for, and the reasons a posting does not make it.

What makes a posting work here

Matching is on skills and tools, not on job titles, so a specific posting genuinely reaches more of the right people. This is the whole trick.

• Name the tools, not just the title

  "Senior Developer" tells the matcher almost nothing. The stack, the frameworks and the day-to-day tools are what a CV can actually be scored against.

• Separate the essentials from the nice-to-haves

  A wish list of twenty requirements reads as twenty essentials and narrows your matches to nobody. Say which few you would not hire without.

• Say what the person will do

  Responsibilities carry skills that a requirements list leaves out, and they are what a candidate reads to decide whether to apply.

• Be exact about where the work happens

  The form asks in structured fields rather than prose because we check it. Remote open to anyone, remote within a region, or on-site in a named city.

Why a posting might not be published

Better to know now than after you have written it. If we cannot publish one, reply to your confirmation email and we will explain.

• The work is not open to people in Georgia

  Michi's candidates are here. A role that cannot legally or practically be done from Georgia has nobody to match, so we do not publish it. The location fields on the form are what we check against, and the form tells you before you submit.

• There is not enough to match on

  A few lines with no skills or tools cannot be scored against a CV. It would surface for the wrong people or for nobody at all.

• It is not a job

  Unpaid work, equity-only offers, course sign-ups and lead-generation pages are not roles, and candidates trust the board because they are not on it.