Built for Recruiters
Share roles and source candidates in industry Facebook groups
Post open roles across professional and local job groups with spintax variation. Lead Radar for hiring and open-to-work intent keywords.
- Plano Buy Sell Trade 41.2K
- Frisco Moms 18.9K
- McKinney Community 27.4K
- Allen TX Neighbors 15.1K
- Prosper Families 9.4K
Bulk group posting
Post one campaign to every Facebook group you have joined.
Spintax and AI copy
A different version of your post in every group, resolved at delivery.
Lead Radar
Find group posts from people asking for what you sell.
Account Health
A 0 to 100 risk score that warns you before you publish.
Candidates talk shop in industry Facebook groups, local job groups, relocation communities, and trade forums, so that’s where recruiters source. The same job ad pasted into thirty of them looks like spam to admins and trips Meta’s duplicate detection.
MaherPost lets staffing teams post roles with spintax, track delivery logs for each req, and watch for intent keywords from both hiring managers and job seekers. Campaign setup is covered in bulk Facebook group posting.
Workflow steps
- Find the groups that allow job posts, and read the pinned rules for frequency caps and link placement.
- Build a master template per role category (engineering, healthcare, trades).
- Sort groups into group bundles: industry professional, local metro, and trade or skill.
- Put application URLs in the first comment wherever body links are banned. Many job groups require it.
- Schedule role posts with posting delays of 4 to 6 minutes between groups.
- Turn on Lead Radar for employer-side and candidate-side keywords, and edit every reply draft before it sends.
- Export delivery logs per req for client reporting, and keep the spintax templates for similar roles later.
Job posts that survive moderation
Vary these with spintax:
- The role title (Engineer vs Developer)
- The opening pitch about the company
- The order of the requirement bullets
- The CTA (“apply via link in comments” vs “message me”)
Compensation and location stay the same in every variant. Never spin salary numbers.
Sample spintax: role announcement
{We're hiring|Now hiring|Open role}: {Senior Software Engineer|Sr. Software Developer|Senior Backend Engineer}
{Join|Come work with|Help us build} a {growing|fast-scaling|remote-first} team working on {meaningful|high-impact|customer-facing} products.
Requirements:
• {5+ years|Five plus years} {backend|server-side} experience
• {Python or Go|Go or Python} proficiency
• {Strong communication|Collaborative mindset|Team player attitude}
{Remote US|Fully remote|Work from anywhere US}. {Competitive pay|Strong compensation|Market-rate salary}.
{Apply via link in comments|Link in first comment|Details in comments below} 👇
Lead Radar on both sides
Employer-side keywords:
- “hiring [role]”
- “looking for recruiter”
- “staffing agency recommend”
Candidate-side keywords:
- “open to work”
- “seeking [role] position”
- “laid off [industry]”
“Hiring” shows up in plenty of jokes, so use STRICT mode to cut false matches. Add negative keywords such as “internship unpaid” and filter out off-topic memes.
Group tiers
| Bundle | Content |
|---|---|
| Industry professional | Role posts, thought leadership |
| Local metro job | Geo-specific reqs |
| Trade / skill | Certification-friendly copy |
A remote-only role in a strictly local group needs an explanation, or it shouldn’t go there at all.
Compliance and fairness
Put EEO language in the base template so every spintax path carries it, and make sure no variant could read as discriminatory. Have your compliance team approve each master template once.
A typical week
| Day | Activity |
|---|---|
| Mon | New req blast to industry bundles (spintax) |
| Tue | Local metro req posts for geo-specific roles |
| Wed | Lead Radar review: employer and candidate threads |
| Thu | Thought leadership or hiring market update (value) |
| Fri | Follow-up req posts for roles still open |
Cap how often you post in each group. Job groups commonly allow one post per role per period.
Protecting recruiter profiles
A stack of open reqs makes it tempting to blast them all at once. Recruiters post from their personal profiles, so Account Health and warmup apply to you just as much as to anyone.
Give a new account 7 to 10 days of manual engagement before bulk posting, keep posting limits conservative, and pause every campaign on any restriction signal. During onboarding, share is auto poster safe? with your compliance team.
Staffing agencies with multiple clients
Keep separate bundles for each client, and never cross-post ads for competing employers. Weekly client reports come straight from the delivery logs. See also MaherPost for agencies and agency managed posting.
What to measure
Groups don’t give you apply-click analytics, so track:
- Delivery success rate
- Inbound messages lined up against post timestamps
- How many Lead Radar replies turn into screen calls
Further reading
- MaherPost vs manual, if you’re juggling a lot of reqs
- Avoid post rejection, for groups that are wary of recruiters
To try it, put one req through 5 groups on the $29/mo plan.
Other teams using MaherPost
Ready when you are
Stop pasting the same post into forty tabs.
$29 a month. Cancel anytime, 7-day refund.