CMA
Miller Vein · Auburn Hills, MI · 3 wk ago
OTHRPart-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate.
We need to parse the posting.
Content:
- Intro: "Do you love to help people? ..." That's like a hook, maybe part of About the role? Could be considered "About the role" or maybe "Company Background". But we have to use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections have content.
Let's extract:
About the role: Could be the Position Summary and maybe intro. The posting has "Position Summary" paragraph: "The Medical Technician (Med Tech) is an integral member...". Also the intro about loving to help people could be part of About the role. We'll include that.
Responsibilities: The "Essential Duties and Responsibilities" list many bullet-like sentences. We'll put those in
- .
Requirements: Might be similar to Qualifications? Usually Requirements are like education, experience. Qualifications maybe credentials. But we have both "Qualifications" heading in posting: includes high school diploma, completion of program, strong customer service, proficiency with computers, preferred experience, credentials, CPR/BLS. Also "Every Miller Vein team member is expected to:" list of behaviors. That could be Skills or Requirements? Might be considered Skills (soft skills). We'll treat "Qualifications" as the formal qualifications (education, experience, credentials). "Skills" as the soft skills and expected behaviors.
Benefits: The posting includes "Miller Vein Perks" list: Competitive pay, 100% employer-paid medical, dental, vision insurance, 401(k), Paid Time Off (PTO), Healthy work-life balance including four-day weekends every other weekend, No evening, weekend, or holiday work (almost never), Paid office closure between Christmas and New Year's Day, Community service opportunities, Continuing education support, Positive upbeat office environments, Fun company outings.
Pay: The posting mentions "Competitive pay" but not specific numbers. According to rule: do NOT create Pay section unless posting actually states them. It says "Competitive pay" which is vague but it's stating pay exists. However rule says: 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. "Competitive pay" is somewhat vague but it's stating that pay is competitive. Is that considered filler? It's not a specific number or range, but it's a statement. The rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Competitive pay" is similar to "commensurate with experience"? Might be considered filler. Safer to not include Pay section unless there is explicit number or range. Since they didn't give a number, we should omit Pay section.
Schedule: The posting mentions "No evening, weekend, or holiday work (almost never)" and "four-day weekends every other weekend". That's schedule info. So we can include Schedule section with those details.
Benefits: we have specific list, so include Benefits.
Skills: we have expected behaviors: Demonstrate compassion, empathy, professionalism; treat patients with dignity; take ownership; protect privacy; create positive environment; contribute to culture. Also "Strong customer service and communication skills", "Proficiency with computers and EMR systems". Those could be skills. We'll include Skills.
Requirements: maybe we can combine education/experience etc. But we already have Qualifications. The posting has a "Qualifications" heading. We'll use that as Qualifications section. For Requirements, maybe we can include nothing? Better to omit Requirements if no distinct content besides Qualifications. But we could treat "Qualifications" as Requirements and not have Qualifications? However the instruction says use headings like Qualifications, Skills, etc. We have a Qualifications section in posting, so we should use that heading. For Requirements, maybe we can omit if no separate content. The posting doesn't have a separate "Requirements" heading besides Qualifications. So we omit Requirements.
About the role: we have Position Summary and intro.
Now we need to ensure we preserve all substantive information, not invent or summarize away detail. We must not drop any substantive info. So we need to include all bullet points from Essential Duties and Responsibilities, all qualifications, all expected behaviors, all perks/benefits, schedule info, company background maybe? The company background is substantive; where to put? Could be part of About the role or maybe a separate section like "Company Background" but not in allowed headings. Since only allowed headings are those list, we could incorporate company background into About the role (makes sense). Or we could put it under About the role as prose.
We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
Now produce HTML fragment.
Structure:
About the role
Intro text + Position Summary + Company Background (maybe combined).
Responsibilities
- ... each duty.
Qualifications
- ... each qualification.
Skills
- ... each skill/behavior.
Benefits
- ... each perk.
Schedule
- ... schedule details.