Split the spoken request into duties and requirements
Age, pressure tolerance, experience, and pay were packed into one sentence. They become four readable blocks: what you will do, requirements, scope, and process.
Hiring request into a posting
A hiring request,
turned into a posting that reads clearly.
A hiring request becomes a job description with duties, requirements, scope, and process written out. No invented salary ranges, benefits, team sizes, or promotion promises, no discriminatory conditions, and no commitments you cannot honour.
Concrete dutiesTiered requirementsNo discriminatory limits
02
Review the posting
Your result will appear here
We split duties from requirements, separate must-haves from nice-to-haves, describe scope and process, and flag the pay and team facts you need to confirm.
SAMPLE OUTPUT
Here is exactly what you receive.
This is the complete output for the source text in the demo above: a clarity score, itemised reasoning, a confirm-before-publishing list, and the structured job description. It is a demonstration, not a customer case.
SAMPLE
Job description (sample)
Clarity score88/100
+50
Remove the age limit and say why
“Under 35” is an age limit. It is removed and replaced with capability requirements rather than kept in softer wording.
Turn unverifiable claims into slots
“Salary negotiable”, “big growth potential”, and “great atmosphere” cannot be checked; they become confirmation items or fields you fill with real information.
Structured job description
# [Role title] ([location] / [employment type]) ## What you will do - Own server-side development and maintenance for [system/module]; deliverables [TO CONFIRM] - Join requirement reviews and align interfaces and scheduling with [counterpart team] ## Requirements **Required**: [language/framework], [N]+ years of server-side experience, [specific capability] **Preferred**: [preferred item] ## Scope - Reports to: [reporting line] - Not covered by this role: [out of scope] ## Hiring process [stages], expected duration [TO CONFIRM] ## To confirm - Salary range: set by company policy and local requirements - Team size and growth: the source wording cannot be verified; add real information The “under 35” age limit was removed. Replace it with capability-based requirements.
WHAT STRUCTURING DOES
Not more attractive. More accurate.
State duties as a verb plus a deliverable
“Handle related work” says nothing. Concrete responsibilities tell a candidate what the job actually is.
Split required from preferred
Stacking everything as mandatory leaves almost nobody qualified, and the role stays open.
State scope and process
Name the reporting line, collaborators, hiring stages, and what the role does not cover.
WHY IT IS WORTH DOING
An inaccurate posting hires the wrong person.
Vague postings get skipped
Candidates who cannot tell what the job involves either scroll past or discover the mismatch after joining.
Too many requirements shrink the pool
A long mandatory list leaves a handful of qualified people, and the role stays open.
Discriminatory conditions carry risk
Age, gender, marital status, and origin limits are discriminatory in most jurisdictions and damage employer reputation.
Note: standard job description practice is concrete duties, tiered requirements, and a stated reporting line and process. Anti-discrimination and pay transparency rules vary by jurisdiction, and some markets require publishing a salary range. This site handles structure and wording only, invents no pay or benefits, and gives no legal advice.
STRUCTURING DEMO
The same hiring request, structured.
Before
Hiring a backend engineer, under 35, must handle pressure, large-company experience preferred, salary negotiable, can own things independently, great team atmosphere, big growth potential.
Structured
# [Role title] ([location] / [employment type]) ## What you will do - Own server-side development and maintenance for [system/module]; deliverables [TO CONFIRM] - Join requirement reviews and align interfaces and scheduling with [counterpart team] ## Requirements **Required**: [language/framework], [N]+ years of server-side experience, [specific capability] **Preferred**: [preferred item] ## Scope - Reports to: [reporting line] - Not covered by this role: [out of scope] ## Hiring process [stages], expected duration [TO CONFIRM] ## To confirm - Salary range: set by company policy and local requirements - Team size and growth: the source wording cannot be verified; add real information The “under 35” age limit was removed. Replace it with capability-based requirements.
Demo sample: a spoken request becomes duties and requirements, the age limit is removed, and unverifiable claims become slots. Paste your request to get your version (sign-in required; one credit per run).
WHY YOU CAN TRUST IT
We put “no invented terms” into our product principles.
No invented pay, benefits, or team size
Salary ranges, benefits, headcount, and promotion promises stay as slots. No plausible figure or claim is added for you.
No discriminatory conditions
Age, gender, marital status, origin, and similar limits are removed and rewritten as capability requirements, not reworded into something acceptable-looking.
No promises you cannot honour
“Big growth potential” and “great atmosphere” cannot be verified; they are flagged and become either checkable information or a slot for you.
Content is not stored
Submitted text is used for this single AI request and is not intentionally persisted. See the Privacy Policy.
FAQ
Ask these before you pay.
Will you fill in the salary range?
No. Pay follows your company policy and local requirements, so it stays a slot to confirm. Some markets require publishing a range; check the rules that apply to you.
Can I keep “under 35”?
No. Age, gender, marital status, and origin conditions are discriminatory in most jurisdictions. They are removed and rewritten as capability requirements, not reworded.
What if team size is not decided?
It becomes a slot in the verification list. Better a [team size] to confirm than a number nobody has settled.
What does one run cost?
One credit per run, usually done in seconds, returning the posting, the reasoning, and items to confirm.
Do credits expire?
No. Credits never expire — whatever you do not use carries over to the next cycle instead of resetting.
Is there batch processing or an API?
Not yet. Each run processes one request and consumes one credit; there is no bulk upload or API today. Email us with your use case and we will assess it.
Is my content stored?
Not intentionally. Text is used for this single AI request only. See the Privacy Policy.
Which requests fit?
New headcount requests, rewrites of old postings, a manager's bullet points, internship and contract roles — in Chinese or English.
SIMPLE PRICING
Prove the value before you upgrade.
Starter
$9/ monthFor an occasional publishing cadence, with a focused monthly credit allocation.
- 50 optimization credits per monthly renewal
- Complete GEO analysis
- Chinese and English output
- Markdown export
Pro
Recommended$29/ monthFor frequent publishers who iterate on content continuously.
- 250 optimization credits per monthly renewal
- Complete GEO analysis
- Chinese and English output
- Markdown export
Advanced
$79/ monthOur largest monthly credit allocation, for the heaviest continuous usage.
- 1,000 optimization credits per monthly renewal
- Complete GEO analysis
- Chinese and English output
- Markdown export
Loading localized prices
Credits never expire: unused credits carry over instead of resetting. Credits apply to this site only and are not shared with other sites.
Prices shown are USD baselines; final currency, taxes, and discounts are determined by Paddle for the checkout location.