Patient Advocate (Part-Time)
Ayr Wellness · Clearwater, FL · 4 wk ago
On-siteHealthcarePart-time
We need to output HTML fragment with sections: Company Description? The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. The posting includes Company Description, Job Summary, Duties and Responsibilities, Qualifications (includes Education, Experience, Knowledge, Skills, And Abilities), Direct reports, Working conditions, Physical requirements, etc. Also includes EEO boilerplate which we should remove. Also includes "Nothing in this job description restricts management’s right..." which is boilerplate? Might be considered generic; but it's not EEO. Might keep? Probably remove as it's generic legal. We'll keep substantive info.
We need to map to headings: About the role (maybe Job Summary), Responsibilities (Duties and Responsibilities), Requirements (Qualifications?), Skills (Knowledge, Skills, And Abilities), Benefits (none), Pay (none), Schedule (none). Also maybe Working conditions and Physical requirements could be under Requirements or separate? The instruction only lists those headings as examples; we can add other headings if needed? It says use
for Company Description. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use headings for every section; we can have paragraphs without heading. But likely they expect headings for each section. We could treat Company Description as part of About the role? Might be odd. Better to add a heading "About the company" but not in list; risk of deviating. However the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. The posting includes Company Description, Job Summary, Duties and Responsibilities, Qualifications (includes Education, Experience, Knowledge, Skills, And Abilities), Direct reports, Working conditions, Physical requirements, etc. Also includes EEO boilerplate which we should remove. Also includes "Nothing in this job description restricts management’s right..." which is boilerplate? Might be considered generic; but it's not EEO. Might keep? Probably remove as it's generic legal. We'll keep substantive info.
We need to map to headings: About the role (maybe Job Summary), Responsibilities (Duties and Responsibilities), Requirements (Qualifications?), Skills (Knowledge, Skills, And Abilities), Benefits (none), Pay (none), Schedule (none). Also maybe Working conditions and Physical requirements could be under Requirements or separate? The instruction only lists those headings as examples; we can add other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings where appropriate. Could also add "Working Conditions" and "Physical Requirements" as headings if content exists. But they are not in the list; but we could still use for any section heading. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. Safer to stick to those headings and incorporate other info under them.
Thus:
- About the role: Job Summary paragraph.
- Responsibilities: Duties and Responsibilities list (maybe bullet list).
- Requirements: Qualifications (including Education, Experience, Must stay current etc.) Could be bullet list.
- Skills: Knowledge, Skills, And Abilities (maybe bullet list).
- Benefits: none -> omit.
- Pay: none -> omit.
- Schedule: none -> omit (though there is mention of scheduling varied shifts, weekends, holidays under Qualifications; but that's a requirement, not schedule details. So we omit Schedule section.)
We need to preserve all substantive information. So include details like "Must stay current and adhere to all policies and regulations of the state cannabis agency." etc.
We need to remove boilerplate: Company Description? That's substantive; keep. Job Summary? keep. Duties and Responsibilities? keep. Qualifications? keep. Knowledge, Skills, And Abilities? keep. Direct reports? maybe include under Requirements? It's a line "Direct reports No direct reports". Could be included as a bullet under Requirements. Working conditions? Could be included under Requirements or maybe as its own section but we don't have heading; maybe include under Requirements as bullet. Physical requirements? same.
We must not include EEO/equal-opportunity boilerplate. Remove that paragraph.
Also remove "Nothing in this job description restricts management’s right..." line.
Also remove "For more information, please visit www.ayrwellness.com." maybe keep? It's part of Company Description; it's a link but not essential; but it's substantive? Might be considered boilerplate; but it's a link to company site. Might keep as part of Company Description paragraph.
We need to output only HTML fragment, no markdown fences.
Let's craft:
About the role
for any section heading. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. Safer to stick to those headings and incorporate other info under them.
Thus:
- About the role: Job Summary paragraph.
- Responsibilities: Duties and Responsibilities list (maybe bullet list).
- Requirements: Qualifications (including Education, Experience, Must stay current etc.) Could be bullet list.
- Skills: Knowledge, Skills, And Abilities (maybe bullet list).
- Benefits: none -> omit.
- Pay: none -> omit.
- Schedule: none -> omit (though there is mention of scheduling varied shifts, weekends, holidays under Qualifications; but that's a requirement, not schedule details. So we omit Schedule section.)
We need to preserve all substantive information. So include details like "Must stay current and adhere to all policies and regulations of the state cannabis agency." etc.
We need to remove boilerplate: Company Description? That's substantive; keep. Job Summary? keep. Duties and Responsibilities? keep. Qualifications? keep. Knowledge, Skills, And Abilities? keep. Direct reports? maybe include under Requirements? It's a line "Direct reports No direct reports". Could be included as a bullet under Requirements. Working conditions? Could be included under Requirements or maybe as its own section but we don't have heading; maybe include under Requirements as bullet. Physical requirements? same.
We must not include EEO/equal-opportunity boilerplate. Remove that paragraph.
Also remove "Nothing in this job description restricts management’s right..." line.
Also remove "For more information, please visit www.ayrwellness.com." maybe keep? It's part of Company Description; it's a link but not essential; but it's substantive? Might be considered boilerplate; but it's a link to company site. Might keep as part of Company Description paragraph.
We need to output only HTML fragment, no markdown fences.
Let's craft:
About the role
About the role
[Company Description + Job Summary combined? Actually Company Description separate; but we can put Company Description under About the role? The heading "About the role" is for role summary; Company Description is about company. Could we have a separate heading? Not in list; but we could still use
for Company Description. 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 we should prefer those. However Company Description is substantive; we could put it under a heading like "About the company" but not listed. Might be okay to include as a
without heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use headings for every section; we can have paragraphs without heading. But likely they expect headings for each section. We could treat Company Description as part of About the role? Might be odd. Better to add a heading "About the company" but not in list; risk of deviating. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies examples, not exhaustive. So we can add other headings as needed. I'll include a heading for Company Description.
Thus:
About the company
About the company
...
ThenAbout the role
with Job Summary. ThenResponsibilities
with- ...
Requirements
with- ...
Skills
with- ...
- ...
About the company
Ayr Wellness is a leading U.S. multi-state cannabis operator with more than 90 licensed retail locations across Florida, Massachusetts, Pennsylvania, Ohio, New Jersey, Nevada, and soon, Virginia. We cultivate, manufacture, and sell a broad portfolio of high-quality cannabis products, proudly serving both medical patients and adult-use consumers across our markets. At Ayr, our strength lies in our