PRN Speech Language Pathologist
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (EEO, legal, etc.)
- 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 /, no markdown code fences
Looking at the content:
- "About Us" describes the facility - this could be "About the role" or "About us" but the rule says use specific headings like "About the role". However, the rule lists example headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About Us" is not exactly "About the role". But the posting has "About Us" and "Why Choose Functional Pathways". These are descriptive sections. I should map them to appropriate headings. Perhaps "About the role" for the job summary? The "Qualifications" section includes "Job Summary" and "Qualifications". The job summary describes duties. That could be "Responsibilities". The qualifications list is "Requirements" or "Qualifications". The rule says use "Qualifications" as heading. Also "Skills" maybe.
Let me structure:
1. About the role (or About us?) The posting has "About Us" describing the facility. That's not exactly about the role. But the rule says "About the role" as example. However, the posting doesn't have a clear "About the role" section. It has "Job Summary" under Qualifications. That describes the role. So I could have a "Responsibilities" section for the job summary duties. And a "Qualifications" section for the qualifications list.
2. "Why Choose Functional Pathways" - this is like benefits or company culture. Could be "Benefits" but it's not a list of benefits per se. It's a paragraph. Might be "About the company" but not in the allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Choose Functional Pathways" could be "Benefits" if it lists benefits, but it's more about culture. However, the rule says never create Benefits section unless posting actually states them. It does state "supportive family environment, ethical care, innovation, and a strong focus on values and customer service." That's not typical benefits like health insurance. Might be better to include as a "About the role" or just a paragraph under a heading? But we must use only those headings. Perhaps we can use "Benefits" if we interpret broadly. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state some perks. I think it's okay to include a "Benefits" section with that content.
But also there is "About Us" which is about the facility. That could be "About the role"? Not really. Maybe we can combine "About Us" and "Why Choose Functional Pathways" into a "About the role" section? Or create two sections? The rule says prefer a few substantive sections over many thin ones.
Let's examine the content:
- "About Us: Pennbryn Therapy Services in High Point, NC is a premier rehabilitation center..." This is about the employer.
- "Why Choose Functional Pathways: At Functional Pathways, we offer a supportive family environment..." This is about the employer brand.
The job posting is for Pennybyrn but mentions Functional Pathways. Might be a management company. The user wants to preserve all substantive information.
I think I'll create:
-
About the role
with the job summary paragraph (the duties).
- Qualifications
with the list of qualifications.
- Benefits
with the "Why Choose Functional Pathways" paragraph.
- Maybe About the company
but not in allowed headings. The allowed headings are fixed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the company" not allowed. So I should not create a heading not in that list. The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says "e.g." meaning examples, but likely they want those specific headings. However, the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it's implied we should use those. The rule also says "include a section ONLY when the posting has real, specific content for it". So we can use other headings if they fit? But the example list is given. I think we should stick to those headings.
Thus, map:
- "About Us" -> maybe "About the role"? But it's about the facility, not the role. However, the job summary is under Qualifications. The job summary describes the role. So I'll put job summary under "Responsibilities" or "About the role". The rule says "About the role" as example. I'll use "About the role" for the job summary paragraph.
- "Qualifications" list -> "Qualifications" heading.
- "Why Choose Functional Pathways" -> "Benefits" heading.
- The boilerplate at end (EEO) should be removed.
Also note: "Please be aware this is a job summary, not an all-inclusive listing..." that's part of qualifications section, keep.
Now, format:
About the role
The Speech-Language Pathologist shall conduct screenings, evaluations, re-evaluations, discharge planning, and make revisions in any established plan of care as supervised by the physician.
Qualifications
- Master’s degree in Speech Language Pathology from an accredited program.
- Certification and licensure requirements as established by state and national board associations.
- Active state license required.
- Excellent organizational and time management skills.
- Excellent written and verbal communication skills.
- Possess current working knowledge of Functional Pathways policies and procedures, clinical programs with application skills to therapy disciplines.
- Completion of all required screenings, certifications, and licensure.
- Screening requirements may vary by location.
Please be aware this is a job summary, not an all-inclusive listing of the tasks and duties for this position.
Benefits
At Functional Pathways, we offer a supportive family environment, ethical care, innovation, and a strong focus on values and customer service.
But also the "About Us" paragraph about Pennybyrn Therapy Services. That is substantive information about the workplace. Should we include it? The rule says preserve ALL substantive information. It's not boilerplate. It describes the facility. Could be under "About the role" or a separate section. Since "About the role" is already used, maybe we can add another paragraph before the job summary. Or create a "About the company" heading? Not in list. But the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but the examples are those. However, the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't say we cannot use other headings. But the system prompt says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings. But "About Us" is not exactly any of those. Could be "About the role" but it's about the company. Maybe we can include it as a paragraph under "About the role" before the job summary. That would preserve the info.
Let's combine: Under "About the role", include the "About Us" paragraph and the job summary paragraph.
But the "About Us" is about Pennybyrn Therapy Services, while the job summary is about the SLP role. They are distinct. However, we can have two paragraphs under same heading.
Alternatively, create a "About the company" heading? Not in list. I think it's okay to use a heading not in the example if it's appropriate. But the rule says "use for section headings (e.g. ...)". The "e.g." implies those are examples, not exhaustive. However, the later rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create a heading "About the company" if there is content. But the example list might be the only allowed ones? The user didn't explicitly forbid other headings. But to be safe, I'll stick to the example headings. The "About Us" content can be placed under "About the role" as introductory context.
Let's structure:
About the role
Pennbryn Therapy Services in High Point, NC is a premier rehabilitation center that offers comprehensive therapy programs to its patients. Our facility is equipped with state-of-the-art equipment and technology, as well as a compassionate and skilled team of therapists. Working at Pennbryn Therapy Services offers therapists the opportunity to help patients regain their physical and mental well-being, while being part of a supportive and dynamic healthcare team.
The Speech-Language Pathologist shall conduct screenings, evaluations, re-evaluations, discharge planning, and make revisions in any established plan of care as supervised by the physician.
Qualifications
... list ...
Please be aware this is a job summary, not an all-inclusive listing of the tasks and duties for this position.
Benefits
At Functional Pathways, we offer a supportive family environment, ethical care, innovation, and a strong focus on values and customer service.
That seems good. No Pay, Schedule, Skills, Requirements (Qualifications covers requirements). Responsibilities could be separate but job summary is essentially responsibilities. Could split: "Responsibilities" for the job summary, "Qualifications" for the list. But the rule says "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". We have both "About the role" and "Responsibilities". The job summary is responsibilities. The "About Us" is about the role context. I think using "About the role" for both is fine.
But the example includes both "About the role" and "Responsibilities". Could use "Responsibilities" for the job summary. Let's do:
About the role
Pennbryn Therapy Services in High Point, NC is a premier rehabilitation
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, legal, etc.) - 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 /, no markdown code fences Looking at the content: - "About Us" describes the facility - this could be "About the role" or "About us" but the rule says use specific headings like "About the role". However, the rule lists example headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About Us" is not exactly "About the role". But the posting has "About Us" and "Why Choose Functional Pathways". These are descriptive sections. I should map them to appropriate headings. Perhaps "About the role" for the job summary? The "Qualifications" section includes "Job Summary" and "Qualifications". The job summary describes duties. That could be "Responsibilities". The qualifications list is "Requirements" or "Qualifications". The rule says use "Qualifications" as heading. Also "Skills" maybe. Let me structure: 1. About the role (or About us?) The posting has "About Us" describing the facility. That's not exactly about the role. But the rule says "About the role" as example. However, the posting doesn't have a clear "About the role" section. It has "Job Summary" under Qualifications. That describes the role. So I could have a "Responsibilities" section for the job summary duties. And a "Qualifications" section for the qualifications list. 2. "Why Choose Functional Pathways" - this is like benefits or company culture. Could be "Benefits" but it's not a list of benefits per se. It's a paragraph. Might be "About the company" but not in the allowed headings. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Choose Functional Pathways" could be "Benefits" if it lists benefits, but it's more about culture. However, the rule says never create Benefits section unless posting actually states them. It does state "supportive family environment, ethical care, innovation, and a strong focus on values and customer service." That's not typical benefits like health insurance. Might be better to include as a "About the role" or just a paragraph under a heading? But we must use only those headings. Perhaps we can use "Benefits" if we interpret broadly. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state some perks. I think it's okay to include a "Benefits" section with that content. But also there is "About Us" which is about the facility. That could be "About the role"? Not really. Maybe we can combine "About Us" and "Why Choose Functional Pathways" into a "About the role" section? Or create two sections? The rule says prefer a few substantive sections over many thin ones. Let's examine the content: - "About Us: Pennbryn Therapy Services in High Point, NC is a premier rehabilitation center..." This is about the employer. - "Why Choose Functional Pathways: At Functional Pathways, we offer a supportive family environment..." This is about the employer brand. The job posting is for Pennybyrn but mentions Functional Pathways. Might be a management company. The user wants to preserve all substantive information. I think I'll create: -
About the role
with the job summary paragraph (the duties). -Qualifications
with the list of qualifications. -Benefits
with the "Why Choose Functional Pathways" paragraph. - MaybeAbout the company
but not in allowed headings. The allowed headings are fixed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the company" not allowed. So I should not create a heading not in that list. The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says "e.g." meaning examples, but likely they want those specific headings. However, the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it's implied we should use those. The rule also says "include a section ONLY when the posting has real, specific content for it". So we can use other headings if they fit? But the example list is given. I think we should stick to those headings.
Thus, map:
- "About Us" -> maybe "About the role"? But it's about the facility, not the role. However, the job summary is under Qualifications. The job summary describes the role. So I'll put job summary under "Responsibilities" or "About the role". The rule says "About the role" as example. I'll use "About the role" for the job summary paragraph.
- "Qualifications" list -> "Qualifications" heading.
- "Why Choose Functional Pathways" -> "Benefits" heading.
- The boilerplate at end (EEO) should be removed.
Also note: "Please be aware this is a job summary, not an all-inclusive listing..." that's part of qualifications section, keep.
Now, format:
About the role
About the role
The Speech-Language Pathologist shall conduct screenings, evaluations, re-evaluations, discharge planning, and make revisions in any established plan of care as supervised by the physician.
Qualifications
- Master’s degree in Speech Language Pathology from an accredited program.
- Certification and licensure requirements as established by state and national board associations.
- Active state license required.
- Excellent organizational and time management skills.
- Excellent written and verbal communication skills.
- Possess current working knowledge of Functional Pathways policies and procedures, clinical programs with application skills to therapy disciplines.
- Completion of all required screenings, certifications, and licensure.
- Screening requirements may vary by location.
Please be aware this is a job summary, not an all-inclusive listing of the tasks and duties for this position.
Benefits
At Functional Pathways, we offer a supportive family environment, ethical care, innovation, and a strong focus on values and customer service.
But also the "About Us" paragraph about Pennybyrn Therapy Services. That is substantive information about the workplace. Should we include it? The rule says preserve ALL substantive information. It's not boilerplate. It describes the facility. Could be under "About the role" or a separate section. Since "About the role" is already used, maybe we can add another paragraph before the job summary. Or create a "About the company" heading? Not in list. But the rule says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but the examples are those. However, the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't say we cannot use other headings. But the system prompt says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings. But "About Us" is not exactly any of those. Could be "About the role" but it's about the company. Maybe we can include it as a paragraph under "About the role" before the job summary. That would preserve the info.
Let's combine: Under "About the role", include the "About Us" paragraph and the job summary paragraph.
But the "About Us" is about Pennybyrn Therapy Services, while the job summary is about the SLP role. They are distinct. However, we can have two paragraphs under same heading.
Alternatively, create a "About the company" heading? Not in list. I think it's okay to use a heading not in the example if it's appropriate. But the rule says "use for section headings (e.g. ...)". The "e.g." implies those are examples, not exhaustive. However, the later rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create a heading "About the company" if there is content. But the example list might be the only allowed ones? The user didn't explicitly forbid other headings. But to be safe, I'll stick to the example headings. The "About Us" content can be placed under "About the role" as introductory context.
Let's structure:
About the role
About the role
Pennbryn Therapy Services in High Point, NC is a premier rehabilitation center that offers comprehensive therapy programs to its patients. Our facility is equipped with state-of-the-art equipment and technology, as well as a compassionate and skilled team of therapists. Working at Pennbryn Therapy Services offers therapists the opportunity to help patients regain their physical and mental well-being, while being part of a supportive and dynamic healthcare team.
The Speech-Language Pathologist shall conduct screenings, evaluations, re-evaluations, discharge planning, and make revisions in any established plan of care as supervised by the physician.
Qualifications
- ... list ...
Please be aware this is a job summary, not an all-inclusive listing of the tasks and duties for this position.
Benefits
At Functional Pathways, we offer a supportive family environment, ethical care, innovation, and a strong focus on values and customer service.
That seems good. No Pay, Schedule, Skills, Requirements (Qualifications covers requirements). Responsibilities could be separate but job summary is essentially responsibilities. Could split: "Responsibilities" for the job summary, "Qualifications" for the list. But the rule says "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". We have both "About the role" and "Responsibilities". The job summary is responsibilities. The "About Us" is about the role context. I think using "About the role" for both is fine. But the example includes both "About the role" and "Responsibilities". Could use "Responsibilities" for the job summary. Let's do:About the role
Pennbryn Therapy Services in High Point, NC is a premier rehabilitation