Data Scientist, Automated Vehicle Testing
for sections present: About the role? Actually description includes "About The Team", "Basic Qualifications", "Preferred Qualifications". Also responsibilities: "Key job responsibilities". Also "A day in the life". Also "Export Control Requirement". Also "Pay" (salary range). Also "Benefits". Also "Schedule"? Not present. Also "Qualifications"? Not separate; we have Basic and Preferred. Could combine? But we need to follow rules: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
Thus we need to decide which sections to include based on content.
We have:
- Export Control Requirement (specific content: citizenship requirement). Could be a section maybe "Requirements"? But we have Basic Qualifications and Preferred Qualifications. Export Control is separate requirement. Could include under "Requirements" heading? The allowed headings list includes Requirements. So we could create a
Requirements
containing export control requirement plus maybe basic qualifications? But we also have Basic Qualifications and Preferred Qualifications separate. Could combine them under Requirements? However the instruction says prefer a few substantive sections over many thin ones. So maybe we create sections: Responsibilities, About the Team, Qualifications (combining basic and preferred), Pay, Benefits. Also maybe Export Control as part of Qualifications? But we need to preserve all substantive info; we can include export control as a inside Qualifications or Requirements.
Let's parse content:
Description: first paragraph about Amazon Leo mission.
Export Control Requirement: paragraph about citizenship.
Then: "We are looking for an experienced Data Scientist to help architect state-of-the-art test infrastructure and lead the development of data models and analysis tools to represent the ground truth about satellite test results in order to facilitate important business decisions. Our team is responsible for core infrastructure and tools that will serve as the backbone of automated satellite testing operations to enable rapid scaling of manufacturing processes."
Then "Key job responsibilities" bullet list (actually sentences). Then "A day in the life" paragraph.
Then "About The Team" paragraph.
Then "Basic Qualifications" list.
Then "Preferred Qualifications" list.
Then EEO boilerplate (remove).
Then accommodation link (remove? It's part of EEO/accommodation; likely remove as boilerplate). Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." (maybe remove as application instruction). Then "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. Amazon also offers 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. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location and salary: "USA, WA, REDMOND - 136,000.00 - 184,000.00 USD annually". Then Company and Job ID (drop).
Thus we have substantive content for:
- Responsibilities (Key job responsibilities)
- A day in the life (maybe could be part of Responsibilities? But it's distinct narrative; we could include as its own section maybe "Day in the Life". Not in allowed headings list but we could still use
for any heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we can use other headings? Probably we should stick to those examples; but "A day in the life" is not in list. Could we omit? It's substantive but we could incorporate into Responsibilities or About the role. However we have no "About the role" section; we have description at top. Could treat that as "About the role". The first paragraph about Amazon Leo mission could be "About the role". Then we could incorporate "A day in the life" into that or Responsibilities. To keep sections few, we could have: About the role, Responsibilities, Qualifications (basic+preferred+export), Pay, Benefits, About the Team. That's many but okay.
But we need to avoid thin sections. Let's see each:
- About the role: includes mission description + maybe day in the life? Could combine.
- Responsibilities: list of duties.
- Qualifications: include export control requirement, basic qualifications, preferred qualifications.
- About the Team: paragraph.
- Pay: salary range.
- Benefits: list of benefits.
That's six sections. Could we merge About the Team into About the role? Possibly but it's distinct. Could we merge Pay and Benefits into one "Compensation and Benefits"? Not in allowed headings but we could still use Compensation and Benefits
. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those as examples. Safer to stick to those. So we keep Benefits and Pay separate.
Now we need to output HTML fragment only, no /. Use for each section heading. Use - for lists. Use
for prose.
We must not repeat job title as heading. Not include Job ID.
We must preserve all substantive info: need to include export control requirement text exactly? We can paraphrase? Must preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact meaning but can rephrase? Usually "preserve ALL substantive information" means we shouldn't omit details, but we can rephrase as long as we keep the info. Safer to copy the sentences.
Let's extract each piece.
About the role (mission): "Amazon Leo is Amazon’s low Earth orbit satellite broadband network. Its mission is to deliver fast, reliable internet to customers and communities around the world, and we’ve designed the system with the capacity, flexibility, and performance to serve a wide range of customers, from individual households to schools, hospitals, businesses, government agencies, and other organizations operating in locations without reliable connectivity."
We could also include "A day in the life" paragraph: "As Amazon Leo Data Scientist you will own the architecture definition and development of data analysis tools to to aid engineering and production teams in deciding flight-worthiness of each Amazon Leo satellite and historical traceability tools to enable simplified discovery and interpretation of past test data. You will work with multiple engineering, software and manufacturing teams across ground and space systems, to specify requirements, define data collection, interpretation strategies, data pipelines and implement data analysis and reporting tools for Integrated Vehicle tests. Your focus will be in optimizing the analysis of test results to enable Amazon Leo production plans."
Note there is a typo "to to". We'll keep as is.
Responsibilities: The bullet list under "Key job responsibilities": Actually it's sentences separated by line breaks? Let's capture:
- Work with engineering, software and manufacturing teams to understand drivers, impacts, and key influences on satellite performance
- Lead the design, build and implementation of production models and make decisions in real time for satellite test results
- Drive actions at scale to optimize test methodology and drive increases to satellite reliability
- Analysis and modeling of satellite telemetry from test results in lab and on-orbit
- Develop models and data pipelines for satellite telemetry
- Create and manage datasets for continued pre-training and supervised fine-tuning of LLMs
- Develop scalable visualizations for analysis of satellite performance
We need to output as
- each.
Qualifications: Include export control requirement: "Due to applicable export control laws and regulations, candidates must be a U.S. citizen or national, U.S. permanent resident (i.e., current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum."
Basic Qualifications list:
- 2+ years of data scientist experience
- 3+ years of data querying languages (e.g. SQL), scripting languages (e.g. Python) or statistical/mathematical software (e.g. R, SAS, Matlab, etc.) experience
- 3+ years of machine learning/statistical modeling data analysis tools and techniques, and parameters that affect their performance experience
- 1+ years of working with or evaluating AI systems experience
- Master's degree in Science, Technology, Engineering, or Mathematics (STEM), or experience working in Science, Technology, Engineering, or Mathematics (STEM)
Preferred Qualifications list:
- Knowledge of machine learning concepts and their application to reasoning and problem-solving
- Experience in Python, Perl, or another scripting language
- Experience in a ML or data scientist role with a large technology company
- Experience in defining and creating benchmarks for assessing GenAI model performance
- Experience working on multi-team, cross-disciplinary projects
- Experience applying quantitative analysis to solve business problems and making data-driven business decisions
- Experience effectively communicating complex concepts through written and verbal communication
We need to preserve all.
About The Team paragraph: "The Automated Vehicle Testing Team is a mix of scientists and software engineers responsible for data infrastructure, tools, and research that serve as the backbone of automated satellite testing operations to enable rapid scaling of manufacturing processes."
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." Then location/salary line: "USA, WA, REDMOND - 136,000.00 - 184,000.00 USD annually". We need to include that as part of Pay section.
Benefits: "Amazon also offers 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. Learn more about our benefits at https://amazon.jobs/en/benefits."
We should keep the link? It's substantive; we can keep as part of paragraph.
Now we need to output HTML fragment.
Structure:
About the role
... mission ...
... day in the life ...
Responsibilities
- ...
...
Qualifications
Export control requirement: Due to applicable export control laws and regulations, candidates must be a U.S. citizen or national, U.S. permanent resident (i.e., current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum.
Basic Qualifications
??? But we shouldn't create headings
- for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include based on content. We have: - Export Control Requirement (specific content: citizenship requirement). Could be a section maybe "Requirements"? But we have Basic Qualifications and Preferred Qualifications. Export Control is separate requirement. Could include under "Requirements" heading? The allowed headings list includes Requirements. So we could create a
Requirements
containing export control requirement plus maybe basic qualifications? But we also have Basic Qualifications and Preferred Qualifications separate. Could combine them under Requirements? However the instruction says prefer a few substantive sections over many thin ones. So maybe we create sections: Responsibilities, About the Team, Qualifications (combining basic and preferred), Pay, Benefits. Also maybe Export Control as part of Qualifications? But we need to preserve all substantive info; we can include export control as ainside Qualifications or Requirements. Let's parse content: Description: first paragraph about Amazon Leo mission. Export Control Requirement: paragraph about citizenship. Then: "We are looking for an experienced Data Scientist to help architect state-of-the-art test infrastructure and lead the development of data models and analysis tools to represent the ground truth about satellite test results in order to facilitate important business decisions. Our team is responsible for core infrastructure and tools that will serve as the backbone of automated satellite testing operations to enable rapid scaling of manufacturing processes." Then "Key job responsibilities" bullet list (actually sentences). Then "A day in the life" paragraph. Then "About The Team" paragraph. Then "Basic Qualifications" list. Then "Preferred Qualifications" list. Then EEO boilerplate (remove). Then accommodation link (remove? It's part of EEO/accommodation; likely remove as boilerplate). Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." (maybe remove as application instruction). Then "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. Amazon also offers 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. Learn more about our benefits at https://amazon.jobs/en/benefits." Then location and salary: "USA, WA, REDMOND - 136,000.00 - 184,000.00 USD annually". Then Company and Job ID (drop). Thus we have substantive content for: - Responsibilities (Key job responsibilities) - A day in the life (maybe could be part of Responsibilities? But it's distinct narrative; we could include as its own section maybe "Day in the Life". Not in allowed headings list but we could still use
for any heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we can use other headings? Probably we should stick to those examples; but "A day in the life" is not in list. Could we omit? It's substantive but we could incorporate into Responsibilities or About the role. However we have no "About the role" section; we have description at top. Could treat that as "About the role". The first paragraph about Amazon Leo mission could be "About the role". Then we could incorporate "A day in the life" into that or Responsibilities. To keep sections few, we could have: About the role, Responsibilities, Qualifications (basic+preferred+export), Pay, Benefits, About the Team. That's many but okay. But we need to avoid thin sections. Let's see each: - About the role: includes mission description + maybe day in the life? Could combine. - Responsibilities: list of duties. - Qualifications: include export control requirement, basic qualifications, preferred qualifications. - About the Team: paragraph. - Pay: salary range. - Benefits: list of benefits. That's six sections. Could we merge About the Team into About the role? Possibly but it's distinct. Could we merge Pay and Benefits into one "Compensation and Benefits"? Not in allowed headings but we could still use
Compensation and Benefits
. The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those as examples. Safer to stick to those. So we keep Benefits and Pay separate. Now we need to output HTML fragment only, no /. Use
for each section heading. Use
- for lists. Use
for prose. We must not repeat job title as heading. Not include Job ID. We must preserve all substantive info: need to include export control requirement text exactly? We can paraphrase? Must preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact meaning but can rephrase? Usually "preserve ALL substantive information" means we shouldn't omit details, but we can rephrase as long as we keep the info. Safer to copy the sentences. Let's extract each piece. About the role (mission): "Amazon Leo is Amazon’s low Earth orbit satellite broadband network. Its mission is to deliver fast, reliable internet to customers and communities around the world, and we’ve designed the system with the capacity, flexibility, and performance to serve a wide range of customers, from individual households to schools, hospitals, businesses, government agencies, and other organizations operating in locations without reliable connectivity." We could also include "A day in the life" paragraph: "As Amazon Leo Data Scientist you will own the architecture definition and development of data analysis tools to to aid engineering and production teams in deciding flight-worthiness of each Amazon Leo satellite and historical traceability tools to enable simplified discovery and interpretation of past test data. You will work with multiple engineering, software and manufacturing teams across ground and space systems, to specify requirements, define data collection, interpretation strategies, data pipelines and implement data analysis and reporting tools for Integrated Vehicle tests. Your focus will be in optimizing the analysis of test results to enable Amazon Leo production plans." Note there is a typo "to to". We'll keep as is. Responsibilities: The bullet list under "Key job responsibilities": Actually it's sentences separated by line breaks? Let's capture: - Work with engineering, software and manufacturing teams to understand drivers, impacts, and key influences on satellite performance - Lead the design, build and implementation of production models and make decisions in real time for satellite test results - Drive actions at scale to optimize test methodology and drive increases to satellite reliability - Analysis and modeling of satellite telemetry from test results in lab and on-orbit - Develop models and data pipelines for satellite telemetry - Create and manage datasets for continued pre-training and supervised fine-tuning of LLMs - Develop scalable visualizations for analysis of satellite performance We need to output as
- each.
Qualifications: Include export control requirement: "Due to applicable export control laws and regulations, candidates must be a U.S. citizen or national, U.S. permanent resident (i.e., current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum."
Basic Qualifications list:
- 2+ years of data scientist experience
- 3+ years of data querying languages (e.g. SQL), scripting languages (e.g. Python) or statistical/mathematical software (e.g. R, SAS, Matlab, etc.) experience
- 3+ years of machine learning/statistical modeling data analysis tools and techniques, and parameters that affect their performance experience
- 1+ years of working with or evaluating AI systems experience
- Master's degree in Science, Technology, Engineering, or Mathematics (STEM), or experience working in Science, Technology, Engineering, or Mathematics (STEM)
Preferred Qualifications list:
- Knowledge of machine learning concepts and their application to reasoning and problem-solving
- Experience in Python, Perl, or another scripting language
- Experience in a ML or data scientist role with a large technology company
- Experience in defining and creating benchmarks for assessing GenAI model performance
- Experience working on multi-team, cross-disciplinary projects
- Experience applying quantitative analysis to solve business problems and making data-driven business decisions
- Experience effectively communicating complex concepts through written and verbal communication
We need to preserve all.
About The Team paragraph: "The Automated Vehicle Testing Team is a mix of scientists and software engineers responsible for data infrastructure, tools, and research that serve as the backbone of automated satellite testing operations to enable rapid scaling of manufacturing processes."
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." Then location/salary line: "USA, WA, REDMOND - 136,000.00 - 184,000.00 USD annually". We need to include that as part of Pay section.
Benefits: "Amazon also offers 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. Learn more about our benefits at https://amazon.jobs/en/benefits."
We should keep the link? It's substantive; we can keep as part of paragraph.
Now we need to output HTML fragment.
Structure:
About the role
... mission ...
... day in the life ...
Responsibilities
- ... ...
Qualifications
Export control requirement: Due to applicable export control laws and regulations, candidates must be a U.S. citizen or national, U.S. permanent resident (i.e., current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum.
Basic Qualifications
??? But we shouldn't create headings
- each.
Qualifications: Include export control requirement: "Due to applicable export control laws and regulations, candidates must be a U.S. citizen or national, U.S. permanent resident (i.e., current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum."
Basic Qualifications list:
- 2+ years of data scientist experience
- 3+ years of data querying languages (e.g. SQL), scripting languages (e.g. Python) or statistical/mathematical software (e.g. R, SAS, Matlab, etc.) experience
- 3+ years of machine learning/statistical modeling data analysis tools and techniques, and parameters that affect their performance experience
- 1+ years of working with or evaluating AI systems experience
- Master's degree in Science, Technology, Engineering, or Mathematics (STEM), or experience working in Science, Technology, Engineering, or Mathematics (STEM)
Preferred Qualifications list:
- Knowledge of machine learning concepts and their application to reasoning and problem-solving
- Experience in Python, Perl, or another scripting language
- Experience in a ML or data scientist role with a large technology company
- Experience in defining and creating benchmarks for assessing GenAI model performance
- Experience working on multi-team, cross-disciplinary projects
- Experience applying quantitative analysis to solve business problems and making data-driven business decisions
- Experience effectively communicating complex concepts through written and verbal communication
We need to preserve all.
About The Team paragraph: "The Automated Vehicle Testing Team is a mix of scientists and software engineers responsible for data infrastructure, tools, and research that serve as the backbone of automated satellite testing operations to enable rapid scaling of manufacturing processes."
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." Then location/salary line: "USA, WA, REDMOND - 136,000.00 - 184,000.00 USD annually". We need to include that as part of Pay section.
Benefits: "Amazon also offers 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. Learn more about our benefits at https://amazon.jobs/en/benefits."
We should keep the link? It's substantive; we can keep as part of paragraph.
Now we need to output HTML fragment.
Structure:
- for lists. Use