Job post drafts from a hiring manager intake form
A hiring manager fills in a short role intake form and an agent drafts a job post in the company's format, flagging vague requirements and wording for HR to review before anything is published.
The use case
Job posts at small companies are often written in a hurry, copied from an old listing, or pieced together from a hiring manager's notes. The result can be vague about the actual work, list requirements nobody really needs, or include wording that discourages qualified people from applying. This agent reads a short intake form covering duties, must-have skills, schedule, location, and pay range, then drafts a post using the company's approved template and boilerplate. It flags requirements that look inflated, phrases tied to age, gender, or other protected characteristics, and any missing details your state may require, such as a pay range. HR edits the draft, confirms the legal details with the hiring manager, and decides when and where to publish. The agent never posts to job boards on its own.
Example workflow
- A hiring manager submits a role intake form in Google Forms or the applicant tracking system with duties, requirements, schedule, and pay range.
- The agent reads the form along with the company's job post template, standard benefits text, and equal opportunity statement from a shared document.
- It drafts the post and lists any required field that is blank, such as pay range, work location, or employment type.
- It flags wording that may be exclusionary or tied to protected characteristics, plus requirements that seem unnecessary for the duties described, with a short reason for each.
- HR reviews the draft and flags with the hiring manager, edits the text, and confirms pay and location details are accurate.
- HR publishes the approved post in Greenhouse or the usual job boards, and the final version is saved with the intake form for reference.
Tools
- Google Forms
- Google Docs
- Greenhouse
- Claude
- Slack
- Zapier or Make
Risks and guardrails
- Draft wording could discourage applicants based on protected characteristics and create exposure under employment-discrimination law — guardrail: the agent flags risky phrases and every post gets human review and approval from HR before it is published, and the agent plays no part in hiring decisions.
- Pay range or location details may be wrong or missing where pay transparency rules apply — guardrail: the agent never fills in pay on its own and marks the post incomplete until HR confirms the figures.
- An old template could carry outdated benefits or policy text — guardrail: boilerplate comes from one dated document that HR owns and reviews on a set schedule.
- The post could go live before review — guardrail: the agent has no publishing access to job boards or the careers page.
Related recipe
Repurpose One Video or Webinar into Posts, Newsletter, Clips, and a Blog Outline: An agent turns one long video transcript into LinkedIn posts, a newsletter section, timestamped clip suggestions, and a blog outline in your brand voice, with a claims check and human approval before publishing.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Greenhouse (official page): support.greenhouse.io/hc/en-us/articles/52090956642075-Greenhouse-MCP (checked 2026-11-19)
- Claude (official page): claude.ai (checked 2026-11-09)
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)
- Zapier MCP (official page): zapier.com/mcp (checked 2026-11-09)
- Make MCP server (official page): developers.make.com/mcp-server (checked 2026-11-09)