Health Unit Coordinator - Providence Valdez
or drop it. But schedule and location are substantive. The rules say: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can include a paragraph with key details like schedule, location, FTE. - There's a paragraph about collaborating with team members, etc. That's "About the role" or "Responsibilities". Could be a section. - "Preferred Qualifications:" with a bullet point: 1 year of Experience (preferably as a HUC) in health care activities or institutional setting. That's a qualifications section. - "Why Join Providence?" with benefits description. That's a Benefits section. - "About Providence" with company description. That's an "About the Company" or "About Providence" section. - Pay range information: "Posted are the minimum and the maximum wage rates... Pay Range: $20.22 - $30.31". That's a Pay section. - There's also a lot of boilerplate: EEO, equal opportunity, scam warning, application instructions, etc. Those should be removed. - The metadata at the bottom: Requsition ID, Company, Job Category, Job Function, Job Schedule, Job Shift, Career Track, Department, Address, Work Location, Workplace Type, Pay Range. Some of this is already in the description. I should fold minor metadata into a short
or drop it. But Pay Range is already mentioned. Job Schedule and Shift are in the description. Location is in description. I can include a short paragraph with key details. The rules: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading... do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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... never create Pay/Schedule/Benefits sections unless the posting actually states them."
The posting does state Pay Range, Benefits, Schedule (part-time, variable shift, 24 hours/week), Location. So I can include Pay, Benefits, Schedule sections if they have substantive content. But Schedule might be just a paragraph. The example headings include Schedule. I could have a "Schedule" section with a paragraph. But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine schedule and location into a "Position Details" paragraph.
Let's outline sections:
1. About the role (or Responsibilities) - the paragraph about collaborating with team members to coordinate department activities and flow of information. That's a responsibility. Could be a section with a paragraph.
2. Qualifications - Preferred Qualifications: 1 year experience preferably as HUC. That's a list (one item). Use
- .
3. Benefits - "Why Join Providence?" and the benefits package description. That's substantive. Use paragraphs and maybe a list? The benefits are described in prose: "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." That's a list of benefits. Could be a
with each benefit as a li. But the text is a sentence. I could break it into a list. However, the rule: "Use - for any list of duties/requirements/benefits". So I should convert that into a list. But the original is a paragraph. I can parse it into a list. That would be preserving substantive information. I'll create a Benefits section with a paragraph intro and a list.
4. Pay - Pay Range: $20.22 - $30.31, with note about additional compensation. That's a Pay section with a paragraph.
5. About Providence - company description. That's a section with paragraphs.
6. Maybe a "Position Details" paragraph for schedule, location, FTE. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule: "Position is part time, 0.6 FTE, variable shift, 24 hours per week. Located onsite at Providence Valdez Medical Center in Valdez, AK!" So I could create a Schedule section with that info. But it's thin. Could be a paragraph under "About the role" or a separate "Schedule & Location" section. The example headings include Schedule. I'll include a Schedule section with a paragraph.
But the user says "Prefer a few substantive sections over many thin ones." So maybe combine schedule and location into a short paragraph at the top, not a separate section. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Schedule is an allowed heading. But only if there's real content. There is real content: part-time, 0.6 FTE, variable shift, 24 hours/week, onsite in Valdez, AK. That's substantive. I'll include a Schedule section.
Also, there's a "Workplace Type: On-site" and "Address". That's location.
I'll structure:
- About the Role
with paragraph about collaborating with team members.
- Responsibilities
maybe? The paragraph says "Collaborates with team members to coordinate department activities and flow of information between teams and other departments." That's a responsibility. Could be a list with one item. But it's a single sentence. I'll keep as a paragraph under About the Role.
- Qualifications
with list of preferred qualifications.
- Schedule & Location
or Schedule
with paragraph.
- Benefits
with paragraph and list.
- Pay
with paragraph.
- About Providence
with paragraphs.
I need to remove boilerplate: EEO, equal opportunity, scam warning, application instructions, HireVue invite, etc. Also remove "Requsition ID: 446470" etc. But the pay range is already in the posting. The metadata at bottom includes Pay Range again. I'll use the pay range from the description.
Now, write HTML fragment.
Let's draft:
About the Role
Collaborates with team members to coordinate department activities and flow of information between teams and other departments.
Qualifications
- 1 year of experience (preferably as a Health Unit Coordinator) in health care activities or institutional setting.
Schedule
Part-time, 0.6 FTE, variable shift, 24 hours per week. On-site at Providence Valdez Medical Center, 911 Meals Ave, Valdez, AK 99686.
Benefits
Providence offers a comprehensive benefits package designed to support you and your family in staying well, growing professionally, and achieving financial security.
- 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
Pay
Base pay range: $20.22 – $30.31 per hour. Additional compensation may be available, such as shift differentials, standby/on-call, overtime, premiums, extra shift incentives, or bonus opportunities. Placement within the range is determined by relevant job experience and other applicable factors.
About Providence
At Providence, our strength lies in Our Promise of “Know me, care for me, ease my way.” Working at our family of organizations means that regardless of your role, we’ll walk alongside you in your career, supporting you so you can support others. We provide best-in-class benefits and foster an inclusive workplace where diversity is valued, and everyone is essential, heard, and respected.
Together, our 120,000 caregivers serve in over 50 hospitals, over 1,000 clinics, and a full range of health and social services across Alaska, California, Montana, New Mexico, Oregon, Texas, and Washington. As a comprehensive health care organization, we are serving more people, advancing best practices, and continuing our more than 100-year tradition of serving the poor and vulnerable.
Providence has a long history of serving Alaska, beginning when the Sisters of Providence first brought health care to Nome in 1902 during the Gold Rush. This pioneering spirit set the standard for modern health care in Alaska and formed the foundation for Providence's growth as the state's largest private employer and leading health care provider. Our award-winning medical centers are located in Anchorage, Eagle River, Kodiak Island, Mat-Su, Seward, and Valdez, with a full spectrum of care including leading-edge diagnostics and treatment, outpatient health centers, physician groups and clinics, outreach programs, and hospice and home care.
That seems good. I should ensure no markdown, just HTML. No or . Just the fragment.
Check for any missing substantive info: The posting mentions "Providence caregivers are not simply valued – they’re invaluable. Join our team at Providence Valdez Medical Center and 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 people, we must empower them." That's part of the "Why Join Providence?" but it's more cultural. Could be included in About Providence or a separate "Culture" section. But the rules say prefer few substantive sections. I'll incorporate that into About Providence or Benefits. I'll add a paragraph in About Providence about culture.
Also, the posting says "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 a disclaimer. Might be considered boilerplate? It's specific to benefits changes. Could be included in Benefits section as a note. But it's not a benefit per se. Might be considered legal boilerplate. The rules say remove legal/EEO/equal-opportunity/scam-warning boilerplate. This is about benefits changes.
for prose. Do NOT repeat the job title as a heading... do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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... never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state Pay Range, Benefits, Schedule (part-time, variable shift, 24 hours/week), Location. So I can include Pay, Benefits, Schedule sections if they have substantive content. But Schedule might be just a paragraph. The example headings include Schedule. I could have a "Schedule" section with a paragraph. But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine schedule and location into a "Position Details" paragraph. Let's outline sections: 1. About the role (or Responsibilities) - the paragraph about collaborating with team members to coordinate department activities and flow of information. That's a responsibility. Could be a section with a paragraph. 2. Qualifications - Preferred Qualifications: 1 year experience preferably as HUC. That's a list (one item). Use
- .
3. Benefits - "Why Join Providence?" and the benefits package description. That's substantive. Use paragraphs and maybe a list? The benefits are described in prose: "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." That's a list of benefits. Could be a
- with each benefit as a li. But the text is a sentence. I could break it into a list. However, the rule: "Use
- for any list of duties/requirements/benefits". So I should convert that into a list. But the original is a paragraph. I can parse it into a list. That would be preserving substantive information. I'll create a Benefits section with a paragraph intro and a list.
4. Pay - Pay Range: $20.22 - $30.31, with note about additional compensation. That's a Pay section with a paragraph.
5. About Providence - company description. That's a section with paragraphs.
6. Maybe a "Position Details" paragraph for schedule, location, FTE. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule: "Position is part time, 0.6 FTE, variable shift, 24 hours per week. Located onsite at Providence Valdez Medical Center in Valdez, AK!" So I could create a Schedule section with that info. But it's thin. Could be a paragraph under "About the role" or a separate "Schedule & Location" section. The example headings include Schedule. I'll include a Schedule section with a paragraph.
But the user says "Prefer a few substantive sections over many thin ones." So maybe combine schedule and location into a short paragraph at the top, not a separate section. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So Schedule is an allowed heading. But only if there's real content. There is real content: part-time, 0.6 FTE, variable shift, 24 hours/week, onsite in Valdez, AK. That's substantive. I'll include a Schedule section. Also, there's a "Workplace Type: On-site" and "Address". That's location. I'll structure: -
About the Role
with paragraph about collaborating with team members. -Responsibilities
maybe? The paragraph says "Collaborates with team members to coordinate department activities and flow of information between teams and other departments." That's a responsibility. Could be a list with one item. But it's a single sentence. I'll keep as a paragraph under About the Role. -Qualifications
with list of preferred qualifications. -Schedule & Location
orSchedule
with paragraph. -Benefits
with paragraph and list. -Pay
with paragraph. -About Providence
with paragraphs. I need to remove boilerplate: EEO, equal opportunity, scam warning, application instructions, HireVue invite, etc. Also remove "Requsition ID: 446470" etc. But the pay range is already in the posting. The metadata at bottom includes Pay Range again. I'll use the pay range from the description. Now, write HTML fragment. Let's draft:About the Role
Collaborates with team members to coordinate department activities and flow of information between teams and other departments.
Qualifications
- 1 year of experience (preferably as a Health Unit Coordinator) in health care activities or institutional setting.
Schedule
Part-time, 0.6 FTE, variable shift, 24 hours per week. On-site at Providence Valdez Medical Center, 911 Meals Ave, Valdez, AK 99686.
Benefits
Providence offers a comprehensive benefits package designed to support you and your family in staying well, growing professionally, and achieving financial security.
- 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
Pay
Base pay range: $20.22 – $30.31 per hour. Additional compensation may be available, such as shift differentials, standby/on-call, overtime, premiums, extra shift incentives, or bonus opportunities. Placement within the range is determined by relevant job experience and other applicable factors.
About Providence
At Providence, our strength lies in Our Promise of “Know me, care for me, ease my way.” Working at our family of organizations means that regardless of your role, we’ll walk alongside you in your career, supporting you so you can support others. We provide best-in-class benefits and foster an inclusive workplace where diversity is valued, and everyone is essential, heard, and respected.
Together, our 120,000 caregivers serve in over 50 hospitals, over 1,000 clinics, and a full range of health and social services across Alaska, California, Montana, New Mexico, Oregon, Texas, and Washington. As a comprehensive health care organization, we are serving more people, advancing best practices, and continuing our more than 100-year tradition of serving the poor and vulnerable.
Providence has a long history of serving Alaska, beginning when the Sisters of Providence first brought health care to Nome in 1902 during the Gold Rush. This pioneering spirit set the standard for modern health care in Alaska and formed the foundation for Providence's growth as the state's largest private employer and leading health care provider. Our award-winning medical centers are located in Anchorage, Eagle River, Kodiak Island, Mat-Su, Seward, and Valdez, with a full spectrum of care including leading-edge diagnostics and treatment, outpatient health centers, physician groups and clinics, outreach programs, and hospice and home care.
That seems good. I should ensure no markdown, just HTML. No or . Just the fragment. Check for any missing substantive info: The posting mentions "Providence caregivers are not simply valued – they’re invaluable. Join our team at Providence Valdez Medical Center and 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 people, we must empower them." That's part of the "Why Join Providence?" but it's more cultural. Could be included in About Providence or a separate "Culture" section. But the rules say prefer few substantive sections. I'll incorporate that into About Providence or Benefits. I'll add a paragraph in About Providence about culture. Also, the posting says "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 a disclaimer. Might be considered boilerplate? It's specific to benefits changes. Could be included in Benefits section as a note. But it's not a benefit per se. Might be considered legal boilerplate. The rules say remove legal/EEO/equal-opportunity/scam-warning boilerplate. This is about benefits changes.
- for any list of duties/requirements/benefits". So I should convert that into a list. But the original is a paragraph. I can parse it into a list. That would be preserving substantive information. I'll create a Benefits section with a paragraph intro and a list.
4. Pay - Pay Range: $20.22 - $30.31, with note about additional compensation. That's a Pay section with a paragraph.
5. About Providence - company description. That's a section with paragraphs.
6. Maybe a "Position Details" paragraph for schedule, location, FTE. But the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule: "Position is part time, 0.6 FTE, variable shift, 24 hours per week. Located onsite at Providence Valdez Medical Center in Valdez, AK!" So I could create a Schedule section with that info. But it's thin. Could be a paragraph under "About the role" or a separate "Schedule & Location" section. The example headings include Schedule. I'll include a Schedule section with a paragraph.
But the user says "Prefer a few substantive sections over many thin ones." So maybe combine schedule and location into a short paragraph at the top, not a separate section. However, the rules say "use