Clinical Dietitian
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
- Include section ONLY when real specific content exists
- Never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Output ONLY HTML fragment, no html/body, no markdown fences
Looking at the content:
- "Who We Are" and "Why Join Us" are company description - could be "About the Company" or similar
- "What You'll Be Doing" includes schedule (Full Time, Monday - Friday) and a paragraph about the role
- "Essential Duties And Responsibilities" is a list of duties
- Three levels of requirements: Clinical Dietitian I, II, III Must Haves - these are qualifications/requirements for different levels
- "What We Offer" is benefits
I need to map to standard headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
The posting has:
- Schedule mentioned: "Full Time, Monday - Friday" - so Schedule section is appropriate
- Duties listed - Responsibilities section
- Requirements for three levels - could be Qualifications or Requirements
- Benefits listed - Benefits section
- No explicit Pay section (just "competitive compensation" in benefits) - so no Pay section
- No Skills section separate from requirements
I'll structure:
1. About the Company (combining Who We Are and Why Join Us) - but the rules say use headings like "About the role", "Responsibilities", etc. "About the Company" isn't listed but "About the role" is. However, the company description is not about the role. The rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It says "e.g." so other headings allowed? But prefer those. I think "About the Company" is okay as it's substantive. But maybe "About the Role" for the description of what you'll be doing? Actually "What You'll Be Doing" includes a paragraph about the role and schedule. I'll make "About the Role" for that paragraph, and "Schedule" for the schedule line.
Let me parse:
"What You'll Be Doing
Schedule: Full Time, Monday - Friday
The Clinical Dietitian provides medical nutrition therapy to patients who are recovering from an eating disorder, including educating patients and families on meal plans and nutritional needs."
So I can have:
-
About the Role
with the paragraph
- Schedule
with the schedule info
Then "Essential Duties And Responsibilities" -> Responsibilities
with ul
Then the three levels of requirements. These are qualifications for different levels. Could be Qualifications
with subsections? But rules say use h3 for section headings. Could have one Qualifications section with three sub-lists? But each level has different requirements. I'll create a Qualifications section with three subsections? But only h3 allowed? The rules say "use for section headings". It doesn't forbid multiple h3. I can have three h3: "Clinical Dietitian I Qualifications", "Clinical Dietitian II Qualifications", "Clinical Dietitian III Qualifications". But that might be too many. Alternatively, one Qualifications section with a list that includes the three levels. But the content is distinct. I think separate h3 for each level is okay as they are distinct requirement sets.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe combine into one Qualifications section with three sub-lists using h4? But only h3 allowed for headings. The rules don't forbid h4, but they say "use for section headings". Could use h3 for main sections and h4 for subsections? But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you can't use other heading levels. However, to be safe, I'll use h3 for each major section. I'll have:
- About the Company (or About Us) - combining Who We Are and Why Join Us
- About the Role
- Schedule
- Responsibilities
- Qualifications (with three subsections? But each is a list. I'll make three separate h3: "Clinical Dietitian I Requirements", "Clinical Dietitian II Requirements", "Clinical Dietitian III Requirements")
- Benefits
But that's many sections. However, each has substantive content. The rules say "include a section ONLY when the posting has real, specific content for it". Each level has specific content. So okay.
Alternatively, I could make one "Requirements" section with three lists labeled. But the heading "Requirements" is in the example. I'll do:
Requirements
and then for each level, maybe a ? But the instruction says use h3 for section headings. It doesn't say you can't use h4. But to follow strictly, maybe use h3 for each level. However, the example headings are generic: "Requirements, Qualifications". I think it's better to have one "Qualifications" section and within it, use for each level? But the output is HTML fragment, and they didn't forbid h4. I'll use h3 for main sections and h4 for sub-levels. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies that the top-level sections should be h3. Subsections could be h4. I'll do that.
Let's structure:
About the Company
...combined Who We Are and Why Join Us...
About the Role
The Clinical Dietitian provides medical nutrition therapy...
Schedule
Full Time, Monday - Friday
Responsibilities
- ...
Qualifications
Clinical Dietitian I
- ...
Clinical Dietitian II
- ...
Clinical Dietitian III
- ...
Benefits
- ...
But the rules say "use for section headings". It doesn't say you cannot use h4. I think it's acceptable.
Alternatively, I could make each level a separate h3: "Clinical Dietitian I Qualifications", etc. That would be more consistent with using only h3. But then we have many h3. The rules say "Prefer a few substantive sections over many thin ones." But each level is substantive. However, they are all qualifications. I'll combine under one Qualifications h3 with h4 subsections.
Now, need to remove boilerplate: The text includes "Founded in 2008..." etc. That's part of Who We Are. Keep it. "Why Join Us" is also company culture. Keep.
"What We Offer" is benefits. Keep.
No EEO, legal, etc. present.
Now, write HTML.
Let's extract content:
Who We Are: "At ERC Pathlight, we’re on a mission to change lives—and we’re looking for people who feel called to do the same. As one of the nation’s leading treatment providers for eating disorders and mood, anxiety, and trauma-related conditions, we bring innovative, evidence-based, and deeply compassionate care to patients across the country. With multiple locations nationwide and extensive virtual programming, we meet patients exactly where they are and help them move toward lasting recovery. Founded in 2008 by renowned psychiatrists and psychologists, ERC Pathlight now supports more than 6,000 patients each year. And as the need for world-class mental health care continues to rise, our commitment is stronger than ever: to expand access, elevate the standard of care, and empower every patient to rebuild their life with dignity and hope."
Why Join Us: "When you join ERC Pathlight, you become part of a team that shows up every day to make a real difference. You’ll work alongside passionate clinicians, dedicated support staff, and mission-driven leaders who believe in collaboration, growth, and doing the right thing—always. Here, your work matters. Your ideas matter. You matter. If you’re energized by purpose, motivated by impact, and ready to help transform the future of mental health treatment, you belong here. Come build hope. Come save lives. Come grow with us."
I'll combine into one About the Company section with two paragraphs.
What You'll Be Doing: "The Clinical Dietitian provides medical nutrition therapy to patients who are recovering from an eating disorder, including educating patients and families on meal plans and nutritional needs."
Schedule: "Full Time, Monday - Friday"
Essential Duties And Responsibilities: list of 6 bullet points (the text is a paragraph but separated by line breaks? Actually it's a list: "Provides medical nutrition therapy...", "Provides individualized nutrition counseling...", "Completes documentation...", "Collaborates with interdisciplinary...", "Facilitates experiential groups...". I'll make each a li.
Clinical Dietitian I Must Haves: list of 7 items (Bachelor’s degree, valid US driver license, Current RD/RDN credential, Current state dietitian/nutritionist license, 0-2 years experience). Actually the text: "Bachelor’s degree (Required), Graduate degree (Preferred) A valid US driver license (Required) Current RD/RDN credential with the Commission on Dietetic Registration Certification/Registration required in all states that offer it. National certification, Registered Dietitian (RD) preferred (Required) Current state dietitian/nutritionist license, as required by state law (Required) 0-2 years of experience as a Registered Dietitian (Required)". I'll split into separate li.
Clinical Dietitian II Must Haves: similar but "2 or more years of experience as an RD, with a minimum of 2 years working with eating disorders. National certification, Registered Dietitian (RD) (Required)"
Clinical Dietitian III Must Haves: "5 or more years of experience as an RD working with eating disorders. National certification, Registered Dietitian (RD) (Required) CEDRD, CDE, CSSD, or CNSC (Preferred)" plus the same degree, license, credential requirements.
What We Offer: "At ERC Pathlight, caring for people is our mission and that begins with caring for our own team. Your well-being matters, and our benefit program is designed to support every part of your life. We offer competitive compensation; comprehensive medical, dental, and vision coverage; generous Paid Time
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no html/body, no markdown fences Looking at the content: - "Who We Are" and "Why Join Us" are company description - could be "About the Company" or similar - "What You'll Be Doing" includes schedule (Full Time, Monday - Friday) and a paragraph about the role - "Essential Duties And Responsibilities" is a list of duties - Three levels of requirements: Clinical Dietitian I, II, III Must Haves - these are qualifications/requirements for different levels - "What We Offer" is benefits I need to map to standard headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting has: - Schedule mentioned: "Full Time, Monday - Friday" - so Schedule section is appropriate - Duties listed - Responsibilities section - Requirements for three levels - could be Qualifications or Requirements - Benefits listed - Benefits section - No explicit Pay section (just "competitive compensation" in benefits) - so no Pay section - No Skills section separate from requirements I'll structure: 1. About the Company (combining Who We Are and Why Join Us) - but the rules say use headings like "About the role", "Responsibilities", etc. "About the Company" isn't listed but "About the role" is. However, the company description is not about the role. The rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". It says "e.g." so other headings allowed? But prefer those. I think "About the Company" is okay as it's substantive. But maybe "About the Role" for the description of what you'll be doing? Actually "What You'll Be Doing" includes a paragraph about the role and schedule. I'll make "About the Role" for that paragraph, and "Schedule" for the schedule line. Let me parse: "What You'll Be Doing Schedule: Full Time, Monday - Friday The Clinical Dietitian provides medical nutrition therapy to patients who are recovering from an eating disorder, including educating patients and families on meal plans and nutritional needs." So I can have: -
About the Role
with the paragraph -Schedule
with the schedule info Then "Essential Duties And Responsibilities" ->Responsibilities
with ul Then the three levels of requirements. These are qualifications for different levels. Could beQualifications
with subsections? But rules say use h3 for section headings. Could have one Qualifications section with three sub-lists? But each level has different requirements. I'll create a Qualifications section with three subsections? But only h3 allowed? The rules say "use for section headings". It doesn't forbid multiple h3. I can have three h3: "Clinical Dietitian I Qualifications", "Clinical Dietitian II Qualifications", "Clinical Dietitian III Qualifications". But that might be too many. Alternatively, one Qualifications section with a list that includes the three levels. But the content is distinct. I think separate h3 for each level is okay as they are distinct requirement sets.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe combine into one Qualifications section with three sub-lists using h4? But only h3 allowed for headings. The rules don't forbid h4, but they say "use for section headings". Could use h3 for main sections and h4 for subsections? But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you can't use other heading levels. However, to be safe, I'll use h3 for each major section. I'll have:
- About the Company (or About Us) - combining Who We Are and Why Join Us
- About the Role
- Schedule
- Responsibilities
- Qualifications (with three subsections? But each is a list. I'll make three separate h3: "Clinical Dietitian I Requirements", "Clinical Dietitian II Requirements", "Clinical Dietitian III Requirements")
- Benefits
But that's many sections. However, each has substantive content. The rules say "include a section ONLY when the posting has real, specific content for it". Each level has specific content. So okay.
Alternatively, I could make one "Requirements" section with three lists labeled. But the heading "Requirements" is in the example. I'll do:
Requirements
and then for each level, maybe a ? But the instruction says use h3 for section headings. It doesn't say you can't use h4. But to follow strictly, maybe use h3 for each level. However, the example headings are generic: "Requirements, Qualifications". I think it's better to have one "Qualifications" section and within it, use for each level? But the output is HTML fragment, and they didn't forbid h4. I'll use h3 for main sections and h4 for sub-levels. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies that the top-level sections should be h3. Subsections could be h4. I'll do that.
Let's structure:
About the Company
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you can't use other heading levels. However, to be safe, I'll use h3 for each major section. I'll have:
- About the Company (or About Us) - combining Who We Are and Why Join Us
- About the Role
- Schedule
- Responsibilities
- Qualifications (with three subsections? But each is a list. I'll make three separate h3: "Clinical Dietitian I Requirements", "Clinical Dietitian II Requirements", "Clinical Dietitian III Requirements")
- Benefits
But that's many sections. However, each has substantive content. The rules say "include a section ONLY when the posting has real, specific content for it". Each level has specific content. So okay.
Alternatively, I could make one "Requirements" section with three lists labeled. But the heading "Requirements" is in the example. I'll do:
Requirements
and then for each level, maybe a ? But the instruction says use h3 for section headings. It doesn't say you can't use h4. But to follow strictly, maybe use h3 for each level. However, the example headings are generic: "Requirements, Qualifications". I think it's better to have one "Qualifications" section and within it, use for each level? But the output is HTML fragment, and they didn't forbid h4. I'll use h3 for main sections and h4 for sub-levels. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies that the top-level sections should be h3. Subsections could be h4. I'll do that.
Let's structure:
About the Company
for each level? But the output is HTML fragment, and they didn't forbid h4. I'll use h3 for main sections and h4 for sub-levels. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies that the top-level sections should be h3. Subsections could be h4. I'll do that.
Let's structure:
About the Company
About the Company
...combined Who We Are and Why Join Us...
About the Role
The Clinical Dietitian provides medical nutrition therapy...
Schedule
Full Time, Monday - Friday
Responsibilities
- ...
Qualifications
Clinical Dietitian I
- ...
Clinical Dietitian II
- ...
Clinical Dietitian III
- ...
Benefits
- ...