Responsible AI in the wild: Lessons learned at AWS

Real-world deployment requires notions of fairness that are task relevant and responsive to the available data, recognition of unforeseen variation in the “last mile” of AI delivery, and collaboration with AI activists.

When we first joined AWS AI/ML as Amazon Scholars over three years ago, we had already been doing scientific research in the area now known as responsible AI for a while. We had authored a number of papers proposing mathematical definitions of fairness and machine learning (ML) training algorithms enforcing them, as well as methods for ensuring strong notions of privacy in trained models. We were well versed in adjacent subjects like explainability and robustness and were generally denizens of the emerging responsible-AI research community. We even wrote a general-audience book on these topics to try to explain their importance to a broader audience.

Related content
Generative AI raises new challenges in defining, measuring, and mitigating concerns about fairness, toxicity, and intellectual property, among other things. But work has started on the solutions.

So we were excited to come to AWS in 2020 to apply our expertise and methodologies to the ongoing responsible-AI efforts here — or at least, that was our mindset on arrival. But our journey has taken us somewhere quite different, somewhere more consequential and interesting than we expected. It’s not that the definitions and algorithms we knew from the research world aren’t relevant — they are — but rather that they are only one component of a complex AI workstream comprising data, models, services, enterprise customers, and end-users. It’s also a workstream in which AWS is uniquely situated due to its pioneering role in cloud computing generally and cloud AI services specifically.

Our time here has revealed to us some practical challenges of which we were previously unaware. These include diverse data modalities, “last mile” effects with customers and end-users, and the recent emergence of AI activism. Like many good interactions between industry and academia, what we’ve learned at AWS has altered our research agenda in healthy ways. In case it’s useful to anyone else trying to parse the burgeoning responsible-AI landscape (especially in the generative-AI era), we thought we’d detail some of our experiences here.

Modality matters

One of our first important practical lessons might be paraphrased as “modality matters”. By this we mean that the particular medium in which an AI service operates (such as visual images or spoken or written language) matters greatly in how we analyze and understand it from both performance and responsible-AI perspectives.

Consider specifically the desire for trained models be “fair”, or free of significant demographic bias. Much of the scientific literature on ML fairness assumes that the features used to compare performance across groups (which might include gender, race, age, and other attributes) are readily available, or can be accurately estimated, in both training and test datasets.

Related content
Two of the world’s leading experts on algorithmic bias look back at the events of the past year and reflect on what we’ve learned, what we’re still grappling with, and how far we have to go.

If this is indeed the case (as it might be for some spreadsheet-like “tabular” datasets recording things like medical or financial records, in which a person’s age and gender might be explicit columns), we can more easily test a trained model for bias. For instance, in a medical diagnosis application we might evaluate the model to make sure the error rates are approximately the same across genders. If these rates aren’t close enough, we can augment our data or retrain the model in various ways until the evaluation is passed to satisfaction.

But many cloud AI/ML services operate on data that simply does not contain explicit demographic information. Rather, these services live in entirely different modalities such as speech, natural language, and vision. Applications such as our speech recognition and transcription services take as input time series of frequencies that capture spoken utterances. Consequently, there are not direct annotations in the data of things like gender, race, or age.

But what can be more readily detected from speech data, and are also more directly related to performance, are regional dialects and accents — of which there are dozens in North American English alone. English-language speech can also feature non-native accents, influenced more by the first languages of the speakers than by the regions in which they currently live. This presents an even more diverse landscape, given the large number of first languages and the international mobility of speakers. And while spoken accents may be weakly correlated or associated with one or more ancestry groups, they are usually uninformative on things like age and gender (speakers with a Philadelphia accent may be young or old; male, female or nonbinary; etc.). Finally, the speech of even a particular person may exhibit many other sources of variation, such as situational stress and fatigue.

Regional dialects.jpeg
Data — such as regional variations in word choice and accents — may lead toward alternative notions of fairness that are more task-relevant, as with word error rates across dialects and accents.

What is the responsible-AI practitioner to do when confronted with so many different accents and other moving parts, in a task as complex as speech transcription? At AWS, our answer is to meet the task and data on their own terms, which in this case involves some heavy lifting: meticulously gathering samples from large populations of representative speakers with different accents and carefully transcribing each word. The “representative” is important here: while it might be more expedient to (for instance) gather this data from professional actors trained in diction, such data would not be typical of spoken language in the wild.

