RN Fellow - Critical Care - SCH November 2026 Cohort
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Must not create sections with filler like "commensurate with experience". Must not invent or summarize away detail.
We need to parse the description.
Key content:
- Title: Swedish is seeking applicants for our November 2026 RN Critical Care Fellowship. (We don't repeat title as heading.)
- Description: RN Fellowship provides foundation and support to become expert. Learn through structured curriculum, simulation, authentic patient experiences guided by preceptors. If you have >12 months continuous RN experience, you owe it to yourself to explore.
- Start date: November 2, 2026.
- Providence nurses are invaluable, culture of patient-focused whole-person care, voice matters, etc. Might be about the role? Could be "About the role" or "About Providence". But we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to extract content for each.
Let's identify sections:
About the role: maybe description of fellowship: "An RN Fellowship with Swedish will provide the foundation and support essential to becoming an expert in your new specialty. Learn through a combination of structured curriculum, simulation, and authentic patient experiences guided by preceptors. If you have more than 12 months of continuous RN experience, you owe it to yourself to explore this exceptional opportunity. This position starts November 2, 2026 Providence nurses are not simply valued – they’re invaluable. You will thrive in our culture of patient-focused, whole-person care built on understanding, commitment, and mutual respect. Your voice matters here, because we know that to inspire and retain the best nurses, we must empower them. Learn why nurses choose to work at Providence by visiting our Nursing Institute page."
That seems like about the role and organization.
Responsibilities: Not explicitly listed. The posting may not have explicit responsibilities list. Might be implied: "Learn through a combination of structured curriculum, simulation, and authentic patient experiences guided by preceptors." That could be responsibilities? But we need to avoid filler. If no explicit responsibilities, we might omit Responsibilities section.
Requirements: maybe "Required Qualifications" list: Graduation from an accredited nursing program, Washington Registered Nurse License upon hire, National Provider BLS - American Heart Association upon hire, National Provider ACLS - American Heart Association within 6 months of hire, 1 year - Nursing experience (new to specialty). Also "If you have more than 12 months of continuous RN experience". So we can put Requirements.
Qualifications: Might be same as Required Qualifications? The posting has "Required Qualifications" heading. Could treat that as Qualifications. But we also have "Why Join Providence?" which is about benefits. Also "About Providence" etc.
Skills: Not explicitly listed. Could be implied: critical care nursing skills? Not given. Might omit.
Benefits: "Our best-in-class benefits are uniquely designed to support you and your family in staying well, growing professionally, and achieving financial security. We take care of you, so you can focus on delivering our mission... Accepting a new position at another facility that is part of the Providence family of organizations may change your current benefits. Changes in benefits, including paid time-off, happen for various reasons... Providence offers a comprehensive benefits package including a retirement 401(k) Savings Plan with employer matching, health care benefits (medical, dental, vision), life insurance, disability insurance, time off benefits (paid parental leave, vacations, holidays, health issues), voluntary benefits, well-being resources and much more. Learn more at providence.jobs/benefits."
Also mention about Unincorporated County of Los Angeles Fair Chance Ordinance.
Pay: "Posted are the minimum and the maximum wage rates on the wage range for this position. The successful candidate's placement on the wage range for this position will be determined based upon relevant job experience and other applicable factors. These amounts are the base pay range; additional compensation may be available for this role, such as shift differentials, standby/on-call, overtime, premiums, extra shift incentives, or bonus opportunities." Then later: "Pay Range: $48.85 - $89.91 The amounts listed are the base pay range; additional compensation may be available for this role, such as shift differentials, standby/on-call, overtime, premiums, extra shift incentives, or bonus opportunities."
Schedule: "Job Schedule: Full time Job Shift: Multiple shifts available". Also maybe "Multiple shifts available". So we have schedule info.
Thus we can create sections:
- About the role (maybe combine description about fellowship and culture). Use About the role
then
with paragraphs. - Requirements:
Requirements
then- items.
- Qualifications: Might be same as Required Qualifications? But we already used Requirements for that. Could treat "Required Qualifications" as Qualifications. But we need to avoid duplication. The posting has "Required Qualifications" heading. We could map that to Qualifications section. Then Requirements could be something else? But there is no separate "Requirements". Might be better to treat Required Qualifications as Qualifications, and maybe Requirements as something like "If you have more than 12 months of continuous RN experience". However that is also a requirement. To avoid duplication, we could combine them into Qualifications. But the instruction says to use headings only when posting has real specific content for it. It didn't say we cannot have both Requirements and Qualifications if content exists. We have content for both? The posting lists "Required Qualifications" and also mentions "If you have more than 12 months of continuous RN experience". That could be considered a requirement. But we could put that under Qualifications as well. However we need to decide.
Better to follow the headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to assign content:
- About the role: description of fellowship, start date, culture, voice matters, etc.
- Responsibilities: maybe not explicit; we could omit if no specific content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we don't have explicit responsibilities, we should omit Responsibilities.
- Requirements: maybe the "If you have more than 12 months of continuous RN experience" and maybe "Graduation from an accredited nursing program" etc. But those are qualifications. However we can treat them as Requirements. Then Qualifications could be something else like "Preferred qualifications"? Not present. So we might omit Qualifications if no distinct content. But we have "Required Qualifications" heading; we could map that to Qualifications. Then Requirements could be something like "Must have >12 months continuous RN experience". But that's also a qualification. Might be splitting hairs.
Given the instruction to prefer a few substantive sections over many thin ones, we should avoid creating thin sections. So better to combine similar info into one section, maybe Qualifications, and omit Requirements if it's redundant. But we need to follow the heading list: we can omit sections we don't have content for. So we can have About the role, Qualifications, Benefits, Pay, Schedule. Possibly also Skills if we can infer critical care nursing skills? Not explicit. Better omit.
Thus final sections: About the role, Qualifications, Benefits, Pay, Schedule.
Check if we have content for each:
- About the role: yes.
- Qualifications: list of required qualifications.
- Benefits: description of benefits.
- Pay: pay range and note about additional compensation.
- Schedule: full time, multiple shifts.
We must not include boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. Also remove "Posted are the minimum and the maximum wage rates..." duplicates? We'll keep pay range info.
We must not include Job ID etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting that are substantive, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can reformat. So we need to include all details from the posting that are substantive, like the list of qualifications, benefits details, pay range, schedule, start date, etc. Also the description about fellowship, culture, voice matters, etc. Also the note about Unincorporated County of Los Angeles Fair Chance Ordinance (that's a legal/EEO? It's about hiring practice; might be considered EEO/legal boilerplate? It's a specific statement about fair chance. Might be considered legal/EEO? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That includes EEO statements. The Fair Chance Ordinance might be considered legal/EEO. Safer to remove it. Also remove "Providence is proud to be an Equal Opportunity Employer..." etc. Remove all that.
Also remove "Learn why nurses choose to work at Providence by visiting our Nursing Institute page." That's maybe okay as part of about the role? It's a link; but we can keep as prose? It's not boilerplate; it's a referral. Might keep.
Also remove "Accepting a new position at another facility that is part of the Providence family of organizations may change your current benefits. Changes in benefits, including paid time-off, happen for various reasons..." That's part of benefits description; we can keep.
Also remove "Posted are the minimum and the maximum wage rates on the wage range for this position. The successful candidate's placement on the wage range for this position will be determined based upon relevant job experience and other applicable factors. These amounts are the base pay range; additional compensation may be available for this role, such as shift differentials, standby/on-call, overtime, premiums, extra shift incentives, or bonus opportunities." That's pay info; keep.
Also remove "Learn more at providence.jobs/benefits." Keep as part of benefits.
Also remove "Applicants in the Unincorporated County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Unincorporated Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act." That's legal; remove.
Also remove "Providence is proud to be an Equal Opportunity Employer..." etc. Remove.
Also remove "For any concerns with this posting relating to the posting requirements in RCW 49.58.110(1), please click here where you can access an email link to submit your concern." Remove.
Also remove "Requsition ID: 445643 Company: Swedish Jobs Job Category: Nursing-Patient Facing Job Function: Nursing Job Schedule: Full time Job Shift: Multiple shifts available Career Track: Nursing Department: 3903 SCH CRITICAL CARE Address: WA Seattle 500 17th Ave Work Location: Swedish Cherry Hill 500 17th-Seattle Workplace Type: On-site". Some of that is metadata; we should not put Job ID/requisition numbers as headings; we can fold minor metadata into a short
or drop it. The schedule info we already have; we can keep schedule from that. The address etc maybe minor metadata; we could drop or fold into a short p. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a short paragraph with address and workplace type maybe. But is that substantive? It's location info; might be considered substantive. The posting includes address and work location. That's relevant. We could include a short paragraph under About the role or maybe a separate section? There's no heading for location. We could just include a
with address and workplace type after the About the role paragraph. That's allowed as