Write a job description
Get a clear job post from a few notes and similar past roles.
People and HR · When you ask · Updated
Works with
- Slack
SlackHow do you write a job description?
To write a job description, send Maito a few notes in Slack or by email. It finds similar past job posts and your levels guide, drafts the role, responsibilities, requirements and pay range, points out old wording that no longer fits, and attaches the result as a document for the hiring manager to edit.
How it's done today
Hiring managers copy an old post and edit it.
What Maito does
- Read the notes
- Check similar past roles and the levels guide
- Draft the post
Example
@Maito Write a job post for a senior backend engineer. Payments team, remote in Europe, replacing the post we used in March.
Draft attached: senior-backend-engineer.docx. It covers the role, what you'll own, requirements, how we work and the pay. • Level: L5 in the levels guide • Range: $150,000 to $180,000 base, from the L5 band • Requirements: 5+ years, Postgres, event-driven systems, payments or ledgers a plus Two fixes from the March post: it asked for 8+ years, but our levels guide says L5 starts at 5. It also said "rockstar", which our hiring guidelines tell us to avoid. I took both out and kept the paragraph on on-call, which candidates liked. Based on the March post, the Payments team notes and the levels guide. Needs your OK and Rosa's before it goes live.
@Maito Rosa wants a shorter version for LinkedIn.
Sent a 180-word version to Rosa and you in a second attachment: senior-backend-engineer-short.docx.
Alex (2:15 PM):
Write a job post for a senior backend engineer. Payments team, remote in Europe, replacing the post we used in March.
Maito (2:17 PM):
Draft attached: senior-backend-engineer.docx. It covers the role, what you'll own, requirements, how we work and the pay.
• Level: L5 in the levels guide
• Range: $150,000 to $180,000 base, from the L5 band
• Requirements: 5+ years, Postgres, event-driven systems, payments or ledgers a plus
Two fixes from the March post: it asked for 8+ years, but our levels guide says L5 starts at 5. It also said "rockstar", which our hiring guidelines tell us to avoid. I took both out and kept the paragraph on on-call, which candidates liked.
Based on the March post, the Payments team notes and the levels guide. Needs your OK and Rosa's before it goes live.
Alex (2:30 PM):
Rosa wants a shorter version for LinkedIn.
Maito (2:31 PM):
Sent a 180-word version to Rosa and you in a second attachment: senior-backend-engineer-short.docx.
How to set it up
- Set up
Nothing to set up. Ask in Slack or by email whenever you need it.
What it won't do
Maito cannot decide the level or salary for a role. Those stay with the hiring manager and HR, and legal review of the wording stays with your team.
Questions
From your levels or pay bands if you have shared them with Maito. If it cannot find a range, it asks instead of guessing.
Yes. Share past posts and it reuses the structure and tone, and tells you what changed from the last version.
No. It attaches a draft. A person publishes it.
