How to do it
- New role triggers a draft Your applicant tracking system or a Make flow sends new job listings through a signed webhook.
- Draft with specifics The agent writes what the person will own, who they work with, and one honest challenge of the role, using the hiring post template as a guide.
- Hiring manager approves The approval.requested webhook pings the hiring manager, who edits and approves from the inbox.
- Welcome posts later When someone joins, a similar flow drafts a new-hire welcome post that the new hire sees before it goes out.
We are hiring a senior backend engineer to own billing. You would rebuild how we meter usage, work daily with our two finance folks, and inherit one very old cron job. Remote in UTC-5 to UTC+2. Salary range in the listing.
Hiring posts are recruiting, not advertising
The best hiring posts are specific: what the person will actually do in their first months, who they will work with, and the tradeoffs. Specific posts get fewer but better applicants. An agent can pull those specifics from a job listing faster than anyone on the team. The hiring manager's review is what keeps them accurate and honest.
Setup
- Connect your company page and the founder's or manager's profile on LinkedIn, plus X if you recruit there.
- Send listings in with a webhook or a Make or Zapier flow.
- Add rules to brand memory: always include location and remote policy, never promise things the offer does not include, and your inclusive-language preferences.
- Give the agent the hiring post template and the new hire welcome template.
Permissions
The hiring agent gets draft only on LinkedIn and X. Hiring posts represent commitments to candidates, so keep them draft-only on the trust ladder. If you use multi-reviewer approvals on Pro, add a recruiter alongside the hiring manager.
Measuring hiring posts
Tag each post's application link with the UTM builder so your applicant tracking system shows which posts brought candidates. Per-post metrics show reach, but applications and qualified candidates are the numbers that matter.
Pitfalls
- Stale posts. When a role closes, add a follow-up or stop reposting it. Rejecting a queued repost takes one tap.
- Welcome posts without consent. Always let new hires approve their welcome post before it is published.
- Vague perks lists. Replace them with one concrete detail about the work. Preview how it looks with the LinkedIn post preview.
- Missing salary information. Where local rules or your own policy require a range, add that rule to brand memory so every draft includes it.