Data Scientist, Research Intern, PhD, Summer 2027
for each section.
We need - for any list of duties/requirements/benefits.
We need
for prose.
Do not repeat job title as heading. The job title is "Data Scientist - Research". Not to be used as heading.
We need to preserve all substantive information, not invent.
Let's extract:
About the role: The paragraph starting "About The Job At Google, data drives all of our decision-making..." That's description. Could be About the role.
Responsibilities: bullet list after "Responsibilities". Actually there is a heading "Responsibilities" then a list of bullet points (starting with "Work with large complex data sets...").
Requirements: Minimum qualifications: list.
Qualifications: Preferred qualifications: list.
Skills: maybe not explicit separate; but we have experience with statistical methods, data analysis, R/Python, etc. Could be under Skills. But we can combine with Requirements? The instruction: Use sections only when posting has real specific content. We have Minimum qualifications and Preferred qualifications. Could treat them as Requirements and Qualifications. Skills maybe not separate; but we could still include Skills if we have explicit skill list. The posting includes "Experience with statistical methods (linear models, multivariate analysis, stochastic processes, sampling methods, etc.). Experience with data analysis. Experience using R or Python and technology to work with datasets such as scripting or statistical software (R, SAS, etc.)." That's skills. Could be under Skills.
Benefits: listed.
Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $118000 - $157000 (USD) + 0% bonus target". That's pay.
Schedule: Not mentioned. So we should not include Schedule section.
Also location info maybe not needed.
We need to remove boilerplate: application instructions, deadlines, EEO, etc.
Now produce HTML.
Structure:
About the role
... description ...
Responsibilities
- Work with large complex data sets, solve difficult non-routine analysis problems, and apply advanced analytical methods.
- Conduct analysis that includes data gathering and requirements specification, processing, analysis, ongoing deliverables, and presentations.
- Build and prototype analysis pipelines iteratively to provide insights at scale.
- Develop a comprehensive understanding of Google data structures and metrics, advocating for changes.
- Interact cross-functionally with a wide variety of people and teams.
- Work closely with engineers to identify opportunities, design and assess improvements to Google products.
- Make business recommendations (e.g., cost-benefit, forecasting, experiment analysis) with effective presentations of findings at multiple levels of stakeholders through visual displays of quantitative information.
- Research and develop analysis, forecasting, and optimization methods to improve the quality of Google's user products.
Requirements
- Currently pursuing a PhD degree in a quantitative discipline (e.g., statistics, biostatistics, physics, applied mathematics, operations research, economics).
- Experience with statistical methods (linear models, multivariate analysis, stochastic processes, sampling methods, etc.).
- Experience with data analysis.
- Experience using R or Python and technology to work with datasets such as scripting or statistical software (R, SAS, etc.).
Qualifications
- Currently attending a degree program in the US and available to work full time for 12 weeks outside of university term time.
- In their penultimate academic year or returning to a degree program after completion of the internship.
- Ability to draw conclusions from data and recommend actions.
- Ability to take on a leadership role and take initiative.
- Interest in learning new techniques.
Maybe Skills section could be separate but we already covered experience with statistical methods etc. Could be under Skills but we already have those in Requirements. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. Could combine Skills into Requirements or Qualifications. But we have separate Requirements and Qualifications already. Skills maybe not needed.
Benefits:
Benefits
- Health, dental, vision insurance
- Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
- Holidays: 13 paid days per year
Pay:
Pay
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $118000 - $157000 (USD) + 0% bonus target
We should not include Schedule.
Check for any other substantive content: The location list maybe could be considered under About the role? But it's not a section heading; we could include as a paragraph under About the role? The instruction: do not create sections unless posting has real specific content for it. Location list is specific but not under a heading. Could we add a paragraph under About the role? It might be considered part of About the role. However the instruction says "Prefer a few substantive sections over many thin ones." Adding location list as a paragraph under About the role is okay. But we need to decide if we should include it. The location list is substantive but not under a heading; we could incorporate it as a paragraph after the description. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." Location list is not minor metadata; it's about where the role may be located. Could be included as a paragraph under About the role.
But we must preserve ALL substantive information. So we should include location list somewhere. Where? Could be under About the role as a paragraph.
Let's extract location list: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Mountain View, CA, USA; Ann Arbor, MI, USA; Atlanta, GA, USA; Austin, TX, USA; Boulder, CO, USA; Bellevue, WA, USA; Cambridge, MA, USA; Chicago, IL, USA; Irvine, CA, USA; Kirkland, WA, USA; Los Angeles, CA, USA; Madison, WI, USA; New York, NY, USA; Palo Alto, CA, USA; Portland, OR, USA; Pittsburgh, PA, USA; Raleigh, NC, USA; Durham, NC, USA; Reston, VA, USA; Redmond, WA, USA; Redwood City, CA, USA; San Diego, CA, USA; Goleta, CA, USA; San Bruno, CA, USA; Seattle, WA, USA; San Francisco, CA, USA; San Jose, CA, USA; Santa Cruz, CA, USA; South San Francisco, CA, USA; Sunnyvale, CA, USA; Washington D.C., DC, USA."
Also earlier: "This role may also be located in our Playa Vista, CA campus." So include that.
We can add a paragraph under About the role after the description: "This role may also be located in our Playa Vista, CA campus. Applicants may indicate a preferred working location from the following list: ..." Then list.
We need to ensure we don't include boilerplate like "Participation in the internship program requires that you are located in the United States for the duration of the internship program." That's substantive? It's a requirement: must be located in US for duration. That's a requirement. Should we include under Requirements? It's a requirement. Yes, we should include that. Also "This internship is intended for students in their penultimate academic year, who are pursuing a PhD degree program in a quantitative discipline..." That's also a requirement but we already have similar. Might be duplicate. We need to preserve all substantive info, not invent or summarize away detail. So we need to include that requirement as well. However we already have "Currently pursuing a PhD degree in a quantitative discipline" and "In their penultimate academic year or returning to a degree program after completion of the internship." That covers. The location US requirement is separate.
Add to Requirements: "Must be located in the United States for the duration of the internship program."
Also "Participation in the internship program requires that you are located in the United States for the duration of the internship program." That's same.
Also "To start the application process, you will need an updated CV or resume and a current unofficial or official transcript in English." That's application instruction, should be removed per instruction: remove application instructions. So drop.
Also "Please ensure you’ve listed your anticipated graduation date (in MM/YY)" etc. Remove.
Also "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based Interns." That's part of benefits but we already have benefits. Could keep as part of benefits preamble but it's not needed; we can keep benefits list.
Also "Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act." etc. That's legal boilerplate; remove.
Also "Google is proud to be an equal opportunity workplace..." remove.
Now we need to ensure we didn't miss any substantive content: The description about Google being engineering company etc. That's part of About the role? The paragraph after "About The Job At Google, data drives all of our decision-making..." includes also later paragraphs about Google being engineering company etc. That's all part of the role description. We should include that entire prose under About the role.
Let's capture the About the role prose:
"About The Job At Google, data drives all of our decision-making. In the Data Scientist - Research role, you will work all across the organization to help shape Google's business and technical strategies by processing, analyzing, and interpreting huge data sets. Using analytical excellence and statistical methods, you will mine through data to identify opportunities for Google and our clients to operate more efficiently, from enhancing advertising efficacy to network infrastructure optimization to studying user behavior. You will work with Engineers, Product Managers, Sales Associates, and Marketing teams to adjust Google's practices according to your findings. Identifying the problem is only half the job; you also figure out the solution. Google is and always will be an engineering company. We hire people with a broad set of technical skills who are ready to address some of technology's greatest challenges and make an impact on millions, if not billions, of users. At Google, engineers not only revolutionize search, they routinely work on massive scalability and storage solutions, large-scale applications and entirely new platforms for developers around the world. From Google Ads to Chrome, Android to YouTube, Social to Local, Google engineers are changing the world one technological achievement after another."
That's the whole block. We'll put that in
.
Now responsibilities list we captured.
Requirements list: we need to include:
- Currently pursuing a PhD degree in a quantitative discipline (e.g., statistics, biostatistics, physics, applied mathematics, operations research, economics).
- Experience with statistical methods (linear models, multivariate analysis, stochastic processes,
for prose. Do not repeat job title as heading. The job title is "Data Scientist - Research". Not to be used as heading. We need to preserve all substantive information, not invent. Let's extract: About the role: The paragraph starting "About The Job At Google, data drives all of our decision-making..." That's description. Could be About the role. Responsibilities: bullet list after "Responsibilities". Actually there is a heading "Responsibilities" then a list of bullet points (starting with "Work with large complex data sets..."). Requirements: Minimum qualifications: list. Qualifications: Preferred qualifications: list. Skills: maybe not explicit separate; but we have experience with statistical methods, data analysis, R/Python, etc. Could be under Skills. But we can combine with Requirements? The instruction: Use sections only when posting has real specific content. We have Minimum qualifications and Preferred qualifications. Could treat them as Requirements and Qualifications. Skills maybe not separate; but we could still include Skills if we have explicit skill list. The posting includes "Experience with statistical methods (linear models, multivariate analysis, stochastic processes, sampling methods, etc.). Experience with data analysis. Experience using R or Python and technology to work with datasets such as scripting or statistical software (R, SAS, etc.)." That's skills. Could be under Skills. Benefits: listed. Pay: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $118000 - $157000 (USD) + 0% bonus target". That's pay. Schedule: Not mentioned. So we should not include Schedule section. Also location info maybe not needed. We need to remove boilerplate: application instructions, deadlines, EEO, etc. Now produce HTML. Structure:
About the role
... description ...
Responsibilities
- Work with large complex data sets, solve difficult non-routine analysis problems, and apply advanced analytical methods.
- Conduct analysis that includes data gathering and requirements specification, processing, analysis, ongoing deliverables, and presentations.
- Build and prototype analysis pipelines iteratively to provide insights at scale.
- Develop a comprehensive understanding of Google data structures and metrics, advocating for changes.
- Interact cross-functionally with a wide variety of people and teams.
- Work closely with engineers to identify opportunities, design and assess improvements to Google products.
- Make business recommendations (e.g., cost-benefit, forecasting, experiment analysis) with effective presentations of findings at multiple levels of stakeholders through visual displays of quantitative information.
- Research and develop analysis, forecasting, and optimization methods to improve the quality of Google's user products.
Requirements
- Currently pursuing a PhD degree in a quantitative discipline (e.g., statistics, biostatistics, physics, applied mathematics, operations research, economics).
- Experience with statistical methods (linear models, multivariate analysis, stochastic processes, sampling methods, etc.).
- Experience with data analysis.
- Experience using R or Python and technology to work with datasets such as scripting or statistical software (R, SAS, etc.).
Qualifications
- Currently attending a degree program in the US and available to work full time for 12 weeks outside of university term time.
- In their penultimate academic year or returning to a degree program after completion of the internship.
- Ability to draw conclusions from data and recommend actions.
- Ability to take on a leadership role and take initiative.
- Interest in learning new techniques.
Benefits
- Health, dental, vision insurance
- Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance
- Holidays: 13 paid days per year
Pay
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $118000 - $157000 (USD) + 0% bonus target
We should not include Schedule. Check for any other substantive content: The location list maybe could be considered under About the role? But it's not a section heading; we could include as a paragraph under About the role? The instruction: do not create sections unless posting has real specific content for it. Location list is specific but not under a heading. Could we add a paragraph under About the role? It might be considered part of About the role. However the instruction says "Prefer a few substantive sections over many thin ones." Adding location list as a paragraph under About the role is okay. But we need to decide if we should include it. The location list is substantive but not under a heading; we could incorporate it as a paragraph after the description. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." Location list is not minor metadata; it's about where the role may be located. Could be included as a paragraph under About the role. But we must preserve ALL substantive information. So we should include location list somewhere. Where? Could be under About the role as a paragraph. Let's extract location list: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Mountain View, CA, USA; Ann Arbor, MI, USA; Atlanta, GA, USA; Austin, TX, USA; Boulder, CO, USA; Bellevue, WA, USA; Cambridge, MA, USA; Chicago, IL, USA; Irvine, CA, USA; Kirkland, WA, USA; Los Angeles, CA, USA; Madison, WI, USA; New York, NY, USA; Palo Alto, CA, USA; Portland, OR, USA; Pittsburgh, PA, USA; Raleigh, NC, USA; Durham, NC, USA; Reston, VA, USA; Redmond, WA, USA; Redwood City, CA, USA; San Diego, CA, USA; Goleta, CA, USA; San Bruno, CA, USA; Seattle, WA, USA; San Francisco, CA, USA; San Jose, CA, USA; Santa Cruz, CA, USA; South San Francisco, CA, USA; Sunnyvale, CA, USA; Washington D.C., DC, USA." Also earlier: "This role may also be located in our Playa Vista, CA campus." So include that. We can add a paragraph under About the role after the description: "This role may also be located in our Playa Vista, CA campus. Applicants may indicate a preferred working location from the following list: ..." Then list. We need to ensure we don't include boilerplate like "Participation in the internship program requires that you are located in the United States for the duration of the internship program." That's substantive? It's a requirement: must be located in US for duration. That's a requirement. Should we include under Requirements? It's a requirement. Yes, we should include that. Also "This internship is intended for students in their penultimate academic year, who are pursuing a PhD degree program in a quantitative discipline..." That's also a requirement but we already have similar. Might be duplicate. We need to preserve all substantive info, not invent or summarize away detail. So we need to include that requirement as well. However we already have "Currently pursuing a PhD degree in a quantitative discipline" and "In their penultimate academic year or returning to a degree program after completion of the internship." That covers. The location US requirement is separate. Add to Requirements: "Must be located in the United States for the duration of the internship program." Also "Participation in the internship program requires that you are located in the United States for the duration of the internship program." That's same. Also "To start the application process, you will need an updated CV or resume and a current unofficial or official transcript in English." That's application instruction, should be removed per instruction: remove application instructions. So drop. Also "Please ensure you’ve listed your anticipated graduation date (in MM/YY)" etc. Remove. Also "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based Interns." That's part of benefits but we already have benefits. Could keep as part of benefits preamble but it's not needed; we can keep benefits list. Also "Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act." etc. That's legal boilerplate; remove. Also "Google is proud to be an equal opportunity workplace..." remove. Now we need to ensure we didn't miss any substantive content: The description about Google being engineering company etc. That's part of About the role? The paragraph after "About The Job At Google, data drives all of our decision-making..." includes also later paragraphs about Google being engineering company etc. That's all part of the role description. We should include that entire prose under About the role. Let's capture the About the role prose: "About The Job At Google, data drives all of our decision-making. In the Data Scientist - Research role, you will work all across the organization to help shape Google's business and technical strategies by processing, analyzing, and interpreting huge data sets. Using analytical excellence and statistical methods, you will mine through data to identify opportunities for Google and our clients to operate more efficiently, from enhancing advertising efficacy to network infrastructure optimization to studying user behavior. You will work with Engineers, Product Managers, Sales Associates, and Marketing teams to adjust Google's practices according to your findings. Identifying the problem is only half the job; you also figure out the solution. Google is and always will be an engineering company. We hire people with a broad set of technical skills who are ready to address some of technology's greatest challenges and make an impact on millions, if not billions, of users. At Google, engineers not only revolutionize search, they routinely work on massive scalability and storage solutions, large-scale applications and entirely new platforms for developers around the world. From Google Ads to Chrome, Android to YouTube, Social to Local, Google engineers are changing the world one technological achievement after another." That's the whole block. We'll put that in
. Now responsibilities list we captured. Requirements list: we need to include: - Currently pursuing a PhD degree in a quantitative discipline (e.g., statistics, biostatistics, physics, applied mathematics, operations research, economics). - Experience with statistical methods (linear models, multivariate analysis, stochastic processes,