Michael Kearns and Aaron Roth seated at a table in front of a large chalk board.
Michael Kearns, left, and Aaron Roth, right, are the co-authors ofThe Ethical Algorithm: The Science of Socially Aware Algorithm Design. Kearns and Roth are leading researchers in machine learning, University of Pennsylvania computer science professors, and Amazon Scholars.
University of Pennsylvania

Amazon Scholars Michael Kearns and Aaron Roth discuss the ethics of machine learning

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.

In November of 2019, University of Pennsylvania computer science professors Michael Kearns and Aaron Roth released The Ethical Algorithm: The Science of Socially Aware Algorithm Design. Kearns is the founding director of the Warren Center for Network and Data Sciences, and the faculty founder and former director of Penn Engineering’s Networked and Social Systems Engineering program. Roth is the co-director of Penn’s program in Networked and Social Systems Engineering and co-authored The Algorithmic Foundations of Differential Privacy with Cynthia Dwork. Kearns and Roth are leading researchers in machine learning, focusing on both the design and real-world application of algorithms.

Their book’s central thesis, which involves “the science of designing algorithms that embed social norms such as fairness and privacy into their code,” was already pertinent when the book was released. Fast forward one year, and the book’s themes have taken on even greater significance.

Amazon Science sat down with Kearns and Roth, both of whom recently became Amazon Scholars, to find out whether the events of the past year have influenced their outlook. We talked about what it means to define and pursue fairness, how differential privacy is being applied in the real world and what it can achieve, the challenges faced by regulators, what advice the two University of Pennsylvania professors would give to students studying artificial intelligence and machine learning, and much more.

Q. How has the narrative around designing socially aware algorithms evolved in the past year, and have the events of the past year altered your outlooks in any way?

Aaron Roth: The main thesis of our book, which is that in any particular problem you have to start by thinking carefully about what you want in terms of fairness or privacy or some other social desideratum, and then how you relatively value things like that compared to other things you might care about, such as accuracy—that fundamental thesis hasn't really changed.

Now with the coronavirus pandemic, what we have seen are application areas where how you want to manage the trade-off between accuracy and privacy, for example, is more extreme than we usually see. So, for example, in the midst of an outbreak, contact tracing might be really important, even though you can't really do contact tracing while protecting individual privacy. Because of the urgency of the situation, you might decide to trade off privacy for accuracy. But because the message of our book really is about thinking things through on a case-by-case basis, the thesis itself hasn't changed.

Michael Kearns: The events of the last year, in particular coronavirus, the resulting restrictions on society and the tensions around these restrictions, and all of the recent social upheaval in the United States, clearly has made the topics of our book much more relevant. The book has focused a lot of attention on the use of algorithms for both good and bad purposes, including things like contact tracing or releasing statistics about people's movements or health data, as well as the use of machine learning, AI, and algorithms more generally for applications like surveillance.

Since our book, at a high level, is about the tensions that arise when there's a battle between social norms like equality or privacy and the use of algorithms for optimizing things like performance or error, I don't think anything in the last year has changed our thinking about the technical aspects of these problems. It's clear that society has been forced to face these problems in a very direct way because of the events of the last year, in a way that we really haven't before. In that sense, our timing was very fortunate because the things we're talking about are more relevant now than ever.

Q. How does that affect your ability to define fairness? Is that something that can ever be a fixed definition, or does it need to be adjusted as events or specific use cases dictate?

Kearns: There's not one correct definition of fairness. In every application you have to think about who the parties are that you're trying to protect, and what the harms are that you're trying to protect them from. That changes both over time and in different scenarios.

Roth: Even before the events of the last year, fairness was always a very context- and beholder- dependent notion. One society might be primarily concerned about fairness by race, and another might be primarily concerned about fairness by gender, and a different community might have other norms. The events of the last year have highlighted cases in which not only will things vary over space or communities, but also over time.

