Travel PCU / Stepdown RN - $2,034 per week

We need to output HTML fragment with sections: Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. Avoid filler like "commensurate with experience". We must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to parse the job posting. Key details: - Job: travel nurse RN PCU - Progressive Care Unit in Randallstown, Maryland. - Specialty: PCU - Progressive Care Unit - Discipline: RN - Start Date: 10/12/2026 - Duration: 14 weeks (but later says 13-week contract position) - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Location: Randallstown, Maryland - Assignment Duration: This is a 13-week contract position. - Schedule: Night shift, 3x12-hour shifts (19:00 - 07:30) - Job Description: seeking experienced RN for PCU/Stepdown unit. Requires strong clinical skills, EKG interpretation, management of cardiac drips. Provide high-quality nursing care to adult and geriatric patients. - Responsibilities: - Monitor and assess patient conditions, vital signs, and EKG rhythms. - Administer medications, including non-titratable drips for cardiac patients. - Provide care for patients requiring peritoneal dialysis and manage chest tubes. - Respond to emergencies as a member of the Code Team. - Coordinate with interdisciplinary teams for comprehensive patient care. - Document patient care and assessments using Cerner iVIEW. - Required Experience / Certifications / Licensure: - Minimum of 2 years of experience in PCU/Stepdown or Med-Surg/Telemetry. - Must possess active Maryland RN license or compact RN license. - Certifications required: ACLS, BLS, advanced EKG assessment, and 4-hour annual stroke CEUs. - Strong EKG experience required; experience managing non-titratable cardiac drips essential. - CVA experience and chest tube management is necessary. - Why ARMStaffing? Benefits: - 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 mentions SIA rankings, Top Workplace, etc. Those are marketing but could be considered part of "Why ARMStaffing?" but maybe not needed as they are not benefits. However they are substantive info about company. Could be included under "About ARMStaffing" but we only have headings list; we could use "About the role" for role description, "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". The posting includes Pay: "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; we should not create Pay section if it's not specific (tax-free stipend amount to be determined). The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Pay package based on 12 hour shifts and 36 hours per week with tax-free stipend amount to be determined. That's still somewhat vague but it's stating something about pay. However "tax-free stipend amount to be determined" is not specific. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "tax-free stipend amount to be determined" is placeholder/TBD. So we should not include Pay section. Schedule: they give shift details: Night shift, 3x12-hour shifts (19:00 - 07:30). That's specific. So we can include Schedule section. Benefits: they list health benefits, onboarding, clinical support, 401k, recruiter matching, extras (travel reimbursement, housing allowance, meals, referral bonuses). Those are specific enough. So include Benefits. We also have "About ARMStaffing" description at end; could be considered "About the role"? Actually "About the role" is for role description. We have a Job Description paragraph. We could put that under "About the role". Or we could put under "About the role" a short prose describing the role. The posting includes "Job Description We are seeking an experienced Registered Nurse..." That's substantive. So we can put that under

About the role

with a

. Responsibilities: list as

