Travel LDRP RN - $3,004 per week
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to parse the job posting.
Key info:
- Cure Healthcare Staffing seeking travel nurse RN Labor and Delivery for travel nursing job in Dickinson, North Dakota.
- Specialty: Labor and Delivery
- Discipline: RN
- Start Date: 10/12/2026
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, rotating
- Employment Type: Travel
- Current North Dakota license and AHA BLS and ACLS required and additional certifications related to this specialty.
- To qualify: primary residence must be located at least 50 miles from facility address.
- This shift is 3x12 Rotating.
- Required: 2 years of recent experience in Labor & Delivery L&D.
- Please inquire for specific job details and confirm shift required by facility.
- Cure Healthcare Staffing Job ID #38290204.
- 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.
- Posted job title: RN:Labor & Delivery L&D,07:00:00-19:00:00 (maybe shift times)
- About Cure Healthcare Staffing: phone number, website, description.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to include sections only if real content.
We have:
- About the role: maybe description of role: travel nurse RN Labor and Delivery in Dickinson, ND. Could be a paragraph.
- Responsibilities: Not explicitly listed. The posting doesn't list duties. So we should not create Responsibilities section.
- Requirements: includes license, certifications, residence distance, experience. So we can have Requirements section.
- Qualifications: maybe overlapping with Requirements. Could combine? But we need separate sections only if content. Could put license etc under Requirements, and experience under Qualifications? But better to have one Requirements section covering all.
- Skills: Not listed.
- Benefits: Not listed explicitly (maybe tax-free stipend amount to be determined). That's vague; we should not create Benefits unless specific. The posting mentions tax-free stipend amount to be determined – not specific. So we should not create Benefits.
- Pay: The posting says "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." That's vague; not specific amount. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on shifts and hours, but not actual pay rate. Is that enough? It says "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." That's still vague; no actual numbers. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "subject to confirmation" and "amount to be determined". That's placeholder. So we should not create Pay section.
- Schedule: The posting says shift: 12 hours, rotating; 36 hours per week; 3x12 Rotating; shift times 07:00:00-19:00:00. That's specific schedule info. So we can create Schedule section with details.
Thus sections: About the role (maybe a paragraph), Requirements, Schedule.
We could also include Qualifications if we separate experience and certifications. But we can combine into Requirements.
We need to use for each section heading.
We need to use - for any list of duties/requirements/benefits. So for Requirements we should list items as
- .
For Schedule we could list details as
- or
. Since it's a list of schedule items, we can use
.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract details:
About the role: "Cure Healthcare Staffing is seeking a travel nurse RN Labor and Delivery for a travel nursing job in Dickinson, North Dakota." Also maybe mention "Cure Healthcare Staffing Job ID #38290204." but that's metadata; we could fold minor metadata into short or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include Job ID in a short paragraph maybe under About the role or separate? Probably better to include in About the role paragraph as minor metadata.
Also "Posted job title: RN:Labor & Delivery L&D,07:00:00-19:00:00" maybe redundant.
We also have About Cure Healthcare Staffing description: phone number, website, description. That's about the company, not the role. Should we include? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not boilerplate; it's substantive about the agency. Could be included maybe under a section like "About the agency"? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we should not create a heading for that. Could we fold that info into About the role? Probably not appropriate. The instruction says to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid including extra info outside those headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. Any other content should be placed under those headings or as
without heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray
outside headings. But likely they expect sections only. However we could include a
for the agency description under maybe "About the role"? That seems odd.
Better to follow the instruction: Use those headings for sections. If we have content that doesn't fit, we could still include as
without heading? The instruction didn't forbid that, but they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the possible headings. It didn't say you cannot have other headings, but to follow the pattern, we should stick to those.
Thus we need to fit all substantive info into those sections.
What about the agency description? Could be considered part of "About the role"? Not really. But maybe we can include it as a brief
under About the role as context. Or we could drop it as minor metadata? The instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." That refers to Job ID etc. The agency description is not minor metadata; it's more substantive. However, we have no heading for it. Perhaps we can include it as a
before any headings, as general info. The instruction didn't forbid stray paragraphs. It said "Output ONLY the HTML fragment — no /, no markdown code fences." So we can have a
then headings.
Thus we can output:
With 20+ years of healthcare staffing experience, Cure Healthcare Staffing helps nurses and allied health professionals rediscover their love of patient care while providing healthcare facilities with flexible staffing solutions. Cure is Joint Commission accredited and only accepts staff meeting Joint Commission quality criteria.
Then sections.
Now About the role: we can describe the position: travel nurse RN Labor and Delivery in Dickinson, ND; start date 10/12/2026; duration 13 weeks; employment type travel; shift details maybe go to Schedule.
We need to avoid duplication.
Let's list all specifics:
- Position: Travel Nurse RN Labor and Delivery (L&D)
- Location: Dickinson, North Dakota
- Start Date: 10/12/2026
- Duration: 13 weeks
- Hours per week: 36 hours
- Shift: 12 hours, rotating (3x12 Rotating); shift times 07:00:00-19:00:00
- Employment Type: Travel
- Requirements:
- Current North Dakota RN license
- AHA BLS and ACLS certification
- Additional certifications related to L&D specialty (unspecified)
- Primary residence at least 50 miles from facility address
- 2 years recent experience in Labor & Delivery L&D
- Pay: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. (We'll not include Pay section due to placeholder.)
- Schedule: as above.
We also have "Please inquire for specific job details and confirm shift required by facility." That's application instruction; we should remove.
Now craft sections.
About the role: maybe a paragraph summarizing the role: "Cure Healthcare Staffing is seeking a travel nurse RN specializing in Labor and Delivery for a 13‑week assignment in Dickinson, North Dakota, starting October 12, 2026. The position entails 36 hours per week on 12‑hour rotating shifts."
We can include start date, duration, location.
Requirements: list as - .
Schedule: list as
- with shift pattern, hours per week, shift times.
We need to ensure we don't include placeholder text like "subject to confirmation" or "amount to be determined". Since we are not making Pay section, fine.
Now produce HTML.
We'll start with a
for agency description.
Then
About the role
...
Then Requirements
...
Then Schedule
...
Make sure no extra whitespace issues.
Let's write.
Agency description paragraph: "With over 20 years of healthcare staffing experience, Cure Healthcare Staffing helps nurses and allied health professionals rediscover their love of patient care while providing facilities with flexible staffing solutions. The agency is Joint Commission accredited and only accepts staff that meet its quality criteria."
Now About the role paragraph: "Cure Healthcare Staffing is seeking a travel nurse RN specializing in Labor and Delivery for a 13‑week assignment in Dickinson, North Dakota, beginning October 12, 2026. The role involves 36 hours per week on 12‑hour rotating shifts."
We could also mention employment type travel.
Now Requirements list:
- Current North Dakota RN license
- AHA BLS and ACLS certification
- Additional certifications related to Labor & Delivery specialty (as required)
- Primary residence must be at least 50 miles from the facility
- Minimum 2 years of recent experience in Labor & Delivery L&D
Now Schedule list:
- 36 hours per week
- 12‑hour shifts, rotating pattern (3×12)
- Typical shift hours: 07:00 – 19:00
- Shift type: rotating (day/night as per facility)
We need to be careful not to add placeholder.
Now output.
Check for any duplicated lines: we have not included Job
- for any list of duties/requirements/benefits. So for Requirements we should list items as
- .
For Schedule we could list details as
- or
. Since it's a list of schedule items, we can use
- .
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract details:
About the role: "Cure Healthcare Staffing is seeking a travel nurse RN Labor and Delivery for a travel nursing job in Dickinson, North Dakota." Also maybe mention "Cure Healthcare Staffing Job ID #38290204." but that's metadata; we could fold minor metadata into short
- .
Schedule: list as
- with shift pattern, hours per week, shift times.
We need to ensure we don't include placeholder text like "subject to confirmation" or "amount to be determined". Since we are not making Pay section, fine.
Now produce HTML.
We'll start with a
for agency description. Then
About the role
...
ThenRequirements
- ...
Schedule
- ...
- with shift pattern, hours per week, shift times.
We need to ensure we don't include placeholder text like "subject to confirmation" or "amount to be determined". Since we are not making Pay section, fine.
Now produce HTML.
We'll start with a
or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include Job ID in a short paragraph maybe under About the role or separate? Probably better to include in About the role paragraph as minor metadata. Also "Posted job title: RN:Labor & Delivery L&D,07:00:00-19:00:00" maybe redundant. We also have About Cure Healthcare Staffing description: phone number, website, description. That's about the company, not the role. Should we include? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not boilerplate; it's substantive about the agency. Could be included maybe under a section like "About the agency"? But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we should not create a heading for that. Could we fold that info into About the role? Probably not appropriate. The instruction says to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid including extra info outside those headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. Any other content should be placed under those headings or as
without heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we cannot have stray
outside headings. But likely they expect sections only. However we could include a
for the agency description under maybe "About the role"? That seems odd. Better to follow the instruction: Use those headings for sections. If we have content that doesn't fit, we could still include as
without heading? The instruction didn't forbid that, but they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the possible headings. It didn't say you cannot have other headings, but to follow the pattern, we should stick to those. Thus we need to fit all substantive info into those sections. What about the agency description? Could be considered part of "About the role"? Not really. But maybe we can include it as a brief
under About the role as context. Or we could drop it as minor metadata? The instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." That refers to Job ID etc. The agency description is not minor metadata; it's more substantive. However, we have no heading for it. Perhaps we can include it as a
before any headings, as general info. The instruction didn't forbid stray paragraphs. It said "Output ONLY the HTML fragment — no /, no markdown code fences." So we can have a
then headings. Thus we can output:
With 20+ years of healthcare staffing experience, Cure Healthcare Staffing helps nurses and allied health professionals rediscover their love of patient care while providing healthcare facilities with flexible staffing solutions. Cure is Joint Commission accredited and only accepts staff meeting Joint Commission quality criteria.
Then sections. Now About the role: we can describe the position: travel nurse RN Labor and Delivery in Dickinson, ND; start date 10/12/2026; duration 13 weeks; employment type travel; shift details maybe go to Schedule. We need to avoid duplication. Let's list all specifics: - Position: Travel Nurse RN Labor and Delivery (L&D) - Location: Dickinson, North Dakota - Start Date: 10/12/2026 - Duration: 13 weeks - Hours per week: 36 hours - Shift: 12 hours, rotating (3x12 Rotating); shift times 07:00:00-19:00:00 - Employment Type: Travel - Requirements: - Current North Dakota RN license - AHA BLS and ACLS certification - Additional certifications related to L&D specialty (unspecified) - Primary residence at least 50 miles from facility address - 2 years recent experience in Labor & Delivery L&D - Pay: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. (We'll not include Pay section due to placeholder.) - Schedule: as above. We also have "Please inquire for specific job details and confirm shift required by facility." That's application instruction; we should remove. Now craft sections. About the role: maybe a paragraph summarizing the role: "Cure Healthcare Staffing is seeking a travel nurse RN specializing in Labor and Delivery for a 13‑week assignment in Dickinson, North Dakota, starting October 12, 2026. The position entails 36 hours per week on 12‑hour rotating shifts." We can include start date, duration, location. Requirements: list as - .
Schedule: list as
- or
- .
For Schedule we could list details as