Certified Medication Aide (CMA)
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- Use `
` 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; 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 (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Extract Content from Posting:**
Let me parse the text and categorize information:
- **Role:** Certified Medication Aide (CMA) - but rule says don't repeat job title as heading
- **Primary purpose:** "prepare, administer, report, and record medications according to the physician’s orders and established policies and procedures, and to ensure that the highest degree of quality care is always maintained"
- **About the Company/Role:** "We strive to create an environment where people feel safe, heard and understood. Our leadership teams embrace our 'Your Voice' philosophy."
- **Newly Certified CMA and walk-ins welcome**
- **Benefits listed:**
- Competitive compensation
- Daily Pay - access earned wages before payday
- 401k with a match
- Company paid holidays and Paid Time Off (PTO) Program
- Health insurance for the entire family
- Scrubs on Wheels
- Voluntary Benefits reviewed and provided at your one-on-one benefit meeting
- Exceptional Corporate Support
- **Qualifications listed:**
- Must be certified as a Qualified Medication Aide, by the Department of Health
- Must possess the ability to make independent decisions
- Previous skilled nursing home experience
- **Company philosophy/EEO:** "We strive to create an environment where people feel safe, heard and understood. Our leadership teams embrace our 'Your Voice' philosophy. Avir Health Group is an equal opportunity employer. All applicants will be considered for employment without attention to race, color, religion, sex, sexual orientation, gender identity, national origin, veteran, or disability status."
- **Removed items:** EEO/equal-opportunity boilerplate, scam warnings, application instructions, duplicate lines, cookie/navigation/legal stuff (not present anyway)
Now, map to allowed sections per rules:
- Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
- Must only include sections when there's real specific content
- Never create Pay/Schedule/Benefits unless posting actually states them
- Preserve all substantive info
Let's evaluate each section:
- **About the role**: The posting has "About the Company" section and primary purpose. I could use "About the role" or maybe "About the Company". But rule says use `
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to choose appropriate headings from that list or similar. The example lists: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should map the content to these meaningfully.
Let's map:
- "About the role" could cover the primary purpose and company description. But there's also "About the Company" paragraph. I'll likely use "About the role" for the job purpose, or maybe split? Rule: "Prefer a few substantive sections over many thin ones." So I should combine where appropriate.
- **Responsibilities**: The primary purpose is essentially responsibilities: "prepare, administer, report, and record medications according to the physician’s orders and established policies and procedures, and to ensure that the highest degree of quality care is always maintained." Also "Newly Certified Medication Aides (CMA) and walk-ins are always welcome!" - that's more about the role environment.
- **Requirements**: Not explicitly separate, but qualifications include certification, decision-making ability, previous experience. I'll map to "Requirements" or "Qualifications". The rule lists both "Requirements" and "Qualifications" as possible headings. I need to decide. Typically, qualifications are what you have; requirements are what's required. Here they overlap. I'll use "Qualifications" for the listed must-haves, or maybe "Requirements". Let's see the exact text: "Qualifications for Certified Medication Aide (CMA) : Must be certified... Must possess... Previous skilled nursing home experience." So "Qualifications" is directly used in the posting. I'll use `Qualifications
`.
- **Skills**: Not explicitly listed separately. The "ability to make independent decisions" could be a skill, but it's already in qualifications. I might not create a Skills section if there's no distinct list. Rule: include section ONLY when posting has real specific content. I'll check if there's meaningful skills content beyond qualifications. Not really. I'll skip or merge.
- **Benefits**: Explicitly listed: Competitive compensation, Daily Pay, 401k match, paid holidays/PTO, health insurance, Scrubs on Wheels, Voluntary Benefits, Exceptional Corporate Support. So I'll create `Benefits
` with `- ` items.
- **Pay**: "Competitive compensation" is mentioned, but no specific pay range. Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive compensation" but that's vague. The rule says never emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive compensation" is substantive but not specific. I need to decide: does it count as "actually states them"? The rule says never create Pay section unless posting actually states them. It does state "Competitive compensation" but it's not a specific pay rate. I think I should include Benefits section with the listed benefits, and maybe include Pay as a subsection or mention it within Benefits, but not create a separate Pay section with vague text. Actually, the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are clearly stated. Pay is loosely stated as "Competitive compensation". I'll include Benefits section, and maybe mention compensation in a
or within Benefits, but not create a standalone Pay section unless there's specific pay info. I'll avoid Pay section.
- **Schedule**: Not mentioned at all. So no Schedule section.
- **About the company/EEO**: The posting has "About the Company" paragraph and EEO statement. Rule says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the EEO boilerplate. The "About the Company" part: "We strive to create an environment where people feel safe, heard and understood. Our leadership teams embrace our 'Your Voice' philosophy." That's substantive and should be kept, probably under "About the role" or a dedicated heading. I'll map it to "About the role" or maybe just include it in prose.
Let's re-read carefully: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So the EEO paragraph at the end must be removed. The "About the Company" paragraph before that is likely substantive and should stay.
Now, structure planning:
Allowed headings from rules: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
I'll use:
- `
About the role
` - for primary purpose and company description
- `Responsibilities
` - for medication duties (maybe combine with About the role, but rule says prefer few substantive sections. I'll keep Responsibilities separate as it's a clear list of duties)
- `Qualifications
` - for the must-be-certified, decision-making, experience
- `Benefits
` - for the listed benefits
- Maybe `Skills` if there's distinct content, but I'll skip if not.
Let's map content:
**About the role**:
- Primary purpose: "prepare, administer, report, and record medications according to the physician’s orders and established policies and procedures, and to ensure that the highest degree of quality care is always maintained"
- Company env: "We strive to create an environment where people feel safe, heard and understood. Our leadership teams embrace our 'Your Voice' philosophy."
- "Newly Certified Medication Aides (CMA) and walk-ins are always welcome!" - could go here or in responsibilities.
**Responsibilities**:
- The primary purpose is essentially responsibilities. I could put the medication duties here. But to avoid duplication, I'll put the core duties under Responsibilities, and maybe company philosophy under About the role.
**Qualifications**:
- Must be certified as a Qualified Medication Aide, by the Department of Health
- Must possess the ability to make independent decisions
- Previous skilled nursing home experience
**Benefits**:
- Competitive compensation
- Daily Pay - access your earned wages before payday!
- 401k with a match!
- Company paid holidays and Paid Time Off (PTO) Program
- Health insurance for the entire family!
- Scrubs on Wheels
- Voluntary Benefits reviewed and provided at your one-on-one benefit meeting
- Exceptional Corporate Support
I need to check: "Competitive compensation" as a benefit item. It's listed first under "Exciting Benefits for Certified Medication Aide (CMA):". So I'll include it as a benefit item.
Now, format:
`About the role
...prose...
`
`Responsibilities
- ...
`
`Qualifications
- ...
`
`Benefits
- ...
`
Check rules again: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I can use any of these, but only include when there's content. I'll use About the role, Responsibilities, Qualifications, Benefits.
"Do NOT repeat the job title as a heading (the page already shows it)" - so no Certified Medication Aide
.
"Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - no job ID in posting anyway.
"
` 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; 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 (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Extract Content from Posting:** Let me parse the text and categorize information: - **Role:** Certified Medication Aide (CMA) - but rule says don't repeat job title as heading - **Primary purpose:** "prepare, administer, report, and record medications according to the physician’s orders and established policies and procedures, and to ensure that the highest degree of quality care is always maintained" - **About the Company/Role:** "We strive to create an environment where people feel safe, heard and understood. Our leadership teams embrace our 'Your Voice' philosophy." - **Newly Certified CMA and walk-ins welcome** - **Benefits listed:** - Competitive compensation - Daily Pay - access earned wages before payday - 401k with a match - Company paid holidays and Paid Time Off (PTO) Program - Health insurance for the entire family - Scrubs on Wheels - Voluntary Benefits reviewed and provided at your one-on-one benefit meeting - Exceptional Corporate Support - **Qualifications listed:** - Must be certified as a Qualified Medication Aide, by the Department of Health - Must possess the ability to make independent decisions - Previous skilled nursing home experience - **Company philosophy/EEO:** "We strive to create an environment where people feel safe, heard and understood. Our leadership teams embrace our 'Your Voice' philosophy. Avir Health Group is an equal opportunity employer. All applicants will be considered for employment without attention to race, color, religion, sex, sexual orientation, gender identity, national origin, veteran, or disability status." - **Removed items:** EEO/equal-opportunity boilerplate, scam warnings, application instructions, duplicate lines, cookie/navigation/legal stuff (not present anyway) Now, map to allowed sections per rules: - Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule - Must only include sections when there's real specific content - Never create Pay/Schedule/Benefits unless posting actually states them - Preserve all substantive info Let's evaluate each section: - **About the role**: The posting has "About the Company" section and primary purpose. I could use "About the role" or maybe "About the Company". But rule says use `
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to choose appropriate headings from that list or similar. The example lists: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should map the content to these meaningfully.
Let's map:
- "About the role" could cover the primary purpose and company description. But there's also "About the Company" paragraph. I'll likely use "About the role" for the job purpose, or maybe split? Rule: "Prefer a few substantive sections over many thin ones." So I should combine where appropriate.
- **Responsibilities**: The primary purpose is essentially responsibilities: "prepare, administer, report, and record medications according to the physician’s orders and established policies and procedures, and to ensure that the highest degree of quality care is always maintained." Also "Newly Certified Medication Aides (CMA) and walk-ins are always welcome!" - that's more about the role environment.
- **Requirements**: Not explicitly separate, but qualifications include certification, decision-making ability, previous experience. I'll map to "Requirements" or "Qualifications". The rule lists both "Requirements" and "Qualifications" as possible headings. I need to decide. Typically, qualifications are what you have; requirements are what's required. Here they overlap. I'll use "Qualifications" for the listed must-haves, or maybe "Requirements". Let's see the exact text: "Qualifications for Certified Medication Aide (CMA) : Must be certified... Must possess... Previous skilled nursing home experience." So "Qualifications" is directly used in the posting. I'll use `Qualifications
`.
- **Skills**: Not explicitly listed separately. The "ability to make independent decisions" could be a skill, but it's already in qualifications. I might not create a Skills section if there's no distinct list. Rule: include section ONLY when posting has real specific content. I'll check if there's meaningful skills content beyond qualifications. Not really. I'll skip or merge.
- **Benefits**: Explicitly listed: Competitive compensation, Daily Pay, 401k match, paid holidays/PTO, health insurance, Scrubs on Wheels, Voluntary Benefits, Exceptional Corporate Support. So I'll create `Benefits
` with `- ` items.
- **Pay**: "Competitive compensation" is mentioned, but no specific pay range. Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive compensation" but that's vague. The rule says never emit heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive compensation" is substantive but not specific. I need to decide: does it count as "actually states them"? The rule says never create Pay section unless posting actually states them. It does state "Competitive compensation" but it's not a specific pay rate. I think I should include Benefits section with the listed benefits, and maybe include Pay as a subsection or mention it within Benefits, but not create a separate Pay section with vague text. Actually, the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are clearly stated. Pay is loosely stated as "Competitive compensation". I'll include Benefits section, and maybe mention compensation in a
or within Benefits, but not create a standalone Pay section unless there's specific pay info. I'll avoid Pay section.
- **Schedule**: Not mentioned at all. So no Schedule section.
- **About the company/EEO**: The posting has "About the Company" paragraph and EEO statement. Rule says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the EEO boilerplate. The "About the Company" part: "We strive to create an environment where people feel safe, heard and understood. Our leadership teams embrace our 'Your Voice' philosophy." That's substantive and should be kept, probably under "About the role" or a dedicated heading. I'll map it to "About the role" or maybe just include it in prose.
Let's re-read carefully: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So the EEO paragraph at the end must be removed. The "About the Company" paragraph before that is likely substantive and should stay.
Now, structure planning:
Allowed headings from rules: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
I'll use:
- `
About the role
` - for primary purpose and company description
- `Responsibilities
` - for medication duties (maybe combine with About the role, but rule says prefer few substantive sections. I'll keep Responsibilities separate as it's a clear list of duties)
- `Qualifications
` - for the must-be-certified, decision-making, experience
- `Benefits
` - for the listed benefits
- Maybe `Skills` if there's distinct content, but I'll skip if not.
Let's map content:
**About the role**:
- Primary purpose: "prepare, administer, report, and record medications according to the physician’s orders and established policies and procedures, and to ensure that the highest degree of quality care is always maintained"
- Company env: "We strive to create an environment where people feel safe, heard and understood. Our leadership teams embrace our 'Your Voice' philosophy."
- "Newly Certified Medication Aides (CMA) and walk-ins are always welcome!" - could go here or in responsibilities.
**Responsibilities**:
- The primary purpose is essentially responsibilities. I could put the medication duties here. But to avoid duplication, I'll put the core duties under Responsibilities, and maybe company philosophy under About the role.
**Qualifications**:
- Must be certified as a Qualified Medication Aide, by the Department of Health
- Must possess the ability to make independent decisions
- Previous skilled nursing home experience
**Benefits**:
- Competitive compensation
- Daily Pay - access your earned wages before payday!
- 401k with a match!
- Company paid holidays and Paid Time Off (PTO) Program
- Health insurance for the entire family!
- Scrubs on Wheels
- Voluntary Benefits reviewed and provided at your one-on-one benefit meeting
- Exceptional Corporate Support
I need to check: "Competitive compensation" as a benefit item. It's listed first under "Exciting Benefits for Certified Medication Aide (CMA):". So I'll include it as a benefit item.
Now, format:
`About the role
...prose...
`
`Responsibilities
- ...
`
`Qualifications
- ...
`
`Benefits
- ...
`
Check rules again: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I can use any of these, but only include when there's content. I'll use About the role, Responsibilities, Qualifications, Benefits.
"Do NOT repeat the job title as a heading (the page already shows it)" - so no Certified Medication Aide
.
"Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - no job ID in posting anyway.
"
or within Benefits, but not create a standalone Pay section unless there's specific pay info. I'll avoid Pay section. - **Schedule**: Not mentioned at all. So no Schedule section. - **About the company/EEO**: The posting has "About the Company" paragraph and EEO statement. Rule says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the EEO boilerplate. The "About the Company" part: "We strive to create an environment where people feel safe, heard and understood. Our leadership teams embrace our 'Your Voice' philosophy." That's substantive and should be kept, probably under "About the role" or a dedicated heading. I'll map it to "About the role" or maybe just include it in prose. Let's re-read carefully: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So the EEO paragraph at the end must be removed. The "About the Company" paragraph before that is likely substantive and should stay. Now, structure planning: Allowed headings from rules: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule I'll use: - `
About the role
` - for primary purpose and company description - `Responsibilities
` - for medication duties (maybe combine with About the role, but rule says prefer few substantive sections. I'll keep Responsibilities separate as it's a clear list of duties) - `Qualifications
` - for the must-be-certified, decision-making, experience - `Benefits
` - for the listed benefits - Maybe `Skills` if there's distinct content, but I'll skip if not.
Let's map content:
**About the role**:
- Primary purpose: "prepare, administer, report, and record medications according to the physician’s orders and established policies and procedures, and to ensure that the highest degree of quality care is always maintained"
- Company env: "We strive to create an environment where people feel safe, heard and understood. Our leadership teams embrace our 'Your Voice' philosophy."
- "Newly Certified Medication Aides (CMA) and walk-ins are always welcome!" - could go here or in responsibilities.
**Responsibilities**:
- The primary purpose is essentially responsibilities. I could put the medication duties here. But to avoid duplication, I'll put the core duties under Responsibilities, and maybe company philosophy under About the role.
**Qualifications**:
- Must be certified as a Qualified Medication Aide, by the Department of Health
- Must possess the ability to make independent decisions
- Previous skilled nursing home experience
**Benefits**:
- Competitive compensation
- Daily Pay - access your earned wages before payday!
- 401k with a match!
- Company paid holidays and Paid Time Off (PTO) Program
- Health insurance for the entire family!
- Scrubs on Wheels
- Voluntary Benefits reviewed and provided at your one-on-one benefit meeting
- Exceptional Corporate Support
I need to check: "Competitive compensation" as a benefit item. It's listed first under "Exciting Benefits for Certified Medication Aide (CMA):". So I'll include it as a benefit item.
Now, format:
`About the role
...prose...
` `Responsibilities
- ...
Qualifications
- ...
Benefits
- ...
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I can use any of these, but only include when there's content. I'll use About the role, Responsibilities, Qualifications, Benefits.
"Do NOT repeat the job title as a heading (the page already shows it)" - so no Certified Medication Aide
.
"Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." - no job ID in posting anyway. "