Aesthetics Manager
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract sections from posting.
The posting includes: About Tareen Dermatology (intro), The Opportunity (overview), What You Will Do (list of duties), What You Bring (Required, Preferred), Work Environment and Physical Requirements, plus maybe Benefits? Not mentioned. Pay? Not mentioned. Schedule? Not mentioned. So we should include sections for which we have content: About the role? Could map "About Tareen Dermatology" and "The Opportunity" as about the role. Could combine into About the role section. Responsibilities: "What You Will Do". Requirements: "What You Bring Required". Qualifications: maybe "Preferred" could be qualifications? But we have both Required and Preferred. Could put Requirements for required, Qualifications for preferred? Or Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide mapping.
We have content: About the role (intro + opportunity). Responsibilities (What You Will Do). Requirements (Required). Qualifications (Preferred). Skills maybe not separate; we could omit if no specific skills beyond those in requirements. Could include Skills if we have skill list: strong verbal/written communication, coaching, organization, analytical, judgment, proficiency with MS Office, ability to travel. Those are skills. Could put them under Skills. But we already have Required includes many of those. Might be redundant. Better to follow typical: Requirements = required experience/qualifications; Qualifications = preferred; Skills = specific abilities. However we have overlapping.
Given instruction: "Prefer a few substantive sections over many thin ones." So we should combine where appropriate. Perhaps we have: About the role, Responsibilities, Requirements (including required and preferred), Work Environment (maybe as a separate section? Not in list but could be under Requirements? Not given heading. Could omit if not in allowed headings? The allowed headings list includes those specific ones; we should only use those headings. So we cannot add a Work Environment heading unless we map it to something like "Skills"? Not appropriate. Could we omit work environment? It's substantive but not in allowed headings. However we could incorporate work environment details into Responsibilities or Requirements? Might be okay to include under Requirements as a bullet? But it's not a requirement. Could we drop it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep work environment info. If we cannot create a heading for it, we need to fit it under an existing heading. Perhaps under "Responsibilities" as part of operational support? Not exactly. Could be under "Requirements" as "Work Environment and Physical Requirements" but that is not a requirement but a description. Could treat as "Qualifications"? Not ideal.
Maybe we can create a section "Work Environment" but not in allowed list; but 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 exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we must map all content to those headings.
Thus we need to decide mapping:
- About the role: intro + opportunity.
- Responsibilities: What You Will Do.
- Requirements: Required.
- Qualifications: Preferred.
- Skills: maybe we can extract skill-based items from Required and Preferred that are skills: strong verbal/written communication, coaching, organization, analytical, judgment, MS Office proficiency, ability to travel. Could list under Skills.
- Benefits: none -> omit.
- Pay: none -> omit.
- Schedule: none -> omit.
We also have Work Environment and Physical Requirements; could we put under Skills? Not really. Could we put under Responsibilities? Not exactly. Could we put under Requirements as a bullet about physical ability? Might be okay: "Ability to lift up to 20 pounds, prolonged sitting, occasional travel." That could be a requirement. So we can include under Requirements.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills.
Now we need to format: About the role
then
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we must map all content to those headings.
Thus we need to decide mapping:
- About the role: intro + opportunity.
- Responsibilities: What You Will Do.
- Requirements: Required.
- Qualifications: Preferred.
- Skills: maybe we can extract skill-based items from Required and Preferred that are skills: strong verbal/written communication, coaching, organization, analytical, judgment, MS Office proficiency, ability to travel. Could list under Skills.
- Benefits: none -> omit.
- Pay: none -> omit.
- Schedule: none -> omit.
We also have Work Environment and Physical Requirements; could we put under Skills? Not really. Could we put under Responsibilities? Not exactly. Could we put under Requirements as a bullet about physical ability? Might be okay: "Ability to lift up to 20 pounds, prolonged sitting, occasional travel." That could be a requirement. So we can include under Requirements.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills.
Now we need to format: About the role
then
with prose combining intro and opportunity. Must not repeat job title. Use
- for lists.
We need to preserve all substantive information. Let's extract.
About Tareen Dermatology: "Tareen Dermatology provides compassionate, state-of-the-art medical, surgical, and cosmetic dermatologic care. We are committed to exceeding our patients’ expectations through individualized, expert, and ethical care while supporting the communities we serve."
The Opportunity: "We are seeking an experienced, organized, and people-focused Aesthetics Manager to help lead the operations of our growing cosmetic services division. The Aesthetics Manager oversees the day-to-day operations that support a consistent, high-quality cosmetic patient experience across multiple locations. This position combines team leadership, scheduling, training, patient coordination, inventory management, performance reporting, and operational support. The Aesthetics Manager serves as a key resource for aestheticians, cosmetic liaisons, injectable assistants, medical providers, and administrative teams. This individual also acts as second-in-command when the Director of Aesthetics is unavailable."
Combine into About the role paragraph(s). Could be two paragraphs.
Responsibilities: "What You Will Do" with subcategories: Team Leadership and Development, Training and Communication, Operations and Performance, Patient and Provider Support, Marketing and Events. Each has bullet points.
We need to output
- for any list of duties/requirements/benefits. So each bullet list under each subheading? The subheadings themselves are not headings (we only use h3 for section headings). We could keep the subheadings as or just plain text inside
- ? Probably better to keep them as part of the
- text. But we need to preserve structure. Could do
- Team Leadership and Development: ... etc. That's acceptable. Let's extract each bullet. Team Leadership and Development: - Provide daily leadership and support to the Cosmetic Liaison and Cosmetic Injectable Assist teams. - Recruit, onboard, train, coach, and develop team members. - Conduct performance reviews and address performance concerns constructively and consistently. - Manage aesthetician staffing, schedules, timecards, PTO requests, and coverage needs. - Coach employees on patient flow, injectable preparation, safety protocols, service standards, and cross-functional teamwork. - Support front desk and administrative teams during peak periods, staffing shortages, events, and promotional launches. Training and Communication: - Develop and refine training programs that promote team readiness and operational consistency. - Coordinate aesthetic and injectable training, including scheduling, logistics, attendance, communication, and follow-up. - Plan and facilitate monthly aesthetic team meetings. - Provide ongoing education about cosmetic services, systems, procedures, and practice protocols. - Communicate operational priorities, promotions, training information, and performance expectations to aestheticians and providers. Operations and Performance: - Oversee daily cosmetic operations and help ensure a seamless, high-quality patient experience. - Maintain and update protocols, standard operating procedures, and pre- and post-care patient education materials. - Monitor cosmetic inventory and communicate restocking needs. - Support accurate payment processing and the administration of financing and loyalty programs. - Maintain provider stipend records and supporting documentation. - Prepare weekly operational reports and monthly aesthetician KPI reports, including rebooking rates, patient volume, and add-on performance. - Identify trends and recommend coaching or process improvements. - Assist with the implementation of new workflows, processes, services, and locations. Patient and Provider Support: - Serve as the primary operational contact for medical providers regarding cosmetic scheduling, training, promotions, and follow-up needs. - Respond to cosmetic service inquiries by phone, email, and in person. - Serve as an escalation point for complex cosmetic service concerns. - Partner with team members to resolve patient concerns with professionalism, empathy, and sound judgment. - Maintain accurate, confidential, and HIPAA-compliant documentation and patient records. Marketing and Events: - Partner with the Marketing team to coordinate aesthetic promotions, cosmetic events, and service launches. - Help ensure teams are prepared to communicate and execute promotions accurately and consistently. Now Requirements (Required): - At least five years of experience in dermatology, medical aesthetics, a salon, spa, or comparable aesthetic setting. - Previous leadership or supervisory experience. - Strong verbal and written communication skills. - Demonstrated ability to coach employees, resolve conflict, and manage competing priorities. - Excellent organization, follow-through, and attention to detail. - Strong analytical and problem-solving skills. - Sound judgment, professionalism, integrity, and discretion. - Proficiency with Microsoft Office or similar business software. - Ability to travel to Tareen Dermatology locations as operational needs arise. Also we could add Work Environment and Physical Requirements as part of Requirements: "This position works primarily in a clinical setting and requires occasional travel between locations. The role includes prolonged periods of sitting and computer work and occasionally requires lifting up to 20 pounds." We'll include as bullet(s) maybe. Preferred (Qualifications): - Bachelor’s degree in business, healthcare administration, hospitality, or a related field. - Leadership experience in dermatology, medical aesthetics, or a multi-location clinical environment. - Experience with staff scheduling, performance reporting, inventory management, and patient-service recovery. Skills: we could list skill-based items not already covered: maybe we can extract from Required: strong verbal/written communication, coaching, organization, analytical, judgment, MS Office proficiency, ability to travel. But those are already in Requirements. To avoid duplication, maybe we omit Skills section. But we need to include all substantive info; if we put them under Requirements, it's fine. So we may not need Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications. We must not include empty sections. Now produce HTML. We'll wrap each section:
- . Might need to keep subheadings inside li as strong.
We'll do:
- Team Leadership and Development: Provide daily leadership and support to the Cosmetic Liaison and Cosmetic Injectable Assist teams. Recruit, onboard, train, coach, and develop team members. Conduct performance reviews and address performance concerns constructively and consistently. Manage aesthetician staffing, schedules, timecards, PTO requests, and coverage needs. Coach employees on patient flow, injectable preparation, safety protocols, service standards, and cross-functional teamwork. Support front desk and administrative teams during peak periods, staffing shortages, events, and promotional launches. ... etc. But that lumps many
About the role
... maybe multiple
paragraphs. We need to ensure no extra whitespace? It's fine. Let's craft. About the role: combine intro and opportunity into maybe two paragraphs. Paragraph1: Tareen Dermatology provides compassionate, state-of-the-art medical, surgical, and cosmetic dermatologic care. We are committed to exceeding our patients’ expectations through individualized, expert, and ethical care while supporting the communities we serve. Paragraph2: We are seeking an experienced, organized, and people-focused Aesthetics Manager to help lead the operations of our growing cosmetic services division. The Aesthetics Manager oversees the day-to-day operations that support a consistent, high-quality cosmetic patient experience across multiple locations. This position combines team leadership, scheduling, training, patient coordination, inventory management, performance reporting, and operational support. The Aesthetics Manager serves as a key resource for aestheticians, cosmetic liaisons, injectable assistants, medical providers, and administrative teams. This individual also acts as second-in-command when the Director of Aesthetics is unavailable. Now Responsibilities:
Responsibilities
then- with each bullet as
- for any list of duties/requirements/benefits. So each bullet list under each subheading? The subheadings themselves are not headings (we only use h3 for section headings). We could keep the subheadings as or just plain text inside