DynamoDB 10-year anniversary Swami Sivasubramanian and Werner Vogels
The early success of the Dynamo database encouraged Swaminathan (Swami) Sivasubramanian (top right), Werner Vogels (lower right) and colleagues to write the Dynamo research paper, and share it at the 2007 ACM Symposium on Operating Systems Principles (SOSP conference). The Dynamo paper served as a catalyst to create the category of distributed database technologies commonly known as NoSQL. Dynamo is the progenitor to Amazon DynamoDB, the company's cloud-based NoSQL database service that launched 10 years ago today.

Amazon’s DynamoDB — 10 years later

Amazon DynamoDB was introduced 10 years ago today; one of its key contributors reflects on its origins, and discusses the 'never-ending journey' to make DynamoDB more secure, more available and more performant.

Ten years ago, Amazon Web Services (AWS) launched Amazon DynamoDB, a fast, flexible NoSQL database service that offers single-digit millisecond performance at any scale.

In an online post on Jan. 18, 2012, Werner Vogels, chief technical officer at Amazon.com, wrote: “Today is a very exciting day as we release Amazon DynamoDB, a fast, highly reliable and cost-effective NoSQL database service designed for internet scale applications. DynamoDB is the result of 15 years of learning in the areas of large scale non-relational databases and cloud services.

“Several years ago we published a paper on the details of Amazon’s Dynamo technology, which was one of the first non-relational databases developed at Amazon,” Vogels continued. “The original Dynamo design was based on a core set of strong distributed systems principles resulting in an ultra-scalable and highly reliable database system. Amazon DynamoDB, which is a new service, continues to build on these principles, and also builds on our years of experience with running non-relational databases and cloud services, such as Amazon SimpleDB and Amazon S3, at scale. It is very gratifying to see all of our learning and experience become available to our customers in the form of an easy-to-use managed service.”

One of Vogels’s coauthors on the 2007 Dynamo paper, and a key contributor to the development of DynamoDB was Swaminathan (Swami) Sivasubramanian, then an Amazon research engineer working on the design, implementation, and analysis of distributed systems technology, and now vice president of Database, Analytics, and Machine Learning at AWS.

More and more, CIOs and organizations are realizing that it is going to be survival of the most informed, and those that put their data to work are the ones that won't just survive, they will thrive.
Swami Sivasubramanian

A decade after the launch of DynamoDB, Sivasubramanian says we’re “experiencing an amazing era of renaissance when it comes to data and machine learning.”

“We now live in an era where you can actually store your data in these databases and quickly start building your data lakes within Amazon S3 and then analyze them using Amazon SageMaker in a matter of a couple of weeks, if not days. That is simply remarkable.

“We now have the opportunity to help customers gain insights from their data faster,” Sivasubramanian added. “This is a mission that truly excites me because customers really want to put their data to work to enable data-driven decision making. More and more, CIOs and organizations are realizing that it is going to be survival of the most informed, and those that put their data to work are the ones that won't just survive, they will thrive.”