People's attitudes about relatively invasive technologies like contact tracing might be quite different now than they were a year ago. If a year ago I told you, “Suppose there was some disease that some people were catching and the most effective way of tamping it down was to do contact tracing.” Many people might have said, “That sounds really invasive to me”, but now that we've all been through one of the alternatives—being on lock down for six months—people's minds might be changed. We’ve definitely seen norms around privacy for health-related data change.

Q. Standard setting bodies have a significant challenge when it comes to auditing algorithms. Given the scope of that challenge, what needs to happen to allow those groups to do that effectively?

Roth: Although it hasn't happened yet, regulatory agencies are thinking about this, and are reaching out to people like us to help them think about doing this in the right way. I don't know of any regulatory agency that is ready yet to audit algorithms at-scale in sensible ways of the technical sort we discuss in the book. But there are regulatory agencies that have gotten the idea that they should be gearing up to do this, and those agencies have started preliminary movements in that direction.

Kearns: Many of the conversations we've had with standard setting bodies make it clear they're realizing that, collectively, they've technologically fallen behind the industries that they regulate. They don't have the right resources or personnel to do some of the more technological types of auditing. But in these conversations, it's also become clear to us that, even if you could snap your fingers and get the right people and the right resources, it will only be part of a broader framework.

Other important pieces involve becoming more precise about best practices, and also thinking carefully about what those specifications should look like. Let me give a concrete example: One of the things that we argue in our book is that there are many laws and regulations in areas like consumer finance, for instance, that try to get at fairness by restricting what kinds of inputs an algorithm can use. These laws and regulations say, “In order to make sure that your model isn't racially discriminatory, you must not use race as a variable.” But, in fact, not using race as a variable is no guarantee that you won't build a model that's discriminatory by race. In fact, it can actually exacerbate that problem. What we advocate in the book is, rather than restricting the inputs, you should specify the behavior you want as outputs. So instead of saying, “Don't use race”, say instead, “The outputs of the models shouldn't be discriminatory by race.”

Q. Differential privacy has progressed from theoretical to applied science in significant ways in the past few years. How is differential privacy being utilized? How does that help balance the trade-off between privacy and accuracy?

Roth: In the last five years or so, differential privacy has gone from an academic topic to a real technology. For example, the 2020 US Decennial Census is going to release all of its statistical products for the first time, subject to the protections of differential privacy. This is because, by law, the Census is required to protect the privacy of the people it is surveying. The ad hoc techniques used in previous decades to protect the statistics have been shown not to work.

I think that what we will see is that the statistics that the Census releases this year will be more protective of the privacy of Americans. However, in the theme of trade off, using rigorous privacy protections is not without cost. Certain kinds of analyses, such as detailed demographic studies that rely on having highly granular Census data, might now be unavailable under differential privacy. We've seen this play out in the public sphere between downstream users of the data and folks at Census who actually have to hammer out the details.

We've seen other interesting uses of differential privacy during the pandemic too. Some tech companies have utilized differential privacy when releasing statistics about personal mobility data gathered during the pandemic. What differential privacy is best at is releasing those kinds of population level statistics: It's exactly designed to prevent you from learning too much about any particular individual. If you want to know how much less people are moving around different cities because of coronavirus restrictions, these data sets let you answer that question without giving up too much privacy for individuals whose mobile devices were providing the data at the most granular level.

Q. So how does differential privacy help protect individual information?

Roth: Oftentimes the things that you will most naturally want to know about a data set are not facts about particular people, but are population level aggregates like, how many people are crowded into my supermarket at 6 a.m. when it opens. If you tell me sufficiently many aggregate statistics, I can do some math and back out particular people's data from that. The fact that aggregate statistics can be disclosive about individual people's data is an unfortunate accident that actually doesn't have too much to do with what you really wanted to learn.

At its most basic level, differential privacy does things like add little bits of noise to the statistics that you're releasing so that what you're telling me is not the exact number of people who were in my local supermarket at 6 a.m., but roughly the number of people who were in the supermarket plus or minus some small number of people. The fortunate mathematical fact is that you can add amounts of noise that are relatively small that still allow you to get good estimates, but are sufficient to wash out the contributions of particular people, making it impossible to learn too much about any particular individual. It lets you get access to these population level questions that you were curious about without incidentally or accidentally learning about particular people, which is the dangerous side.

