Sales Manager
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content.
We need to extract content: Overview, General Summary & Scope, Principal Duties & Responsibilities (Performance, People, Process), Job Qualifications (Education, Experience, Skills, Special Position Requirements), Working Conditions, Pay range, Benefits info.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove the "About At Ulta Beauty (NASDAQ: ULTA)..." maybe that's about company; could be considered "About the role"? Actually "About" heading is allowed? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe overview). We'll include an About the role section summarizing overview and mission.
Responsibilities: combine Performance, People, Process duties.
Requirements: maybe Education, Experience, Special Position Requirements? Actually Requirements could be Education and Experience. Qualifications maybe same? But we have both Qualifications and Skills headings allowed. We'll put Education and Experience under Requirements? Or Qualifications? The instruction says we can use those headings; we need to decide based on content.
We have: Education Bachelor’s degree is preferred. Experience 2-3+ years... Financial management..., Retail management..., Leadership management... That's qualifications. Then Skills: Proficient with basic technology..., Excellent written..., Strong collaboration..., Strong organizational..., Ability to react under pressure...
Special Position Requirements: Work a flexible full-time schedule..., Attend corporate business meetings... That's schedule? Actually schedule is separate heading; we could put schedule under Schedule heading. But we also have Working Conditions (physical demands). We could put Working Conditions under maybe a separate heading? Not in list but we could include as a section if content exists; but instruction says use those headings for section headings (e.g...). It doesn't forbid other headings, but 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 should map content to those headings.
Thus:
- About the role: overview and mission summary.
- Responsibilities: principal duties (Performance, People, Process).
- Requirements: Education and Experience (maybe also Special Position Requirements? but schedule separate).
- Qualifications: maybe the leadership/financial/retail management specifics? Actually those are under Experience bullet points. Could be part of Requirements. But we have both Requirements and Qualifications headings; we could put Education under Requirements, Experience under Qualifications? Or combine.
Better: Requirements: Education and Experience (including financial, retail, leadership). Qualifications: Skills (technology, communication, collaboration, organizational, adaptability). Benefits: Full-time positions eligible for paid time off, health, dental, vision, life and disability benefits. Part-time positions eligible for dental, vision, life, and disability benefits. Also mention link? We can keep description.
Pay: The pay range $26.00 - $34.00 / Hour with opportunity for additional compensation pursuant to bonus plan. Exact pay based on factors.
Schedule: Work a flexible, full-time schedule to include days, evenings, weekends, holidays; Attend corporate business meetings and conferences.
We should not include boilerplate like "If an associate has a disability..." maybe that's working conditions but not required; could be omitted as it's EEO? It's accommodation statement; might be considered legal boilerplate; better to drop.
Also drop "WORKING CONDITIONS" details? Those are physical demands; could be considered part of Responsibilities? Not exactly. Might be considered job requirements; but we have no heading for Working Conditions. Could we include under Requirements? Might be okay but not listed. Safer to omit? But we must preserve ALL substantive information; cannot drop details like physical demands unless they are boilerplate. They are substantive. However we have no heading for them; we could include them under Requirements as a bullet list? Or under Responsibilities? Probably under Requirements as "Physical Requirements". But instruction says use those headings for section headings (e.g...). It doesn't forbid other headings but suggests prefer those. However to be safe, we could include a section "Requirements" and within that include sub-bullets for education, experience, physical demands. Or we could add a separate heading "Working Conditions" but not in list; risk of being considered not following instruction. I'd rather include physical demands under Requirements as a bullet.
Similarly "Special Position Requirements" about schedule and attending meetings; we already have Schedule heading.
Now produce HTML:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings.
Thus:
- About the role: overview and mission summary.
- Responsibilities: principal duties (Performance, People, Process).
- Requirements: Education and Experience (maybe also Special Position Requirements? but schedule separate).
- Qualifications: maybe the leadership/financial/retail management specifics? Actually those are under Experience bullet points. Could be part of Requirements. But we have both Requirements and Qualifications headings; we could put Education under Requirements, Experience under Qualifications? Or combine.
Better: Requirements: Education and Experience (including financial, retail, leadership). Qualifications: Skills (technology, communication, collaboration, organizational, adaptability). Benefits: Full-time positions eligible for paid time off, health, dental, vision, life and disability benefits. Part-time positions eligible for dental, vision, life, and disability benefits. Also mention link? We can keep description.
Pay: The pay range $26.00 - $34.00 / Hour with opportunity for additional compensation pursuant to bonus plan. Exact pay based on factors.
Schedule: Work a flexible, full-time schedule to include days, evenings, weekends, holidays; Attend corporate business meetings and conferences.
We should not include boilerplate like "If an associate has a disability..." maybe that's working conditions but not required; could be omitted as it's EEO? It's accommodation statement; might be considered legal boilerplate; better to drop.
Also drop "WORKING CONDITIONS" details? Those are physical demands; could be considered part of Responsibilities? Not exactly. Might be considered job requirements; but we have no heading for Working Conditions. Could we include under Requirements? Might be okay but not listed. Safer to omit? But we must preserve ALL substantive information; cannot drop details like physical demands unless they are boilerplate. They are substantive. However we have no heading for them; we could include them under Requirements as a bullet list? Or under Responsibilities? Probably under Requirements as "Physical Requirements". But instruction says use those headings for section headings (e.g...). It doesn't forbid other headings but suggests prefer those. However to be safe, we could include a section "Requirements" and within that include sub-bullets for education, experience, physical demands. Or we could add a separate heading "Working Conditions" but not in list; risk of being considered not following instruction. I'd rather include physical demands under Requirements as a bullet.
Similarly "Special Position Requirements" about schedule and attending meetings; we already have Schedule heading.
Now produce HTML:
About the role
Overview text...
ThenResponsibilities
- ... each duty
maybe as . But instruction says output only HTML fragment; we can include . Pay: The pay range for this position is $26.00 - $34.00 / Hour with the opportunity for eligible associates to earn additional compensation pursuant to the Company’s bonus plan. Exact pay will be based on factors including, but not limited to relevant education, qualifications, certifications, experience, level, shift, geographic location, and business and organizational needs. Schedule: Work a flexible, full-time schedule to include days, evenings, weekends, and holidays; Attend corporate business meetings and conferences. Now ensure we don't include boilerplate like EEO etc. We removed the "We will consider for employment all qualified applicants..." that's EEO; drop. Also drop the "About At Ulta Beauty (NASDAQ: ULTA)..." maybe that's company overview; could be considered About the role? But we already have About the role; we could incorporate some of that? The overview already includes mission etc. The "About At Ulta Beauty" is more about company; could be considered part of About the role but maybe redundant. We could keep it as part of About the role? The instruction says preserve ALL substantive information; we should not drop company overview if it's substantive. However the "About At Ulta Beauty" is a generic description; might be considered boilerplate? It's not navigation/legal/EEO; it's about the company. Could be considered substantive. But we already have an About the role section;