To mark the 10-year anniversary of the launch of Amazon DynamoDB, Amazon Science asked Sivasubramanian three questions about the origins of DynamoDB, its progenitor Dynamo, and the future of DynamoDB.

  1. Q. 

    You were a co-author on the 2007 Dynamo paper. At that time, the industry was transitioning to a scale out vs scale up architectural approach. Can you tell us about the origin story for Dynamo?

    A. 

    To get to 2007, I have to start with 2004, 2005. Even as I was working on my PhD [Sivasubramanian earned his PhD in computer science in 2006 from Vrije Universiteit Amsterdam] I was contemplating where I would work. Ultimately what convinced me to join Amazon as a research engineer intern [2005] was seeing how Amazon was pushing the boundaries of scale.

    I admit I was a little bit of a skeptic as an outsider. At that time, AWS didn’t even exist. But when I joined, I soon had an ‘a ha moment’ that, yes, Amazon was an e-commerce company, but actually it was a technology company that also did e-commerce. It was an interesting revelation for me seeing how Amazon had to invent so many new technologies to even support its e-commerce workload.

    As an intern, I was working as an engineer on amazon.com and during our peak holiday traffic time we experienced a serious scaling failure due to a database transaction deadlocking issue. The problem was caused by the relational database from a commercial vendor that we were using at the time. A bunch of engineers got together and wrote what we call a COE, a correction of errors document in which we say what happened, what we learned, how we fixed the issue, and how we would avoid a recurrence.

    I don't know if it was me being naive or just being confident in the way only a 20 something intern can be, but I asked the question ‘Why are we using a relational database for this? These workloads don't need the SQL level of complexity and transactional guarantees.’

    Peter Vosshall presents Dynamo at 2007 ACM Symposium on Operating System Principles (SOSP).

    This led us to start rethinking how we architected our underlying data stores altogether. At the time there wasn’t a scalable non-relational database. This is what led us to build the original Dynamo, and which led us to write the paper. Dynamo was not the only thing we were rethinking about our architecture at this time. We realized we also needed a scalable storage system, which led us to build S3, and we also realized that we needed a more managed relational database with the ability to do automated replication, failover, and backups/restore, which led us to build Amazon RDS.

    One rule we had related to writing the original Dynamo paper was not to publish when we developed the original design, but first let Dynamo run in production supporting several Amazon.com services, so that the Dynamo paper would be an end-to-end experience paper. Werner and I felt very strongly about this because we didn't want it to be just another academic paper. That’s why I was very proud when 10 years later that paper was awarded a test of time award.

  2. Q. 

    What’s the origin story for DynamoDB, and how has the technology evolved in the past decade?

    A. 

    The idea behind DynamoDB developed from discussions with customers like Don MacAskill, the CEO of SmugMug and Flickr. More and more companies like Don’s were web-based companies, and the number of users online was exploding. The traditional relational database model of storing all the data in a single box was not scaling well. It forced the complexity back on the users to shard their relational databases and then manage all the partitioning and re-partitioning and so forth.

    This wasn’t new to us; these challenges are why we built the original Dynamo, but it wasn’t yet a service. It was a software system that Amazon engineers had to operate. At some point in one of our customer advisory board meetings, Don said, ‘You all started Dynamo and showed what is possible with a scalable non-relational database system. Why can't we have that as an external service?’

    All senior AWS executives were there, and honestly it was a question we were asking ourselves at the time. Don wasn’t the only customer asking for it, more and more customers wanted that kind of scalable database where they didn't have to deal with partitioning and re-partitioning, and they also wanted extreme availability. This led to the genesis of our thinking about what it would take to build a scalable cloud database that wasn’t constrained by the SQL API.

    DynamoDB was different from the original Dynamo because it actually exposed several of the original Dynamo components via very easy-to-use cloud controls. Our customers didn’t have to provision clusters anymore. They could just create a table and seamlessly scale it up and down; they didn’t have to deal with any of the operations, or even install a single library to operate a database. This evolution of Dynamo to DynamoDB was important because we truly embraced the cloud, and its elasticity and scalability in an unprecedented manner.

    Werner Vogels, vice president and chief technology officer of Amazon.com, introduced DynamoDB on Jan. 18, 2012 with this post in which he said DynamoDB "brings the power of the cloud to the NoSQL database world."

    We launched it on January 18th, 2012 and it was a hit right out of the gate. Don’s company and several others started using it. Right from the launch, not just elasticity, but single-digit latency performance was something that resonated really well with customers. We had innovated quite a bit, all the way from the protocol layer, to the underlying storage layer for SSD storage, and other capabilities that we enabled.

    One of the first production projects was a customer with an interesting use case; they were doing a Super Bowl advertisement. Because DynamoDB was extremely elastic it could seamlessly scale up to 100,000 writes a second, and then scale down after the Super Bowl was over so they wouldn’t incur costs anymore. This was a big deal; it wasn’t considered possible at that time. It seems super obvious now, but at that time databases were not that elastic and scalable.

    It was a bold vision. But DynamoDB’s built-for-the-cloud architecture made all of these scale-out use cases possible, and that is one of the reasons why DynamoDB now powers multiple high-traffic Amazon sites and systems including Alexa, Amazon.com, and all Amazon fulfillment centers. Last year, over the course of our 66-hour Prime Day, these sources made trillions of API calls and DynamoDB maintained high availability with single-digit millisecond performance, peaking at 89.2 million requests per second.

    And since 2012, we have added so many innovations, not just for its underlying availability, durability, security and scale, but ease-of-use features as well.

    Swami Sivasubramanian, AWS | CUBE Conversation, January 2022

    We’ve gone beyond key value store and now support not just a hash-based partition but also range-based partitioning, and we’ve added support for secondary indexes to enable more complex query capabilities —without compromising on scale or availability.

    We also now support scalable change data capture through Amazon Kinesis Data Steams for DynamoDB. One of the things I strongly believe with any database is that it should not be an island; it can’t be a dead end. It should generate streams of what data changed and then use that to bridge it to your analytics applications, or other data stores.

    We have continued innovating across the board on features like backup and restore. For a large-scale database system like DynamoDB with millions of partitions, doing backup and restore isn’t easy, and a lot of great innovations went into making this experience easy for customers.

    We have also added the ability to do global tables so customers can operate across multiple regions. And then we added the ability to do transactions with DynamoDB, all with an eye on how do you continue to keep DynamoDB’s mission around availability and scalability?

    Recently we also launched the ability to reduce the cost of storage with the Amazon DynamoDB Standard Infrequent Access table class. Customers often need to store data long term, and while this older data may be accessed infrequently, it must remain highly available. For example, end users of social media apps rarely access older posts and uploaded images, but the app must ensure that these artifacts are immediately accessible when requested. This infrequently accessed data can represent significant storage expense for customers due to their growing volume and the relatively high cost of storing this data, so customers optimize costs in these cases by writing code to move older, less frequently accessed data from DynamoDB to lower cost storage alternatives like Amazon S3. So at the most recent re:Invent we launched Amazon DynamoDB Standard-Infrequent Access table class, a new cost-efficient table class to store infrequently accessed data, yet maintain the high availability and performance of DynamoDB.

    We are on this journey of maintaining the original vision of DynamoDB as the guiding light, but continue to innovate to help customers with use cases around ease of querying, the ability to do complex, global transaction replication, while also continuing to manage costs.

  3. Q. 

    What might the next 10 years bring?

    A. 

    When we started with DynamoDB ten years ago, the cloud itself was something customers were just starting to understand better — its benefits and what they could do.

    Now we live in a world where cloud is the new normal in terms of how customers are building IT applications, and scale is also the new normal because every app is being built to handle viral moments. DynamoDB itself will be on this continuous journey where we will continue to innovate on behalf of customers. One of the things we will continue moving toward is an end-to-end data strategy mission because, as I mentioned earlier, no database is an island.

    Customers no longer want to just store and query the data in their databases. They then want to analyze that data to create value, whether that’s a better personalization or recommendation engine, or a forecasting system that you can run predictive analytics against using machine learning. Connecting the dots end to end, and continuing to make DynamoDB more secure, more available, more performant, and easier to use will be our never-ending journey.