Related content
Both secure multiparty computation and differential privacy protect the privacy of data used in computation, but each has advantages in different contexts.

We also gather speech data that exhibits variability along other important dimensions, including the acoustic conditions during recording (varying amounts and types of background noise, recordings made via different mobile-phone handsets, whose microphones may vary in quality, etc.). The sheer number of combinations makes obtaining sufficient coverage challenging. (In some domains such as computer vision, coverage issues that are similar — variability across visual properties such as skin tone, lighting conditions, indoor vs. outdoor settings, and so on — have led to increased interest in synthetic data to augment human-generated data, including for fairness testing here at AWS.)

Once curated, such datasets can be used for training a transcription model that is not only good overall but also roughly equally performant across accents. And “performant” here means something more complex than in a simple prediction task; speech recognition typically uses a measure like the word error rate. On top of all the curation and annotations above, we also annotate some data by self-reported speaker demographics to make sure we’re fair not just by accent but by race and gender as well, as detailed in the service’s accompanying service card.

Our overarching point here is twofold. First, while as a society we tend to focus on dimensions such as race and gender when speaking about and assessing fairness, sometimes the data simply doesn’t permit such assessments, and it may not be a good idea to impute such dimensions to the data (for instance, by trying to infer race from speech signals). And second, in such cases the data may lead us toward alternative notions of fairness that might be more task-relevant, as with word error rates across dialects and accents.

The last mile of responsible AI

The specific properties of individuals that can or cannot (or should not) be gleaned from a particular dataset or modality are not the only things that may be out of the direct control of AI developers — especially in the era of cloud computing. As we have seen above, it’s challenging work to get coverage of everything you can anticipate. It’s even harder to anticipate everything.

The supply chain phrase “the last mile” refers to the fact that “upstream” providers of goods and products may have limited control over the “downstream” suppliers that directly connect to end-users or consumers. The emergence of cloud providers like AWS has created an AI service supply chain with its own last-mile challenges.

Related content
The team’s latest research on privacy-preserving machine learning, federated learning, and bias mitigation.

AWS AI/ML provides enterprise customers with API access to services like speech transcription because many want to integrate such services into their own workflows but don’t have the resources, expertise, or interest to build them from scratch. These enterprise customers sit between the general-purpose services of a cloud provider like AWS and the final end-users of the technology. For example, a health care system might want to provide cloud speech transcription services optimized for medical vocabulary to allow doctors to take verbal notes during their patient rounds.

As diligent as we are at AWS at battle-testing our services and underlying models for state-of-the-art performance, fairness, and other responsible-AI dimensions, it is obviously impossible to anticipate all possible downstream use cases and conditions. Continuing our health care example, perhaps there is a floor of a particular hospital that has new and specialized imaging equipment that emits background noise at a specific regularity and acoustic frequency. In the likely event that these exact conditions were not represented in either the training or test data, it’s possible that overall word error rates will not only be higher but may be so differentially across accents and dialects.

Such last-mile effects can be as diverse as the enterprise customers themselves. With time and awareness of such conditions, we can use targeted training data and customer-side testing to improve downstream performance. But due to the proliferation of new use cases, it is an ever-evolving process, not one that is ever “finished”.

AI activism: from bugs to bias

It’s not only cloud customers whose last miles may present conditions that differ from those during training and testing. We live in a (healthy) era of what might be called AI activism, in which not only enterprises but individual citizens — including scientists, journalists, and members of nonprofit organizations — can obtain API or open-source access to ML services and models and perform their own evaluations on their own curated datasets. Such tests are often done to highlight weaknesses of the technology, including shortfalls in overall performance and fairness but also potential security and privacy vulnerabilities. As such, they are typically performed without the AI developer’s knowledge and may be first publicized in both research and mainstream media outlets. Indeed, we have been on the receiving end of such critical publicity in the past.

Related content
Technique that mixes public and private training data can meet differential-privacy criteria while cutting error increase by 60%-70%.

To date, the dynamic between AI developers and activists has been somewhat adversarial: activists design and conduct a private experimental evaluation of a deployed AI model and report their findings in open forums, and developers are left to evaluate the claims and make any needed improvements to their technology. It is a dynamic that is somewhat reminiscent of the historical tensions between more traditional software and security developers and the ethical and unethical hacker communities, in which external parties probe software, operating systems, and other platforms for vulnerabilities and either expose them for the public good or exploit them privately for profit.

