Travel Step Down RN - $2,442 per week
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate.
We need to parse the posting.
Key info:
- Job: travel nurse RN Stepdown in Cleveland, Ohio.
- Specialty: Stepdown
- Discipline: RN
- Start Date: 10/23/2026
- Duration: 18 weeks (but later says 13-week contract position? There's conflict: earlier says Duration: 18 weeks, then Assignment Duration says 13-week contract position. We must preserve all substantive info; we can include both statements. Might need to note both. We'll keep both as sentences.
- 36 hours per week
- Shift: 12 hours, rotating
- Employment Type: Travel
- Location: Cleveland, OH
- Assignment Duration: This is a 13-week contract position.
- Schedule: Day 3x12-Hour (07:00 - 19:30) and Night 3x12-Hour (19:00 - 07:30). Rotating shifts with variable scheduling as needed.
- Job Description: Provide care for diverse patient population, may float to different units if required, including J1-2, J33, and the Emergency Department. Role necessitates strong assessment and critical thinking skills, focus on high-quality patient care.
- Responsibilities list bullet points:
- Provide patient-centered care in a progressive care setting
- Monitor and assess patient vitals and health status
- Administer medications and treatments as prescribed
- Collaborate with interdisciplinary teams to enhance patient care outcomes
- Maintain accurate documentation of patient records
- Facilitate patient education and support discharge planning
- Required Experience / Certifications / Licensure:
- 12 months of permanent experience in the specialty applied for is required
- Active Ohio RN license or compact state license
- Current BLS, ACLS, and NIHSS certifications
- PCU/Progressive care experience preferred, but not required
- Why ARMStaffing? Benefits list:
- Health Benefits: Medical, Dental, Vision, Life, and more
- Onboarding Made Easy: We handle physicals, titers, and more so you can focus on care
- Clinical Support: In-house clinical team available to assist and advocate
- 401k Retirement Plan: Eligible after waiting period; 4% match with 5% contribution
- Recruiter Matching: Get paired with a recruiter based on your location and specialty
- Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more
- Also some accolades (SIA top-50 etc.) but those are maybe not benefits; could be considered "About ARMStaffing" but we have no heading for that. Could include under "About the role"? Not exactly. Might be considered boilerplate? It's promotional but still substantive. However guidelines: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those; it's company info. Could be included under a section like "About ARMStaffing" but we don't have that heading. The allowed headings are limited to those list. We could put under "About the role" maybe? But that is supposed to be about the role, not company. However we could create a section "About the role" with description of role and maybe include company benefits? The instructions: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings. We should include sections only when posting has real, specific content for it.
Thus we need to decide which sections to include:
- About the role: we have a job description paragraph. Could put that there.
- Responsibilities: we have bullet list.
- Requirements: we have required experience/certifications/licensure.
- Qualifications: maybe same as Requirements? Could combine? But we need to avoid thin sections. Could merge Requirements and Qualifications into one? But we have separate headings allowed. We could put Requirements for experience/licensure, and Qualifications for preferred experience (PCU/Progressive care experience preferred). But that's thin. Better to combine into Requirements section and omit Qualifications if not enough distinct content. However we must not invent headings; we can omit Qualifications if not enough specific content. The instruction: "Prefer a few substantive sections over many thin ones." So we can skip Qualifications if it's not substantive.
- Skills: maybe we could list strong assessment and critical thinking skills, but that's already in job description. Could be thin. Might skip.
- Benefits: we have health benefits, onboarding, clinical support, 401k, recruiter matching, extras (travel reimbursement, housing allowance, meals, referral bonuses). Also accolades maybe not benefits. We'll include Benefits section.
- Pay: 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 not specific numbers, but it's still pay info. It says "tax-free stipend amount to be determined." That's vague but still some content. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay package, albeit not specific numbers. So we can include Pay section with that sentence.
- Schedule: we have shift details: 12 hours, rotating; Day 3x12-Hour (07:00 - 19:30) and Night 3x12-Hour (19:00 - 07:30). Rotating shifts with variable scheduling as needed. Also 36 hours per week. So we can include Schedule section.
We also have Start Date and Duration. Could be included in About the role or maybe a separate section? Not in headings list. Could incorporate into About the role paragraph.
We must not include Job ID. Remove boilerplate like "About ARMStaffing" long paragraph; that's not under allowed headings. Could we put that under About the role? It's about company, not role. Might be considered boilerplate? It's promotional but not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. However we have limited headings; we could include a short paragraph about the company under About the role? Might be okay but could be considered irrelevant. Safer to omit that long "About ARMStaffing" paragraph as it's not directly about the role and not covered by headings. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit that paragraph, we lose substantive info about the company. But we could incorporate into Benefits? Not really. Could we create a section "About the role" and include both role description and company overview? The heading is "About the role" not "About the company". Might be stretching but maybe acceptable. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not an exhaustive list? 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 stick to those. If we have info that doesn't fit any, we might need to omit it? But they said preserve ALL substantive information. So we need to fit all substantive info into those sections. So we must embed company info somewhere appropriate, maybe under Benefits? Not ideal. Could we put under "About the role" a description that includes both role and company? The heading is ambiguous but could be interpreted as "About the role/company". I'd risk including company overview under About the role.
Let's craft:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not an exhaustive list? 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 stick to those. If we have info that doesn't fit any, we might need to omit it? But they said preserve ALL substantive information. So we need to fit all substantive info into those sections. So we must embed company info somewhere appropriate, maybe under Benefits? Not ideal. Could we put under "About the role" a description that includes both role and company? The heading is ambiguous but could be interpreted as "About the role/company". I'd risk including company overview under About the role.
Let's craft:
About the role
About the role
ARMStaffing is seeking a travel nurse RN Stepdown for a travel nursing job in Cleveland, Ohio. Specialty: Stepdown. Discipline: RN. Start Date: 10/23/2026. Duration: 18 weeks (also noted as a 13‑week contract position). 36 hours per week. Shift: 12 hours, rotating. Employment Type: Travel. The position is for a Registered Nurse in the Stepdown unit, providing care for a diverse patient population and may float to different units if required, including J1‑2, J33, and the Emergency Department. The role necessitates strong assessment and critical thinking skills, with a focus on providing high‑quality patient care.
Then Responsibilities ul. Then Requirements ul (including experience, license, certifications, preferred PCU experience). Then Benefits ul (health benefits, onboarding, clinical support, 401k, recruiter matching, extras: travel reimbursement, housing allowance, meals, referral bonuses; also accolades maybe? Could include accolades as part of benefits? Not exactly. Could add a sentence about company recognitions inside Benefits? Might be okay.) Then PayPay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax‑free stipend amount to be determined.
Then Schedule- Day shift: 3×12‑hour (07:00‑19:30)
- Night shift: 3×12‑hour (19:00‑07:30)
- Rotating shifts with variable scheduling as needed
- 36 hours per week