Manager of Patient Workplace Safety
Rogers Behavioral Health · Oconomowoc, WI · 1 mo ago
ManagementFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content.
We have summary description (About the role). Then Job Duties & Responsibilities (Responsibilities). Then Education/Training Requirements (Qualifications). Also mention Additional Job Description includes some other details like proficiency, driver license, etc. Benefits are listed: Health, dental, vision, 401(k), employee share program, life/disability, flex spending, tuition reimbursement, health and wellness program, EAP. Also mention something about Machine-Readable Files but that's boilerplate? It's about transparency; maybe we can include as part of Benefits? It's not a benefit per se but it's a note. Probably we can ignore as boilerplate? It's not typical benefit but it's still a statement about transparency; but it's not a benefit. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The Machine-Readable Files note might be considered legal/boilerplate; better to drop.
Pay and Schedule not mentioned, so we should not create those sections.
Skills: maybe we can extract from requirements: proficiency with EHR, MS Office, driver license, insurable status, etc. Could be under Skills or Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have About the role (summary). Responsibilities (Job Duties & Responsibilities). Qualifications (Education/Training Requirements). Skills maybe separate: proficiency with EHR, MS Office, driver license, insurable status. Benefits we have. No Pay or Schedule.
We must not repeat job title as heading. So we output something like:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content.
We have summary description (About the role). Then Job Duties & Responsibilities (Responsibilities). Then Education/Training Requirements (Qualifications). Also mention Additional Job Description includes some other details like proficiency, driver license, etc. Benefits are listed: Health, dental, vision, 401(k), employee share program, life/disability, flex spending, tuition reimbursement, health and wellness program, EAP. Also mention something about Machine-Readable Files but that's boilerplate? It's about transparency; maybe we can include as part of Benefits? It's not a benefit per se but it's a note. Probably we can ignore as boilerplate? It's not typical benefit but it's still a statement about transparency; but it's not a benefit. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The Machine-Readable Files note might be considered legal/boilerplate; better to drop.
Pay and Schedule not mentioned, so we should not create those sections.
Skills: maybe we can extract from requirements: proficiency with EHR, MS Office, driver license, insurable status, etc. Could be under Skills or Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have About the role (summary). Responsibilities (Job Duties & Responsibilities). Qualifications (Education/Training Requirements). Skills maybe separate: proficiency with EHR, MS Office, driver license, insurable status. Benefits we have. No Pay or Schedule.
We must not repeat job title as heading. So we output something like:
About the role
... summary ...
Responsibilities
- ... each duty ...
Qualifications
- ... education/training requirements ...
Skills
- ... proficiency ...
Benefits
- ... benefits ...
. Now we need to output only HTML fragment, no markdown fences. Let's construct. We'll have:
About the role
...
Responsibilities
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...