Over time the software community has developed mechanisms to alter these dynamics to be more productive than adversarial, in particular in the form of bug bounty programs. These are formal events or competitions in which software developers invite the hacker community to deliberately find vulnerabilities in their technology and offer financial or other rewards for reporting and describing them to the developers.

Bias bounties.png
In a fair-ML (“bias bounty”) competition, different teams (x-axis) focus on different demographic features (y-axis) in the dataset, indicating that crowdsourced bias mitigation can help contend with the breadth of possible sources of bias. (The darker the blue, the greater the use of the feature.)

In the last couple of years, the ideas and motivations behind bug bounties have been adopted and adapted by the AI development community, in the form of “bias bounties”. Rather than finding bugs in traditional software, participants are invited to help identify demographic or other biases in trained ML models and systems. Early versions of this idea were informal hackathons of short duration focused on finding subsets of a dataset on which a model underperformed. But more recent proposals incubated at AWS and elsewhere include variants that are more formal and algorithmic in nature. The explosion of models, interest in, and concerns about generative AI have also led to more codified and institutionalized responsible-AI methodologies such as the HELM framework for evaluating large language models.

We view these recent developments — AI developers opening up their technology and its evaluation to a wider community of stakeholders than just enterprise customers, and those stakeholders playing an active role in identifying necessary improvements in both technical and nontechnical ways — as healthy and organic, a natural outcome of the complex and evolving AI industry. Indeed, such collaborations are in keeping with our recent White House commitments to external testing and model red-teaming.

Responsible AI is neither a problem to be “solved” once and for all, nor a problem that can be isolated to a single location in the pipeline stretching from developers to their customers to end-users and society at large. Developers are certainly the first line where best practices must be established and implemented and responsible-AI principles defended. But the keys to the long-term success of the AI industry lie in community, communication, and cooperation among all those affected by it.

Related content

