Events Manager
Ways2Well · Austin, TX · 1 mo ago
HybridManagementFull-time
We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to include only sections that have real specific content. The posting includes: Position Summary (maybe About the role). Key Responsibilities. Required Qualifications. Preferred Qualifications. Work Environment & Physical Requirements (maybe part of Requirements or Skills). Featured Benefits. Also maybe "Why Join Ways2Well?" could be About the role? But we can treat that as part of About the role or maybe separate but not required.
We must not include boilerplate like EEO, Reasonable Accommodations, AI statement, etc. Also remove duplicated lines, navigation, cookie, legal, etc.
We need to preserve all substantive information. So we need to include content from Position Summary, Key Responsibilities, Required Qualifications, Preferred Qualifications, Work Environment & Physical Requirements, Featured Benefits, Why Join Ways2Well? (maybe as part of About the role). Also maybe "Position Summary" is like About the role.
We must not create Pay or Schedule sections unless posting actually states them. There's no explicit pay or schedule details besides "Willingness and ability to work evenings, weekends, and holidays as event schedules require, and to travel for events (30-40%)" and "Flexibility to work non-standard hours (evenings, weekends, holidays) and to travel as needed". That's schedule info but not explicit schedule like "Full-time". However we could treat schedule info under Work Environment & Physical Requirements maybe. But we should not create a Schedule section unless posting actually states them. The phrase "Willingness and ability to work evenings, weekends, and holidays as event schedules require" is schedule-related but not a defined schedule. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated (Competitive salary, Comprehensive health, dental, and vision insurance, 401k with employer match, Paid Time Off, Employee Perks & Discounts). So Benefits section is okay. Pay: they mention "Competitive salary" but that's vague; they said "Competitive salary" under Benefits. That's still pay info. Should we create a Pay section? The posting states "Competitive salary" as part of Benefits. It might be considered pay info but it's under Benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they state "Competitive salary" we could include a Pay section with that detail. However they also list benefits separate. Might be better to keep Pay as part of Benefits? But they said "Prefer a few substantive sections over many thin ones." Could combine Pay and Benefits? But they want separate headings for Benefits, Pay, Schedule. If we have Pay info, we should include a Pay section. However the posting only says "Competitive salary" under Benefits; no specific numbers. That's still stating pay (competitive salary). So we can include a Pay section with that line.
Schedule: they mention willingness to work evenings, weekends, holidays, travel 30-40%, flexibility to work non-standard hours. That's schedule info. So we could include a Schedule section with those details.
But we must avoid filler like "commensurate with experience", "not specified", etc. "Competitive salary" is not filler; it's a statement. So okay.
Thus sections: About the role (position summary + why join?), Responsibilities, Requirements (maybe combine Required Qualifications + Work Environment & Physical Requirements?), Qualifications (maybe Preferred Qualifications?), Skills (maybe not separate), Benefits, Pay, Schedule.
We need to decide which headings to use. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if we have content.
We need to avoid empty sections. So we will include:
- About the role: combine Position Summary and Why Join Ways2Well? (maybe also brief intro). Must preserve all substantive info.
- Responsibilities: list from Key Responsibilities (bullet points). Use