Senior Research Data Scientist
for each section heading. Use - for lists. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove the lines about providing information, privacy notice, etc. Also remove "Accommodations" maybe keep? It's substantive: Roku welcomes applicants... Provide accommodation contact. That's substantive, keep.
We need to decide which sections to include based on content.
Let's parse the posting:
- Intro paragraph about Roku mission etc. Could be part of About the team? Actually there is "About the team" heading later. The intro before that is generic company description. Could be part of About the team or maybe a separate "About Roku"? Not specified as a heading. We could include it under About the team as prose, or create a separate section like "About Roku". But the instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those as examples, but we can also use other headings if they appear in posting. The posting has headings: "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?", "Accommodations", "What should I know about Roku's culture?" Also there is "For New York Only - The estimated annual base salary..." which we can put under Pay.
We should keep those headings as
. Also we might combine some if they are thin, but they have substantive content.
We need to output only HTML fragment, no markdown fences.
Let's extract content for each section.
First, "About the team": The paragraph after that heading: "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."
We should keep that as
.
Second, "About the role": Paragraph: "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."
Third, "What you'll be doing": bullet list of duties. Let's extract each line:
- 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'll put these in
- .
Fourth, "We're excited if you have": list of qualifications.
- 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
We'll put in
.
Fifth, "What's Roku's approach to hybrid working?": 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."
We'll put as under Schedule heading? Actually heading is that question; we could use that as heading. But instruction says use headings like Schedule. However we can still use that exact heading as
. It's okay. We'll keep the heading as is.
Sixth, "What are some of the benefits?": paragraph: "Roku is committed to offering a diverse range of benefits as part of our compensation package to support our employees and their families. Our comprehensive benefits include 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. It's important to note that not every benefit is available in all locations or for every role. For details specific to your location, please consult with your recruiter."
Additionally earlier they listed: "This role is eligible for health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, and paid time off." That is more specific. We should include that as part of Benefits. Could combine.
We'll create a Benefits section with listing those specific benefits: health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, paid time off. Also mention global access to mental health and financial wellness support, etc. Could be prose.
We'll keep the paragraph as and then maybe a
for the specific list.
Seventh, "Accommodations": paragraph: "Roku welcomes applicants of all backgrounds and provides reasonable accommodations and adjustments in accordance with applicable law. If you require reasonable accommodation at any point in the hiring process, please direct your inquiries to EmployeeRelations@Roku.com."
We'll keep as .
Eighth, "What should I know about Roku's culture?": paragraph: multiple sentences. We'll keep as
.
Also we need Pay section: "For New York Only - The estimated annual base salary for this position is between $217,000 - $303,200. Compensation packages are based on factors unique to each candidate, including but not limited to skill set, certifications, and specific geographical location." We'll put as
under Pay heading.
Also maybe we need to include the earlier line about "This role is eligible for health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, and paid time off." Already in Benefits.
We should not include duplicated lines. Ensure we don't include boilerplate like "By providing your information..." etc.
Now construct HTML.
We'll start with
About the team
then ...
Then About the role
...
Then What you'll be doing
- ...
Then We're excited if you have
- ...
Then What's Roku's approach to hybrid working?
...
Then Pay
For New York Only - The estimated annual base salary for this position is between $217,000 - $303,200. Compensation packages are based on factors unique to each candidate, including but not limited to skill set, certifications, and specific geographical location.
Then Benefits
Roku is committed to offering a diverse range of benefits as part of our compensation package to support our employees and their families. Our comprehensive benefits include 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. It's important to note that not every benefit is available in all locations or for every role. For details specific to your location, please consult with your recruiter.
- health insurance
- equity awards
- life insurance
- disability benefits
- parental leave
- wellness benefits
- paid time off
Then Accommodations
Roku welcomes applicants of all backgrounds and provides reasonable accommodations and adjustments in accordance with applicable law. If you require reasonable accommodation at any point in the hiring process, please direct your inquiries to EmployeeRelations@Roku.com.
Then What should I know about Roku's culture?
Roku is a great place for people who want to work in a fast-paced environment where everyone is focused on the company's success rather than their own. We try to surround ourselves with people who are great at their jobs, who are easy to work with, and who keep their egos in check. We appreciate a sense of humor. We believe a fewer number of very talented folks can do more for less cost than a larger number of less talented teams. We're independent thinkers with big ideas who act boldly, move fast and accomplish extraordinary things through collaboration and trust. In short, at Roku you'll be part of a company that's changing how the world watches TV. We have a unique culture that we are proud of. We think of ourselves primarily as problem-solvers, which itself is a two-part idea. We come up with
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove the lines about providing information, privacy notice, etc. Also remove "Accommodations" maybe keep? It's substantive: Roku welcomes applicants... Provide accommodation contact. That's substantive, keep. We need to decide which sections to include based on content. Let's parse the posting: - Intro paragraph about Roku mission etc. Could be part of About the team? Actually there is "About the team" heading later. The intro before that is generic company description. Could be part of About the team or maybe a separate "About Roku"? Not specified as a heading. We could include it under About the team as prose, or create a separate section like "About Roku". But the instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those as examples, but we can also use other headings if they appear in posting. The posting has headings: "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?", "Accommodations", "What should I know about Roku's culture?" Also there is "For New York Only - The estimated annual base salary..." which we can put under Pay. We should keep those headings as
. Also we might combine some if they are thin, but they have substantive content. We need to output only HTML fragment, no markdown fences. Let's extract content for each section. First, "About the team": The paragraph after that heading: "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." We should keep that as
. Second, "About the role": Paragraph: "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." Third, "What you'll be doing": bullet list of duties. Let's extract each line: - 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'll put these in
- .
Fourth, "We're excited if you have": list of qualifications.
- 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
We'll put in
- .
Fifth, "What's Roku's approach to hybrid working?": 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."
We'll put as
- ...
- ...
- health insurance
- equity awards
- life insurance
- disability benefits
- parental leave
- wellness benefits
- paid time off
under Schedule heading? Actually heading is that question; we could use that as heading. But instruction says use headings like Schedule. However we can still use that exact heading as
. It's okay. We'll keep the heading as is. Sixth, "What are some of the benefits?": paragraph: "Roku is committed to offering a diverse range of benefits as part of our compensation package to support our employees and their families. Our comprehensive benefits include 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. It's important to note that not every benefit is available in all locations or for every role. For details specific to your location, please consult with your recruiter." Additionally earlier they listed: "This role is eligible for health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, and paid time off." That is more specific. We should include that as part of Benefits. Could combine. We'll create a Benefits section with
- listing those specific benefits: health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, paid time off. Also mention global access to mental health and financial wellness support, etc. Could be prose.
We'll keep the paragraph as
and then maybe a
- for the specific list.
Seventh, "Accommodations": paragraph: "Roku welcomes applicants of all backgrounds and provides reasonable accommodations and adjustments in accordance with applicable law. If you require reasonable accommodation at any point in the hiring process, please direct your inquiries to EmployeeRelations@Roku.com."
We'll keep as
. Eighth, "What should I know about Roku's culture?": paragraph: multiple sentences. We'll keep as
. Also we need Pay section: "For New York Only - The estimated annual base salary for this position is between $217,000 - $303,200. Compensation packages are based on factors unique to each candidate, including but not limited to skill set, certifications, and specific geographical location." We'll put as
under Pay heading. Also maybe we need to include the earlier line about "This role is eligible for health insurance, equity awards, life insurance, disability benefits, parental leave, wellness benefits, and paid time off." Already in Benefits. We should not include duplicated lines. Ensure we don't include boilerplate like "By providing your information..." etc. Now construct HTML. We'll start with
About the team
then...
ThenAbout the role
...
ThenWhat you'll be doing
We're excited if you have
What's Roku's approach to hybrid working?
...
ThenPay
For New York Only - The estimated annual base salary for this position is between $217,000 - $303,200. Compensation packages are based on factors unique to each candidate, including but not limited to skill set, certifications, and specific geographical location.
ThenBenefits
Roku is committed to offering a diverse range of benefits as part of our compensation package to support our employees and their families. Our comprehensive benefits include 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. It's important to note that not every benefit is available in all locations or for every role. For details specific to your location, please consult with your recruiter.
Accommodations
Roku welcomes applicants of all backgrounds and provides reasonable accommodations and adjustments in accordance with applicable law. If you require reasonable accommodation at any point in the hiring process, please direct your inquiries to EmployeeRelations@Roku.com.
ThenWhat should I know about Roku's culture?
Roku is a great place for people who want to work in a fast-paced environment where everyone is focused on the company's success rather than their own. We try to surround ourselves with people who are great at their jobs, who are easy to work with, and who keep their egos in check. We appreciate a sense of humor. We believe a fewer number of very talented folks can do more for less cost than a larger number of less talented teams. We're independent thinkers with big ideas who act boldly, move fast and accomplish extraordinary things through collaboration and trust. In short, at Roku you'll be part of a company that's changing how the world watches TV. We have a unique culture that we are proud of. We think of ourselves primarily as problem-solvers, which itself is a two-part idea. We come up with