Predicts Senior Analyst

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: THE POSITION: description: "Our roster has an opening with your name on it FanDuel is looking for a Senior Analyst to help us execute our Predicts commercial strategy & deliver critical consumer insights. You will be responsible for monitoring the business performance, spotting trends/criticalities, completing simple & complex analyses to inform business decisions, and report periodically to the leadership team. This is a highly collaborative role, and you will work closely with Product, Marketing, & Finance teams at FanDuel. A successful candidate will be a self-motivated and organized individual who can easily problem solve, who can make quick but well-informed decisions, and who can clearly present complex analyses. This is an exciting opportunity to help elevate a new product at a premier gaming company. In addition to the specific responsibilities outlined above, employees may be required to perform other such duties as assigned by the Company. This ensures operational flexibility and allows the Company to meet evolving business needs." THE GAME PLAN: list of responsibilities: "Support the creation of forecasts across customer acquisition and engagement Develop standardized reporting and monitor daily performance of FanDuel PredictsPerform custom analysis and experiments that uncover critical Predicts customer insights Analyze and recommend improvements to existing processes across various teams, including but not limited to Marketing, Product, Data Engineering, and Customer OperationsAnalyze & regularly report on the efficacy of promotions and marketing tacticsBecome an expert of FanDuel Predicts customer experience end to end (e.g. media, registration funnel, funding, odds, UX, promos, CS) and proactively look for opportunities to improve" THE STATS: qualifications: "3+ years’ experience working in an analytical, technical, consulting, or commercial field preferredBachelor's Degree in a highly numerate major (Math, Stats, Econ, etc.) or relevant experience in data and/or business analysisProficiency in SQL and Tableau/data visualization required, experience with Databricks preferredStrong analytical proficiency & Excel-based modeling skills, experience in statistical and experimentation methods preferredTrack record of transforming data into actionable insights and presentationsAbility to take initiative and produce results in a fast-paced environmentExperience working in real-money gaming, prediction market, or adjacent industry preferredKnowledge of and interest in sports & technology preferred; ability to quickly develop a deep understanding of the industry and company will be critical to success" About Fanduel: description of company. Might be considered "About the role"? Actually "About Fanduel" is company overview. Could be a section "About the company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We need sections: About the role (intro description), Responsibilities (list from THE GAME PLAN), Requirements (maybe "THE STATS" includes experience, degree, etc.), Qualifications (maybe overlapping), Skills (proficiency in SQL, Tableau, etc.), Benefits (from Player Benefits section), Pay (salary range), Schedule (maybe not present). There's no explicit schedule info. So we should not include Schedule unless present. Also Benefits: we have details about benefits. Pay: salary range $106,000 - $133,000 USD. We must not include placeholder like "commensurate with experience". We have actual salary range. We must not repeat job title as heading. We must not include boilerplate like EEO, legal, etc. Remove those paragraphs. We must preserve all substantive info. So we need to include details about benefits: health plans, PTO, bonus, 401k match, commuter benefits, pet insurance, etc. Also mention that benefits differ across location, role, level. Also mention short-term/long-term incentive compensation, cash bonuses, stock program participation, paid personal time off, 14 paid company holidays, paid sick time per state/federal law, Massachusetts lie detector test law. Also mention that they offer amazing benefits above basics, health plans as low as $0 per paycheck, fertility, mental health, fitness benefits. Also mention "check out all our benefits here: FanDuel Total Rewards." That's a link; we can keep as text. We must not include navigation/cookie etc. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... intro paragraph ...

Responsibilities

• Support the creation of forecasts across customer acquisition and engagement
• Develop standardized reporting and monitor daily performance of FanDuel Predicts
• Perform custom analysis and experiments that uncover critical Predicts customer insights
• Analyze and recommend improvements to existing processes across various teams, including but not limited to Marketing, Product, Data Engineering, and Customer Operations
• Analyze and regularly report on the efficacy of promotions and marketing tactics
• Become an expert of FanDuel Predicts customer experience end to end (e.g. media, registration funnel, funding, odds, UX, promos, CS) and proactively look for opportunities to improve

