Applied Science Manager, Fleet Autonomy, Amazon Robotics
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info; not invent or summarize away detail. So we need to include all details from description, responsibilities, day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay.
We must not include boilerplate like EEO, accommodation link, etc. Also remove duplicated lines.
We need to decide what goes where.
Section headings:
- About the role: could be the initial description paragraph: "We are seeking an Applied Science Manager to lead the team that invents how our autonomous mobile robot fleet thinks - from how robots negotiate shared space to adapting fleet behavior as tasks and deadlines change. This is a rare opportunity to own the evolution of multi-robot coordination in free space at an unprecedented scale. Proteus is Amazon's first fully autonomous mobile robot and navigates freely alongside people in our fulfillment centers, perceiving its environment and making decisions in real time. The fleet is growing quickly in scale, diversity, and intelligence, with thousands of robots deployed and new platforms including mobile manipulation entering the mix. The science challenge is making a diverse, heterogeneous fleet perform reliably in a world that changes constantly — where priorities shift hour to hour, new capabilities come online, and operational conditions create new constraints. Your team will own algorithms at multiple layers of this system: how groups of robots autonomously coordinate through intersections and corridors, how fleet traffic is shaped across the road network, which tasks are assigned to which robots and when, and a new fleet orchestration layer that interacts directly with Operations to take in requests, collaborate to solve complex operational challenges, and adapt fleet performance and behavior on the fly. Whether you've been leading a research team in industry and want a bigger canvas, or you've been driving impactful academic research in close partnership with industry and are ready to make the leap, this is a role where your ideas become fleets of robots, and those robots deliver for hundreds of millions of customers."
That's substantive.
- Responsibilities: "Key job responsibilities" bullet list: Set the technical vision and research agenda; identify the right problems and sequence bets across near-term production needs and long-horizon research; Build, hire, and develop a team of applied scientists; provide scientific mentorship and grow careers; Drive algorithms from research through production deployment in partnership with engineering; Represent the team externally through publications, academic collaborations, and community engagement.
We should keep each as
- .
- About The Team: maybe could be part of About the role? But we have a separate section "About The Team". Could treat as "About the Team" heading. The content: "You would join a multi-disciplinary science organization with deep expertise in planning, optimization, machine learning, and robotics — working at the frontier of multi-robot coordination where scale, diversity, and dynamism intersect. Our algorithms ship to real robots within months of conception, and we learn from the operational data they generate. We maintain active academic collaborations and contribute to the research community through publications, workshops, and open problems."
We could put that under "About the Team" heading. However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list About the Team. But we can still include if posting has real specific content? The instruction says: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." We could combine About the Team into About the role or maybe omit separate heading. However we need to preserve all substantive info; we could include About the Team content under About the role heading as additional paragraphs. That would keep sections fewer. But we must not lose info. So we could merge About the Team into About the role.
Similarly "A day in the life" could be part of About the role or Responsibilities? It describes typical activities; could be part of About the role. We'll incorporate.
Thus sections: About the role (includes description, day in the life, about the team). Responsibilities (list). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills (maybe programming languages etc). Benefits (benefits description). Pay (salary range). No Schedule.
We need to decide what goes into Skills: The posting mentions "Experience programming in Java, C++, Python or related language", "Experience building machine learning models or developing algorithms for business application", "Strong understanding of autonomous mobile robots and how they navigate". Also maybe "Experience deploying robotic systems into the field". Those could be considered skills. We'll put them under Skills as list.
Requirements (Basic Qualifications) list: PhD in engineering, technology, computer science, machine learning, robotics, operations research, statistics, mathematics or equivalent quantitative field; 5+ years of industry or academic research experience; 2+ years of scientists or machine learning engineers management experience; Experience programming in Java, C++, Python or related language; Experience building machine learning models or developing algorithms for business application; Strong understanding of autonomous mobile robots and how they navigate; Experience deploying robotic systems into the field.
But note some of those overlap with Skills. To avoid duplication, we could keep Requirements as the basic qualifications list (including PhD, years experience, management experience). Skills could be the technical skills (programming languages, ML models, robotics understanding, deployment). However the basic qualifications also include programming experience etc. To avoid duplication, we could split: Requirements: PhD, 5+ years research, 2+ years management. Skills: programming languages, ML models, robotics navigation, deployment. Preferred Qualifications: list of preferred items.
We must preserve all info; not lose any. So we need to ensure each piece appears somewhere.
Let's extract:
Basic Qualifications:
- PhD in engineering, technology, computer science, machine learning, robotics, operations research, statistics, mathematics or equivalent quantitative field
- 5+ years of industry or academic research experience
- 2+ years of scientists or machine learning engineers management experience
- Experience programming in Java, C++, Python or related language
- Experience building machine learning models or developing algorithms for business application
- Strong understanding of autonomous mobile robots and how they navigate
- Experience deploying robotic systems into the field
Preferred Qualifications:
- Experience building complex software systems, especially involving deep learning, machine learning and computer vision, that have been successfully delivered to customers
- Experience with mobile robot fleets in industrial or logistics settings
- Experience developing computationally efficient decision making algorithms for live production systems
Benefits: comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and 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, and parental leave. Also mention sign-on payments and restricted stock units (RSUs). Also link to benefits page (but we should remove links? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link might be considered navigation? It's a link to benefits page. Might be considered navigation? Safer to remove the URL but keep description. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The benefits link is not exactly those, but it's a link. Might be considered navigation. Safer to omit the URL but keep the text "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; could be considered navigation. I'd remove the URL and just keep "Learn more about our benefits." But that might be considered boilerplate? Not sure. Safer to keep the sentence but maybe drop the URL. The instruction says remove navigation; a link is navigation. So we should remove the URL. Keep the phrase "Learn more about our benefits." That's still a bit generic but okay.
Pay: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. USA, MA, N.Reading - 183,800.00 - 248,700.00 USD annually". Also mention Company - Amazon.com LLC but we shouldn't repeat job title; company maybe not needed. We'll include salary range and mention sign-on payments and RSUs.
We must not include Job ID.
Now produce HTML.
Structure:
About the role
... (combined description, day in the life, about the team)
Responsibilities
- Set the technical vision and research agenda; identify the right problems and sequence bets across near-term production needs and long-horizon research
- Build, hire, and develop a team of applied scientists; provide scientific mentorship and grow careers
- Drive algorithms from research through production deployment in partnership with engineering
- Represent the team externally through publications, academic collaborations, and community engagement
Requirements
- PhD in engineering, technology, computer science, machine learning, robotics, operations research, statistics, mathematics or equivalent quantitative field
- 5+ years of industry or academic research experience
- 2+ years of scientists or machine learning engineers management experience
Skills
- Experience programming in Java, C++, Python or related language
- Experience building machine learning models or developing algorithms for business application
- Strong understanding of autonomous mobile robots and how they navigate
- Experience deploying robotic systems into the field
Qualifications
- Experience building complex software systems, especially involving deep learning, machine learning and computer vision, that have been successfully delivered to customers
- Experience with mobile robot fleets in industrial or logistics settings
- Experience developing computationally efficient decision making algorithms for live production systems
Benefits
Comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and 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, and parental leave. Sign-on payments and restricted stock units (RSUs) are part of the compensation package. Learn more about our
for prose. We must preserve all substantive info; not invent or summarize away detail. So we need to include all details from description, responsibilities, day in the life, about the team, basic qualifications, preferred qualifications, benefits, pay. We must not include boilerplate like EEO, accommodation link, etc. Also remove duplicated lines. We need to decide what goes where. Section headings: - About the role: could be the initial description paragraph: "We are seeking an Applied Science Manager to lead the team that invents how our autonomous mobile robot fleet thinks - from how robots negotiate shared space to adapting fleet behavior as tasks and deadlines change. This is a rare opportunity to own the evolution of multi-robot coordination in free space at an unprecedented scale. Proteus is Amazon's first fully autonomous mobile robot and navigates freely alongside people in our fulfillment centers, perceiving its environment and making decisions in real time. The fleet is growing quickly in scale, diversity, and intelligence, with thousands of robots deployed and new platforms including mobile manipulation entering the mix. The science challenge is making a diverse, heterogeneous fleet perform reliably in a world that changes constantly — where priorities shift hour to hour, new capabilities come online, and operational conditions create new constraints. Your team will own algorithms at multiple layers of this system: how groups of robots autonomously coordinate through intersections and corridors, how fleet traffic is shaped across the road network, which tasks are assigned to which robots and when, and a new fleet orchestration layer that interacts directly with Operations to take in requests, collaborate to solve complex operational challenges, and adapt fleet performance and behavior on the fly. Whether you've been leading a research team in industry and want a bigger canvas, or you've been driving impactful academic research in close partnership with industry and are ready to make the leap, this is a role where your ideas become fleets of robots, and those robots deliver for hundreds of millions of customers." That's substantive. - Responsibilities: "Key job responsibilities" bullet list: Set the technical vision and research agenda; identify the right problems and sequence bets across near-term production needs and long-horizon research; Build, hire, and develop a team of applied scientists; provide scientific mentorship and grow careers; Drive algorithms from research through production deployment in partnership with engineering; Represent the team externally through publications, academic collaborations, and community engagement. We should keep each as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." We could combine About the Team into About the role or maybe omit separate heading. However we need to preserve all substantive info; we could include About the Team content under About the role heading as additional paragraphs. That would keep sections fewer. But we must not lose info. So we could merge About the Team into About the role.
Similarly "A day in the life" could be part of About the role or Responsibilities? It describes typical activities; could be part of About the role. We'll incorporate.
Thus sections: About the role (includes description, day in the life, about the team). Responsibilities (list). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills (maybe programming languages etc). Benefits (benefits description). Pay (salary range). No Schedule.
We need to decide what goes into Skills: The posting mentions "Experience programming in Java, C++, Python or related language", "Experience building machine learning models or developing algorithms for business application", "Strong understanding of autonomous mobile robots and how they navigate". Also maybe "Experience deploying robotic systems into the field". Those could be considered skills. We'll put them under Skills as list.
Requirements (Basic Qualifications) list: PhD in engineering, technology, computer science, machine learning, robotics, operations research, statistics, mathematics or equivalent quantitative field; 5+ years of industry or academic research experience; 2+ years of scientists or machine learning engineers management experience; Experience programming in Java, C++, Python or related language; Experience building machine learning models or developing algorithms for business application; Strong understanding of autonomous mobile robots and how they navigate; Experience deploying robotic systems into the field.
But note some of those overlap with Skills. To avoid duplication, we could keep Requirements as the basic qualifications list (including PhD, years experience, management experience). Skills could be the technical skills (programming languages, ML models, robotics understanding, deployment). However the basic qualifications also include programming experience etc. To avoid duplication, we could split: Requirements: PhD, 5+ years research, 2+ years management. Skills: programming languages, ML models, robotics navigation, deployment. Preferred Qualifications: list of preferred items.
We must preserve all info; not lose any. So we need to ensure each piece appears somewhere.
Let's extract:
Basic Qualifications:
- PhD in engineering, technology, computer science, machine learning, robotics, operations research, statistics, mathematics or equivalent quantitative field
- 5+ years of industry or academic research experience
- 2+ years of scientists or machine learning engineers management experience
- Experience programming in Java, C++, Python or related language
- Experience building machine learning models or developing algorithms for business application
- Strong understanding of autonomous mobile robots and how they navigate
- Experience deploying robotic systems into the field
Preferred Qualifications:
- Experience building complex software systems, especially involving deep learning, machine learning and computer vision, that have been successfully delivered to customers
- Experience with mobile robot fleets in industrial or logistics settings
- Experience developing computationally efficient decision making algorithms for live production systems
Benefits: comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and 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, and parental leave. Also mention sign-on payments and restricted stock units (RSUs). Also link to benefits page (but we should remove links? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link might be considered navigation? It's a link to benefits page. Might be considered navigation? Safer to remove the URL but keep description. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The benefits link is not exactly those, but it's a link. Might be considered navigation. Safer to omit the URL but keep the text "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; could be considered navigation. I'd remove the URL and just keep "Learn more about our benefits." But that might be considered boilerplate? Not sure. Safer to keep the sentence but maybe drop the URL. The instruction says remove navigation; a link is navigation. So we should remove the URL. Keep the phrase "Learn more about our benefits." That's still a bit generic but okay.
Pay: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. USA, MA, N.Reading - 183,800.00 - 248,700.00 USD annually". Also mention Company - Amazon.com LLC but we shouldn't repeat job title; company maybe not needed. We'll include salary range and mention sign-on payments and RSUs.
We must not include Job ID.
Now produce HTML.
Structure:
About the role
... (combined description, day in the life, about the team)
Responsibilities
- Set the technical vision and research agenda; identify the right problems and sequence bets across near-term production needs and long-horizon research
- Build, hire, and develop a team of applied scientists; provide scientific mentorship and grow careers
- Drive algorithms from research through production deployment in partnership with engineering
- Represent the team externally through publications, academic collaborations, and community engagement
Requirements
- PhD in engineering, technology, computer science, machine learning, robotics, operations research, statistics, mathematics or equivalent quantitative field
- 5+ years of industry or academic research experience
- 2+ years of scientists or machine learning engineers management experience
Skills
- Experience programming in Java, C++, Python or related language
- Experience building machine learning models or developing algorithms for business application
- Strong understanding of autonomous mobile robots and how they navigate
- Experience deploying robotic systems into the field
Qualifications
- Experience building complex software systems, especially involving deep learning, machine learning and computer vision, that have been successfully delivered to customers
- Experience with mobile robot fleets in industrial or logistics settings
- Experience developing computationally efficient decision making algorithms for live production systems
Benefits
Comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and 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, and parental leave. Sign-on payments and restricted stock units (RSUs) are part of the compensation package. Learn more about our