We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description, why join, what you'll do, what you'll need, required experience, preferred experience. We need to map to sections.
We should not repeat job title. No Job ID. Remove boilerplate.
We need to decide which sections to include.
We have content for About the role: description of company and opportunity. Could be under "About the role". Provide paragraph.
Responsibilities: "What You’ll Do" bullet list.
Requirements: maybe "What You’ll Need" includes required experience? Actually "What You’ll Need" includes product ownership, technical depth, etc. That's more like qualifications/skills. Required Experience list is separate.
We can have sections: About the role, Responsibilities, Qualifications (or Requirements), Skills, Preferred Experience (maybe as Skills?), Benefits? Not mentioned. Pay? Not mentioned. Schedule? Not mentioned (full-time given but not schedule details). So we should not include Benefits, Pay, Schedule unless present. The posting says Type: Full-time but that's not schedule detail like hours. We could maybe include Schedule as full-time? But rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It states Type: Full-time, which is schedule type. Might be considered schedule. However they said "do not create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Type: Full-time. So we could include a Schedule section with "Full-time". But they also said prefer few substantive sections over many thin ones. A schedule section with just "Full-time" might be thin. Might be better to omit schedule section because it's not detailed. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but we could still omit if we think it's too thin? The instruction: "Prefer a few substantive sections over many thin ones." So we could omit schedule if it's just a single line. I'd lean to omit schedule.
Benefits: not mentioned. Pay: not mentioned.
Thus sections: About the role, Responsibilities, Qualifications (or Requirements), Skills, Preferred Experience? Could combine qualifications and skills. But we have "What You’ll Need" which includes product ownership, technical depth, experimentation literacy, metric judgment, storytelling, stakeholder range, prioritization, adaptability, mentorship. Those are more like skills/qualifications. Then "Required Experience" list: 6-10+ years, 3+ years PM, SQL, modern data stack, experimentation program, defining company-level metrics, shipping internal platform products. Those are requirements/experience. Then "Preferred Experience" list.
We could have sections: About the role, Responsibilities, Requirements, Qualifications, Preferred Experience. Or combine Requirements and Qualifications. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use any of those that have content.
Thus we can have:
About the role
...
Responsibilities
Requirements
(from Required Experience)
Qualifications
(from What You’ll Need)
Preferred Experience
(from Preferred Experience)
We should not include Skills if we used Qualifications for skills. But we could also put Skills separate. However we have both Qualifications and Skills headings available; we could put skill-based items under Skills and experience-based under Qualifications. But the "What You’ll Need" includes both skill and experience? It's more like abilities. Could treat as Skills. Then Requirements as experience. Let's map:
Skills: product ownership over technical domain, technical depth (AI, SQL, DBT), experimentation literacy, metric judgment, storytelling, stakeholder range, prioritization under pressure, adaptability and speed, mentorship and team development.
Qualifications: 6-10+ years in data engineering, analytics, or data science; 3+ years as a product manager for data, analytics, or platform products; Strong SQL; Hands-on experience with modern data stack; Proven track record owning experimentation program end to end; Experience defining company-level metrics and driving adoption; Experience shipping internal platform products with real internal customers.
Preferred Experience: list.
Thus we have sections: About the role, Responsibilities, Skills, Qualifications, Preferred Experience.
We should not include Benefits, Pay, Schedule.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details. We need to capture all bullet points from each section.
Let's extract details.
About the role: The description includes location, type, company description, opportunity, why join bullet points. We need to preserve all substantive information. So we need to include location (Provo, UT), type Full-time, company description, opportunity description, why join bullet points (High-Growth Company, Massive Impact, Extreme Ownership, Mission-Driven Culture, Future of Streaming). Also maybe the link angel.com/watch. Should we include that? It's part of description. Yes preserve.
Thus About the role paragraph(s) could include multiple paragraphs. We'll use
for prose. Could break into multiple
but okay.
Responsibilities: "What You’ll Do" bullet list. Need to capture each bullet.
Let's list them:
- Build the Angel knowledge platform. One place to ask a question and get a real answer, grounded in our own systems: application and analytics data, infrastructure and Datadog, build and deploy history, Notion, Slack, and the general institutional knowledge that currently lives in people's heads. Own ingestion, retrieval quality, freshness, and permissions.
- Build evaluation loops. Create feedback loops to track questions and improve answer trust and accuracy. Make it quick and easy to get trusted data.
- Own the data pipelines end to end. Ingestion, warehouse, transformation layer, semantic models, BI, and activation. Every layer has a customer and you're accountable for all of them.
- Increase platform trustworthiness. Data quality, freshness, lineage, and clear ownership of data sources. Answers that nobody trusts are worse than no answers at all.
- Make one number mean one thing. Define and govern the metrics the company runs on (retention, conversion, watch time, Pay It Forward rate, theatrical ROI) so finance, product, and content stop bringing three versions of the same answer to the same meeting.
- Turn data into slate decisions. Partner with content, theatrical, and marketing to build the reporting that informs what we greenlight, where we open, and how we spend.
- Treat internal teams as customers. Interview them, prioritize their requests, and measure whether they can correctly answer their own questions using AI
- Level up the experimentation. Drive forward the A/B testing platform and the practices around it. Keep it fast to launch a test, hard to read it wrong, and normal to kill a feature that didn't work.
- Set the guardrails. Identity, permissions that respect existing access, data boundaries, audit trails, and a clear policy on what agents may touch. Especially for member data.
- Prioritize ruthlessly. Say no to the projects that won’t move the needle and yes to the models that better build our foundation and best serve the team. Make build-versus-buy calls with real numbers attached.
- Measure it. Adoption by team, success rate, time saved, cost per outcome. Report the numbers honestly, including the ones that say a project isn't working.
We need to preserve each bullet as
.
Skills: from "What You’ll Need" bullet list:
- Product ownership over a technical domain. You think like an owner of a platform, not a ticket router for analytics requests.
- Technical depth. Fluent in AI, SQL, DBT. Fluent in a conversation about warehouse cost, event schemas, and pipeline design.
- Experimentation literacy. You understand power, sample size, guardrail metrics, and the ways an A/B test lies to you.
- Metric judgment. You can take a fuzzy business question and turn it into a definition that survives contact with finance.
- Storytelling. You can take a messy analysis and land it as a one-page recommendation an executive acts on.
- Stakeholder range. You work as comfortably with data engineers as with a theatrical distribution lead or a CFO.
- Prioritization under pressure. You can hold a roadmap steady while a dozen teams each believe their request is urgent.
- Adaptability and speed. Comfort working in a fast-moving environment with evolving priorities and incomplete information.
- Mentorship and team development. You elevate team members through feedback, coaching, and shared standards.
Qualifications: from "Required Experience":
- 6-10+ years in data engineering, analytics, or data science
- 3+ years as a product manager for data, analytics, or platform products
- Strong SQL, used regularly and independently
- Hands-on experience with a modern data stack (cloud warehouse, transformation layer, BI or semantic layer)
- Proven track record owning an experimentation program end to end
- Experience defining company-level metrics and driving adoption of them
- Experience shipping internal platform products with real internal customers
Preferred Experience: from "Preferred Experience":
- Streaming, media, or subscription business experience
- Familiarity with recommendation systems, personalization, or audience segmentation
- Experience with dbt, a semantic layer, and modern BI tooling
- Experience with a dedicated experimentation platform
- Customer data platforms, identity resolution, or attribution across web, mobile, and TV
- Working knowledge of privacy regulation (GDPR, CCPA) and data governance practice
- Exposure to ML or AI enablement, including feature stores and model evaluation
- Background in box office, theatrical distribution, or direct-to-consumer funnel analytics
- Familiarity with Angel, the Angel Guild, and our body of work (films, series, and other projects).
We also have location and type: Provo, UT; Full-time.
We should include those in About the role maybe as a short paragraph.
Now produce HTML.
We must not include any markdown fences. Just raw HTML.
We'll produce:
About the role
Location: Provo, UT. Type: Full-time. Angel is changing the future of American entertainment and is one of the fastest-growing Distributors in America. Our rapidly expanding library of light-amplifying stories has grown 10x in under 2 years. Gone is the old model where the deepest pockets pick the stories we share. Angel restores choice to our 3+ million guild members and growing who decide what we produce, what we take to theaters, and most importantly what parents bring to their homes. Check out angel.com/watch. Opportunity: Angel runs on decisions that data should be making faster: which stories to greenlight, where to focus attention with theatrical campaigns, what a Guild member sees first when they open the app, and whether the thing we shipped last week actually worked. Today that data exists. It's spread across pipelines, dashboards, and the heads of many different people. We need a product manager who will turn it into a platform: one set of trusted data, one connected knowledge base, and high trust self-serve answers for every team that needs them. This is a high-ownership role. You'll guide the roadmap for the data team, define what awesome looks like, and work closely with the data pipelines to refine them. Why Join Angel? High-Growth Company: Angel is one of the fastest-growing media companies, with record-breaking independent theatrical releases and millions of streaming users worldwide. See our recent interview with Evan Shapiro. Massive Impact: Your work will shape how audiences experience the stories they love—and help amplify light around the globe. Extreme Ownership: We are a team of owners and entrepreneurs. This is your chance to operate like a startup founder inside a fast-scaling media company. Mission-Driven Culture: We strive to amplify light in everything we do. Join a team