"We are bullish about algorithms"
Michael Kearns and Aaron Roth talked to Oxford Academic about the future of AI.

Kearns: To make this slightly more concrete, say what I want to do is each day tell everybody how many people were in the supermarket a couple blocks from me at 1 p.m. If you happened to be at that supermarket at one o’clock, then your GPS data is one of the data points that goes into the count. You may consider your presence at supermarket at 1 p.m. to be the kind of private information that you don't want the whole world to know. So then let's say that, on a typical day, there might be a couple hundred people at the supermarket, but that I add a number which is an order of magnitude, plus or minus 25. The addition of that random number mathematically and provably obscures any individual’s contributions to that count. I won't be able to look at that count and try to figure out any particular person who was present. If I add a number that's between minus 25 and 25, I can't affect the overall count by 100. I'll still have an accurate count up to some resolution, but I will have provided privacy to everybody who was present at the supermarket and, actually, all the people who weren't present as well.

Q. How are topics like fairness, accountability, transparency, interpretability, and privacy showing up in computer science curriculum at Penn and elsewhere within higher education?

Kearns: When Aaron and I first started working on the technical aspects of fairness in machine learning and related topics, it was pretty sparsely populated. This was maybe six or seven years ago, and there weren't many papers on the topics. There were some older ones, more from the statistics literature, but there wasn't really a community of any size within machine learning that thought about these problems. On the research side, the opposite is now true. All of the major machine learning conferences have significant numbers of papers and workshops on these topics; they have workshops devoted to these topics. There are now standalone conferences about fairness, accountability, and explainability in machine learning that are growing every year. It's a very vibrant, active research community now. Additionally, even though it's still early, it's an important enough topic that there are now starting to be efforts to teach this even at the undergraduate level.

The last two years at Penn, for example, I have piloted a course called The Science of Data Ethics. It’s deliberately called that and not The Ethics of Data Science. What that represents is that it’s about the science of making algorithms that are more ethical by different norms, like fairness and privacy. It's not your typical engineering ethics course, which at some level is meant to teach you to be a good, responsible person in that you look at case studies where things went wrong and you talk about what you would do differently. This class is a science class. It says: Here are the standard principles of machine learning, here's how those standard principles can lead to discriminatory behavior in my predictive models, and here are alternate principles, or modifications of those principles and the algorithms that implement them, that avoid or mitigate that behavior.

Q. Is there a more multidisciplinary approach to this set of challenges?

Roth: It's definitely a multidisciplinary area. At Penn, we've been actively collaborating with interested folks in the law school and the criminology department. So far, we don't really have interdisciplinary undergraduate courses on these topics. Those courses would be good in the long run, but at the research and graduate level we've been having interdisciplinary conversations for a number of years.

In particular, one critique that we try to anticipate in the book, and that we’re very aware of, is that technical work on making algorithms more ethical is only one piece of a much larger sociological, or what some people would call socio-technical, pipeline.
Michael Kearns

Kearns: Not just at the teaching level, but even in the research community, there's a real melting pot of viewpoints on these topics. Even though our book is focused on the scientific aspects of these issues, we do spend some time mentioning the fact that the science will only take us so far. In particular, one critique that we try to anticipate in the book, and that we’re very aware of, is that technical work on making algorithms more ethical is only one piece of a much larger sociological, or what some people would call socio-technical, pipeline. Machine learning begins with data and ends with a model. But upstream from the data is the entire manner in which the data was collected and the conditions under which it was collected.

One of the things that's very interesting, exciting, and necessary about the dialogue around these kinds of issues is that, even when there's quite a bit to say on them scientifically, you don't want to just put your head down and look at the science. You want to talk to people who are upstream and downstream from the machine learning part of this pipeline because they bring very different perspectives, and can often point out perspectives which can help you change the way you look at things scientifically in a positive way.

