Measuring the effectiveness of software development tools and practices

New cost-to-serve-software metric that accounts for the full software development lifecycle helps determine which software development innovations provide quantifiable value.

At Amazon, we constantly seek ways to optimize software development tools, processes, and practices in order to improve outcomes and experiences for our customers. Internally, Amazon has the variety of businesses, team sizes, and technologies to enable research on engineering practices that span a wide variety of circumstances. Recently, we've been exploring how generative artificial intelligence (genAI) affects our cost-to-serve-software (CTS-SW) metric. This post delves into the research that led to CTS-SW’s development, how various new AI-powered tools can lower CTS-SW, and our future plans in this exciting area.

Understanding CTS-SW

We developed cost to serve software as a metric to quantify how investments in improving the efficiency of building and supporting software enable teams to easily, safely, and continually deploy software to customers. It bridges the gap between our existing framework, which tracks many metrics (similar to DORA and SPACE), and the quantifiable bottom-line impact on the business. It allows developer experience teams to express their business benefits in either effective capacity (engineering years saved) or the monetary value of those savings. In a recent blog post on the AWS Cloud Enterprise Strategy Blog, we described how CTS-SW can evaluate how initiatives throughout the software development lifecycle affect the ability to deliver for customers.

Related content
In a keynote address at the latest Amazon Machine Learning Conference, Amazon academic research consultant, Stanford professor, and recent Nobel laureate Guido Imbens offered insights on the estimation of causal effects in “panel data” settings.

At a high level, CTS-SW tracks the dollars spent per unit of software reaching customers (i.e., released for use by customers). The best unit of software to use varies based on the software architecture. Deployment works well for microservices. Code reviews or pull requests that are shipped to a customer work well for monolith-based teams or software whose release is dictated by a predetermined schedule. Finally, commits that reach customers make sense for teams that contribute updates to a central code “trunk”. We currently use deployments, as it fits our widespread use of service-oriented architecture patterns and our local team ownership.

CTS-SW is based on the same theory that underlies the cost-to-serve metric in Amazon’s fulfillment network, i.e., that the delivery of a product to a customer is the result of an immeasurably complex and highly varied process and would be affected by the entirety of any changes to it. That process is so complex, and it changes so much over time, that the attempt to quantify each of its steps and assign costs to them, known as activity-based costing, is likely to fail. This is especially true of software engineering today, as new AI tools are changing the ways software engineers do their jobs.

Cost to serve simplifies this complex process by modeling only the input costs and the output units. We can then work backwards to understand drivers and opportunities for improvement.

CTS-16x9.gif
This equation represents the high-level CTS-SW setup.

In the context of software development, working backwards means that we investigate changes that could affect the metric, beyond the core coding experience of working in an IDE and writing logic. We also include continuous integration/continuous delivery (CI/CD) practices, work planning, incident management practices, maintenance of existing systems, searching for information, and many other factors that characterize software development at Amazon. By working backwards, we look across the collective software builder experience and investigate how changes in different areas, such as reducing the number of alarms engineers receive, affects developers’ ability to build new experiences for customers. We have used a variety of research methods to explore these relationships, but we have primarily relied on mathematical models.

From a science perspective, Amazon is an interesting place in which to build these models because of our established culture of small software teams that manage their own services. A longstanding Amazon principle is that these teams should be small enough to be fed by two pizzas, so we refer to them as “two-pizza teams”. This local-ownership model has led to the creation of thousands of distinct services solving customer problems across the company.

Amazon’s practice of working backwards from the best possible customer experience means software teams choose the optimal combination of tooling and technology to enable that experience. These choices have led to the implementation of many different software architectures at Amazon. That variety offers an opportunity to explore how different architectures affect CTS-SW.

Related content
Combining a cutting-edge causal-inference technique and end-to-end machine learning reduces root-mean-square error by 27% to 38%.

The Amazon Software Builder Experience (ASBX) team, our internal developer experience team, has access to rich telemetry data about these architectures and different ways of working with them. Using this data, we created a panel dataset representing the work of thousands of two-pizza teams over the past five years and including features we thought could affect CTS-SW. We model CTS-SW using the amount of developer time — the largest component of CTS-SW — per deployment. This data offers an opportunity for modeling the complete process from inception to delivery at a scale rarely seen in developer experience research.

