Travel Med Surg RN - $1,992 per week
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID / requisition numbers as headings — fold into short
or drop
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions)
- Include section ONLY when real specific content exists — never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Let me structure this:
1. The opening paragraph about seeking talented healthcare professionals - this could be "About the role" or similar.
2. Benefits section (the industry-leading benefits list) - definitely a Benefits section.
3. Required Skills & Experience - this is Requirements/Qualifications.
4. Preferred Skills & Experience - could be part of Requirements or separate.
5. Education (Required and Preferred) - Qualifications.
6. Required Certifications & Licensure - Qualifications/Requirements.
7. About Medical Solutions - company description, maybe "About the company" but not a standard heading. Could be "About the employer" but the rules list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Medical Solutions" might not fit. Could include as a paragraph under a heading? But the rule says use h3 for those specific headings. Might just include as a paragraph without heading? But it's substantive. Could use "About the role" for the intro paragraph and then "About the company" not allowed. Maybe just include as a paragraph after benefits? The rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., so maybe other headings allowed? But prefer those. I think "About the company" is not in the list, but we can still use h3 for it? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid others, but says "e.g." So we can use other headings if needed. However, "Prefer a few substantive sections over many thin ones." So maybe combine.
Also, there is a "Benefits" list at the end (weekly pay, holiday pay, etc.) - that's another benefits list. Might combine with the earlier benefits? They are different: first is "industry-leading benefits enjoyed by Medical Solutions travel nurses", second is "Benefits" list (weekly pay, holiday pay, etc.). Could be two separate benefits sections? But they are both benefits. Could combine into one Benefits section with two sub-lists? But the rule says use ul li for any list. Could have one Benefits heading with two lists? But they are distinct. Might keep as one Benefits section with both lists.
Also, there is pay information: "Estimated pay package based on bill rate... Pay package is based on 12 hour shifts and 36.0 hours per week... with tax-free stipend amount to be determined." This is pay information but not a specific pay rate. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package details, but not a specific number. It says "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..." This is not a concrete pay figure. Might not warrant a Pay section. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package details, but it's vague. I'd probably not create a Pay section because it's not a specific pay rate. However, the schedule is stated: "36 hours per week, Shift: 12 hours, nights". That's schedule information. Could create a Schedule section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule. But the example headings include Schedule. Could include a Schedule section with the shift details. But the job details at top include duration, hours, shift, employment type. That's schedule. Might include a Schedule section.
But the rule also says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The job details (specialty, discipline, duration, hours, shift, employment type) are metadata. Could fold into a short paragraph.
Let me plan sections:
- About the role: introductory paragraph about seeking talented healthcare professionals.
- Benefits: the industry-leading benefits list (Day One Medical, Dental, Vision, etc.) AND the later benefits list (weekly pay, holiday pay, etc.) - combine into one Benefits section with two lists? Or separate? They are both benefits. I'll combine under one Benefits heading with two sub-lists? But the rule says use ul li for any list. Could have two uls under same heading. That's fine.
- Requirements: Required Skills & Experience, Required Certifications & Licensure, Required Education.
- Qualifications: Preferred Skills & Experience, Preferred Education.
- About the company: the "About Medical Solutions" paragraph.
- Schedule: maybe include shift details? But the shift details are in the metadata. Could include a short paragraph about schedule.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one "Requirements & Qualifications" section? But the example headings are separate: Requirements, Qualifications. I'll keep separate.
Let's map:
- About the role: the first paragraph after job details.
- Benefits: both benefits lists.
- Requirements: Required Skills & Experience, Required Certifications & Licensure, Required Education.
- Qualifications: Preferred Skills & Experience, Preferred Education.
- About the company: the About Medical Solutions paragraph.
- Schedule: maybe a short paragraph with shift details.
But the job details at top: "Specialty: Med Surg Discipline: RN Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel" - this is metadata. Could put in a paragraph at top.
Also, the pay package note: "Estimated pay package based on bill rate... Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is pay info but not specific. Could include in a paragraph under About the role or Schedule.
The Job ID: "Medical Solutions Job ID #1205547." - fold into a short paragraph or drop. I'll drop it as per rule.
Now, let's write HTML.
Structure:
Job details paragraph
About the role
Intro paragraph
Benefits
... first benefits list ...
... second benefits list ...
Requirements
... required skills, certifications, education ...
Qualifications
... preferred skills, education ...
About the company
About Medical Solutions paragraph
Schedule
Shift details
But the second benefits list is under a "Benefits" heading in the original. It's a list of benefits. The first benefits list is also benefits. So combine.
Now, need to ensure we don't include boilerplate: "Equal Employment Opportunity And More!" is boilerplate? It's in the first benefits list. Might keep as a list item? It's a benefit? Actually it's EEO statement, which is boilerplate. The rule says remove EEO/equal-opportunity boilerplate. So I should remove "Equal Employment Opportunity And More!" from the benefits list. Also "Estimated pay package based on bill rate..." is not boilerplate, it's pay info. But it's not a specific pay. Might keep as paragraph.
Also, "Required Skills & Experience:" has bullet points that are generic: "To perform this job successfully...", "The requirements list must be representative...", "Reasonable accommodations may be made..." These are generic HR statements, not specific requirements. The rule says preserve ALL substantive information. But these are generic. However, they are part of the posting. Might keep but they are not specific duties. The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." These might be considered legal boilerplate. The first two are generic statements about job performance and requirements list. The third is ADA accommodation. That's legal boilerplate. I think we should remove them. But the rule says "Preserve ALL substantive information". What is substantive? The actual requirements: "Previous experience as a Registered Nurse is preferred." That's under Preferred Skills. The required skills section doesn't list specific skills, just generic statements. The real requirements are in Required Certifications & Licensure and Required Education. So maybe the Required Skills & Experience section is just boilerplate. I'll include only the substantive parts: maybe the required skills section is empty of specifics. But the posting says "Required Skills & Experience:" then three bullet points that are generic. I'll omit those bullet points as they are boilerplate. However, the rule says "Preserve ALL substantive information". The generic statements are not substantive. I'll drop them.
Similarly, "Preferred Skills & Experience:" has "Previous experience as a Registered Nurse is preferred." That's substantive.
Education: Required Education: ASN, graduation from accredited School of Nursing. Preferred Education: Bachelor's degree of Nursing preferred.
Certifications: Current RN license in state of practice, BLS, ACLS/NRP/PALS as appropriate.
Now, the second benefits list: "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". That's a list.
First 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 And More!" - remove EEO.
Now, the About Medical Solutions paragraph is long. Keep as prose.
Now, schedule: "Duration: 13 weeks, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel". Could put in a Schedule
for prose - Do NOT repeat job title as heading - Do NOT put Job ID / requisition numbers as headings — fold into short
or drop - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning, duplicated lines, application instructions) - Include section ONLY when real specific content exists — never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Let me structure this: 1. The opening paragraph about seeking talented healthcare professionals - this could be "About the role" or similar. 2. Benefits section (the industry-leading benefits list) - definitely a Benefits section. 3. Required Skills & Experience - this is Requirements/Qualifications. 4. Preferred Skills & Experience - could be part of Requirements or separate. 5. Education (Required and Preferred) - Qualifications. 6. Required Certifications & Licensure - Qualifications/Requirements. 7. About Medical Solutions - company description, maybe "About the company" but not a standard heading. Could be "About the employer" but the rules list specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Medical Solutions" might not fit. Could include as a paragraph under a heading? But the rule says use h3 for those specific headings. Might just include as a paragraph without heading? But it's substantive. Could use "About the role" for the intro paragraph and then "About the company" not allowed. Maybe just include as a paragraph after benefits? The rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., so maybe other headings allowed? But prefer those. I think "About the company" is not in the list, but we can still use h3 for it? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid others, but says "e.g." So we can use other headings if needed. However, "Prefer a few substantive sections over many thin ones." So maybe combine.
Also, there is a "Benefits" list at the end (weekly pay, holiday pay, etc.) - that's another benefits list. Might combine with the earlier benefits? They are different: first is "industry-leading benefits enjoyed by Medical Solutions travel nurses", second is "Benefits" list (weekly pay, holiday pay, etc.). Could be two separate benefits sections? But they are both benefits. Could combine into one Benefits section with two sub-lists? But the rule says use ul li for any list. Could have one Benefits heading with two lists? But they are distinct. Might keep as one Benefits section with both lists.
Also, there is pay information: "Estimated pay package based on bill rate... Pay package is based on 12 hour shifts and 36.0 hours per week... with tax-free stipend amount to be determined." This is pay information but not a specific pay rate. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package details, but not a specific number. It says "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..." This is not a concrete pay figure. Might not warrant a Pay section. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay package details, but it's vague. I'd probably not create a Pay section because it's not a specific pay rate. However, the schedule is stated: "36 hours per week, Shift: 12 hours, nights". That's schedule information. Could create a Schedule section? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule. But the example headings include Schedule. Could include a Schedule section with the shift details. But the job details at top include duration, hours, shift, employment type. That's schedule. Might include a Schedule section.
But the rule also says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The job details (specialty, discipline, duration, hours, shift, employment type) are metadata. Could fold into a short paragraph. Let me plan sections: - About the role: introductory paragraph about seeking talented healthcare professionals. - Benefits: the industry-leading benefits list (Day One Medical, Dental, Vision, etc.) AND the later benefits list (weekly pay, holiday pay, etc.) - combine into one Benefits section with two lists? Or separate? They are both benefits. I'll combine under one Benefits heading with two sub-lists? But the rule says use ul li for any list. Could have two uls under same heading. That's fine. - Requirements: Required Skills & Experience, Required Certifications & Licensure, Required Education. - Qualifications: Preferred Skills & Experience, Preferred Education. - About the company: the "About Medical Solutions" paragraph. - Schedule: maybe include shift details? But the shift details are in the metadata. Could include a short paragraph about schedule. But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one "Requirements & Qualifications" section? But the example headings are separate: Requirements, Qualifications. I'll keep separate. Let's map: - About the role: the first paragraph after job details. - Benefits: both benefits lists. - Requirements: Required Skills & Experience, Required Certifications & Licensure, Required Education. - Qualifications: Preferred Skills & Experience, Preferred Education. - About the company: the About Medical Solutions paragraph. - Schedule: maybe a short paragraph with shift details. But the job details at top: "Specialty: Med Surg Discipline: RN Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Travel" - this is metadata. Could put in a paragraph at top. Also, the pay package note: "Estimated pay package based on bill rate... Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." This is pay info but not specific. Could include in a paragraph under About the role or Schedule. The Job ID: "Medical Solutions Job ID #1205547." - fold into a short paragraph or drop. I'll drop it as per rule. Now, let's write HTML. Structure:
Job details paragraph
About the role
Intro paragraph
Benefits
- ... first benefits list ...
- ... second benefits list ...
Requirements
- ... required skills, certifications, education ...
Qualifications
- ... preferred skills, education ...
About the company
About Medical Solutions paragraph
Schedule
Shift details
But the second benefits list is under a "Benefits" heading in the original. It's a list of benefits. The first benefits list is also benefits. So combine. Now, need to ensure we don't include boilerplate: "Equal Employment Opportunity And More!" is boilerplate? It's in the first benefits list. Might keep as a list item? It's a benefit? Actually it's EEO statement, which is boilerplate. The rule says remove EEO/equal-opportunity boilerplate. So I should remove "Equal Employment Opportunity And More!" from the benefits list. Also "Estimated pay package based on bill rate..." is not boilerplate, it's pay info. But it's not a specific pay. Might keep as paragraph. Also, "Required Skills & Experience:" has bullet points that are generic: "To perform this job successfully...", "The requirements list must be representative...", "Reasonable accommodations may be made..." These are generic HR statements, not specific requirements. The rule says preserve ALL substantive information. But these are generic. However, they are part of the posting. Might keep but they are not specific duties. The rule says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." These might be considered legal boilerplate. The first two are generic statements about job performance and requirements list. The third is ADA accommodation. That's legal boilerplate. I think we should remove them. But the rule says "Preserve ALL substantive information". What is substantive? The actual requirements: "Previous experience as a Registered Nurse is preferred." That's under Preferred Skills. The required skills section doesn't list specific skills, just generic statements. The real requirements are in Required Certifications & Licensure and Required Education. So maybe the Required Skills & Experience section is just boilerplate. I'll include only the substantive parts: maybe the required skills section is empty of specifics. But the posting says "Required Skills & Experience:" then three bullet points that are generic. I'll omit those bullet points as they are boilerplate. However, the rule says "Preserve ALL substantive information". The generic statements are not substantive. I'll drop them. Similarly, "Preferred Skills & Experience:" has "Previous experience as a Registered Nurse is preferred." That's substantive. Education: Required Education: ASN, graduation from accredited School of Nursing. Preferred Education: Bachelor's degree of Nursing preferred. Certifications: Current RN license in state of practice, BLS, ACLS/NRP/PALS as appropriate. Now, the second benefits list: "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". That's a list. First 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 And More!" - remove EEO. Now, the About Medical Solutions paragraph is long. Keep as prose. Now, schedule: "Duration: 13 weeks, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel". Could put in a Schedule