Q. If I were a student exploring AI or ML and I wanted to influence this particular conversation, beyond technical skills, what kind of skills should I be developing?

Kearns: What I would very strongly advocate is: think widely, think broadly, think big. Yes, you're going to be doing technical work in particular models and frameworks, and you know you want to get results in those frameworks. But also read what people who are from very, very different fields think about these problems. Go to their conferences, don't just go to the machine learning conferences and to the sub-track on fairness and machine learning. Go to the interdisciplinary conferences and workshops that are deliberately meant to bring together scientists, legal scholars, philosophers, sociologists, and regulators. Hear their views on these problems, keep an ear out for whether they even think you're working on a problem that's relevant or even has a solution.

That's the way I have approached my career: focus on what I'm good at and what I think is interesting from a scientific standpoint, but not in a scientific vacuum. I deliberately expose myself whenever possible to what people from a completely different perspective are thinking about the same set of topics. The good news is that there's a lot of opportunity for that right now. If you work in some branch of material science, it may not be possible to wander out in the world and get diverse perspectives, but everybody has an opinion on AI and machine learning ethics these days, so there is no shortage of sources from which this hypothetical student could go out and find their own technical views challenged or broadened.

Roth: One trap that is very easy for a new PhD student, or even an established researcher, to fall into is to write the introductions to your papers motivated by some kind of fairness problem, but then find yourself solving some narrow technical problem that ultimately has little connection to the world. I am sometimes guilty of this myself, but this is an area where there really are lots of important problems to solve. It's an area where theoretical approaches, if wielded correctly, can be extremely valuable. The thing that’s valuable is to be, sort of, multilingual. It can be difficult to talk to people from other fields because those fields have different vocabularies and a different world view. However, it's important to understand the perspective of these different communities. There are interdisciplinary groups looking at fairness, accountability, and transparency, which bring people together from all sorts of backgrounds to actively work on developing, at the very least, a shared vocabulary—and hopefully a shared world view.

Q. You've become Amazon Scholars fairly recently. What inspired you to take on this role?

Roth: I've spent most of my career as a theorist, so the ways I've been primarily thinking about privacy and fairness are in the abstract. I've had fun thinking about questions like: What kinds of things are, and are not, possible in principle with differential privacy? Or what kinds of semantic fairness promises can you make to people in a way that is still consistent with trying to learn something from the data? The attraction of Amazon and AWS is that it's where the rubber meets the road. Here we are deploying real machine learning products, and the privacy and the fairness concerns are real and pressing.

My hope is that by having a foot in the practice of these problems, not just their theory, not only will I have some effect on how consequential products actually work, but I’ll learn things that will be helpful in developing new theory that is grounded in the real world.

Kearns: I've had a kind of second life in the quantitative finance industry up until I joined Amazon. While I spent time doing practical things in the world of finance, it was more just using my general knowledge in machine learning. The opportunity to come to Amazon and really think about the topics we've been discussing in a practical technological setting seemed like a great opportunity. I'm also a long-term fan and observer of the company. I’ve known people here for many years, and have had great conversations with them. So I’ve watched with great interest over the last decade plus as Amazon grew its machine learning effort from scratch and gradually grew it to have wider and wider applications. It’s now at a point where not only is machine learning used widely within the company to optimize all kinds of processes and recommendations and the like, but it’s also used by customers worldwide in the form of services like Amazon SageMaker.

I have watched this with great interest because when I was studying machine learning in graduate school back in the late 80s, trust me, it was an obscure corner of AI that people kind of raised their eyebrows at. I never would have thought we would reach the point where not only does The Wall Street Journal expect everyone to know what they mean when they write about machine learning, but that it would actually be a product sold at scale.

I've watched these developments from academia and from the world of finance.  It seemed like a great opportunity to combine my very specific current research and other interests with an inside look at one of the great technology companies. Like Aaron, my expectations, which were high, have only been exceeded in the time I've spent here.

Research areas

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