Last year, as a first exploration of this dataset, we fit a set of linear mixed models to CTS-SW, to identify other metrics and behaviors that are highly correlated with it. Within ASBX, we were looking for input metrics that teams could optimize to lower CTS-SW. Correlations with linear mixed models can also help establish causal links between factors in the linear mixed models and CTS-SW. Linear mixed models are a good fit for this sort of problem because they have two components, one that captures the underlying relation between the outcome variable and the predictors, irrespective of team, and one that captures differences across teams.

Once we’d fit our models, we found that the following input metrics stood out as being the largest potential drivers of CTS-SW after a sensitivity analysis:

  • Team velocity: This measures how many code reviews (CRs) a software team merges each week per developer on the team. Teams that check in more code have a lower CTS-SW. Our science validates that software is a team sport, and framing this as a team-level outcome instead of an individual one prevents using CR flow as a performance metric for individual engineers. Having strong engineering onboarding and deployment safety helps teams reach and sustain high velocity. This was our largest single predictor of CTS-SW.
  • Delivery health (interventions per deploy, rollback rates): We find that teams that have implemented CI/CD with automation and change safety best practices have better CTS-SW outcomes. Our data demonstrates that when you spend less time wrestling with deployment friction and more time creating value, both productivity and job satisfaction improve.
  • Pages per on-call builder: This measures how many pages a team gets per week. We find that an increase in paging leads to lower CTS-SW, as paging can result in a deployment to production. However, we believe that work done in this reactive way may not be the most useful to customers in the long term. Understanding how this urgent, unplanned work interacts with new-feature delivery is an area for future research.

Our research has shown strong relationships between development factors and CTS-SW, making it an effective tool for measuring software development efficiency. We are working to expand the data we use in these models to better capture the ways in which teams build and operate their services. With this data, we will investigate the effects of software architecture decisions, informing architecture recommendations for teams across Amazon.

Validating linear mixed models with causal inference

Once we found that model fitting implied a correlation between team velocity and CTS-SW, we started looking for natural experiments that would help us validate the correlation with causal evidence. The rapidly emerging set of generative AI-powered tools provided that set of natural experiments.

Related content
New features go beyond conventional effect estimation by attributing events to individual components of complex systems.

The first of these tools adopted at scale across Amazon was Amazon Q Developer. This tool automatically generates code completions based on existing code and comments. We investigated the tool’s effect on CR velocity by building a panel regression model with dynamic two-way fixed effects.

This model uses time-varying covariates based on observations of software builder teams over multiple time periods during a nine-month observation window, and it predicts either CR velocity or deployment velocity. We specify the percentage of the team using Q Developer in each week and pass that information to the model as well.

We also evaluate other variables passed to the model to make sure they are exogenous, i.e., not influenced by Q Developer usage, to ensure that we can make claims of a causal relationship between Q Developer usage and deployment or CR velocity. These variables include data on rollbacks and manual interventions in order to capture the impact of production and deployment incidents, which may affect the way builders are writing code.

Here’s our model specification:

yit = ai + λt + βyi,t-1 + γXit + εit

In this equation, 𝑦𝑖𝑡 is the normalized deployments per builder week or team weekly velocity for team 𝑖 at time 𝑡, 𝑎𝑖 is the team-specific fixed effect, 𝜆𝑡 is the time-specific fixed effect, 𝑦𝑖,𝑡―1 is the lagged normalized deployments or team velocity, 𝑋𝑖𝑡 is the vector of time-varying covariates (Q Developer usage rate, rollback rate, manual interventions), 𝛽𝑖𝑡 is the persistence of our dependent variable over time (i.e., it shows how much of the past value of 𝑦 carries over into the current period), and 𝜀𝑖𝑡 is the error term.

Related content
New method goes beyond Granger causality to identify only the true causes of a target time series, given some graph constraints.

Early evidence shows that Q Developer has accelerated CR velocity and deployment velocity. More important, we found causal evidence that the launch of a new developer tool can lower CTS-SW for adopting teams and that we can measure that impact. As agentic AI grows, there will be agents for a range of tasks that engineers perform, beyond just writing code. That will require a unit of measurement that can capture their contributions holistically, without overly focusing on one area. CTS-SW enables us to measure the effects of AI across the software development lifecycle, from agents giving feedback on design docs to agents suggesting fixes to failed builds and deployments.

The road ahead

We recognize that combining experimental results can sometimes overstate an intervention’s true impact. To address this, we're developing a baseline model that we can use to normalize our tool-based approach to ensure that our estimates of AI impact are as accurate as possible.

