Senior Research Data Scientist

We need to output HTML fragment with sections: About the team, About the role, What you'll be doing, We're excited if you have, What's Roku's approach to hybrid working?, What are some of the benefits?, maybe Pay section (salary range), Benefits already covered. Also include maybe "About the team" and "About the role". Also include "What you'll be doing" as responsibilities. Also "We're excited if you have" as qualifications/requirements. Also "What's Roku's approach to hybrid working?" could be Schedule? Actually schedule/hybrid working. Could be a Schedule section. Also "What are some of the benefits?" Benefits section. We must not repeat job title. No Job ID. Remove boilerplate like EEO, scam warning, application instructions, privacy notice, etc. Also remove duplicated lines. We need to preserve all substantive information. So we need to include the salary range for CA, NY, MA. Also mention compensation package includes health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, paid time off. Also mention benefits details later. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must only include sections when posting has real specific content. So we will include: - About the team - About the role - What you'll be doing (Responsibilities) - We're excited if you have (Qualifications/Requirements) - What's Roku's approach to hybrid working? (Schedule) - What are some of the benefits? (Benefits) - Pay (salary range) maybe as its own section. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. We need to preserve all substantive info: include details about role, responsibilities, qualifications, hybrid work, benefits, salary. Let's extract content. From posting: Teamwork makes the stream work. Roku is changing how the world watches TV... (intro). Not needed as heading? Could be part of About the team? Actually "About the team" heading appears later. The intro paragraphs before "About the team" are generic company description. Could be included as part of About the team? But we have a specific "About the team" section later. We could keep the intro as part of About the team? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the team as a heading? Not listed but we can still use it as heading? The examples are not exhaustive; they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use About the team as heading as well. It's a section heading. Thus:

  About the team

  then paragraph(s) describing team. Then

  About the role

  then paragraph. Then

  What you'll be doing

  then list of duties as
  • . Then

    We're excited if you have

    then list of qualifications as
    • . Then

      What's Roku's approach to hybrid working?

      then paragraph. Then

      What are some of the benefits?

      then list of benefits as
      • . Then

        Pay

        then paragraph with salary range and note about compensation package. We must not include duplicated lines. Ensure we don't repeat the same sentences. Let's extract each section content. **About the team**: From text: "Our Data Science team is a high-impact research team actively shaping the future of TV, using Big Data to build and enhance the user experience on the Roku streaming platform. Our production-ready machine learning models and statistical solutions optimize the user experience across all of Roku's core business models and products, and our scientists engage closely with business, product, and engineering leaders to make material and measurable impacts on the success and growth of the platform." Also earlier: "From your first day at Roku, you'll make a valuable - and valued - contribution. We're a fast-growing public company where no one is a bystander. We offer you the opportunity to delight millions of TV streamers around the world while gaining meaningful experience across a variety of disciplines." That's more generic but could be part of About the team? Actually it's before About the team heading. Might be considered part of About the team? But we can include it as part of About the team paragraph. Thus combine: "From your first day at Roku, you'll make a valuable - and valued - contribution. We're a fast-growing public company where no one is a bystander. We offer you the opportunity to delight millions of TV streamers around the world while gaining meaningful experience across a variety of disciplines. Our Data Science team is a high-impact research team actively shaping the future of TV, using Big Data to build and enhance the user experience on the Roku streaming platform. Our production-ready machine learning models and statistical solutions optimize the user experience across all of Roku's core business models and products, and our scientists engage closely with business, product, and engineering leaders to make material and measurable impacts on the success and growth of the platform." **About the role**: Text: "As a Senior Research Data Scientist on Roku's Data Science team, you will lead the development of a best-in-class causal inference platform that measures and optimizes the true incremental impact of customer actions, product features, and business interventions on long-term outcomes. Partnering with the Customer Growth organization, you will build the methods and systems that enable Roku to make high-confidence decisions from observational data when randomized experiments are not feasible. You will own the full lifecycle of causal measurement—from gathering business requirements and defining estimation approaches, to partnering with Engineering to productionize scalable causal pipelines and communicating findings to senior leadership. Your work will directly inform growth, retention, and monetization strategy across the platform, making this role ideal for an applied economist or econometrician who excels at the intersection of rigorous research and production engineering. This is someone equally comfortable deriving identification strategies and building estimators on terabyte-scale data." **What you'll be doing** (Responsibilities): List: - Design, build, and productionize a causal inference platform that standardizes how Roku measures the incremental impact of customer actions and business decisions - Research and implement causal estimation methods, including heterogeneous treatment effects, tailored to Roku's data and business questions - Build long-term outcome frameworks that enable impact projection from limited observation windows - Develop diagnostic and validation standards at scale to ensure credibility of causal estimates - Leverage AI to create counterfactual scenarios and build tools that help users run, understand, and act on causal estimates correctly - Work cross-functionally with Data Engineering, Product Management, and Core Analytics to translate business questions into well-defined causal problems and deploy production-ready solutions - Contribute to the technical vision of the Data Science team and the broader research agenda across causal inference, predictive modeling, and experimentation **We're excited if you have** (Qualifications/Requirements): List: - PhD in Economics, Econometrics, Statistics, or a closely related quantitative field with a strong emphasis on causal inference - 10+ years of experience applying causal inference and machine learning methods to real-world problems, with a demonstrated track record of measurable impact - Deep expertise in observational causal methods such as propensity score matching, Double Machine Learning, doubly robust estimation, instrumental variables, and difference-in-differences - Experience building reusable causal inference tools or platforms beyond one-off analyses - Proficiency with Spark, Ray, SQL, Python, and ML frameworks such as scikit-learn, XGBoost, and LightGBM - Experience with terabyte- or petabyte-scale datasets in distributed computing environments - Strong communication skills with the ability to translate econometric findings into clear business recommendations - Technology industry experience; connected TV, streaming, or advertising experience is a plus **What's Roku's approach to hybrid working?** (Schedule): Paragraph: "Roku fosters an inclusive and collaborative environment where teams generally work in the office Monday through Thursday. Fridays are generally flexible for remote work, except for employees whose specific roles or assigned office location require five days' a week attendance." **What are some of the benefits?** (Benefits): List: - Global access to mental health and financial wellness support and resources - Local benefits include statutory and voluntary benefits which may include healthcare (medical, dental, and vision), life, accident, disability, commuter, and retirement options (401(k)/pension) - Employees are supported in taking time off, in accordance with local leave policies and other personal needs to support their evolving work and life needs - Note: not every benefit is available in all locations or for every role. Also earlier: "This role is eligible for health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, and paid time off." That's also benefits. Should we include that? Yes, it's part of benefits. Could combine. Thus benefits list could include: health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, paid time off, plus the later list. We need to avoid duplication but can combine. Let's create a combined list: - Health insurance - Equity awards - Life insurance - Disability benefits - Parental leave - Wellness benefits - Paid time off - Global access to mental health and financial wellness support and resources - Local benefits including healthcare (medical, dental, and vision), life, accident, disability, commuter, and retirement options (401(k)/pension) - Support for taking time off per local leave policies and personal needs Note: Not every benefit available in all locations. **Pay** section: Paragraph: "For California, New York, and Massachusetts only - The estimated annual base salary for this position is between $330,000- $375,000 annually. Compensation packages are based on factors unique to each candidate, including but not limited to skill set, certifications, and specific geographical location. This role is eligible for health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, and paid time off." But we already listed benefits; we might not repeat eligibility. However we can keep salary range and note that compensation packages based on factors. We should not repeat benefits list again; but we can mention eligibility briefly. However the instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the sentence about eligibility. It's okay to repeat some info if it's in original; but we should avoid duplication if possible. However we already have benefits section listing those items; repeating eligibility may be considered duplication but it's still substantive. Might be okay to keep both. But we could incorporate eligibility into benefits section: mention that this role is eligible for those benefits. However the benefits section already lists them; we could add a note that this role is eligible for them. That's not duplication but adds info. Thus benefits section could have a preamble: "This role is eligible for health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, and paid time off." Then list other benefits. Let's do that. Now produce HTML. We must not include or . Just fragment. Let's craft:

        About the team

        From your first day at Roku, you'll make a valuable - and valued - contribution. We're a fast-growing public company where no one is a bystander. We offer you the opportunity to delight millions of TV streamers around the world while gaining meaningful experience across a variety of disciplines. Our Data Science team is a high-impact research team actively shaping the future of TV, using Big Data to build and enhance the user experience on the Roku streaming platform. Our production-ready machine learning models and statistical solutions optimize the user experience across all of Roku's core business models and products, and our scientists engage closely with business, product, and engineering leaders to make material and measurable impacts on the success and growth of the platform.