Events Manager
Meow Wolf · California, United States · 1 mo ago
Management$80k–$89k/yrFull-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. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: privacy notice, EEO, etc. Also remove duplicated lines, application instructions, cookie/navigation/legal etc.
We need to parse the posting.
Key parts:
- Intro: "Privacy Notice for California Applicants and Employees Applicants must be currently authorized to work in the United States on a full-time basis. We are unable to sponsor or take over sponsorship of an employment Visa at this time." This is likely boilerplate (privacy notice, work auth). Should be removed? It's not about role, but it's a requirement. However it's about work authorization. Could be considered a requirement. But it's also a privacy notice. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Privacy notice maybe considered legal boilerplate. Might remove. However "Applicants must be currently authorized to work in the United States on a full-time basis. We are unable to sponsor or take over sponsorship of an employment Visa at this time." That's a substantive requirement (work authorization). Should we keep? Probably yes as part of Requirements. But the surrounding "Privacy Notice for California Applicants and Employees" is boilerplate; we can drop that phrase but keep the sentence.
- Then "Meow Wolf opens portals of possibility..." etc. That's about company mission, values. Could be "About the role"? Actually it's about company. Could be considered "About the role" or maybe not needed. The instruction: Use under
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have an "About the role" section summarizing the role description. The job summary is present: "Job Summary The Events Manager is the operational lead..." That's substantive. So we can put that under About the role. - Then "Key Responsibilities" with bullet-like paragraphs. We'll convert each sentence or clause into
- . Must preserve all substantive info.
- Then "Required Qualifications" list. That's qualifications. Could be under Requirements or Qualifications. The instruction includes both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has "Required Qualifications". So we can use
- ... each responsibility item.
Qualifications
and list items. - Then "Work Environment and Physical Demands" includes Work Environment, Physical Demands. Could be under Requirements? Might be separate but not in allowed headings. Could be omitted or folded into Requirements? The instruction: Prefer a few substantive sections over many thin ones. So we could include Work Environment under Requirements or maybe under a generic "Requirements" heading. But we already have Qualifications. Could combine Requirements and Qualifications? However we have separate headings allowed. We could have a "Requirements" section for work environment and physical demands, and a "Qualifications" section for experience/skills. Or we could merge them into Qualifications. But we need to preserve all info; we can put them under Qualifications as sub-items? Might be okay. - Then "Work Schedule" is a specific heading allowed. So we should have a Schedule section with content: "This is a full-time position that requires the ability to work a flexible schedule including evenings, weekends and holidays." - Then "Supervisor Responsibilities", "Travel", "Other Duties" etc. Those are not in allowed headings; we can drop or fold into Responsibilities? The instruction: Remove duplicated lines, boilerplate. "Other Duties Please note this job description is not designed to cover or contain a comprehensive listing..." That's boilerplate; we can drop. - Then "Meow Wolf will consider qualified applicants with criminal histories..." that's EEO/boilerplate; drop. - Then "IMPACT: ..." about B Corp; maybe not needed but could be part of About the role? It's about company values; could be included in About the role? Might be considered boilerplate? It's not about the role specifically. Probably drop. - Then "INCLUSION: Meow Wolf is an equal opportunity employer..." drop. - Then "Benefits" section with details. That's allowed heading Benefits. So we need a Benefits section with list. - Then "Please visit www.meowwolf.com/careers for more information." That's application instruction; drop. - Also there is "Compensation: The salary range for this position is $79,720 to $88,560. "Off-scale salaries" and other components of pay, i.e., a salary that is higher than the published system-wide salary at the designated position grade, are offered when necessary to meet competitive conditions." That's Pay info. So we need a Pay section. - Also location: "(On-site) Los Angeles, CA". Could be part of About the role or maybe a separate heading? Not in allowed headings; we can fold into About the role paragraph. - Also "Job Disclosures Location: (On-site) Los Angeles, CA Compensation: ..." Already captured. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce sections:About the role
... (including location, job summary, maybe company mission? but we can keep job summary and location). We'll incorporate location and job summary.