Looking ahead, we plan to expand our analysis to include AI's impact on more aspects of the developer experience. By leveraging CTS-SW and developing robust methodologies for measuring AI's impact, we're ensuring that our AI adoption is truly customer obsessed, in that it makes Amazon’s software development more efficient. As we continue to explore and implement AI solutions, we remain committed to using data-driven approaches to improve outcomes and experiences for our customers. We look forward to sharing them with you at a later date.

Research areas

Related content

US, WA, Seattle
Amazon's eCommerce Foundation (eCF) organization provides the core technologies that drive and power Amazon's Stores, Digital, and Other (SDO) businesses. Millions of customer page views and orders per day are enabled by the systems eCF builds from the ground up. CloudTune, within eCF, empowers growth and business agility needs by automatically and efficiently managing AWS capacity and business processes needed to safely meet Amazon's customer demand. CloudTune serves its primary customers, internal software teams, through forecast-driven automation of cost controllership, capacity management, and scaling. We predict expected load, and drive procurement and allocation of AWS capacity for new product launches and high-velocity events like Prime Day and Cyber Monday. CloudTune is looking for a Data Scientist to join our forecasting and optimization team. The team develops sophisticated algorithms that combine machine learning-based demand forecasting with mathematical optimization to solve large-scale capacity planning problems under uncertainty. We work with massive datasets — spanning thousands of availability zone and instance family combinations across global regions — to determine optimal resource allocation strategies that balance infrastructure holding costs against service availability requirements. These models directly inform multi-million dollar capacity investment decisions and drive automated procurement, retention, and release policies across Amazon's compute infrastructure. As a Data Scientist in CloudTune, you will work with other scientists, software engineers, data engineers, and product managers on a variety of important research problems in the areas of stochastic optimization, time series modeling, and operations research. You will work on statistical problems with a high level of ambiguity. You will analyze and process large amounts of data, develop new algorithms and improve existing approaches based on statistical models, machine learning algorithms and big data solutions to automatically scale Amazon’s compute infrastructure, optimizing the balance between availability risk and cost efficiency for all of Amazon businesses. Key job responsibilities - Process and analyze large data sets, mining additional data sources as needed - Build statistical models and drive scalable solutions for multi-year capacity demand forecasting horizons - Create, enhance, and maintain technical documentation, and present to other scientists and business leaders - Process and analyze large-scale operational data to identify patterns and inform model development - Create, enhance, and maintain technical documentation, and present research findings to scientists, engineering teams, and senior leadership
US, WA, Redmond
At Amazon, we’re inventing on behalf of customers, and with Amazon Leo, we’re redefining what global connectivity looks like. Our mission is to deliver fast, affordable broadband to unserved and underserved communities around the world through a constellation of low Earth orbit (LEO) satellites. Every system we build helps connect people to education, healthcare, opportunity, and each other. As a Data Scientist, you will be responsible for developing advanced analytics and machine learning solutions for user terminals. You will develop predictive models to proactively identify possible user terminal failures in the field. You will work in a collaborative environment with a multi-disciplinary team, including constellation, RF, antenna, silicon, algorithm, and software engineers. Key job responsibilities As a Data Scientist, you will develop analytic tools for a team developing current and future user terminals. Your responsibilities include: • Develop statistical and analytical tool to enable the regression decision from on-orbit and lab measurement of user terminals • Publish documents and create compelling visualizations and presentations to communicate insights to stakeholders • Create and manage datasets for continued pre-training and supervised fine-tuning of LLMs • Develop scalable visualizations for analysis of user terminal performance • Work closely with constellation, RF, antenna, silicon, algorithm, and software engineers to root-cause the failures using data as the primary tool • Drive consensus on metrics and analysis approaches to support product development strategy 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. A day in the life As a Data Scientist in the LEO Customer Terminal Team, you will work daily with satellite constellation, algorithm, RF, antenna, silicon, hardware, and software teams in a collaborative environment. Your focus will be using data as an intelligence source to enable design decisions for the team. About the team The LEO Customer Terminal team is responsible for developing both outdoor and indoor devices that enable customers to access internet service via the LEO satellite network. We own the entire process from early prototypes through mass production, including requirements documentation, architecture definition, hardware development, algorithm development, and all integration and verification testing.
US, CA, Irvine
Do you want to write the algorithms that control next-generation batteries, and shape the future of energy storage? This role sits where electrochemistry, data/ML, and control theory meet. You will develop the physics-informed and data-driven methods that estimate state of charge, health, power capability, and remaining life, and validate them against lab and fleet data until they are ready to ship. Your algorithms will decide how hard a battery can be pushed, when it needs attention, and how long it will last, so they shape the safety, warranty, and economics of the whole product. You will work side by side with cell, systems, and software engineers, and as an early hire you will help define how we develop and validate battery algorithms. This role can be based in Boston, Irvine, Sunnyvale, or Seattle, and involves occasional domestic and international travel, up to 10% of the time. Key job responsibilities • Develop and own algorithms for state of charge, state of health, power capability, and remaining useful life, combining physics-based models with data-driven and estimation methods. • Deliver validated reference implementations, test vectors, and accuracy targets that define what production code must achieve. • Design the test plans and data needed to develop and validate algorithms, working with the cell and testing teams to turn lab and field data into model improvements. • Analyze algorithm performance across the deployed fleet, find where models drift or fail, and drive improvements. • Own the accuracy and robustness of battery algorithms, and sign off that production implementations match the validated reference. Provide algorithm evidence for safety certification. A day in the life Your week moves between data, models, and experiments. One day you might be working out why a health estimate drifts on cells that have aged in the field, and the next deciding which model structure holds accuracy at cold temperatures. You could be designing a test with the cell team to expose a behavior your model misses, or reviewing an implementation with an applied scientist to confirm that what ships matches what you validated. You will regularly share results with software, systems, and cell leaders, and your findings will shape decisions well beyond the algorithm itself. About the team We are building Amazon's energy storage capability, providing power for advanced technologies while contributing to a stable grid. Our product is highly connected, yet secure and resilient by design. We own it end to end, from software, ML, and controls through system design to cell selection and supply, and on to a safety-certified product in the field. The organization operates like a startup inside Amazon: small, fast-moving, and accountable for our decisions. We work across hardware, software, and science, with suppliers and partners worldwide, and with Amazon infrastructure, procurement, legal, and finance. The organization is at an early stage and growing quickly. You will be among the first algorithm hires, so you will help shape how we design, build, certify, and ship, with a direct line of sight to the product and business decisions your work informs. This is a dynamic role that will regularly present new challenges as the product and organization evolve.
US, CA, San Francisco
The Amazon Center for Quantum Computing (CQC) is seeking an Applied Scientist to research and design cryogenic control hardware for large-scale quantum processors, with an emphasis on superconducting digital circuits. Controlling and reading out orders of magnitude more qubits than today's systems demands rethinking where classical control lives and what technology implements it; you will design and model superconducting digital logic (e.g., single-flux-quantum-family circuits) and related cryogenic electronics, evaluate them against the wiring, power, and thermal budgets of a scaled system, and co-design control approaches with the qubit devices they serve. You will carry designs from concept through simulation, layout, design review, and fabrication handoff, and your evaluations will inform which control-electronics directions the organization invests in. Key job responsibilities • Design and simulate superconducting digital circuits and cryogenic control/readout electronics for scalable qubit control • Develop and validate Josephson-junction circuit models, timing and margin analyses, and verification methodology for superconducting digital designs • Quantify system-level trade-offs — wiring count, power dissipation at each cryogenic stage, latency, footprint — across candidate control architectures, and communicate recommendations • Co-design control interfaces with qubit-device colleagues so control electronics and quantum devices are developed as one system • Deliver design artifacts through the organization's design-request and design-review processes, including tapeout-ready layouts and verification reports • Present results internally and, where appropriate, publish in peer-reviewed venues About the team The Enabling Technologies team develops technologies and relationships facilitating scaling, including alternative quantum processor architectures, superconducting qubit device packaging, and cryogenic control device electronics. We work alongside a co-located quantum processor design team focused on current-generation devices; the two teams share design and review processes, and moving ideas between them is an explicit part of our charter.
US, WA, Redmond
Amazon Leo is building a constellation of thousands of low Earth orbit satellites. It will bring fast, reliable internet to customers beyond the reach of existing networks. On the Guidance, Navigation and Control (GNC) team, you will design the algorithms, simulations and onboard autonomy that keep every satellite precisely pointed and stable. Your work lets the payload serve customers on the ground, and it keeps the fleet flying safely. This is satellite GNC at constellation scale. The constellation is launching and growing today, so you will see your work go from concept to orbit, and then fly on many satellites. In this role, you will: - Take your GNC algorithms from concept to orbit, and stay with them through integration, test and on-orbit operations. - Write the production C++ flight code for your own algorithms. The code that flies is the code you write. - Solve hard problems in precise pointing, payload cueing and fleet autonomy. - Work across design, simulation, test and flight operations, not a narrow slice of the lifecycle. **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 - Design and analyze algorithms for state estimation, attitude determination and control, precise pointing and payload cueing against demanding performance requirements. - Implement these algorithms in production C++ flight software. Our GNC engineers own their algorithms all the way into flight, and partner with our embedded software engineers to integrate and test them. - Write concepts of operations for each phase of a satellite's life, from launch and orbit raising to service and deorbit, including failures and recovery. Balance what the payload needs against momentum, power, thermal and ground-contact limits. - Develop momentum management strategies with reaction wheels and magnetic torquers. Help select, size and place the GNC sensors and actuators for future satellites, and design the algorithms that use them. These include star trackers, magnetometers, sun sensors, IMUs and GNSS receivers. - Develop onboard autonomy, including Fault Detection, Isolation and Recovery (FDIR), so that the fleet operates safely at scale with minimal ground intervention. - Build and validate satellite and constellation models and simulations at several levels of fidelity, including 6-DOF simulation and Monte Carlo analysis. Verify closed-loop performance in hardware-in-the-loop (HITL) tests. - Support component environmental tests, functional and performance checkout, and subsystem and satellite integration in our labs. - Analyze telemetry from the whole fleet. Build the metrics, dashboards and tools that track pointing performance and payload operations time as the constellation grows, and use them to improve the fleet. - Operate the GNC system on orbit and take part in the team's on-call rotation. Review fleet data, support maneuvers, and resolve anomalies when on-orbit behavior differs from the ground model. - Review designs and code with the team, and document your algorithms, analyses and results clearly. A day in the life This role covers a wide range of problems across the spacecraft and the network. You will derive and prototype estimation and control algorithms, and then turn them into production flight code. You will prove them in 6-DOF and Monte Carlo simulation and in hardware-in-the-loop tests in the lab. You will support satellite integration. When a satellite does not behave as the ground model predicted, you will dig into fleet telemetry, find the cause and drive the fix. You will own each problem end to end, with the focus to go deep on it. GNC is at the center of safe flight, so you will work across the whole program. The payload, power, thermal and operations teams all depend on GNC, and you will balance their needs against the pointing and momentum budgets. You will partner closely with avionics, flight software and embedded software engineers to make your algorithms run reliably on the spacecraft. You will help the mechanical teams shape the next generation of satellite hardware, from reaction wheels to star trackers. As satellites move from design through manufacturing into orbit, you will work with systems engineering and Assembly, Integration and Test. The problems are hard: tight pointing requirements, a large constellation to keep flying safely, and the chance to invent capabilities that do not exist yet. Constant work with other teams makes this a place where you keep learning and growing. About the team You will join the Satellite Attitude Determination and Control team. We own GNC for our satellites end to end: algorithm design, flight software, lab integration, and flight operations of our own satellites on orbit. Our engineers bring deep experience from many satellite programs and other flight vehicles, with real strength in both our mission and the core GNC disciplines. We design, prototype, test, iterate and learn together. Because GNC is central to safe flight, we drive the concepts of operations and many of the system-level analyses on the program. We also have a lot of freedom. We trust our engineers to choose their own tools and approaches for the problems they face, and to own the results. If you want the autonomy to solve hard problems your way, with a team of strong engineers, you will feel at home here.
US, WA, Redmond
Amazon Leo is building a constellation of thousands of low Earth orbit satellites. It will bring fast, reliable internet to customers beyond the reach of existing networks. On the Guidance, Navigation and Control (GNC) team, you will design the algorithms, simulations and onboard autonomy that keep every satellite precisely pointed and stable. Your work lets the payload serve customers on the ground, and it keeps the fleet flying safely. This is satellite GNC at constellation scale. The constellation is launching and growing today, so you will see your work go from concept to orbit, and then fly on many satellites. In this role, you will: - Take your GNC algorithms from concept to orbit, and stay with them through integration, test and on-orbit operations. - Write the production C++ flight code for your own algorithms. The code that flies is the code you write. - Solve hard problems in precise pointing, payload cueing and fleet autonomy. - Work across design, simulation, test and flight operations, not a narrow slice of the lifecycle. **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 - Design and analyze algorithms for state estimation, attitude determination and control, precise pointing and payload cueing against demanding performance requirements. - Implement these algorithms in production C++ flight software. Our GNC engineers own their algorithms all the way into flight, and partner with our embedded software engineers to integrate and test them. - Write concepts of operations for each phase of a satellite's life, from launch and orbit raising to service and deorbit, including failures and recovery. Balance what the payload needs against momentum, power, thermal and ground-contact limits. - Develop momentum management strategies with reaction wheels and magnetic torquers. Help select, size and place the GNC sensors and actuators for future satellites, and design the algorithms that use them. These include star trackers, magnetometers, sun sensors, IMUs and GNSS receivers. - Develop onboard autonomy, including Fault Detection, Isolation and Recovery (FDIR), so that the fleet operates safely at scale with minimal ground intervention. - Build and validate satellite and constellation models and simulations at several levels of fidelity, including 6-DOF simulation and Monte Carlo analysis. Verify closed-loop performance in hardware-in-the-loop (HITL) tests. - Support component environmental tests, functional and performance checkout, and subsystem and satellite integration in our labs. - Analyze telemetry from the whole fleet. Build the metrics, dashboards and tools that track pointing performance and payload operations time as the constellation grows, and use them to improve the fleet. - Operate the GNC system on orbit and take part in the team's on-call rotation. Review fleet data, support maneuvers, and resolve anomalies when on-orbit behavior differs from the ground model. - Review designs and code with the team, and document your algorithms, analyses and results clearly. A day in the life This role covers a wide range of problems across the spacecraft and the network. You will derive and prototype estimation and control algorithms, and then turn them into production flight code. You will prove them in 6-DOF and Monte Carlo simulation and in hardware-in-the-loop tests in the lab. You will support satellite integration. When a satellite does not behave as the ground model predicted, you will dig into fleet telemetry, find the cause and drive the fix. You will own each problem end to end, with the focus to go deep on it. GNC is at the center of safe flight, so you will work across the whole program. The payload, power, thermal and operations teams all depend on GNC, and you will balance their needs against the pointing and momentum budgets. You will partner closely with avionics, flight software and embedded software engineers to make your algorithms run reliably on the spacecraft. You will help the mechanical teams shape the next generation of satellite hardware, from reaction wheels to star trackers. As satellites move from design through manufacturing into orbit, you will work with systems engineering and Assembly, Integration and Test. The problems are hard: tight pointing requirements, a large constellation to keep flying safely, and the chance to invent capabilities that do not exist yet. Constant work with other teams makes this a place where you keep learning and growing. About the team You will join the Satellite Attitude Determination and Control team. We own GNC for our satellites end to end: algorithm design, flight software, lab integration, and flight operations of our own satellites on orbit. Our engineers bring deep experience from many satellite programs and other flight vehicles, with real strength in both our mission and the core GNC disciplines. We design, prototype, test, iterate and learn together. Because GNC is central to safe flight, we drive the concepts of operations and many of the system-level analyses on the program. We also have a lot of freedom. We trust our engineers to choose their own tools and approaches for the problems they face, and to own the results. If you want the autonomy to solve hard problems your way, with a team of strong engineers, you will feel at home here.
US, WA, Seattle
Do you want to make AI provably correct for chip design and verification? We're hiring an Applied Scientist to combine large language models with formal methods such as Lean 4 and turn AI from a helpful assistant into a trusted engineering tool for silicon. Our team builds the formal verification methods behind custom silicon at Amazon scale. As AI agents take on more of chip design and verification, we need people who can make sure their output is checkable, sound and grounded in mathematics. You will research and build systems where LLMs work alongside interactive theorem provers, SMT solvers and model checkers. Engineers write the specifications. AI refines them against RTL, generates proof steps and closes proofs at machine speed. Every result is checked by a formal kernel, not trusted on faith. Work at the frontier of AI reasoning, theorem proving and hardware verification Ship solutions that directly affect real chips running in AWS data centers Publish and help shape how the industry formalizes AI use in hardware engineering Key job responsibilities Design and build LLM-driven systems for formal verification and design tasks, including proof generation, invariant and lemma discovery, spec-to-RTL refinement, and counterexample analysis Develop frameworks in Lean 4 (and related tools such as SMT solvers, model checkers and commercial FV engines) that formally check AI-generated artifacts, so they are correct by construction rather than just plausible Formalize hardware semantics, ISAs and microarchitectural properties in Lean 4 to create machine-checkable foundations for AI agents to reason over Track and evaluate state-of-the-art AI work (LLM agents, autoformalization, neural theorem proving, reinforcement learning from proof feedback) and turn promising research into production tools Build benchmarks and evaluation methods that measure AI soundness, proof success rate and engineering impact on real designs Partner with FV and design engineers to find the highest-leverage problems and deploy solutions into active chip programs Publish research, file patents and represent Amazon in the formal methods and AI communities Mentor engineers and scientists on applying formal AI methods
US, CA, Pasadena
We are seeking Applied Scientists to join Amazon. In this role, you will develop and deploy the science of safe autonomy on highly dynamic robots, advancing the frontier through both foundational research and realization on hardware. You will contribute to achieving safe autonomy across three key areas: control barrier function (CBF) theory for robust and performant safety on hardware; safe reinforcement learning for agile whole-body control; and layered safety filters that interface with learning, perception, and semantic reasoning systems. You will validate your work experimentally on state-of-the-art robotic platforms — removing bottlenecks to deployment and enabling robots to safely operate around humans. You will work with the inventor of CBFs, as well as top scientists and engineers at Amazon developing the next generation of safe autonomy. Key job responsibilities -Advance the science of safe autonomy from formal foundations to the integration with learning and perception to validation on hardware — with particular emphasis on methods that bridge these domains. -Test and validate hardware, with a focus on next generation robotic systems. Including locomotion, manipulation and loco-manipulation. -Leverage the deployments on hardware to validate the underlying science, identifying gaps between theory and practice that drive the next cycle of research. hardware to validate the underlying science, identifying gaps between theory and practice that drive the next cycle of research. -Publish research at top-tier robotics, control, and ML venues, and contribute to Amazon’s scientific reputation in advanced robotics. -Collaborate with SAF Lab and Amazon production teams to move research into robots deployed at Amazon scale. A day in the life Amazon offers a full range of benefits that support you and eligible family members, including domestic partners and their children. Benefits can vary by location, the number of regularly scheduled hours you work, length of employment, and job status such as seasonal or temporary employment. The benefits that generally apply to regular, full-time employees include: -Medical, Dental, and Vision Coverage -Maternity and Parental Leave Options -Paid Time Off (PTO) -401(k) Plan If you are not sure that every qualification on the list above describes you exactly, we’d still love to hear from you! At Amazon, we value people with unique backgrounds, experiences, and skillsets. If you’re passionate about this role and want to make an impact on a global scale, please apply! About the team The Safe Autonomy Frontiers (SAF) Lab is the first industry research lab dedicated to safe autonomy, founded by the inventor of control barrier functions. We are developing a universal safety layer for the next generation of robotic systems: mobile robots, manipulators, quadrupeds, and humanoids. Here you will advance performant safety for highly dynamic robots — CBF theory integrated with perception and learning, evaluated on next-generation platforms — and your work will underpin robots operating alongside people at Amazon’s unprecedented scale.
US, MA, North Reading
Robotics Applied Scientist II Intern/Co-op (2027) Are you passionate about robotics and research? Do you want to solve real customer problems through innovative technology? Do you enjoy working on scalable research and projects in a collaborative team environment? Do you want to see your science solutions directly impact millions of customers worldwide? We’re looking for current PhD students with a passion for robotic research and applications to join us in 2027 as Robotics Applied Scientist II Interns/Co-ops to shape the future of robotics and transform automation at Amazon’s scale. By applying to this role, you will be considered for Robotics Applied Scientist II Intern/Co-op (2027) opportunities across various Robotics teams at Amazon with different robotics research focus. Internship positions are available for multiple locations, durations (3 to 6+ months), and year-round start dates (winter, spring, summer, fall). Join us at the forefront of Applied Science, where your contributions will shape the future of Robotics! Key job responsibilities As a Robotics Applied Scientist II Intern/Co-op, you will work alongside global experts to advance the state of the art in robotics and artificial intelligence, tackling innovative problems that bridge the gap between research and real-world robotics implementation to innovate and build solutions on behalf of our customers. We are particularly interested in students with specialization and expertise in one or more of the following research areas: - Robotics - Artificial Intelligence - Robotics Manipulation (e.g., robot arm, grasping, dexterous manipulation, end of arm tools/end effector) - Autonomous Mobile Robots - Mobile Manipulation - Multi-Robot Coordination - Autonomous Navigation - Locomotion - Motion/Path Planning - Controls - Perception - Sensing - Robot Learning - Machine Learning - Computer Vision - Large Language Models (LLM), Vision-Language-Action Models (VLA), Vision-Language-Models (VLM) - World Models - Human-Robot Interaction - Robotics Simulation - Optimization - And related! Key responsibilities may include: - Develop novel, scalable algorithms and/or modeling techniques that advance the state-of-the-art in science areas such as robotics, artificial intelligence, or related - Tackle challenging, innovative research problems within robotics, artificial intelligence, or related that bridge the gap between theoretical advancement and practical robotics implementation - Collaborate with cross-functional teams to solve complex problems, and to communicate research findings clearly, leveraging your expertise in robotics, artificial intelligence, or related - Demonstrate the ability to work independently, thrive in a fast-paced, ever-changing environment - Leverage AI-powered tools where applicable to accelerate research, experimentation, and prototyping. - Critically review and validate outputs from AI tools and automated systems. About the team Explore Robotics Teams at Amazon At Amazon, robotics is where innovative research meets real-world deployment. There are many different specialized robotics teams, including the few highlighted below. Learn more about Robotics at Amazon here: https://www.amazon.science/research-areas/robotics Fulfillment Technologies and Robotics We build dynamic partnerships between people and intelligent machines. This intricate collaboration helps Amazon fulfill orders with unmatched accuracy. Working in symphony with our robotic technology, you’ll have the opportunity to extend your technical capabilities by working alongside some of the industry’s most advanced technologies. This includes our fleet of autonomous mobile robots, sophisticated control software, and technologies like language perception, machine learning, object recognition, and semantic understanding of commands. These technologies help us deliver an ever-improving customer and employee experience, as well as improve the safety of our facilities. Amazon Robotics Amazon Robotics is at the epicenter of robotics innovation. We design, test, and build mobile robots and mechatronic systems. Our offices, labs, test floors, and factories are close together, which means we can design the hardware, write the code, test, build, and watch it all come to life. Our areas of focus include advancements in autonomous mobility, AI, robotic management software, and much more. Fauna Fauna is focused on building capable, safe, and genuinely delightful robots for everyday life. Fauna’s goal is simple: make robots people actually want to live and interact with everyday. Fauna develops tightly integrated hardware and software systems that make it faster, safer, and more intuitive to create real-world robotic products. Fauna’s work spans the full stack: mechanical design, control systems, dynamic modeling, and intelligent software. The focus is not just functionality, but overall experience. Amazon Fulfillment Technologies Amazon Fulfillment Technologies develops tech solutions that create network optimizations for all Amazon sites worldwide. We own network infrastructure and devices in all buildings and labor planning and scheduling technology for fulfillment centers in North America and Europe.
US, NY, New York
About Sponsored Products and Brands: The Sponsored Products and Brands (SPB) organization at Amazon Ads is re-imagining the advertising landscape through industry leading generative AI technologies, revolutionizing how millions of customers discover products and engage with brands across Amazon.com and beyond. We are at the forefront of re-inventing advertising experiences, bridging human creativity with artificial intelligence to transform every aspect of the advertising lifecycle from ad creation and optimization to performance analysis and customer insights. We are a passionate group of innovators dedicated to developing responsible and intelligent AI technologies that balance the needs of advertisers, enhance the shopping experience, and strengthen the marketplace. If you're energized by solving complex challenges and pushing the boundaries of what's possible with AI, join us in shaping the future of advertising. About Our Team: The Brand Beacon team is responsible for inventing impressions offerings for brands to increase share of voice via premium experiences, helping brands get discovered, acquire new customers and sustainably grow customer lifetime value. We build end-to-end solutions that enable brands to drive discovery, visibility and share of voice. This includes building advertiser controls, shopper experiences, monetization strategies and optimization features. We succeed when (1) shoppers discover, engage and build affinity with brands and (2) brands can grow their business at scale with our advertising products. About This Role: As an Applied Scientist on our team, you will: * Develop AI solutions for advertiser and shopper experiences. Build monetization and optimization systems that leverage generative models to value and improve campaign performance. * Define a long-term science vision and roadmap for our Brand Beacon advertising business, driven from our customers' needs, translating that direction into specific plans for applied scientists and engineering teams. This role combines science leadership, organizational ability, technical strength, product focus, and business understanding. * Design and conduct A/B experiments to evaluate proposed solutions based on in-depth data analyses. * Effectively communicate technical and non-technical ideas with teammates and stakeholders; * Stay up-to-date with advancements and the latest modeling techniques in the field. * Think big about the arc of development of Gen AI over a multi-year horizon and identify new opportunities to apply these technologies to solve real-world problems. #GenAI