US, WA, Seattle
Are you excited about using economic reasoning to shape decisions that affect millions of customers? Do you want to tackle ambiguous, high-impact problems where your analysis directly influences strategy and investment? We are looking for a Senior Economist to join Amazon and drive economic solutions for complex business challenges. In this role, you will define and prioritize analytical approaches, build rigorous econometric models, and translate findings into actionable recommendations for leadership. You will partner with engineers, product managers, scientists, and business leaders to deliver measurable outcomes. If you thrive on turning unstructured problems into clear, data-driven strategies, this is the role for you. Key job responsibilities - Lead the design, implementation, and delivery of economic analyses for complex or ambiguous business problems, providing strategic direction that informs organizational goals and investment decisions. - Develop and apply econometric models—including causal inference, structural estimation, and forecasting methods—choosing the right approach for each problem and validating results through rigorous testing. - Collaborate with cross-functional partners including engineers, product managers, and applied scientists to implement scalable solutions and translate economic insights into product and business improvements. - Communicate findings through clear narratives and technical documents for audiences ranging from peer economists to senior leaders, building consensus and influencing key decisions. - Evaluate and integrate generative AI tools where appropriate to augment research productivity, while mentoring other economists and raising the bar on analytical best practices across the team. A day in the life You might start your morning reviewing model performance metrics and refining an econometric specification before a working session with engineers on data pipeline requirements. After lunch, you could present preliminary findings from a causal analysis to business stakeholders, fielding questions and aligning on next steps. Later in the afternoon, you join a peer review for a fellow economist's research design, offering constructive feedback. Throughout the day, you balance hands-on analytical work with strategic conversations that connect your research to real business outcomes. About the team Our team of economists partners across Amazon to solve some of the company's most consequential business questions. We combine deep expertise in economic theory and applied econometrics with access to rich, large-scale data to deliver insights that shape long-term strategy. We value intellectual curiosity, collaborative problem-solving, and a commitment to rigorous science. If you are looking for an environment where your economic thinking directly drives impact at scale, we would love to hear from you.
US, WA, Redmond
Amazon Leo is building a low Earth orbit satellite broadband network to bring fast, affordable connectivity to customers worldwide. We're looking for a Senior Applied Scientist to invent the machine learning that will let the network predict, explain and prevent its own failures. You'll work on open research problems at large scale. These include anomaly detection on non-stationary, high-dimensional telemetry, causal root-cause inference over constantly changing satellite and ground network graphs, and trustworthy ML for operators making decisions under pressure. You'll own the science agenda, from forming hypotheses and designing new models to putting them into production systems that protect customer connectivity. 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. Key job responsibilities Define and lead a multi-year applied research agenda in network observability, anomaly prediction and availability modeling. Invent new time-series and spatio-temporal graph models, such as graph neural networks (GNNs), foundation models and dynamic baselining, to predict network and ground-segment failures before customers are affected. Develop causal inference and causal discovery methods for automated root-cause attribution across a large, interdependent event surface. Research probabilistic models that break availability and throughput into causal drivers (coverage, ground, network, terminal, payload, planning) and separate true signal from noise. Advance methods for alert correlation, deduplication, uncertainty quantification and metric-quality scoring. Explore large language models (LLMs) and agentic approaches for reasoning over telemetry, logs and incident narratives. Design rigorous offline and online evaluation, including backtesting against real closed incidents and gameday-based benchmarks. Take research into production on AWS (SageMaker, Bedrock), working with engineers on scalability, drift detection and explainability. Publish at top-tier venues, file patents and raise the scientific bar through mentoring and design reviews. A day in the life You might start the morning reading new literature on causal discovery and sketching how it applies to Leo's network graph. Later you could review a scientist's experiment design and debate the best evaluation methodology. During an event, you would test your attribution model live on the incident call. You might finish the day prototyping a new spatio-temporal anomaly detector and backtesting it against last quarter's incidents. About the team Amazon Leo Networking Software builds the software behind Leo's satellite and ground network. Our applied science team works on hard, open-ended problems with real-world impact. We value scientific rigor, curiosity and ownership, and we encourage publishing and contributing to the research community. As a Senior Applied Scientist, you'll help build this science function from the ground up and set the technical bar for the scientists who join after you.
US, WA, Bellevue
We are seeking a Senior Applied Scientist to push the state of the art in robot learning and help bring capable robots out of the lab and into everyday homes at Fauna Robotics. In this role, you will design novel algorithms across perception, manipulation, sim2real transfer, reinforcement learning, and multi-task learning, closing the gap between research and real-world deployment. You will work where robotics research meets production systems. You'll combine hands-on technical work with scientific leadership to guide the team toward the most promising directions. Working closely with software engineers and scientists, you will turn new ideas into robust solutions for dynamic, unstructured home environments. Homes bring challenges that structured settings like warehouses don't, and consumer-grade sensors and actuators have real limits, so this work calls for creative, out-of-the-box approaches. Key job responsibilities - Lead technical initiatives in areas such as robotics foundation models, reinforcement learning and manipulation - - Design experiments to identify the limitations of current state-of-the-art models and developing new models or techniques that can surpass these models - Design and implement novel deep learning architectures that push the boundaries of what robots can understand and accomplish - Mentor fellow scientists while maintaining strong individual technical contributions - Collaborate with engineering teams to optimize and scale models for real-world applications - Influence technical decisions and implementation strategies within your area of focus - Experienced in communicating complex technical work to a non-technical audience - The ability to work with minimal guidance, be proactive and to handle ambiguity and the challenge of quickly evolving goals About the team Fauna Robotics, an Amazon company, is building capable, safe, and genuinely delightful robots for everyday life. Our goal is simple: make robots people actually want to live and interact with in everyday human spaces. We believe that future won’t arrive until building for robotics becomes far more accessible. Today, too much effort is spent reinventing the fundamentals. We’re changing that by developing tightly integrated hardware and software systems that make it faster, safer, and more intuitive to create real-world robotic products. Our work spans the full stack: mechanical design, control systems, dynamic modeling, and intelligent software. The focus is not just functionality, but experience. We’re building robots that feel responsive, expressive, and genuinely useful. At Fauna, you’ll work at the frontier of this space, helping define how robots move, manipulate, and interact with people in natural environments. It’s an opportunity to solve hard problems across hardware and software with a team focused on making robotics accessible and joyful to build. If you care about making robotics real for everyone and building systems that are as delightful as they are capable, we’re interested in hearing from you.
US, WA, Seattle
MULTIPLE POSITIONS AVAILABLE Employer: AMAZON.COM SERVICES LLC Offered Position: Research Scientist II Job Location: Seattle, Washington Job Number: AMZ10564041 Position Responsibilities: Interact with various software and business groups to develop an understanding of their business requirements and operational processes. Utilize acquired knowledge and business judgment to build decision-supporting and operational tools to improve the bottom line. Build quantitative mathematical models to represent a wide range of supply chain, transportation and logistics systems. Implement these models and tools through the use of modeling languages and engineering code in software languages such as Java, C++, C# or C. Gather required data for analysis and mathematical model building by writing ad-hoc scripts and database queries. Perform quantitative, economic, and numerical performance analyses of these systems under uncertainty using statistical and optimization tools. Create computer simulations to support operational decision-making. Identify areas with potential for improvement and work with internal teams to generate requirements to realize improvements. Design optimal or near optimal solution methodologies to be used by in-house decision support tools and software. Create software prototypes to verify and validate the devised solutions methodologies. Integrate prototypes into production systems using standard software development tools and methodologies. 40 hours / week, 8:00am-5:00pm, Salary Range: $136,000/year to $184,000/year Amazon is a total compensation company. Dependent on the position offered, equity, sign-on payments, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits. For more information, visit: https://www.aboutamazon.com/workplace/employee-benefits. Amazon.com is an Equal Opportunity-Affirmative Action Employer – Minority / Female / Disability / Veteran / Gender Identity / Sexual Orientation.#0000
US, NY, New York
MULTIPLE POSITIONS AVAILABLE Employer: AMAZON.COM SERVICES LLC Offered Position: Applied Scientist II Job Location: New York, New York Job Number: AMZ10564066 Position Responsibilities: Participate in the design, development, evaluation, deployment and updating of data-driven models and analytical solutions for machine learning (ML) and/or natural language (NL) applications. Develop and/or apply statistical modeling techniques (e.g. Bayesian models and deep neural networks), optimization methods, and other ML techniques to different applications in business and engineering. Routinely build and deploy ML models on available data. Research and implement novel ML and statistical approaches to add value to the business. Mentor junior engineers and scientists. 40 hours / week, 8:00am-5:00pm, Salary Range: $172,400/year to $223,400/year. Amazon is a total compensation company. Dependent on the position offered, equity, sign-on payments, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits. For more information, visit: https://www.aboutamazon.com/workplace/employee-benefits. Amazon.com is an Equal Opportunity-Affirmative Action Employer – Minority / Female / Disability / Veteran / Gender Identity / Sexual Orientation.#0000
US, TX, Austin
MULTIPLE POSITIONS AVAILABLE Employer: AMAZON.COM SERVICES LLC Offered Position: Data Scientist III Job Location: Austin, Texas Job Number: AMZ10593703 Position Responsibilities: Own the data science elements of various products to help with data-based decision making, product performance optimization, and product performance tracking. Work directly with product managers to help drive the design of the product. Work with Technical Product Managers to help drive the build planning. Translate business problems and products into data requirements and metrics. Initiate the design, development, and implementation of scientific analysis projects or deliverables. Own the analysis, modelling, system design, and development of data science solutions for products. Write documents and make presentations that explain model/analysis results to the business. Bridge the degree of uncertainty in both problem definition and data scientific solution approaches. Build consensus on data, metrics, and analysis to drive business and system strategy. Position Requirements: Master's degree or foreign equivalent degree in Statistics, Applied Mathematics, Economics, Engineering, Computer Science or a related field and two years of experience in the job offered or a related occupation. Employer will accept a Bachelor's degree or foreign equivalent degree in Statistics, Applied Mathematics, Economics, Engineering, Computer Science, or a related field and five years of progressive post-baccalaureate experience in the job offered or a related occupation as equivalent to the Master's degree and two years of experience. Must have one year of experience in the following skills: (1) building statistical models and machine learning models using large datasets from multiple resources; (2) building complex data analyses by leveraging scripting languages including Python, Java, or related scripting language; and (3) communicating with users, technical teams, and management to collect requirements, evaluate alternatives, and develop processes and tools to support the organization. Amazon.com is an Equal Opportunity-Affirmative Action Employer – Minority / Female / Disability / Veteran / Gender Identity / Sexual Orientation. 40 hours / week, 8:00am-5:00pm, Salary Range $159,200/year to $215,300/year. Amazon is a total compensation company. Dependent on the position offered, equity, sign-on payments, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits. For more information, visit: https://www.aboutamazon.com/workplace/employee-benefits. #0000
US, WA, Bellevue
Within Amazon's North American Operations, we are tackling mission-critical problems to optimize network operations. We build complex causal, forecasting, and optimization models to better understand, predict, and govern processes across hundreds of warehouses. We are seeking a Data Scientist to drive the development of these models, deeply integrate with business stakeholders, and leverage generative AI to more intelligently build for our customers. Check out the hiring managers background - https://www.linkedin.com/pulse/from-nuclear-power-network-intelligence-david-plews-brittany-sdkbe/ Key job responsibilities - Interfacing with stakeholders to understand business problems and translating these into high and low-level design documents. - Building machine learning, optimization, and causal inference models that target business-specific challenges. - Sourcing, cleaning, and analyzing large and complex data sets associated with warehouse operations to provide business-critical insights at scale. - Leveraging AI-based solutions to drive development and provide nuanced insights into model outcomes. A day in the life You will be a single-threaded owner of projects within Amazon Operations, owning project scoping, stakeholder engagement, data enablement, and model development. Your work will be directly consumed by partner teams throughout Operations and Finance, and hence a strong sense of ownership is required to educate both technical and non-technical stakeholders on developed science solutions. About the team Our team is comprised of Data Scientists, Applied Scientists, and Economists, and are trusted to make data-driven solutions that power operations decision making. We strive to build consensus on divisive topics through clear presentation of problem statements paired with deep analyses that gain visibility throughout all levels of the organization from operators to executives.
US, CA, Santa Clara
Amazon Customer Service (CS) org’s mission is to make customer service interactions so good they become the primary reason customers choose Amazon. Customer Experience Products (CXP) supports this vision by building customer-facing solutions customers prefer because they work - reducing effort, shortening time to resolution, and building trust with every interaction. Our science team evaluates AI and Large Language Models (LLM)-driven solutions for both consumer-facing and CS associates-facing AI applications. We evaluate multi-modal, multi-turn, goal-oriented dialog systems (e.g. chatbot, voicebot) that can resolve customer issues and provide informational answers grounded by Amazon policy and help articles, at Amazon scale across multiple languages, intents and locales. These fine-tuned LLM solutions are designed to adapt to changing company policies and automate solutions to customer problems with conversational intelligence. Additionally, we're exploring with the partner associate-facing org on defining quality of LLM capabilities to improve the productivity of associates. Key job responsibilities - Lead development of Customer Service specific multi modal foundational models that improve chat and voice experiences. - Establish and evaluate rigorous testing and validation protocols for AI-driven systems. - Lead ongoing quality improvements for launched AI solutions - Collaborate closely with Product Managers, UX Designers, Applied Scientists, and Software Development Engineers. - Practice thought leadership and contribute to the overall science vision and strategic direction for AI-driven customer experience transformation initiatives. - Stay at the forefront of AI and machine learning technologies.
US, WA, Redmond
Amazon Leo is building a low Earth orbit satellite broadband network to deliver fast, affordable connectivity to customers around the world, including those underserved by traditional infrastructure. Operating a live constellation and its ground network at scale means service disruptions are an inevitable reality, and how quickly we detect them, understand them, and prevent them from recurring defines the trust we earn as a connectivity provider. We are seeking a talented Senior Data Scientist to build the next generation of observability and availability science for the Leo network. Leo already detects outages, notifies affected customers, and restores service. The frontier is prediction and prevention: reasoning over complex network and ground-segment telemetry to autonomously detect anomalies before they reach customers, attribute root cause automatically across a sprawling event surface, and rationalize a large, still-maturing metric set so responders trust what the system tells them. In this role you will work backwards from the needs of customers and operations teams. You will own the scientific direction end to end, partnering closely with network engineers, the Network Operations Center, and the Incident Management team, and the Software and Networking orginization to translate a long-term science vision into concrete research and delivery roadmaps. 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. Key job responsibilities * Own the observability and availability science end to end, from long-term vision to research roadmap to production delivery, working backwards from the needs of customers, the NOC, and network engineering. * Develop time-series and graph-based models with dynamic baselining that detect network and ground-segment anomalies before they cross the High Severity threshold, enabling proactive investigation rather than reactive response. * Reason over complex, multi-system telemetry to attribute cause automatically during live HSEs and LSEs, so Call Leaders and engineers spend time mitigating, not hunting. * Provide the science behind the network's bucketed availability decomposition (geometric and satellite coverage, ground and network segments, customer terminals, payload, and planning), attributing every movement to a true cause rather than noise, so leadership steers on signal and engineering effort lands where it actually moves availability and throughput. * Deliver the models, analyses, and metrics that feed the daily system readiness and validation review consumed by senior leadership and product and engineering, turning availability and throughput data into a defensible, evidence-based read on progress against GA entry criteria. * Own the recurring, fleet-wide "hot topic" investigations that span ASIC, firmware, payload, network, and planning, separating correlated symptoms from true root cause across thousands of nodes, quantifying how much availability or throughput each is costing, and answering whether it is a launch-blocking risk and whether it is improving. * Deliver alert correlation and deduplication, false-positive reduction, and metric-quality scoring so responders trust what the system tells them, directly supporting a large, still-maturing KPI set. * Tie your science to the unit the org actually measures: reduce detection and attribution time, raise availability against the network's bar, and increase the share of events prevented before customer impact. * Partner day to day with the Network Operations Center, Network Engineering, and the Incident Management (Call Leader) program; sit on live HSE/LSE bridges as the science partner and turn event learnings into model improvements. * Feed COEs and RCAs back into detection and attribution so recurring signatures are caught earlier, and help design and score gamedays that stress-test both the network and your models against real, closed events. * Build and deploy production pipelines on AWS (e.g., SageMaker, Bedrock, Glue) with model validation, monitoring, drift detection, and explainability, because operations teams must be able to trust and act on model output under pressure. * Set data-science standards, mentor scientists, and drive best practices across the Leo networking organization as the science function scales. * Produce explainable output and written narratives that let responders and leaders three or more levels up act on your models during and between events. A day in the life You might start by reviewing overnight anomaly detections and availability movements, join an HSE bridge as the science partner by midday, and spend the afternoon refining root-cause attribution models or presenting availability findings at the readiness review. About the team Amazon Leo Networking Software builds and operates the software behind Leo's satellite and ground network. Our science function partners with the NOC, Network Engineering and Incident Management to make the network more available and resilient, moving from reacting to outages to predicting and preventing them. As a Data Scientist III, you'll help shape that function as it grows.
US, NY, New York
MULTIPLE POSITIONS AVAILABLE Employer: AMAZON.COM SERVICES LLC Offered Position: Data Scientist III Job Location: New York, New York Job Number: AMZ10444216 Position Responsibilities: Own the data science elements of various products to help with data-based decision making, product performance optimization, and product performance tracking. Work directly with product managers to help drive the design of the product. Work with Technical Product Managers to help drive the build planning. Translate business problems and products into data requirements and metrics. Initiate the design, development, and implementation of scientific analysis projects or deliverables. Own the analysis, modelling, system design, and development of data science solutions for products. Write documents and make presentations that explain model/analysis results to the business. Bridge the degree of uncertainty in both problem definition and data scientific solution approaches. Build consensus on data, metrics, and analysis to drive business and system strategy. Position Requirements: Master's degree or foreign equivalent degree in Statistics, Applied Mathematics, Economics, Engineering, Computer Science or a related field and two years of experience in the job offered or a related occupation. Employer will accept a Bachelor's degree or foreign equivalent degree in Statistics, Applied Mathematics, Economics, Engineering, Computer Science, or a related field and five years of progressive post-baccalaureate experience in the job offered or a related occupation as equivalent to the Master's degree and two years of experience. Must have one year of experience in the following skills: (1) building statistical models and machine learning models using large datasets from multiple resources; (2) building complex data analyses by leveraging scripting languages including Python, Java, or related scripting language; and (3) communicating with users, technical teams, and management to collect requirements, evaluate alternatives, and develop processes and tools to support the organization. Amazon.com is an Equal Opportunity-Affirmative Action Employer – Minority / Female / Disability / Veteran / Gender Identity / Sexual Orientation. 40 hours / week, 8:00am-5:00pm, Salary Range $175,100/year to $236,900/year. Amazon is a total compensation company. Dependent on the position offered, equity, sign-on payments, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits. For more information, visit: https://www.aboutamazon.com/workplace/employee-benefits.#0000