Senior Staffing Coordinator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the description. Key content: - Description paragraph: responsibilities: preparing and maintaining staffing schedules for assigned departments/units, managing time and attendance for department/unit personnel, partnering with Department/Unit Manager and Administrative Supervisor to adjust staffing needs. Use predictive staffing analytics and other data driven protocols to manipulate schedules to fulfill staffing needs and prevent premium pay shifts when possible. Successful execution helps departments achieve targeted budget goals and provides inputs and oversight for Kronos accuracy. Additionally serves as staffing support personnel for South Puget Sound Region, to appropriately staff units for day to day operations, managing personnel to limit use of premium pay shifts and create financial stewardship. Exhibits high level of scheduling, staffing, timekeeping accuracy, incorporates predictive staffing models and data driven protocols. Functions as engaged, collaborative, participative member of interdisciplinary team, consistent with mission, vision, values of Providence Swedish Healthcare. Then a paragraph about Providence caregivers etc. That's more about company culture, maybe not needed but could be part of About the role? Might be considered fluff but it's substantive? The instruction: 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. The paragraph about Providence caregivers not simply valued etc. That's marketing fluff but maybe considered part of description; but we can keep as part of About the role? However we need to decide sections. We have Required Qualifications: Associate's Degree in business, healthcare or Equivalent education from a college or technical school OR 1 year of experience in a similar or related field 1 year of experience with staffing, scheduling and/or timekeeping Preferred Qualifications: 1 year of Familiarity with electronic scheduling systems such as ShiftWise and Kronos software 1 year of Basic knowledge of medical terminology 1 year of Customer service experience Why Join Providence? paragraph about benefits. About Providence paragraph about mission etc. Posted are the minimum and the maximum wage rates on the wage range for this position... (Pay range). Additional compensation may be available... Providence offers a comprehensive benefits package including retirement 401(k) Savings Plan with employer matching, health care benefits (medical, dental, vision), life insurance, disability insurance, time off benefits (paid parental leave, vacations, holidays, health issues), voluntary benefits, well-being resources and much more. Learn more at providence.jobs/benefits. Applicants in the Unincorporated County of Los Angeles: ... (EEO stuff) - we should remove EEO boilerplate. About The Team paragraph about Providence history etc. Might be considered fluff but maybe we keep as part of About the role? However we need to avoid duplication and boilerplate. The "About The Team" is not boilerplate but it's descriptive of organization; could be considered part of About the role? But we have limited sections. We also have Job Schedule: Per-Diem, Job Shift: Variable, Career Track: Admin Support, Department etc. Address etc. Work Location etc. Workplace Type: On-site. Pay Range: $25.23 - $38.61. We need to include Pay section if posting actually states them. Yes, we have Pay Range. So include Pay section with that range. Schedule section: we have Job Schedule: Per-Diem, Job Shift: Variable. So we can include Schedule section with that info. Benefits section: we have description of benefits. So include Benefits. Responsibilities: we have description of duties. So include Responsibilities. Requirements: we have Required Qualifications and Preferred Qualifications. Could combine into Requirements section? Or separate Requirements and Qualifications? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content exists. But we need to avoid thin sections. We have both required and preferred qualifications; we could put them under Requirements (maybe combine). Or we could have Requirements for required, Qualifications for preferred. That seems appropriate. Skills: maybe we can extract skills like scheduling, timekeeping, predictive staffing analytics, data driven protocols, Kronos, ShiftWise, medical terminology, customer service. Could be a Skills section. About the role: we could have a brief summary of the role from description. Could combine responsibilities? But we need to avoid duplication. Perhaps About the role includes overview of purpose: preparing staffing schedules, managing time/attendance, partnering with managers, using predictive analytics, etc. Responsibilities could be more detailed list. However we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine overview and responsibilities into Responsibilities section, and skip About the role. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't mandate we must include all; we include only those with real content. So we can choose which to include. We need to preserve all substantive info. If we omit About the role, we must ensure its content is covered elsewhere. The description includes a lot of narrative about role; we could put that under Responsibilities. That seems fine. Thus sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Check if we have content for each: - Responsibilities: the description paragraphs about preparing schedules, managing time/attendance, partnering, predictive staffing analytics, preventing premium pay, achieving budget goals, Kronos accuracy, staffing support for South Puget Sound Region, managing personnel to limit premium pay, financial stewardship, high level of accuracy, incorporates predictive models, functions as engaged collaborative member. That's substantive. - Requirements: Required Qualifications: Associate's Degree in business, healthcare or Equivalent education from a college or technical school OR 1 year of experience in a similar or related field 1 year of experience with staffing, scheduling and/or timekeeping We need to preserve exactly. Might need to format as list. - Qualifications: Preferred Qualifications: 1 year of Familiarity with electronic scheduling systems such as ShiftWise and Kronos software 1 year of Basic knowledge of medical terminology 1 year of Customer service experience - Skills: Could list: scheduling, staffing, timekeeping, predictive staffing analytics, data driven protocols, Kronos, ShiftWise, medical terminology, customer service, collaborative teamwork, financial stewardship, budget goal achievement. Might be derived from description. Ensure we don't invent. We can extract from responsibilities: scheduling, staffing, timekeeping, predictive staffing analytics, data driven protocols, Kronos accuracy, partnering with managers, adjusting staffing needs, managing personnel to limit premium pay, financial stewardship, collaborative interdisciplinary team member. Also from preferred qualifications: familiarity with ShiftWise and Kronos, basic medical terminology, customer service. So we can list those. - Benefits: paragraph about best-in-class benefits, retirement 401(k) Savings Plan with employer matching, health care benefits (medical, dental, vision), life insurance, disability insurance, time off benefits (paid parental leave, vacations, holidays, health issues), voluntary benefits, well-being resources, plus mention of learn more at providence.jobs/benefits. Also earlier "Why Join Providence?" paragraph about benefits. We'll combine. - Pay: Pay Range: $25.23 - $38.61; note that amounts are base pay range; additional compensation may be available such as shift differentials, standby/on-call, overtime, premiums, extra shift incentives, or bonus opportunities. - Schedule: Job Schedule: Per-Diem; Job Shift: Variable. We also have Work Location: Providence St Peter Hospital-Olympia, Address: WA Olympia 413 Lilly Rd NE, Workplace Type: On-site. Should we include? Could be part of About the role? But we don't have About the role section. Could add a section "Work Location" but not in allowed headings list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those. However we need to preserve all substantive info; if we drop location info, we lose substantive. Could we incorporate location into Responsibilities or Benefits? Not appropriate. Maybe we can add a heading "Location" but not in list. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive. So we can add other headings if needed, as long as they are