Note: The original had some run-on sentences without punctuation; we need to split appropriately. We need to ensure we preserve all substantive info: also mention monitoring business performance, spotting trends/criticalities, completing simple & complex analyses to inform business decisions, report periodically to leadership team, work closely with Product, Marketing, & Finance teams, self-motivated, organized, problem solve, quick but well-informed decisions, clearly present complex analyses, elevate new product, may perform other duties as assigned. Those are part of About the role or Responsibilities? The initial paragraph under THE POSITION includes those. We could incorporate them into About the role or Responsibilities. Since we have a Responsibilities section from THE GAME PLAN, we could also include the earlier duties in About the role. But we must not duplicate content. We can include them in About the role as prose. Thus About the role paragraph: combine the introductory sentences: "FanDuel is looking for a Senior Analyst to help us execute our Predicts commercial strategy & deliver critical consumer insights. You will be responsible for monitoring the business performance, spotting trends/criticalities, completing simple & complex analyses to inform business decisions, and report periodically to the leadership team. This is a highly collaborative role, and you will work closely with Product, Marketing, & Finance teams at FanDuel. A successful candidate will be a self-motivated and organized individual who can easily problem solve, who can make quick but well-informed decisions, and who can clearly present complex analyses. This is an exciting opportunity to help elevate a new product at a premier gaming company. In addition to the specific responsibilities outlined above, employees may be required to perform other such duties as assigned by the Company. This ensures operational flexibility and allows the Company to meet evolving business needs." That covers. Now Requirements: maybe we can combine "THE STATS" into Requirements and Qualifications and Skills. But we need to follow headings list. We could have:

Requirements

3+ years’ experience working in an analytical, technical, consulting, or commercial field preferred; Bachelor's Degree in a highly numerate major (Math, Stats, Econ, etc.) or relevant experience in data and/or business analysis.

Qualifications

Proficiency in SQL and Tableau/data visualization required, experience with Databricks preferred; Strong analytical proficiency & Excel-based modeling skills, experience in statistical and experimentation methods preferred; Track record of transforming data into actionable insights and presentations; Ability to take initiative and produce results in a fast-paced environment; Experience working in real-money gaming, prediction market, or adjacent industry preferred; Knowledge of and interest in sports & technology preferred; ability to quickly develop a deep understanding of the industry and company will be critical to success.

But we also have Skills: maybe we can separate SQL/Tableau etc. However we risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine Requirements and Qualifications into one section? But we have headings list; we can choose to include only those sections that have real content. We could include Requirements (experience/education), Skills (technical proficiencies), and maybe Qualifications (other attributes). However that's three sections; maybe okay. But we need to avoid thin sections. Let's see content: Requirements: experience + education. Qualifications: analytical proficiency, Excel, stats methods, track record, initiative, fast-paced, gaming experience, sports/tech interest. Skills: SQL, Tableau, Databricks. That seems reasonable. Alternatively we could merge Qualifications and Skills into one "Skills & Qualifications". But headings list doesn't have that combined. We could still use Skills heading for technical proficiencies, and Qualifications for other attributes. That seems fine. Now Benefits: we need to include all substantive benefits info. We need to exclude boilerplate like "FanDuel is an equal opportunities employer..." etc. Also remove the Massachusetts lie detector test law? That is legal info; might be considered boilerplate? It's a specific law statement; but it's still legal. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should remove the Massachusetts lie detector test law line as legal. Also remove the EEO paragraph. Also remove the accommodation request line? That's also legal/accommodation. Might be considered legal. Better to remove. We should keep benefits description: "We treat our team right We offer amazing benefits above and beyond the basics. We have an array of health plans to choose from (some as low as $0 per paycheck) that include programs for fertility and family planning, mental health support, and fitness benefits. We offer generous paid time off (PTO & sick leave), annual bonus and long-term incentive opportunities (based on performance), 401k with up to a 5% match, commuter benefits, pet insurance, and more - check out all our benefits here: FanDuel Total Rewards. *Benefits differ across location, role, and level." Also later: "This role may offer the following benefits: medical, vision, and dental insurance; life insurance; disability insurance; a 401(k) matching program; among other employee benefits. This role may also be eligible for short-term or long-term incentive compensation, including, but not limited to, cash bonuses and stock program participation. This role includes paid personal time off and 14 paid company holidays. FanDuel offers paid sick time in accordance with all applicable state and federal laws." We need to preserve all substantive info, so combine. We should not include the line about "check out all our benefits here: FanDuel Total Rewards." as a link but we can keep as text. Now Pay: we have salary range: $106,000 - $133,000 USD, dependent on factors. We should include that in Pay section. Schedule: none, so omit. Now ensure we don't repeat content. Let's craft HTML. We'll need to escape any HTML special characters? Not needed. We'll produce:

About the role

...

Responsibilities

...

Requirements

...

Skills

...

maybe list SQL, Tableau, Databricks.

Qualifications

...

Benefits

...

maybe list benefits.

Pay

...

Check for duplication: Ensure we didn't include same info twice. Let's extract