Research areas

Related content

US, CA, Pasadena
The Amazon Web Services (AWS) Center for Quantum Computing (CQC) in Pasadena, CA, is hiring an Applied Scientist to lead integration research and development for superconducting quantum devices. You will design, model, and test the chip-to-chip, chip-to-package, and signal-delivery interfaces that let superconducting quantum computers scale, and you will characterize integrated assemblies at cryogenic temperatures to learn how integration choices affect qubit performance, yield, and manufacturability. You will join a multi-disciplinary team of theoretical and experimental physicists, materials scientists, and hardware and software engineers working at the forefront of quantum computing. You will carry integration technologies from concept through hardware demonstration, build the test standards and automation that make results reproducible across devices, and collaborate with fabrication, hardware, and circuit design engineers to remove the dominant sources of yield loss. You will also contribute to multi-year roadmap planning for integration and scaling capabilities and help establish the scientific foundation for this capability area within the Device team. Key job responsibilities In this role you will develop the integration technologies that let superconducting quantum computers scale. Your work will span four connected areas: - Integration research and development: Design, model, and test integration solutions for superconducting quantum devices, including chip-to-chip, chip-to-package, and signal-delivery interfaces. Build electromagnetic, thermal, and mechanical models to predict and optimize performance, and characterize integrated assemblies at cryogenic temperatures. - Scaling technologies: Develop and evaluate approaches to scaling superconducting quantum hardware against yield, reusability, manufacturability, and scalability, and carry the most promising ones from concept through hardware demonstration. - Test standards and automation: Define test standards that give rigorous, reproducible measurements of how integration affects qubit coherence, loss, and crosstalk. Automate data collection and reporting against these standards so characterization scales across devices and configurations. - Yield and manufacturability: Work with fabrication, hardware, printed circuit board, and circuit design engineers to identify and remove the largest sources of yield loss and integration uncertainty, and to design processes and components that are reused across device generations and manufactured at scale. About the team The Device team at the AWS Center for Quantum Computing designs, builds, and measures the superconducting quantum devices at the heart of our processors, and develops the integration and packaging that turn individual devices into working systems. You will work alongside physicists, materials scientists, and hardware and software engineers across design, fabrication, measurement, and theory, in a lab built for rapid iteration from concept to cryogenic test. Over the coming years the team's focus is making superconducting quantum hardware scale, and this role establishes integration as a scientific capability area within that effort. Why AWS? Amazon Web Services (AWS) is the world's most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that's why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses. AWS Utility Computing (UC) provides product innovations — from foundational services such as Amazon's Simple Storage Service (S3) and Amazon Elastic Compute Cloud (EC2), to consistently released new product innovations that continue to set AWS's services and features apart in the industry. As a member of the UC organization, you'll support the development and management of Compute, Database, Storage, Internet of Things (IoT), Platform, and Productivity Apps services in AWS. Within AWS UC, Amazon Dedicated Cloud (ADC) roles engage with AWS customers who require specialized security solutions for their cloud services. Inclusive Team Culture: Here at AWS, it's in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion that empower us to be proud of our differences. Ongoing events and learning experiences, including our Conversations on Race and Ethnicity (CORE) and AmazeCon (diversity) conferences, inspire us to never stop embracing our uniqueness. Diverse Experiences: AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn't followed a traditional path, or includes alternative experiences, don't let it stop you from applying. Mentorship & Career Growth: We're continuously raising our performance bar as we strive to become Earth's Best Employer. That's why you'll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional. Work/Life Balance: We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there's nothing we can't achieve in the cloud.
US, VA, Arlington
PXT Central Science is seeking an exceptional Data Scientist to join our team. The ideal candidate will thrive in a dynamic, multifaceted role where you'll translate complex business challenges into rigorous quantitative frameworks, extract actionable insights from structured and unstructured datasets, and architect science-backed, scalable solutions that elevate the experience of our 1 million+ employees worldwide. If you're energized by the opportunity to apply data science to our mission of making Amazon Earth's Best Employer, we want to hear from you. Key job responsibilities • Own the design, development, and maintenance of scalable models and prototypes leveraging statistical, machine learning, or GenAI methodologies to enhance employee experience. • Partner with scientists, engineers, and product leaders to solve for employee experience defects using scientific approaches, building new services and tools that deliverable measurable impact. • Author and maintain detailed technical documentation related to the projects you drive. • Communicate results to diverse audiences of varying technical background with effective writing, visualizations, and presentations • Stay current with emerging methods and technologies, and implement them strategically to amplify the team’s impact. About the team The Central Science Team within Amazon’s People Experience and Technology org (PXTCS) uses economics, behavioral science, statistics, machine learning, and Generative AI to proactively identify mechanisms and process improvements which simultaneously improve Amazon and the lives, well-being, and the value of work to Amazonians. We are an interdisciplinary team, which combines the talents of science, engineering, and UX to develop and deliver solutions that measurably achieve this goal.
CA, BC, Vancouver
Building AI first solutions in a complex regulated space at Amazon scale. Would you like to work on one of the world's largest product classification and Tax computation engine? Or perhaps teaching AI to understanding nuances of domain specific language is what piques your interest? We are responsible for the tax calculation platform, providing the core services that calculate indirect taxes (sales tax and VAT) for all Amazon sales, physical and digital, globally. We are responsible for classifying billions of products in Amazon’s catalogue, calculating accurate Tax amount for every transaction that happens on Amazon’s global platform. Our engineering services are relied upon globally, built to be resilient across some of highest peak traffic demands in the world, while constantly evolving with the state of the art technology. We use language models at scale for Tax classification of the diverse products in Amazon catalogue and comprehending nuances of legislations and legal parlour.Our challenges include staying on top of the complex and fast-changing global tax legislations while ensuring computing calculations correctly and quickly, thousands of times a second, and each one needs to be accurate. Applied Scientists in Tax Engine works closely with Tax specialists, Product team , SDEs and Business teams - tackling a growing portfolio of core-science problems that includes balance of predictive and generative AI -including language comprehension, causal reasoning and active learning. As an Applied scientist, you will provide machine learning expertise to the team that helps increase the accuracy of Tax classification based on product information in Amazon catalogue. You will build various machine learning models to predict accuracy of tax classification, work with large reasoning models to reason with large volumes of system data and expert artefacts to teach domain intuition to AI. You will on variety of legislative changes acting as causal determinants to changes in our systems. You will help us innovate different ways to enhance for our global customers of Amazon.You will need to be entrepreneurial, work in a highly collaborative environment with SDEs, Product managers and businesses. We like to move fast, experiment, iterate and then scale quickly, thoughtfully balancing speed and quality. Whether you're passionate about taking your scientific solves to global reach and scale or one who seeks to solve complex problems under high scrutiny of an audited field, Tax Engine’s scope could offer you an intersting challenge to solve.
US, NY, New York
Prime Video is a first-stop entertainment destination offering customers a vast collection of premium programming in one app available across thousands of devices. Prime members can customize their viewing experience and find their favorite movies, series, documentaries, and live sports – including Amazon MGM Studios-produced series and movies; licensed fan favorites; and programming from Prime Video subscriptions such as Apple TV+, HBO Max, Peacock, Crunchyroll and MGM+. All customers, regardless of whether they have a Prime membership or not, can rent or buy titles via the Prime Video Store, and can enjoy even more content for free with ads. Are you interested in shaping the future of entertainment? Prime Video's technology teams are creating best-in-class digital video experience. As a Prime Video team member, you’ll have end-to-end ownership of the product, user experience, design, and technology required to deliver state-of-the-art experiences for our customers. You’ll get to work on projects that are fast-paced, challenging, and varied. You’ll also be able to experiment with new possibilities, take risks, and collaborate with remarkable people. We’ll look for you to bring your diverse perspectives, ideas, and skill-sets to make Prime Video even better for our customers. With global opportunities for talented technologists, you can decide where a career Prime Video Tech takes you! Key job responsibilities The science challenges include: - Heterogeneous customer responses. The same customer responds differently to ads depending on what they’re watching, how engaged they are, and their broader streaming context. We need to understand and predict this variation to make better advertising decisions in real time. - Signal sparsity in streaming. Unlike search or retail advertising, streaming offers no clicks, no conversions, and limited direct feedback. We must develop creative approaches to infer customer preferences, intent, and tolerance from indirect behavioral signals. - Personalization at scale. A one-size-fits-all ad experience leaves value on the table for both customers and the business. We build systems that adapt ad load, placement, and content to individual viewers across 100M+ customers and 100k+ titles. - Small effects, large variance. Ad interventions typically produce 0.1-2% shifts in engagement, effects easily overwhelmed by natural behavioral variance. Measuring, attributing, and optimizing these small signals requires rigorous experimental design and causal methodologies. - Competing objectives. Revenue, customer engagement, long-term retention, and advertiser value are in tension. We develop principled frameworks to navigate these tradeoffs and optimize for sustainable outcomes rather than any single metric. A day in the life - Lead the research and development of ML models that personalize advertising decisions for 100M+ customers across 100k+ titles, with production deployment in mind - Develop deep learning architectures (multi-task learning, embedding-based representations) for customer behavior prediction at scale - Design and analyze large-scale A/B experiments, applying causal inference techniques to measure and optimize the impact of ad strategies on customer engagement and monetization - Partner with engineering to ensure models meet production latency and scalability requirements - Collaborate with product managers to frame business problems as tractable ML problems and translate findings into product decisions - Shape the team’s scientific roadmap, identifying high-impact research directions About the team Prime Video Ads is pioneering the use of Generative AI, Deep Learning and Causal ML to empower the next generation of Ads experience in Prime Video. Our vision is to build the world’s most valuable and differentiated ad-supported streaming platform: one where every ad is relevant to the viewer, and every dollar spent by an advertiser delivers measurable results. We are seeking lead applied scientists who have demonstrated experience in advancing state of the art ML algorithms, particularly in Personalization, Relevance, Casual Inference and Gen-AI areas. Your role will be to deliver these innovations as production-ready systems at Amazon scale.
US, WA, Seattle
MULTIPLE POSITIONS AVAILABLE Employer: AMAZON.COM SERVICES LLC Offered Position: Applied Scientist II Job Location: Seattle, Washington Job Number: AMZ10564086 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. Specialize in the field of Computational Advertising, directly advancing the techniques in Online Advertising Technology focusing on model optimization and latency reduction. Develop sophisticated machine learning algorithms and models using PyTorch. Develop advanced deep learning architectures to automate the discovery of complex, non-linear feature interactions, effectively capturing high-dimensional data patterns that traditional statistical models are unable to process. Investigate and implement high-order feature interaction architectures, such as DeepFM and DCN-V2, using PyTorch to capture complex non-linear relationships within sparse categorical datasets. Develop custom embedding layers in PyTorch to map high-dimensional, sparse features (e.g., Ad IDs) into dense, low-dimensional vector spaces. Conduct systematic research into the trade-offs between model architecture complexity and inference speed, utilizing PyTorch profiling tools to identify and optimize bottleneck layers. 40 hours / week, 8:00am-5:00pm, Salary Range: $163,617/year to $193,200/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, WA, Redmond
Amazon Leo is Amazon’s low Earth orbit satellite constellation initiative designed to bring fast, affordable broadband connectivity to unserved and underserved communities around the world. We are building a next-generation satellite system from the ground up — designing everything from the spacecraft and payload to the ground infrastructure and customer terminals. This is a rare opportunity to join a team that is shaping the future of global connectivity at scale. The Leo Antenna team is looking for an RF Systems Scientist who is excited to work at the intersection of radio frequency engineering, phased array antennas, large-scale data analysis, and hardware reliability. You will turn data from our customer terminal fleet into engineering decisions. Every terminal in the field reports a steady stream of telemetry: downlink and uplink signal quality, link state, antenna pointing, temperature, and reboots. Every terminal was also tested in the factory before it shipped, and the network sees every contact it makes with a satellite. Your job is to connect these sources. You'll find out which field behaviors trace back to the antenna hardware and which come from the installation, the sky around the terminal, the network, or a software release. You'll also look for patterns that point to weaknesses in the design. Your findings will shape how we design, build, test, and support the next generation of customer terminals. A typical problem starts small. A few terminals spend far more time recovering their link than their neighbors, run a little hotter than the rest of the fleet, or reboot more often than they should. You'll work out whether it's a real effect or noise, whether it's spreading, and what the affected terminals have in common. They might share a hardware revision, a software version, a location, or a signature in their factory test history. From there you'll form a hypothesis about the physical cause and argue it in front of antenna, RF, and software engineers who will push back hard. You'll also have to say plainly when the data rules your own idea out. To find the cause, you'll pull in the rest of each terminal's history: its factory and thermal test results, its software and reboot record, and what the satellite measured on the other side of the link. Some questions can be answered from data we already collect. For the rest, you'll decide what new measurement or test would answer them, work with the teams who can run it, and report what the results show and what should happen next. Beyond individual investigations, you'll build the fleet-level view. That means expected performance for a healthy terminal given where it is and what it sees, early warning signals for hardware that is starting to fail, and measures of how software releases and hardware revisions change the fleet. You'll decide which recurring analyses should become automated monitoring and work with software engineers to build them into our fleet health system. You'll be the person the team turns to when someone asks "is this terminal normal?" The ideal candidate understands how radio links and phased array antennas behave, is curious about how hardware fails, and is comfortable with messy data from many sources. They can turn "a few terminals look odd" into a rigorous analysis and a clear recommendation. 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 Analyze customer terminal telemetry to measure antenna and link performance in the field, and detect failing hardware and slow degradation early Investigate underperforming terminals and field service requests, separating hardware effects from installation, obstruction, network, and software effects, and decide what should happen next Connect events across the fleet by hardware revision, manufacturing lot, software version, and location, and measure the effect of software releases and hardware changes on the fleet Correlate field behavior with factory and thermal test results, and feed what you learn back into test limits, screening, and the design of the next generation of terminals Define the fleet health metrics and baselines, specify the telemetry they need, and work with software engineers to turn recurring analyses into automated monitoring Build dashboards and AI-assisted tools that support fleet health reviews, field investigations, and design reviews Lead investigations that span several teams, from the first hypothesis to a decision, and present the evidence and recommendation to senior engineering leaders About the team The Leo Antenna team designs the phased array antenna inside Leo's customer terminals. It is the electronically steered panel that tracks satellites across the sky and carries every customer's connection. We own the antenna from simulation and design through factory test automation and thermal testing, and we own how it performs once it's installed at a customer's site. That includes the telemetry analysis and the fleet health system that keeps a daily hardware health record for every terminal in the field. We are a hardware-facing team that writes a lot of software, and we sit where several disciplines meet: antenna and RF design, terminal software, manufacturing, network operations, and field service. Every terminal has a part-level history, from its factory test results to every satellite contact it makes in the field. A large part of our work is investigation. When a terminal underperforms, we work out whether the cause is the hardware, the installation, the sky around it, the network, or the software, and we decide what should happen next. We have built analyses that map each terminal's view of the sky from its pointing and signal data, dashboards the wider organization uses every day, and AI-assisted tools that let engineers query telemetry and turn raw data into conclusions. We care about evidence over assumption. A ticket that lists a terminal doesn't explain it, and an obstruction request isn't an obstruction until the data shows one. Theories get tested against the data before they're accepted. Because we own both ends, from the first factory test to performance in the field, the loop is closed within the team. What we learn from the fleet goes straight back into our designs and test screens, so the next terminal we ship is more likely to work well for the customer who receives it.
US, WA, Seattle
Here at Amazon, we embrace our differences. We are committed to furthering our culture of diversity and inclusion of our teams within the organization. How do you get items to customers quickly, cost-effectively, and—most importantly—safely, in less than an hour? And how do you do it in a way that can scale? Our teams of hundreds of scientists, engineers, aerospace professionals, and futurists have been working hard to do just that! We are delivering to customers, and are excited for what’s to come. Check out more information about Prime Air on the About Amazon blog (https://www.aboutamazon.com/news/transportation/amazon-prime-air-delivery-drone-reveal-photos). If you are seeking an iterative environment where you can drive innovation, apply state-of-the-art technologies to solve real world delivery challenges, and provide benefits to customers, Prime Air is the place for you. Come work on the Amazon Prime Air Team! Prime Air's Flight Sciences High-Fidelity Methods (HFM) team is seeking an outstanding Applied Scientist to develop and verify drone systems models and flight physics models. These models form the backbone of every flight simulation performed within Prime Air, directly informing aircraft design, system verification, certification, and business decisions. The HFM team's work enables prediction of critical vehicle performance metrics—including range, maneuverability, tracking error, and aircraft stability—and connects vehicle design and operational decisions to business outcomes such as customer reachability. Our models are also a crucial input to the design of flight control algorithms and software verification. Because the accuracy and reliability of these models underpin so many facets of Prime Air's mission, the scientist in this role will have broad, high-visibility impact on the program's success. Key job responsibilities The Applied Scientist in this role will own the end-to-end lifecycle of simulation models—from development and deployment through verification and ongoing maintenance. This begins with gathering downstream customer needs, selecting the most suitable modeling approach and level of fidelity, and coordinating the generation of input data. It extends through model training, development and maintenance of software interfaces, and verification of model accuracy. A core aspect of this role is determining the right modeling approach for a given physical phenomenon. The scientist will need a working understanding of the physics and systems being modeled, including vehicle aerodynamics, propeller performance, multibody dynamics, atmospheric physics, electric powertrain components, and guidance and navigation system (GNS) sensors. They will design experiments to generate the data needed to build and verify models, and apply uncertainty quantification and statistical analyses to validate model fidelity.
US, CA, Palo Alto
Amazon Ads helps advertisers reach customers across Amazon's stores, Prime Video, Fire TV, Alexa, Twitch, and the open internet. Every ad we serve has to be safe, compliant, and trustworthy. The Ads Trust science team builds the AI systems that does this by reviewing billions of ads across text, image, video, audio, and product listings. We are looking for a Principal Applied Scientist to set the science direction for this work. This is an opportunity to apply as well as build state-of-the-art AI to problems where accuracy, scale, and customer trust all matter at once. This role suits a scientist who wants to own a hard problem end to end: inventing methods, proving them with strong evaluation, and putting them in front of customers. You will design the core modeling approach behind moderation at Amazon scale. That includes multimodal large language and vision-language models, retrieval-based labeling, model distillation for production, and customer facing agentic systems. You will take ambiguous, high-stakes problems, turn them into scientific roadmaps, and stay hands-on in the technical decisions that matter most. You will set the bar for scientific rigor, evaluation, and design reviews across a multi-team organization. You will also mentor senior scientists and partner with engineering, product, and policy leaders to get research into production. Key job responsibilities - Set the multi-year science strategy for automated content moderation, with high accuracy and efficiency as the goals. - Lead the design of multimodal and multilingual models for labeling and policy classification across text, image, video, audio, and product assets. - Drive methods that turn frontier-model quality into cost-efficient production systems, such as distillation, retrieval-augmented labeling, and efficient inference. - Define evaluation standards and measurement frameworks that set the quality bar for production models. - Own science low-level design reviews across teams and raise the technical bar for modeling, experimentation, and launch readiness. - Mentor and develop senior and mid-level scientists, and grow scientific leadership across the organization. - Influence engineering, product, and policy partners, and represent Amazon Ads science through publications and external collaborations.
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.