Marketing Representative

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Remove boilerplate, EEO, etc. We need to parse the posting. First, there is an introductory paragraph about Pyramid Healthcare: "Pyramid Healthcare is dedicated to offering the highest quality of care..." etc. That's about the organization, maybe "About the role"? Actually "About the role" would be summary of role. The posting includes a "Summary: This role is responsible for the utilization of Pyramid Healthcare’s continuum of care by developing and maintaining direct referral relationships in designated market(s). Catchment Area: Roanoke Region". That's about the role. So we can put that in

About the role

with

containing that summary. Then "Essential Duties And Responsibilities" list: Provide clientele, marketing and customer service activities within the marketing department while maintaining positive community/public relations. Maintain existing referral sources, expand referral base and develop business relationships with the assigned region. Input into the overall company-marketing plan. Prepare reports as required. Assist in setting financial goals for the assigned region. Required to interface with the programs to understand client/program/referral source needs. Completes required trainings and mandatory training hours. Other duties as assigned. We need to put these as

• items under

  Responsibilities

  . Then "Supervisory Responsibilities None" - we can ignore as no content. Then "Required Qualifications Education, Licensure, & Experience" includes: High school diploma or equivalent with one year of related experience required. Bachelor’s degree in a related Behavioral Health or Business/Marketing field preferred. 3-5 years’ experience in D&A and/or Mental Health field preferred. 3-5 years’ experience as a Counselor, Assessor or Community Relations in direct client care preferred. We need to decide where to put qualifications vs skills. The posting has "Job Knowledge, Skills, And Abilities" section with list of knowledge/skills. So we can have

  Qualifications

  for education/experience, and

  Skills

  for knowledge/skills/abilities. But the instruction says use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They also mention "Requirements" as a possible heading. We could combine education/experience under "Requirements" or "Qualifications". Usually "Requirements" includes education/experience, while "Qualifications" maybe similar. But we need to follow instruction: use those headings only when content exists. We have content for education/experience (Required Qualifications). We also have content for knowledge/skills/abilities (Job Knowledge, Skills, And Abilities). We could map "Requirements" to education/experience, and "Skills" to knowledge/skills/abilities. Or we could put both under "Qualifications". But better to follow the list: we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (education/experience), Qualifications (maybe we could treat as same as Requirements? but we need distinct). Actually the posting has "Required Qualifications Education, Licensure, & Experience". That's qualifications. Then "Job Knowledge, Skills, And Abilities". That's skills. So we can put education/experience under "Requirements" (or "Qualifications") and knowledge/skills under "Skills". Let's decide: Use "Requirements" for education/experience, "Skills" for knowledge/skills/abilities. Then we might not need a separate "Qualifications" heading unless we have other qualifications like certifications etc. But we have "Required Qualifications" heading in posting; we could treat that as "Qualifications". However we need to avoid duplicate/thin sections. We could combine education/experience and knowledge/skills under "Qualifications". But the instruction says we can use those headings; we should include only when posting has real specific content. It does have both education/experience and knowledge/skills. So we could have two sections: "Requirements" (education/experience) and "Skills" (knowledge/skills). Or we could have "Qualifications" (education/experience) and "Skills" (knowledge/skills). Which is more appropriate? The list includes both "Requirements" and "Qualifications". Usually "Requirements" are mandatory, "Qualifications" are preferred. In the posting, education/experience includes both required and preferred. The "Job Knowledge, Skills, And Abilities" are also required to perform job successfully. So maybe we treat "Requirements" as the mandatory items (high school diploma or equivalent with one year of related experience required). The preferred items (Bachelor's degree, 3-5 years experience) could be under "Qualifications". But the instruction says we should not invent or summarize away detail. We need to preserve all substantive information. So we need to include both required and preferred details. We could put all under "Requirements" but then we lose distinction. However it's okay as long as we preserve info. The instruction says prefer a few substantive sections over many thin ones. So maybe combine education/experience and knowledge/skills into one "Qualifications" section. But we also have "Skills" heading available. Let's think: The posting has a clear "Job Knowledge, Skills, And Abilities" list. That is definitely skills. So we should have a Skills section. Then we have education/experience under either Requirements or Qualifications. Since we have both headings, we could put education/experience under Requirements (since it's about required experience) and maybe also include preferred under Qualifications? But that would be two sections with similar content. Better to put education/experience under Requirements, and skills under Skills. Then we can omit Qualifications heading (since we don't have separate content beyond what's already covered). However the posting uses "Required Qualifications" heading; but we can treat that as Requirements. The instruction says we should not repeat the job title as heading and not put Job ID etc. It didn't forbid using Requirements for qualifications. So we can do:

  About the role

  Summary: This role is responsible for the utilization of Pyramid Healthcare’s continuum of care by developing and maintaining direct referral relationships in designated market(s). Catchment Area: Roanoke Region

  Responsibilities

  • Provide clientele, marketing and customer service activities within the marketing department while maintaining positive community/public relations.
  • Maintain existing referral sources, expand referral base and develop business relationships with the assigned region.
  • Input into the overall company-marketing plan.
  • Prepare reports as required.
  • Assist in setting financial goals for the assigned region.
  • Required to interface with the programs to understand client/program/referral source needs.
  • Completes required trainings and mandatory training hours.
  • Other duties as assigned.

  Requirements

  • High school diploma or equivalent with one year of related experience required.
  • Bachelor’s degree in a related Behavioral Health or Business/Marketing field preferred.
  • 3-5 years’ experience in D&A and/or Mental Health field preferred.
  • 3-5 years’ experience as a Counselor, Assessor or Community Relations in direct client care preferred.

  Skills

  • Knowledge of chemical dependency and psychiatric treatment
  • Knowledge of marketing methods in a behavioral healthcare setting
  • Ability to empathize and provide strong customer service
  • Ability to prioritize and multi-task
  • Self-starter with the ability to adapt to changes and turn things around quickly
  • Working knowledge of Microsoft Office Suite and computer programs
  • Ability to thrive in a fast-paced environment
  • Attends and participate in required meetings.
  • Completion of all required trainings as designated by the company and accreditation/licensing entities.
  • A working knowledge of federal and state standards as well as regulating body and compliance standards.
  Now Benefits: The posting includes "Total Rewards For Full-Time Positions Medical, Dental, and Vision Insurance Flexible Spending Accounts Life Insurance Paid Time Off 401(k) with Company Match Tuition Reimbursement Employee Recognition Programs Referral Bonus opportunities And More!" That's benefits. So we need a Benefits section. Pay: The posting includes "The starting compensation for this role is $50,000/year; final compensation will be determined based on skills, experience, and qualifications." That's pay info. So we need Pay section. Schedule: The posting includes "This position will be scheduled based on operational need & will be required to provide own transportation." Also earlier: "This position will require local travel." That's schedule info? It mentions schedule based on operational need. So we can include Schedule section with that info. We need to ensure we don't include boilerplate like EEO, etc. Also remove duplicated lines. Also remove "Pyramid CORE Values" etc? That's not a section heading we have; but it's substantive? It's about values, but not a standard heading. The instruction says to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The CORE values could be considered content but not under any of the prescribed headings. We could either omit it or incorporate into About the role? But it's not about the role; it's about company values. The instruction says to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. CORE values is not boilerplate but it's not a standard heading. Should we include it? The instruction says to use headings for those specific sections only. It didn't forbid adding other headings, but says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should limit to those headings. It also says "Prefer a few substantive sections over many thin ones." So we should not add extra headings like CORE values. We could incorporate that info into About the role maybe? But About the role is supposed to be summary of role. Could we add a paragraph about company values under About the role? That might be stretching. Better to omit CORE values as it's not under prescribed headings and not essential to the role description? However it's substantive info about company culture. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must preserve CORE values info. But we cannot create a heading outside the list? The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. It might be okay to use other headings if needed, but they gave a list of likely sections. However they also said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a heading like "Company Values" if there is content. But they didn't list that as an example. The safe approach: we could incorporate the CORE values into a paragraph under About the role or maybe under a separate

  About the company

  but that's not in the list. 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 they gave examples. To be safe, we could add a section "Company Values" as