We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We need to parse the posting.
Content:
- Job title: local contract nurse RN ED - Emergency Department in Houston, Texas.
- Specialty: ED - Emergency Department
- Discipline: RN
- Duration: 6 weeks
- 48 hours per week
- Shift: 12 hours, nights
- Employment Type: Local Contract
- Description: "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game. Those that want flexibility and high pay, we have the positions for you!" That's prose.
- Benefits list: Day One Medical, Dental, and Vision with low premiums; Day One 401(k) with Company Contribution; Personalized Compensation Packages; Paid, Private, Fully Furnished, Pet-Friendly Housing; Dedicated Recruiter and 24/7 Customer Care Line; Per Diem Allowance and Paid Travel; Licensure and Certification Reimbursement; Free Liability Coverage; Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance; Equal Employment Opportunity (but we remove EEO boilerplate). Also later "Benefits" section includes: Weekly pay, Holiday Pay, Guaranteed Hours, Continuing Education, 401k retirement plan, Pet insurance, Company provided housing options, Cancelation protection, Wellness and fitness programs, Mileage reimbursement, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits, Benefits start day 1, License and certification reimbursement, Life insurance, Discount program.
- Pay: "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." No specific numbers. So we should not create Pay section because no concrete pay info. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits we have specifics, so we can include Benefits. Pay we have only vague statement, not specific numbers, so we should not include Pay section.
- Schedule: we have shift details: 48 hours per week, Shift: 12 hours, nights. That's schedule info. So we can include Schedule section.
- About the role: maybe we can put description under About the role? The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have:
- About the role: could include the description about seeking talent, adventure game, flexibility, high pay. That's prose.
- Responsibilities: not explicitly listed. Could infer but we should not invent. So skip.
- Requirements: we have specialty, discipline, duration, hours, shift, employment type, location. Those could be considered requirements. But we need to see if they are specific. Yes: Specialty: ED - Emergency Department; Discipline: RN; Duration: 6 weeks; 48 hours per week; Shift: 12 hours, nights; Employment Type: Local Contract; Location: Houston, Texas. Those are requirements/qualifications. Could put under Requirements or Qualifications. The instruction says we can use Requirements, Qualifications, Skills. We need to avoid thin sections. Perhaps combine into Requirements (or Qualifications). We'll include Requirements with list items.
- Skills: not explicitly listed; skip.
- Benefits: we have list; include Benefits section with ul.
- Schedule: we have shift details; include Schedule section with maybe ul or p. Since schedule info is specific: 48 hours per week, Shift: 12 hours, nights. Could be a list.
- Pay: we have only vague statement; do not include.
- About Medical Solutions: that's company description; could be under About the role? Or maybe a separate section like About the company but not in allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit company description maybe under About the role? But About the role is for role description. Could also put under About the role a paragraph about the company? Might be okay. However we already have About the role for role description. We could put company description under About the role as additional paragraph. Or we could omit because not required? The instruction: "Prefer a few substantive sections over many thin ones." We could include About the role (role description) and Requirements (qualifications) and Benefits and Schedule. That's four sections.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include location, duration, hours, shift, employment type, specialty, discipline. Also the adventure game line. Also the benefits list. Also schedule details.
We must not include boilerplate like EEO, navigation, legal, duplicated lines, application instructions. Also remove "Equal Employment Opportunity" and "And More!" etc. Also remove "GL Code: 6700-1033800 - 710020", "Medical Solutions Job ID #1189086L.", "Posted job title: ER (Emergency Room)". Also remove "About Medical Solutions" paragraph? It's company description; maybe we can keep as part of About the role? But it's not about the role; it's about the company. However we might keep it as part of About the role? The instruction says we should not repeat the job title as a heading; we already not. It didn't forbid including company description. But we need to preserve ALL substantive information. The company description is substantive? It's about the company, not the job. Might be considered boilerplate? It's not navigation/legal/EEO. It's a description of the company. Might be considered substantive. However the allowed headings do not include "About the company". Could we put it under About the role? That might be misleading but still preserve info. Alternatively we could create a section like "About Medical Solutions" but not allowed heading. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings. So we need to fit company description somewhere else, maybe as a paragraph under About the role or under Requirements? But that would be odd.
We could decide to omit company description because it's not strictly required for the job? But instruction says preserve ALL substantive information. However maybe they consider company description as boilerplate? It's not navigation/legal/EEO, but it's promotional. Might be considered fluff. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not those. So we should keep it.
We could put it under About the role as a paragraph after the role description. That would preserve it.
Now we need to format.
Structure:
About the role
We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game. Those that want flexibility and high pay, we have the positions for you!
Medical Solutions is one of the nation’s largest providers of total workforce solutions in the healthcare industry, connecting nurses and allied health clinicians with hospitals and healthcare systems across the country and around the corner. Through our family of brands, we also serve a segment of clients outside of the healthcare space. And we’re the very best at what we do. You’ll love our culture that’s filled with heart and soul. As a company and employer, we’re sincerely and unabashedly us. We lead as humans first and believe the unique qualities of each team member make us better together. We share a purpose for helping others and the drive to make a difference. And we offer endless opportunities for personal and professional growth, throughout your career. At Medical Solutions, you’ll find a great place to work and a career home. We’ve received Best Places to Work awards, landed top industry awards, and received accolades for the impact we’ve made in business and within our community. But the only way to really get to know us, is to join us. We think you’ll fit right in.
But that's a lot; maybe we can shorten? We must preserve all substantive information; we cannot summarize away detail. So we need to keep the entire company description verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit any details from the company description. So we need to include the whole paragraph(s). However we can keep as is; it's long but okay.
Now Requirements section: list items.
We need to capture:
- Specialty: ED - Emergency Department
- Discipline: RN
- Duration: 6 weeks
- 48 hours per week
- Shift: 12 hours, nights
- Employment Type: Local Contract
- Location: Houston, Texas
We could also include that it's a local contract nursing job.
We'll make a
- for each.
Now Benefits section: we have two lists of benefits: first list from earlier (Day One Medical..., etc.) and second list under "Benefits" heading (Weekly pay, Holiday Pay, etc.). We need to combine all benefits without duplication. Let's extract all distinct benefits:
From first list:
- Day One Medical, Dental, and Vision with low premiums
- Day One 401(k) with Company Contribution
- Personalized Compensation Packages
- Paid, Private, Fully Furnished, Pet-Friendly Housing
- Dedicated Recruiter and 24/7 Customer Care Line
- Per Diem Allowance and Paid Travel
- Licensure and Certification Reimbursement
- Free Liability Coverage
- Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance
From second list:
- Weekly pay
- Holiday Pay
- Guaranteed Hours
- Continuing Education
- 401k retirement plan (note similar to Day One 401(k) with Company Contribution but we keep both? Might be duplicate; we can keep as separate but maybe it's same. We'll keep both but note duplication? The instruction says remove duplicated lines. So we should deduplicate. "Day One 401(k) with Company Contribution" vs "401k retirement plan". They are similar but not identical; could be considered duplicate concept. Safer to keep both? Might be considered duplicated. I'd deduplicate by keeping the more specific: Day One 401(k) with Company Contribution. We'll drop generic 401k retirement plan.
- Pet insurance (already in Voluntary Benefits)
- Company provided housing options (similar to Paid, Private, Fully Furnished, Pet-Friendly Housing)
- Cancelation protection
- Wellness and fitness programs
- Mileage reimbursement
- Referral bonus
- Employee assistance programs
- Medical benefits (similar to Day One Medical)
- Dental benefits (similar)
- Vision benefits (similar)
- Benefits start day 1 (already implied)
- License and certification reimbursement (duplicate)
- Life insurance
- Discount program
We need to deduplicate similar items. Let's create a unified list:
- Day One Medical, Dental, and Vision with low premiums
- Day One 401(k) with Company Contribution
- Personalized Compensation Packages
- Paid, Private, Fully Furnished, Pet-Friendly Housing
- Dedicated Recruiter and 24/7 Customer Care Line
- Per Diem Allowance and Paid Travel
- Licensure and Certification Reimbursement