. But we should avoid creating thin sections. Location is substantive. Could add a section "Location". However the instruction says "Prefer a few substantive sections over many thin ones." Adding Location adds another section but it's substantive. Could we fold location into Responsibilities? Not really. Could add a brief

after the sections? The instruction says output ONLY the HTML fragment. We could include a

for location after the sections without a heading. That would preserve info without extra heading. That seems acceptable: we can include a

with location details. Similarly, we could include Workplace Type: On-site. Could be in same

. Thus we will have sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Then after those, a

for location and workplace type. We must not include Job ID etc. Also remove duplicated lines, boilerplate like EEO, Fair Chance, etc. Also remove "About Providence" and "About The Team" paragraphs (they are fluff). Also remove "Why Join Providence?" maybe we incorporated benefits; but we need to ensure we don't lose substantive benefits info. The "Why Join Providence?" paragraph is about benefits; we already have benefits section. So we can drop that paragraph. We also need to remove "Posted are the minimum and the maximum wage rates..." we kept pay. We need to remove "Applicants in the Unincorporated County of Los Angeles:" etc (EEO). Remove. We need to remove "Providence caregivers are not simply valued – they’re invaluable..." etc (fluff). Remove. We need to remove "About Providence" paragraph (history). Remove. We need to remove "About The Team" paragraph (history). Remove. We need to remove "Requsition ID: 460574 Company: Providence Jobs Job Category: Administrative Support Job Function: Administration Job Schedule: Per-Diem Job Shift: Variable Career Track: Admin Support Department: 3030 NUR ADMIN 2ND RAINIER1 Address: WA Olympia 413 Lilly Rd NE Work Location: Providence St Peter Hospital-Olympia Workplace Type: On-site Pay Range: $25.23 - $38.61". We'll keep schedule, pay, location, workplace type. Now craft HTML. We'll use

for each section heading. Inside each section, use

for prose,

• for lists. Responsibilities: we can make a
  list of duties. Let's extract duties as bullet points: - Preparing and maintaining staffing schedules for assigned departments/units - Managing time and attendance for department/unit personnel - Partnering with the Department/Unit Manager and Administrative Supervisor to adjust staffing needs - Using predictive staffing analytics and other data-driven protocols to manipulate schedules to fulfill staffing needs and prevent premium pay shifts when possible - Helping departments