Product Operations Manager II
The Walt Disney Company · Glendale, CA · 1 mo ago
On-siteManufacturing$107k–$143k/yrFull-time
We need to output HTML fragment with sections: headings using for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph about Disney Entertainment and ESPN Product & Technology. That's about the role? Could be "About the role" or "About the team". Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph about Disney Entertainment and ESPN Product & Technology. That's about the role? Could be "About the role" or "About the team". Use About the role
maybe.
- Then bullet list of reasons why you'd love working here: Building the future..., Reach, Scale & Impact, Innovation. Those are reasons; could be part of About the role or separate? Probably part of About the role.
- Then description of Content Platforms & Operations responsibilities: This includes ... The global team also plays a critical role... As a member of the Product Operations team, you will have the opportunity... Working in a cross-functional team environment... This is more about role.
- Then "Job Summary" heading (but we should not repeat job title; we can treat as About the role). The Job Summary paragraph: The Content Platforms team is seeking a Product Operations Manager II... etc.
- Then "Responsibilities" heading with bullet list.
- Then "Basic Qualifications" heading with bullet list.
- Then "Preferred Qualifications" heading with bullet list.
- Then compensation: "The hiring range for this position in Glendale, CA is $106,900 - $143,300 per year. The base pay actually offered will take into account internal equity and also may vary depending on the candidate’s geographic region, job-related knowledge, skills, and experience among other factors. A bonus and/or long-term incentive units may be provided as part of the compensation package, in addition to the full range of medical, financial, and/or other benefits, dependent on the level and position offered."
We need to include Pay section if posting actually states them. Yes, they give hiring range. So we should include Pay
with that info.
Benefits: They mention "full range of medical, financial, and/or other benefits". That's vague but it's a statement about benefits. Should we include Benefits section? The rule: include a section ONLY when the posting has real, specific content for it — 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. They do state benefits: "full range of medical, financial, and/or other benefits". That's somewhat generic but it's a statement. I'd include Benefits section with that sentence.
Schedule: No mention of schedule. So omit.
We also need to include maybe Skills? Not explicit; but Preferred Qualifications includes skills. Could combine under Qualifications? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Basic Qualifications and Preferred Qualifications; could combine into Qualifications? But we have both; maybe we can have Qualifications
and include both basic and preferred as sublists? However they said prefer a few substantive sections over many thin ones. Could combine Basic and Preferred into Qualifications with two sub-sections? But we must use for section headings only; we could have Qualifications
and then inside have
Qualifications
and then inside haveBasic Qualifications:
- ... and
Preferred Qualifications:
- ... That would be okay.
Alternatively keep Basic Qualifications and Preferred Qualifications as separate headings? The allowed headings list includes Qualifications (singular). Might be better to have one Qualifications section.
Responsibilities we keep as