Registered Nurse - Full-Time - Night Shift
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule).
- Use `- ` for lists of duties/requirements/benefits.
- Use `
` for prose.
- Do NOT repeat job title as heading (page already shows it).
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it.
- 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.
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and 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.
2. **Parse the Input Data:**
- Role: Registered nurse providing high-level clinical care to patients, utilizing the nursing process for assessment, planning, implementation, and evaluation.
- Responsibilities:
- Deliver direct and indirect patient care in accordance with unit standards.
- Supervise and collaborate with team members and multidisciplinary teams to ensure age-appropriate care.
- Communicate clearly, build collaborative relationships, and promote a positive patient experience.
- Take accountability for performance, seek professional growth, and contribute to a team environment.
- Qualifications & Skills:
- Graduate of an accredited nursing program; BSN preferred.
- Current Basic Life Support certification and applicable departmental certifications.
- Valid nursing license for the practice location or eligibility to obtain one.
- At least 1 year of labor & delivery RN experience.
- Additional Information:
- The role involves providing specialized care in a leading hospital known for trauma, stroke, and neonatal services, with a focus on professional development and teamwork in a diverse, award-winning environment.
- Note: The input has sections like "Responsibilities", "Qualifications & Skills", "Additional Information". No Pay, Schedule, Benefits mentioned. No Job ID/requisition numbers visible. No boilerplate mentioned in this snippet, but I should remove any generic stuff if present (none seen here).
3. **Map to HTML Structure per Rules:**
- Headings: `
` for sections. Allowed examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
- I need to choose appropriate headings from the content. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I must use all of them, only include a section when there's real content. Also, "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an `` for "Registered nurse" or similar.
- The input has: Responsibilities, Qualifications & Skills, Additional Information. I could map these to "Responsibilities", "Qualifications", maybe "About the role" or keep "Additional Information" but need to see if it fits a heading. The rules list examples but I can use relevant ones. I'll use: Responsibilities, Qualifications, and maybe a section for the additional info, but need to check if it's substantive enough. It describes the hospital, trauma/stroke/neonatal services, professional development, teamwork, diverse award-winning environment. That's substantive.
- I should NOT create Pay/Schedule/Benefits sections since they're not in the posting.
- I need to use `- ` for lists of duties/requirements/benefits. The responsibilities and qualifications are lists.
- Use `
` for prose. The "Additional Information" prose part can be a `
`, or I could integrate it.
- Remove any boilerplate - none present in snippet.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
Let's structure:
- `
Responsibilities
` followed by `- ...` list items.
- `
Qualifications
` followed by `- ...` list items. Note: input says "Qualifications & Skills", I'll split or combine as appropriate. Rules say I can use "Qualifications, Skills" as headings. I'll probably do `
Qualifications
` and include skills within, or `Qualifications & Skills
`. To be safe, I'll use `Qualifications & Skills
` since that's exactly in the input and it's substantive.
- `About the role
` or similar for the Additional Information. The rules list "About the role" as an example heading. The additional info describes the hospital, services, environment. I'll use `About the role
` and put the prose there, or maybe `` after. But rules say "include a section ONLY when the posting has real, specific content for it". This section has content. I could also just use a `
` after the qualifications, but the rule says use `
` for section headings, and "About the role" is an example. I'll use `About the role
` and then `
...
` with the text.
Wait, let's re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This means I should use those heading names if those sections exist. It doesn't force me to use all, but I can map the input sections to these. The input has "Responsibilities", "Qualifications & Skills", "Additional Information". I'll map:
- Responsibilities -> `Responsibilities
`
- Qualifications & Skills -> `Qualifications & Skills
` (matches example)
- Additional Information -> could be `About the role
` or just keep as is. I'll use `About the role
` since it's in the example list and fits.
- For lists: `- ` for each item.
- For prose in Additional Information: `
...
`.
- Check if any list items should be combined or kept as is. I'll keep each bullet as a separate ` - `.
- "Do NOT repeat the job title as a heading" - I won't add an `
` for "Registered nurse".
- "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - None present, fine.
- "Preserve ALL substantive information; do NOT invent or summarize away detail." - I'll include every line from the input.
- "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - None in snippet.
- "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them." - I won't create Pay/Schedule/Benefits. I will only have sections with real content.
- "Prefer a few substantive sections over many thin ones." - I'll have three sections: Responsibilities, Qualifications & Skills, About the role. That's fine.
Now, construct HTML fragment:
`
Responsibilities
`
``
`- Deliver direct and indirect patient care in accordance with unit standards.
`
`- Supervise and collaborate with team members and multidisciplinary teams to ensure age-appropriate care.
`
`- Communicate clearly, build collaborative relationships, and promote a positive patient experience.
`
`- Take accountability for performance, seek professional growth, and contribute to a team environment.
`
`
`
`Qualifications & Skills
`
``
`- Graduate of an accredited nursing program; BSN preferred.
`
`- Current Basic Life Support certification and applicable departmental certifications.
`
`- Valid nursing license for the practice location or eligibility to obtain one.
`
`- At least 1 year of labor & delivery RN experience.
`
`
`
`About the role
`
`The role involves providing specialized care in a leading hospital known for trauma, stroke, and neonatal services, with a focus on professional development and teamwork in a diverse, award-winning environment.
`
Check rules again: "use for prose" - yes. "Use
- for any list of duties/requirements/benefits" - yes. "Do NOT repeat the job title as a heading" - I have no heading for job title. Good. "Do NOT put Job ID / requisition numbers as headings" - none. "include a section ONLY when the posting has real, specific content for it" - all three have content. "never emit a heading followed by filler/placeholder text" - no fillers. "never create Pay/Schedule/Benefits sections unless the posting actually states them" - I won't. "Output ONLY the HTML fragment — no /, no markdown code fences." - I'll output just the HTML, no fences.
One thing: The input says "Qualifications & Skills" as a combined heading. I'll keep it as `
Qualifications & Skills
`. That's fine.
Also, note that the first line "Role: Registered nurse providing high-level clinical care to patients, utilizing the nursing process for assessment, planning, implementation, and evaluation." - This seems like a description. I could incorporate it into "About the role" or just ignore since rules say don't repeat job title. But it's substantive content about the role. I'll include it in the "About the role" paragraph or before it. Actually, the first line might be considered the job summary. I'll add it to the `` under "About the role", or make a separate `
` before the heading? Rules say use `
` for section headings, and "About the role" is an example. I'll structure the additional info paragraph to include that sentence. Let's see: "The role involves providing specialized care in a leading hospital known for trauma, stroke, and neonatal services, with a focus on professional development and teamwork in a diverse, award-winning environment." The first sentence "Registered nurse providing high-level clinical care to patients, utilizing the nursing process for assessment, planning, implementation, and evaluation." could be part of it. I'll combine or put it in the paragraph. To be safe, I'll make the `
` include both, or start with that description. Actually, I'll just put the additional info as is, and maybe add the first line as part of the paragraph. But the rules say "Preserve ALL substantive information". So I should include that first line. I'll make the paragraph: "The role involves providing specialized care in a leading hospital known
` for prose. - Do NOT repeat job title as heading (page already shows it). - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it. - 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. - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and 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. 2. **Parse the Input Data:** - Role: Registered nurse providing high-level clinical care to patients, utilizing the nursing process for assessment, planning, implementation, and evaluation. - Responsibilities: - Deliver direct and indirect patient care in accordance with unit standards. - Supervise and collaborate with team members and multidisciplinary teams to ensure age-appropriate care. - Communicate clearly, build collaborative relationships, and promote a positive patient experience. - Take accountability for performance, seek professional growth, and contribute to a team environment. - Qualifications & Skills: - Graduate of an accredited nursing program; BSN preferred. - Current Basic Life Support certification and applicable departmental certifications. - Valid nursing license for the practice location or eligibility to obtain one. - At least 1 year of labor & delivery RN experience. - Additional Information: - The role involves providing specialized care in a leading hospital known for trauma, stroke, and neonatal services, with a focus on professional development and teamwork in a diverse, award-winning environment. - Note: The input has sections like "Responsibilities", "Qualifications & Skills", "Additional Information". No Pay, Schedule, Benefits mentioned. No Job ID/requisition numbers visible. No boilerplate mentioned in this snippet, but I should remove any generic stuff if present (none seen here). 3. **Map to HTML Structure per Rules:** - Headings: `
` for sections. Allowed examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
- I need to choose appropriate headings from the content. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I must use all of them, only include a section when there's real content. Also, "Do NOT repeat the job title as a heading (the page already shows it)". So I shouldn't have an `` for "Registered nurse" or similar.
- The input has: Responsibilities, Qualifications & Skills, Additional Information. I could map these to "Responsibilities", "Qualifications", maybe "About the role" or keep "Additional Information" but need to see if it fits a heading. The rules list examples but I can use relevant ones. I'll use: Responsibilities, Qualifications, and maybe a section for the additional info, but need to check if it's substantive enough. It describes the hospital, trauma/stroke/neonatal services, professional development, teamwork, diverse award-winning environment. That's substantive.
- I should NOT create Pay/Schedule/Benefits sections since they're not in the posting.
- I need to use `- ` for lists of duties/requirements/benefits. The responsibilities and qualifications are lists.
- Use `
` for prose. The "Additional Information" prose part can be a `
`, or I could integrate it.
- Remove any boilerplate - none present in snippet.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
Let's structure:
- `
Responsibilities
` followed by `- ...` list items.
- `
Qualifications
` followed by `- ...` list items. Note: input says "Qualifications & Skills", I'll split or combine as appropriate. Rules say I can use "Qualifications, Skills" as headings. I'll probably do `
Qualifications
` and include skills within, or `Qualifications & Skills
`. To be safe, I'll use `Qualifications & Skills
` since that's exactly in the input and it's substantive.
- `About the role
` or similar for the Additional Information. The rules list "About the role" as an example heading. The additional info describes the hospital, services, environment. I'll use `About the role
` and put the prose there, or maybe `` after. But rules say "include a section ONLY when the posting has real, specific content for it". This section has content. I could also just use a `
` after the qualifications, but the rule says use `
` for section headings, and "About the role" is an example. I'll use `About the role
` and then `
...
` with the text.
Wait, let's re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This means I should use those heading names if those sections exist. It doesn't force me to use all, but I can map the input sections to these. The input has "Responsibilities", "Qualifications & Skills", "Additional Information". I'll map:
- Responsibilities -> `Responsibilities
`
- Qualifications & Skills -> `Qualifications & Skills
` (matches example)
- Additional Information -> could be `About the role
` or just keep as is. I'll use `About the role
` since it's in the example list and fits.
- For lists: `- ` for each item.
- For prose in Additional Information: `
...
`.
- Check if any list items should be combined or kept as is. I'll keep each bullet as a separate ` - `.
- "Do NOT repeat the job title as a heading" - I won't add an `
` for "Registered nurse".
- "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - None present, fine.
- "Preserve ALL substantive information; do NOT invent or summarize away detail." - I'll include every line from the input.
- "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - None in snippet.
- "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them." - I won't create Pay/Schedule/Benefits. I will only have sections with real content.
- "Prefer a few substantive sections over many thin ones." - I'll have three sections: Responsibilities, Qualifications & Skills, About the role. That's fine.
Now, construct HTML fragment:
`
Responsibilities
`
``
`- Deliver direct and indirect patient care in accordance with unit standards.
`
`- Supervise and collaborate with team members and multidisciplinary teams to ensure age-appropriate care.
`
`- Communicate clearly, build collaborative relationships, and promote a positive patient experience.
`
`- Take accountability for performance, seek professional growth, and contribute to a team environment.
`
`
`
`Qualifications & Skills
`
``
`- Graduate of an accredited nursing program; BSN preferred.
`
`- Current Basic Life Support certification and applicable departmental certifications.
`
`- Valid nursing license for the practice location or eligibility to obtain one.
`
`- At least 1 year of labor & delivery RN experience.
`
`
`
`About the role
`
`The role involves providing specialized care in a leading hospital known for trauma, stroke, and neonatal services, with a focus on professional development and teamwork in a diverse, award-winning environment.
`
Check rules again: "use for prose" - yes. "Use
- for any list of duties/requirements/benefits" - yes. "Do NOT repeat the job title as a heading" - I have no heading for job title. Good. "Do NOT put Job ID / requisition numbers as headings" - none. "include a section ONLY when the posting has real, specific content for it" - all three have content. "never emit a heading followed by filler/placeholder text" - no fillers. "never create Pay/Schedule/Benefits sections unless the posting actually states them" - I won't. "Output ONLY the HTML fragment — no /, no markdown code fences." - I'll output just the HTML, no fences.
One thing: The input says "Qualifications & Skills" as a combined heading. I'll keep it as `
Qualifications & Skills
`. That's fine.
Also, note that the first line "Role: Registered nurse providing high-level clinical care to patients, utilizing the nursing process for assessment, planning, implementation, and evaluation." - This seems like a description. I could incorporate it into "About the role" or just ignore since rules say don't repeat job title. But it's substantive content about the role. I'll include it in the "About the role" paragraph or before it. Actually, the first line might be considered the job summary. I'll add it to the `` under "About the role", or make a separate `
` before the heading? Rules say use `
` for section headings, and "About the role" is an example. I'll structure the additional info paragraph to include that sentence. Let's see: "The role involves providing specialized care in a leading hospital known for trauma, stroke, and neonatal services, with a focus on professional development and teamwork in a diverse, award-winning environment." The first sentence "Registered nurse providing high-level clinical care to patients, utilizing the nursing process for assessment, planning, implementation, and evaluation." could be part of it. I'll combine or put it in the paragraph. To be safe, I'll make the `
` include both, or start with that description. Actually, I'll just put the additional info as is, and maybe add the first line as part of the paragraph. But the rules say "Preserve ALL substantive information". So I should include that first line. I'll make the paragraph: "The role involves providing specialized care in a leading hospital known
` for "Registered nurse" or similar.
- The input has: Responsibilities, Qualifications & Skills, Additional Information. I could map these to "Responsibilities", "Qualifications", maybe "About the role" or keep "Additional Information" but need to see if it fits a heading. The rules list examples but I can use relevant ones. I'll use: Responsibilities, Qualifications, and maybe a section for the additional info, but need to check if it's substantive enough. It describes the hospital, trauma/stroke/neonatal services, professional development, teamwork, diverse award-winning environment. That's substantive.
- I should NOT create Pay/Schedule/Benefits sections since they're not in the posting.
- I need to use `- ` for lists of duties/requirements/benefits. The responsibilities and qualifications are lists.
- Use `
` for prose. The "Additional Information" prose part can be a `
`, or I could integrate it.
- Remove any boilerplate - none present in snippet.
- Preserve ALL substantive information; do NOT invent or summarize away detail.
Let's structure:
- `
Responsibilities
` followed by `- ...` list items.
- `
Qualifications
` followed by `- ...` list items. Note: input says "Qualifications & Skills", I'll split or combine as appropriate. Rules say I can use "Qualifications, Skills" as headings. I'll probably do `
Qualifications
` and include skills within, or `Qualifications & Skills
`. To be safe, I'll use `Qualifications & Skills
` since that's exactly in the input and it's substantive.
- `About the role
` or similar for the Additional Information. The rules list "About the role" as an example heading. The additional info describes the hospital, services, environment. I'll use `About the role
` and put the prose there, or maybe `` after. But rules say "include a section ONLY when the posting has real, specific content for it". This section has content. I could also just use a `
` after the qualifications, but the rule says use `
` for section headings, and "About the role" is an example. I'll use `About the role
` and then `
...
` with the text.
Wait, let's re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This means I should use those heading names if those sections exist. It doesn't force me to use all, but I can map the input sections to these. The input has "Responsibilities", "Qualifications & Skills", "Additional Information". I'll map:
- Responsibilities -> `Responsibilities
`
- Qualifications & Skills -> `Qualifications & Skills
` (matches example)
- Additional Information -> could be `About the role
` or just keep as is. I'll use `About the role
` since it's in the example list and fits.
- For lists: `- ` for each item.
- For prose in Additional Information: `
...
`.
- Check if any list items should be combined or kept as is. I'll keep each bullet as a separate ` - `.
- "Do NOT repeat the job title as a heading" - I won't add an `
` for "Registered nurse".
- "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - None present, fine.
- "Preserve ALL substantive information; do NOT invent or summarize away detail." - I'll include every line from the input.
- "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - None in snippet.
- "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them." - I won't create Pay/Schedule/Benefits. I will only have sections with real content.
- "Prefer a few substantive sections over many thin ones." - I'll have three sections: Responsibilities, Qualifications & Skills, About the role. That's fine.
Now, construct HTML fragment:
`
Responsibilities
`
``
`- Deliver direct and indirect patient care in accordance with unit standards.
`
`- Supervise and collaborate with team members and multidisciplinary teams to ensure age-appropriate care.
`
`- Communicate clearly, build collaborative relationships, and promote a positive patient experience.
`
`- Take accountability for performance, seek professional growth, and contribute to a team environment.
`
`
`
`Qualifications & Skills
`
``
`- Graduate of an accredited nursing program; BSN preferred.
`
`- Current Basic Life Support certification and applicable departmental certifications.
`
`- Valid nursing license for the practice location or eligibility to obtain one.
`
`- At least 1 year of labor & delivery RN experience.
`
`
`
`About the role
`
`The role involves providing specialized care in a leading hospital known for trauma, stroke, and neonatal services, with a focus on professional development and teamwork in a diverse, award-winning environment.
`
Check rules again: "use for prose" - yes. "Use
- for any list of duties/requirements/benefits" - yes. "Do NOT repeat the job title as a heading" - I have no heading for job title. Good. "Do NOT put Job ID / requisition numbers as headings" - none. "include a section ONLY when the posting has real, specific content for it" - all three have content. "never emit a heading followed by filler/placeholder text" - no fillers. "never create Pay/Schedule/Benefits sections unless the posting actually states them" - I won't. "Output ONLY the HTML fragment — no /, no markdown code fences." - I'll output just the HTML, no fences.
One thing: The input says "Qualifications & Skills" as a combined heading. I'll keep it as `
Qualifications & Skills
`. That's fine.
Also, note that the first line "Role: Registered nurse providing high-level clinical care to patients, utilizing the nursing process for assessment, planning, implementation, and evaluation." - This seems like a description. I could incorporate it into "About the role" or just ignore since rules say don't repeat job title. But it's substantive content about the role. I'll include it in the "About the role" paragraph or before it. Actually, the first line might be considered the job summary. I'll add it to the `` under "About the role", or make a separate `
` before the heading? Rules say use `
` for section headings, and "About the role" is an example. I'll structure the additional info paragraph to include that sentence. Let's see: "The role involves providing specialized care in a leading hospital known for trauma, stroke, and neonatal services, with a focus on professional development and teamwork in a diverse, award-winning environment." The first sentence "Registered nurse providing high-level clinical care to patients, utilizing the nursing process for assessment, planning, implementation, and evaluation." could be part of it. I'll combine or put it in the paragraph. To be safe, I'll make the `
` include both, or start with that description. Actually, I'll just put the additional info as is, and maybe add the first line as part of the paragraph. But the rules say "Preserve ALL substantive information". So I should include that first line. I'll make the paragraph: "The role involves providing specialized care in a leading hospital known
` for prose. The "Additional Information" prose part can be a `
`, or I could integrate it. - Remove any boilerplate - none present in snippet. - Preserve ALL substantive information; do NOT invent or summarize away detail. Let's structure: - `
Responsibilities
` followed by `- ...` list items.
- `
Qualifications
` followed by `- ...` list items. Note: input says "Qualifications & Skills", I'll split or combine as appropriate. Rules say I can use "Qualifications, Skills" as headings. I'll probably do `
Qualifications
` and include skills within, or `Qualifications & Skills
`. To be safe, I'll use `Qualifications & Skills
` since that's exactly in the input and it's substantive. - `About the role
` or similar for the Additional Information. The rules list "About the role" as an example heading. The additional info describes the hospital, services, environment. I'll use `About the role
` and put the prose there, or maybe `` after. But rules say "include a section ONLY when the posting has real, specific content for it". This section has content. I could also just use a `
` after the qualifications, but the rule says use `
` for section headings, and "About the role" is an example. I'll use `
About the role
` and then `...
` with the text. Wait, let's re-read carefully: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This means I should use those heading names if those sections exist. It doesn't force me to use all, but I can map the input sections to these. The input has "Responsibilities", "Qualifications & Skills", "Additional Information". I'll map: - Responsibilities -> `
Responsibilities
` - Qualifications & Skills -> `Qualifications & Skills
` (matches example) - Additional Information -> could be `About the role
` or just keep as is. I'll use `About the role
` since it's in the example list and fits. - For lists: `- ` for each item.
- For prose in Additional Information: `
...
`. - Check if any list items should be combined or kept as is. I'll keep each bullet as a separate ` - `.
- "Do NOT repeat the job title as a heading" - I won't add an `
` for "Registered nurse". - "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - None present, fine. - "Preserve ALL substantive information; do NOT invent or summarize away detail." - I'll include every line from the input. - "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." - None in snippet. - "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them." - I won't create Pay/Schedule/Benefits. I will only have sections with real content. - "Prefer a few substantive sections over many thin ones." - I'll have three sections: Responsibilities, Qualifications & Skills, About the role. That's fine. Now, construct HTML fragment: `
Responsibilities
` `- `
`
- Deliver direct and indirect patient care in accordance with unit standards. ` `
- Supervise and collaborate with team members and multidisciplinary teams to ensure age-appropriate care. ` `
- Communicate clearly, build collaborative relationships, and promote a positive patient experience. ` `
- Take accountability for performance, seek professional growth, and contribute to a team environment. ` `
Qualifications & Skills
` `- `
`
- Graduate of an accredited nursing program; BSN preferred. ` `
- Current Basic Life Support certification and applicable departmental certifications. ` `
- Valid nursing license for the practice location or eligibility to obtain one. ` `
- At least 1 year of labor & delivery RN experience. ` `
About the role
` `The role involves providing specialized care in a leading hospital known for trauma, stroke, and neonatal services, with a focus on professional development and teamwork in a diverse, award-winning environment.
` Check rules again: "usefor prose" - yes. "Use
- for any list of duties/requirements/benefits" - yes. "Do NOT repeat the job title as a heading" - I have no heading for job title. Good. "Do NOT put Job ID / requisition numbers as headings" - none. "include a section ONLY when the posting has real, specific content for it" - all three have content. "never emit a heading followed by filler/placeholder text" - no fillers. "never create Pay/Schedule/Benefits sections unless the posting actually states them" - I won't. "Output ONLY the HTML fragment — no /, no markdown code fences." - I'll output just the HTML, no fences.
One thing: The input says "Qualifications & Skills" as a combined heading. I'll keep it as `
Qualifications & Skills
`. That's fine. Also, note that the first line "Role: Registered nurse providing high-level clinical care to patients, utilizing the nursing process for assessment, planning, implementation, and evaluation." - This seems like a description. I could incorporate it into "About the role" or just ignore since rules say don't repeat job title. But it's substantive content about the role. I'll include it in the "About the role" paragraph or before it. Actually, the first line might be considered the job summary. I'll add it to the `` under "About the role", or make a separate `
` before the heading? Rules say use `
` for section headings, and "About the role" is an example. I'll structure the additional info paragraph to include that sentence. Let's see: "The role involves providing specialized care in a leading hospital known for trauma, stroke, and neonatal services, with a focus on professional development and teamwork in a diverse, award-winning environment." The first sentence "Registered nurse providing high-level clinical care to patients, utilizing the nursing process for assessment, planning, implementation, and evaluation." could be part of it. I'll combine or put it in the paragraph. To be safe, I'll make the `
` include both, or start with that description. Actually, I'll just put the additional info as is, and maybe add the first line as part of the paragraph. But the rules say "Preserve ALL substantive information". So I should include that first line. I'll make the paragraph: "The role involves providing specialized care in a leading hospital known
- ` for each item.
- For prose in Additional Information: `
- ...` list items. Note: input says "Qualifications & Skills", I'll split or combine as appropriate. Rules say I can use "Qualifications, Skills" as headings. I'll probably do `