Scheduling Manager - Canton, OH
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule).
- Use - for lists,
for prose.
- Do NOT repeat job title as heading.
- Do NOT put Job ID / requisition numbers as headings (there's #MGR-H at end, ignore).
- Preserve ALL substantive information; do NOT invent or summarize away detail.
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text.
- Never create Pay/Schedule/Benefits sections unless the posting actually states them.
- Prefer a few substantive sections over many thin ones.
- Output ONLY the HTML fragment — no /, no markdown code fences.
Now, let's map sections:
1. "What We Do:" - This is company description. Could be "About the Company" or "About the Role"? The heading suggestions include "About the role". But this is about the company. I'll use "About the Company" as an h3.
2. "Job Description:" - This is an overview of the role. Could be "About the Role" or "Role Overview". I'll use "About the Role".
3. "Job Responsibilities:" - This is a list of duties. Use "Responsibilities" heading.
4. "Employee and Fringe Benefits:" - This lists benefits. Use "Benefits" heading.
5. "Education & Certifications:" - This is requirements. Use "Requirements" or "Qualifications". The rules mention "Requirements, Qualifications". I'll use "Qualifications".
6. "Preferred Skills:" - Use "Skills" heading.
7. "Physical Requirements:" - This is physical demands. Could be "Physical Requirements" heading.
8. "Work Environment:" - Could be "Work Environment" heading.
Pay: The posting mentions "$40,000 + Benefits & Bonus Opportunities" in the title line. That's pay information. Should I include a "Pay" section? The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay in the title line: "$40,000 + Benefits & Bonus Opportunities". Also in benefits section, there's "Growth Bonus, WOTC Bonus, Phone Stipend". So pay is mentioned. I should include a Pay section with that info. However, the title line also includes "Full-Time | Management Role". That's schedule/type. Could include a "Schedule" section? The rule says only if posting actually states them. It says "Full-Time" in the title line. That's schedule. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. But the user says "Prefer a few substantive sections over many thin ones." I could combine pay and schedule into one section? But the headings are separate. I'll include Pay and Schedule if they have content.
But note: The title line is "Scheduling Manager - Cornerstone Caregiving Canton, OH | Full-Time | Management Role | $40,000 + Benefits & Bonus Opportunities". That's metadata. The rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This includes location, full-time, management role, pay. That's minor metadata? But pay is substantive. The rule says "fold minor metadata into a short
or drop it." I think I should include pay in a Pay section because it's specific: $40,000 + Benefits & Bonus Opportunities. Also schedule: Full-Time. But the posting doesn't have a separate schedule section. I could include a short "Pay & Schedule" section? But the headings are separate. I'll create a "Pay" section with the salary and bonus info, and a "Schedule" section with "Full-Time" and maybe "Management Role". However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them in the title line. But the title line is not a section; it's the header. The user says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So the title line includes location, full-time, management role, pay. That's metadata. I should fold that into a short
maybe at the top? But the output is only HTML fragment, no page context. I could include a brief introductory paragraph with that metadata. However, the rule says "Output ONLY the HTML fragment". I think I should include a short
at the beginning with the key metadata: location, full-time, management role, pay. Then proceed with sections.
But the user says "Preserve ALL substantive information". The pay is substantive. I'll include a "Pay" section with the salary and bonus details. The schedule: "Full-Time" is mentioned. I'll include a "Schedule" section with "Full-Time". But the posting also mentions "on-call responsibilities" which is part of responsibilities. That's not schedule per se.
Let's examine the content for each section:
- About the Company: "Cornerstone Caregiving is passionate about helping seniors age in place in a setting and manner of their choosing. We believe seniors deserve the opportunity to age in a healthy, dignified environment. As a leading, nationwide home care organization serving seniors in more than 450 locations, Cornerstone remains committed to providing the highest quality of care to those that cared for us."
- About the Role: "As a Scheduling Manager, you will work directly with the Recruiting Manager and both roles will report to and assist the Operating Director. The Scheduling Manager’s primary focus will be to provide scheduling, administrative, and operating support for the office. The Scheduling Manager will also be responsible for sharing on-call responsibilities with the other managers."
- Responsibilities: list of 6 items (Caregiver Management, Scheduling, On-Call, General Office Support, In-home Assessments, Client Care, Compliance). Actually 7 items? Let's count: Caregiver Management, Scheduling, On-Call, General Office Support, In-home Assessments, Client Care, Compliance. That's 7.
- Benefits: list: Access to company-sponsored benefits plan (health, dental, vision, life, other insurance), PTO accrues at 1 day per month, Growth Bonus, WOTC Bonus, Phone Stipend.
- Qualifications (Education & Certifications): High school diploma or equivalent; Associates and/or Bachelor Degree; may substitute Degree requirement with combination of education/experience; minimum two years' experience as Administrator and/or managing sales, customer service, and human resource functions within an office setting; Valid drivers license; Valid state required proof of auto insurance.
- Skills (Preferred Skills): Ability to work autonomously in fast-paced environment; Comfortable working with technology; Experience with oversight of frontline employees; Experience with shift planning and employee scheduling; Strong interpersonal and communication skills; Proficient in Google Workspace.
- Physical Requirements: described in paragraph and list. The posting says "The physical demands described here are representative... This position may involve any or all of the following (not a complete list): sitting and standing for long periods; bending and stooping; lifting up to 10 lbs regularly and up to 50+ lbs may be required; using computer for extended periods; using fingers, wrists, arms; stress on back may occur." I'll put as a paragraph and maybe a list.
- Work Environment: two subsections: Office Environment and Client's Environment. Each with descriptions. I'll include as sub-lists or paragraphs.
Now, EEO boilerplate and legal text at the end should be removed.
Also, the "#MGR-H" at end is job ID, drop.
Now, structure HTML:
Start with a short
for metadata? The rule says "fold minor metadata into a short
or drop it." The metadata includes location (Canton, OH), Full-Time, Management Role, $40,000 + Benefits & Bonus Opportunities. I'll include a
at the top: "Location: Canton, OH | Full-Time | Management Role | Salary: $40,000 + Benefits & Bonus Opportunities". But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Scheduling Manager". The page already shows it, so we don't need to repeat. But the metadata includes the title? The title line includes "Scheduling Manager - Cornerstone Caregiving Canton, OH | Full-Time | Management Role | $40,000 + Benefits & Bonus Opportunities". That's the job title plus metadata. Since the page already shows the job title, we can drop the title but keep the metadata. I'll include a
with the metadata.
But the user says "Output ONLY the HTML fragment". So I'll output a series of sections.
Let's decide on headings:
- About the Company
- About the Role
- Responsibilities
- Benefits
- Qualifications
- Skills
- Physical Requirements
- Work Environment
- Pay (maybe)
- Schedule (maybe)
But the rule: "Prefer a few substantive sections over many thin ones." Physical Requirements and Work Environment are specific and substantive. They should be included.
Pay: The posting states "$40,000 + Benefits & Bonus Opportunities". That's a specific pay figure. I'll include a Pay section with that. Also the benefits section includes bonuses. But the Pay section could include the base salary and mention bonuses. However, the benefits section already lists bonuses. Might be duplication. I'll include Pay section with the base salary and note that bonuses are detailed in Benefits.
Schedule: The posting says "Full-Time". That's a schedule. I'll include a Schedule section with "Full-Time". Also maybe "Management Role" is a type. But that's minor.
Alternatively, I could fold pay and schedule into the introductory paragraph. The rule says "fold minor metadata into a short
or drop it." Pay is not minor; it's substantive. But the rule also says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So I'll create them.
But the user example headings include "Pay, Schedule". So I'll include them.
Now, let's write HTML.
I'll start with a
for metadata: "Canton, OH | Full-Time | Management Role | $40,000 + Benefits & Bonus Opportunities"
Then sections.
Note: The headings should be
. Use - for lists. Use
for prose.
For Responsibilities, each bullet is a duty with description. I'll keep the bolded term and description.
For Benefits, list each benefit.
For Qualifications, list each requirement.
For Skills, list each skill.
for prose. - Do NOT repeat job title as heading. - Do NOT put Job ID / requisition numbers as headings (there's #MGR-H at end, ignore). - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. - Never create Pay/Schedule/Benefits sections unless the posting actually states them. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no /, no markdown code fences. Now, let's map sections: 1. "What We Do:" - This is company description. Could be "About the Company" or "About the Role"? The heading suggestions include "About the role". But this is about the company. I'll use "About the Company" as an h3. 2. "Job Description:" - This is an overview of the role. Could be "About the Role" or "Role Overview". I'll use "About the Role". 3. "Job Responsibilities:" - This is a list of duties. Use "Responsibilities" heading. 4. "Employee and Fringe Benefits:" - This lists benefits. Use "Benefits" heading. 5. "Education & Certifications:" - This is requirements. Use "Requirements" or "Qualifications". The rules mention "Requirements, Qualifications". I'll use "Qualifications". 6. "Preferred Skills:" - Use "Skills" heading. 7. "Physical Requirements:" - This is physical demands. Could be "Physical Requirements" heading. 8. "Work Environment:" - Could be "Work Environment" heading. Pay: The posting mentions "$40,000 + Benefits & Bonus Opportunities" in the title line. That's pay information. Should I include a "Pay" section? The rule says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay in the title line: "$40,000 + Benefits & Bonus Opportunities". Also in benefits section, there's "Growth Bonus, WOTC Bonus, Phone Stipend". So pay is mentioned. I should include a Pay section with that info. However, the title line also includes "Full-Time | Management Role". That's schedule/type. Could include a "Schedule" section? The rule says only if posting actually states them. It says "Full-Time" in the title line. That's schedule. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. But the user says "Prefer a few substantive sections over many thin ones." I could combine pay and schedule into one section? But the headings are separate. I'll include Pay and Schedule if they have content. But note: The title line is "Scheduling Manager - Cornerstone Caregiving Canton, OH | Full-Time | Management Role | $40,000 + Benefits & Bonus Opportunities". That's metadata. The rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This includes location, full-time, management role, pay. That's minor metadata? But pay is substantive. The rule says "fold minor metadata into a short
or drop it." I think I should include pay in a Pay section because it's specific: $40,000 + Benefits & Bonus Opportunities. Also schedule: Full-Time. But the posting doesn't have a separate schedule section. I could include a short "Pay & Schedule" section? But the headings are separate. I'll create a "Pay" section with the salary and bonus info, and a "Schedule" section with "Full-Time" and maybe "Management Role". However, the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them in the title line. But the title line is not a section; it's the header. The user says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So the title line includes location, full-time, management role, pay. That's metadata. I should fold that into a short
maybe at the top? But the output is only HTML fragment, no page context. I could include a brief introductory paragraph with that metadata. However, the rule says "Output ONLY the HTML fragment". I think I should include a short
at the beginning with the key metadata: location, full-time, management role, pay. Then proceed with sections. But the user says "Preserve ALL substantive information". The pay is substantive. I'll include a "Pay" section with the salary and bonus details. The schedule: "Full-Time" is mentioned. I'll include a "Schedule" section with "Full-Time". But the posting also mentions "on-call responsibilities" which is part of responsibilities. That's not schedule per se. Let's examine the content for each section: - About the Company: "Cornerstone Caregiving is passionate about helping seniors age in place in a setting and manner of their choosing. We believe seniors deserve the opportunity to age in a healthy, dignified environment. As a leading, nationwide home care organization serving seniors in more than 450 locations, Cornerstone remains committed to providing the highest quality of care to those that cared for us." - About the Role: "As a Scheduling Manager, you will work directly with the Recruiting Manager and both roles will report to and assist the Operating Director. The Scheduling Manager’s primary focus will be to provide scheduling, administrative, and operating support for the office. The Scheduling Manager will also be responsible for sharing on-call responsibilities with the other managers." - Responsibilities: list of 6 items (Caregiver Management, Scheduling, On-Call, General Office Support, In-home Assessments, Client Care, Compliance). Actually 7 items? Let's count: Caregiver Management, Scheduling, On-Call, General Office Support, In-home Assessments, Client Care, Compliance. That's 7. - Benefits: list: Access to company-sponsored benefits plan (health, dental, vision, life, other insurance), PTO accrues at 1 day per month, Growth Bonus, WOTC Bonus, Phone Stipend. - Qualifications (Education & Certifications): High school diploma or equivalent; Associates and/or Bachelor Degree; may substitute Degree requirement with combination of education/experience; minimum two years' experience as Administrator and/or managing sales, customer service, and human resource functions within an office setting; Valid drivers license; Valid state required proof of auto insurance. - Skills (Preferred Skills): Ability to work autonomously in fast-paced environment; Comfortable working with technology; Experience with oversight of frontline employees; Experience with shift planning and employee scheduling; Strong interpersonal and communication skills; Proficient in Google Workspace. - Physical Requirements: described in paragraph and list. The posting says "The physical demands described here are representative... This position may involve any or all of the following (not a complete list): sitting and standing for long periods; bending and stooping; lifting up to 10 lbs regularly and up to 50+ lbs may be required; using computer for extended periods; using fingers, wrists, arms; stress on back may occur." I'll put as a paragraph and maybe a list. - Work Environment: two subsections: Office Environment and Client's Environment. Each with descriptions. I'll include as sub-lists or paragraphs. Now, EEO boilerplate and legal text at the end should be removed. Also, the "#MGR-H" at end is job ID, drop. Now, structure HTML: Start with a short
for metadata? The rule says "fold minor metadata into a short
or drop it." The metadata includes location (Canton, OH), Full-Time, Management Role, $40,000 + Benefits & Bonus Opportunities. I'll include a
at the top: "Location: Canton, OH | Full-Time | Management Role | Salary: $40,000 + Benefits & Bonus Opportunities". But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Scheduling Manager". The page already shows it, so we don't need to repeat. But the metadata includes the title? The title line includes "Scheduling Manager - Cornerstone Caregiving Canton, OH | Full-Time | Management Role | $40,000 + Benefits & Bonus Opportunities". That's the job title plus metadata. Since the page already shows the job title, we can drop the title but keep the metadata. I'll include a
with the metadata. But the user says "Output ONLY the HTML fragment". So I'll output a series of sections. Let's decide on headings: - About the Company - About the Role - Responsibilities - Benefits - Qualifications - Skills - Physical Requirements - Work Environment - Pay (maybe) - Schedule (maybe) But the rule: "Prefer a few substantive sections over many thin ones." Physical Requirements and Work Environment are specific and substantive. They should be included. Pay: The posting states "$40,000 + Benefits & Bonus Opportunities". That's a specific pay figure. I'll include a Pay section with that. Also the benefits section includes bonuses. But the Pay section could include the base salary and mention bonuses. However, the benefits section already lists bonuses. Might be duplication. I'll include Pay section with the base salary and note that bonuses are detailed in Benefits. Schedule: The posting says "Full-Time". That's a schedule. I'll include a Schedule section with "Full-Time". Also maybe "Management Role" is a type. But that's minor. Alternatively, I could fold pay and schedule into the introductory paragraph. The rule says "fold minor metadata into a short
or drop it." Pay is not minor; it's substantive. But the rule also says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So I'll create them. But the user example headings include "Pay, Schedule". So I'll include them. Now, let's write HTML. I'll start with a
for metadata: "Canton, OH | Full-Time | Management Role | $40,000 + Benefits & Bonus Opportunities" Then sections. Note: The headings should be
. Use - for lists. Use
for prose.
For Responsibilities, each bullet is a duty with description. I'll keep the bolded term and description.
For Benefits, list each benefit.
For Qualifications, list each requirement.
For Skills, list each skill.
for prose. For Responsibilities, each bullet is a duty with description. I'll keep the bolded term and description. For Benefits, list each benefit. For Qualifications, list each requirement. For Skills, list each skill.