• . Requirements: could be split into Required Experience / Certifications / Licensure. Could be under "Requirements" or "Qualifications". The instruction says use headings like Requirements, Qualifications, Skills. We need to decide which to use. We have experience, licensure, certifications. That's more like Requirements/Qualifications. We could put under

  Requirements

  the experience and license, and under

  Qualifications

  the certifications and specific skills (EKG, cardiac drips, CVA, chest tube). Or we could combine. But better to follow typical: Requirements = experience + license; Qualifications = certifications + specific skills. Skills could be EKG interpretation, cardiac drips management, peritoneal dialysis, chest tube management, Code Team, Cerner iVIEW. However those are also responsibilities. Might be overlapping. We need to avoid duplication. Let's think: The posting includes "Required Experience / Certifications / Licensure". Then bullet list of items: Minimum of 2 years experience..., Must possess active Maryland RN license..., Certifications required: ACLS, BLS, advanced EKG assessment, and 4-hour annual stroke CEUs., Strong EKG experience required; experience managing non-titratable cardiac drips essential., CVA experience and chest tube management is necessary. We could treat that as a single section "Requirements" containing all. Or we could split: "Requirements" for experience and license; "Qualifications" for certifications and specific skills; "Skills" maybe not needed. But we must not create thin sections. Let's see if we have enough content for each. - About the role: we have job description paragraph. - Responsibilities: we have list of 6 items. - Requirements: we have experience (2 years) and license (MD RN or compact). - Qualifications: we have certifications (ACLS, BLS, advanced EKG assessment, 4-hour annual stroke CEUs) plus specific skills (strong EKG experience, managing non-titratable cardiac drips, CVA experience, chest tube management). - Skills: maybe we could list EKG interpretation, cardiac drips management, peritoneal dialysis, chest tube management, Code Team response, interdisciplinary coordination, Cerner iVIEW documentation. But those overlap with responsibilities. Better to not duplicate. - Benefits: we have list. - Schedule: we have shift details. Thus we can output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. We must not include Pay because it's placeholder. We must not include repeated lines like "Job ID", "Posted job title", etc. Remove those. We must not include boilerplate like "We're not the only ones who think ARMStaffing should be your first choice..." etc. That's marketing but maybe could be considered part of Benefits? It's not a benefit; it's company accolades. Could be omitted as not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The accolades are not boilerplate but could be considered fluff. However they are substantive info about company. But we have no heading for "About the company". Not in allowed headings. Could we put under "About the role"? No. Could we put under "Benefits"? Not really. Could we omit them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info if it's substantive. But we don't have a heading for it. However we could incorporate it into a paragraph under "About the role" or maybe under a generic

  without heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It doesn't say we cannot have other headings, but we should follow the pattern. Probably we should only use those headings. If we have info that doesn't fit, we could incorporate into existing sections as prose. The accolades: "SIA’s Top-50 Fastest Growing Healthcare Staffing Firms – 2019 SIA’s Largest Healthcare Staffing Agencies in the U.S. – 2023 Top Workplace in the Lehigh Valley – 2022, 2023 Perfect scores for 'Name, Not a Number' and 'Recruiters' Personalities' on Highway Hypodermics We've earned The Joint Commission’s Gold Seal of Approval for healthcare staffing 15 years strong and counting!" This is about the company, not the role. Could be placed under a paragraph after Benefits maybe as a general statement about ARMStaffing. But we have no heading for "About the company". Could we add a

  after Benefits without heading? The instruction says output ONLY the HTML fragment; we can include

  elements anywhere. It didn't say we must wrap everything in headings. So we can add a

  after Benefits with that info. That would preserve substantive info. Similarly, there is a description of ARMStaffing at the end: "About ARMStaffingAllied Resources Medical Staffing (ARMStaffing) places the most qualified medical professionals..." That's also company description. Could be added as another

  . We must avoid duplication: there is also "Why ARMStaffing?" section with benefits list; we already captured benefits. The "Why ARMStaffing?" also includes the accolades and the company description? Actually after benefits list, there is "We're not the only ones who think ARMStaffing should be your first choice. Here’s why: SIA’s Top-50..." then later "About ARMStaffingAllied Resources Medical Staffing (ARMStaffing) places..." So we can capture those as prose. We must also remove duplicated lines: there is "Contract & local rates may vary based on location and applicant residency. Ask your ARMStaffing recruiter for details!" That's vague; could be omitted as not substantive? It's about pay variation; but it's not specific. Might be considered filler. We'll omit. Also "Posted job title: RN:PCU,19:00:00-07:00:00" - remove. Now let's craft HTML. We'll start with

  About the role

  then

  with job description paragraph: "We are seeking an experienced Registered Nurse to join our team in the PCU/Stepdown unit. This role requires strong clinical skills, particularly in EKG interpretation and the management of cardiac drips. The RN will be responsible for providing high-quality nursing care to adult and geriatric patients with varied conditions." Then

  Responsibilities

  then
  • items. Then

    Requirements

    then

    maybe combine experience and license as a list? Could be <