Applied Scientist, Responsible AI
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which content goes where.
About the role: maybe a paragraph summarizing mission and role.
Responsibilities: list bullet points.
Requirements: list bullet points (basic qualifications).
Qualifications: list bullet points (preferred qualifications).
Skills: maybe list programming languages? Could be under Requirements but we can create Skills section with list of languages: Java, C++, Python.
Benefits: list bullet points.
Pay: maybe a paragraph with salary range and sign-on/RSU.
Schedule: omit.
We must not create empty sections.
Let's craft.
First, About the role: combine mission and what you will do.
Paragraph: "We are Amazon's central Responsible AI team. Our mission is to advance the science and practice of Responsible AI (RAI) to enable Amazon's tens of thousands of builders to build and deploy AI solutions to the high standards that our customers and society expect. As a Scientist on this team, you will understand in depth the technical and scientific issues related to RAI, including controllability, security, privacy, safety, veracity, robustness, fairness, explainability, transparency, and governance; help define the strategies, priorities and metrics for RAI; solve open problems in RAI to unblock traditional, generative and/or agentic AI use cases and solutions, publishing as appropriate; help develop our team; and liaise with internal and external stakeholders, including the academic community, on issues related to RAI."
That's a paragraph.
Responsibilities: could be bullet list of the duties we just mentioned. But we already included them in paragraph. To avoid duplication, we could keep paragraph as About the role and then Responsibilities as bullet list of specific duties. However that would duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It's okay to have some overlap? Might be considered duplication but not prohibited. However better to split: About the role could be a brief overview, Responsibilities list the duties. But we need to ensure we don't lose any detail. We can keep overview in About the role and then list responsibilities in bullet form, but that repeats some details. Might be okay but could be considered summarizing away detail? Not really; we are just repeating. Safer to put all duties in Responsibilities and keep About the role as a short description of the team/mission. Let's do that.
About the role: short paragraph about team mission.
Responsibilities: bullet list of duties.
Requirements: bullet list of basic qualifications.
Qualifications: bullet list of preferred qualifications.
Skills: bullet list of programming languages (Java, C++, Python) and maybe ML tech areas? But those are in requirements. Could put programming languages under Skills.
Benefits: bullet list.
Pay: paragraph.
Now ensure we don't include any boilerplate like "Amazon is an equal opportunity employer..." etc. Remove those lines.
Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; could be considered navigation? It's a link to benefits page. Might be considered boilerplate? It's not EEO but it's a link. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not exactly navigation but could be considered navigation. Safer to omit the link and just keep the description.
Also remove "If you have a disability..." accommodation lines.
Remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner."
Remove "Amazon is an equal opportunity employer..." lines.
Remove "Our inclusive culture empowers Amazonians..." etc.
Now produce HTML.
Let's draft:
About the role
We are Amazon's central Responsible AI team. Our mission is to advance the science and practice of Responsible AI (RAI) to enable Amazon's tens of thousands of builders to build and deploy AI solutions to the high standards that our customers and society expect.
Responsibilities
- Understand in depth the technical and scientific issues related to RAI, including controllability, security, privacy, safety, veracity, robustness, fairness, explainability, transparency, and governance.
- Help define the strategies, priorities and metrics for RAI.
- Solve open problems in RAI to unblock traditional, generative and/or agentic AI use cases and solutions, publishing as appropriate.
- Help develop the team.
- Liaise with internal and external stakeholders, including the academic community, on issues related to RAI.
Requirements
- PhD, or Master's degree and 4+ years of CS, CE, ML or related field experience.
- Experience programming in Java, C++, Python or related language.
- Experience with one of the following areas: machine learning technologies, Reinforcement Learning, Deep Learning, Computer Vision, Natural Language Processing (NLP) or related applications.
Qualifications
- Experience prioritizing and delivering projects on time in a fast‑moving environment.
- Passion for responsibly building and operating complex AI/ML systems, with consideration for controllability, privacy, security, safety, veracity, robustness, fairness, explainability, transparency, and governance.
- Excellent verbal and written communication skills, with demonstrated ability to synthesize large amounts of complex data and communicate complex concepts effectively to internal and external stakeholders.
- Publication record on issues in responsible AI or related to responsible AI.
Skills
- Java
- C++
- Python
Benefits
- Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage)
- 401(k) matching
- Paid time off
- Parental leave
Pay
The base salary range for this position is $142,800.00 – $193,200.00 USD annually (Seattle, WA). The total package includes sign‑on payments and restricted stock units (RSUs). Final compensation is determined based on experience, qualifications, and location.
We omitted Schedule.
Check for any leftover boilerplate: none.
Check for duplicate content: we have programming languages listed both in Requirements and Skills. That's duplication but maybe acceptable. Could we move programming languages to Skills only and remove from Requirements? Requirements currently includes "Experience programming in Java, C++, Python or related language." If we remove that, we lose that requirement detail. We could keep it in Requirements and not duplicate in Skills, or keep Skills as a summary of languages. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be considered redundant. However better to avoid duplication: we can keep programming languages in Requirements and not have a separate Skills section, or we can keep Skills but remove from Requirements. Which is more appropriate? The requirement is about programming languages; we could treat that as a skill. So we could move it to Skills and remove from Requirements. But then Requirements would lose the programming language experience. However we could keep a generic statement: "Experience programming in Java, C++, Python or related language." That's substantive. If we move it to Skills, we still preserve it. So we can have Skills section list languages, and Requirements section can omit that line. Let's adjust.
Requirements: PhD/Master's + 4+ years experience; experience with ML tech areas.
Skills: Java, C++, Python.
Now check if we lost any other requirement: we still have the ML tech areas.
Now ensure we haven't missed any other substantive info: The description also mentions "help define the strategies, priorities
for prose. We need to decide which content goes where. About the role: maybe a paragraph summarizing mission and role. Responsibilities: list bullet points. Requirements: list bullet points (basic qualifications). Qualifications: list bullet points (preferred qualifications). Skills: maybe list programming languages? Could be under Requirements but we can create Skills section with list of languages: Java, C++, Python. Benefits: list bullet points. Pay: maybe a paragraph with salary range and sign-on/RSU. Schedule: omit. We must not create empty sections. Let's craft. First, About the role: combine mission and what you will do. Paragraph: "We are Amazon's central Responsible AI team. Our mission is to advance the science and practice of Responsible AI (RAI) to enable Amazon's tens of thousands of builders to build and deploy AI solutions to the high standards that our customers and society expect. As a Scientist on this team, you will understand in depth the technical and scientific issues related to RAI, including controllability, security, privacy, safety, veracity, robustness, fairness, explainability, transparency, and governance; help define the strategies, priorities and metrics for RAI; solve open problems in RAI to unblock traditional, generative and/or agentic AI use cases and solutions, publishing as appropriate; help develop our team; and liaise with internal and external stakeholders, including the academic community, on issues related to RAI." That's a paragraph. Responsibilities: could be bullet list of the duties we just mentioned. But we already included them in paragraph. To avoid duplication, we could keep paragraph as About the role and then Responsibilities as bullet list of specific duties. However that would duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It's okay to have some overlap? Might be considered duplication but not prohibited. However better to split: About the role could be a brief overview, Responsibilities list the duties. But we need to ensure we don't lose any detail. We can keep overview in About the role and then list responsibilities in bullet form, but that repeats some details. Might be okay but could be considered summarizing away detail? Not really; we are just repeating. Safer to put all duties in Responsibilities and keep About the role as a short description of the team/mission. Let's do that. About the role: short paragraph about team mission. Responsibilities: bullet list of duties. Requirements: bullet list of basic qualifications. Qualifications: bullet list of preferred qualifications. Skills: bullet list of programming languages (Java, C++, Python) and maybe ML tech areas? But those are in requirements. Could put programming languages under Skills. Benefits: bullet list. Pay: paragraph. Now ensure we don't include any boilerplate like "Amazon is an equal opportunity employer..." etc. Remove those lines. Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; could be considered navigation? It's a link to benefits page. Might be considered boilerplate? It's not EEO but it's a link. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not exactly navigation but could be considered navigation. Safer to omit the link and just keep the description. Also remove "If you have a disability..." accommodation lines. Remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Remove "Amazon is an equal opportunity employer..." lines. Remove "Our inclusive culture empowers Amazonians..." etc. Now produce HTML. Let's draft:
About the role
We are Amazon's central Responsible AI team. Our mission is to advance the science and practice of Responsible AI (RAI) to enable Amazon's tens of thousands of builders to build and deploy AI solutions to the high standards that our customers and society expect.
Responsibilities
- Understand in depth the technical and scientific issues related to RAI, including controllability, security, privacy, safety, veracity, robustness, fairness, explainability, transparency, and governance.
- Help define the strategies, priorities and metrics for RAI.
- Solve open problems in RAI to unblock traditional, generative and/or agentic AI use cases and solutions, publishing as appropriate.
- Help develop the team.
- Liaise with internal and external stakeholders, including the academic community, on issues related to RAI.
Requirements
- PhD, or Master's degree and 4+ years of CS, CE, ML or related field experience.
- Experience programming in Java, C++, Python or related language.
- Experience with one of the following areas: machine learning technologies, Reinforcement Learning, Deep Learning, Computer Vision, Natural Language Processing (NLP) or related applications.
Qualifications
- Experience prioritizing and delivering projects on time in a fast‑moving environment.
- Passion for responsibly building and operating complex AI/ML systems, with consideration for controllability, privacy, security, safety, veracity, robustness, fairness, explainability, transparency, and governance.
- Excellent verbal and written communication skills, with demonstrated ability to synthesize large amounts of complex data and communicate complex concepts effectively to internal and external stakeholders.
- Publication record on issues in responsible AI or related to responsible AI.
Skills
- Java
- C++
- Python
Benefits
- Health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage)
- 401(k) matching
- Paid time off
- Parental leave
Pay
The base salary range for this position is $142,800.00 – $193,200.00 USD annually (Seattle, WA). The total package includes sign‑on payments and restricted stock units (RSUs). Final compensation is determined based on experience, qualifications, and location.
We omitted Schedule. Check for any leftover boilerplate: none. Check for duplicate content: we have programming languages listed both in Requirements and Skills. That's duplication but maybe acceptable. Could we move programming languages to Skills only and remove from Requirements? Requirements currently includes "Experience programming in Java, C++, Python or related language." If we remove that, we lose that requirement detail. We could keep it in Requirements and not duplicate in Skills, or keep Skills as a summary of languages. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be considered redundant. However better to avoid duplication: we can keep programming languages in Requirements and not have a separate Skills section, or we can keep Skills but remove from Requirements. Which is more appropriate? The requirement is about programming languages; we could treat that as a skill. So we could move it to Skills and remove from Requirements. But then Requirements would lose the programming language experience. However we could keep a generic statement: "Experience programming in Java, C++, Python or related language." That's substantive. If we move it to Skills, we still preserve it. So we can have Skills section list languages, and Requirements section can omit that line. Let's adjust. Requirements: PhD/Master's + 4+ years experience; experience with ML tech areas. Skills: Java, C++, Python. Now check if we lost any other requirement: we still have the ML tech areas. Now ensure we haven't missed any other substantive info: The description also mentions "help define the strategies, priorities