How we built Cedar with automated reasoning and differential testing

The new development process behind Amazon Web Services’ Cedar authorization-policy language.

Cedar is a new authorization-policy language used by the Amazon Verified Permissions and AWS Verified Access managed services, and we recently released it publicly. Using Cedar, developers can write policies that specify fine-grained permissions for their applications. The applications then authorize access requests by calling Cedar’s authorization engine. Because Cedar policies are separate from application code, they can be independently authored, updated, analyzed, and audited. 

Related content
CAV keynote lecture by the director of applied science for AWS Identity explains how AWS is making the power of automated reasoning available to all customers.

We want to assure developers that Cedar’s authorization decisions will be correct. To provide that assurance, we follow a two-part process we call verification-guided development when we’re working on Cedar. First, we use automated reasoning to prove important correctness properties about formal models of Cedar’s components. Second, we use differential random testing to show that the models match the production code. In this blog post we present an overview of verification-guided development for Cedar.

A primer on Cedar

Cedar is a language for writing and enforcing authorization policies for custom applications. Cedar policies are expressed in syntax resembling natural language. They define who (the principal) can do what (the action) on what target (the resource) under which conditions (when)?

To see how Cedar works, consider a simple application, TinyTodo, designed for managing task lists. TinyTodo uses Cedar to control who can do what. Here is one of TinyTodo’s policies:

// policy 1
permit(principal, action, resource)
when {
	resource has owner && resource.owner == principal
};

This policy states that any principal (a TinyTodo User) can perform any action on any resource (a TinyTodo List) as long as the resource’s creator, defined by its owner attribute, matches the requesting principal. Here’s another TinyTodo Cedar policy:

// policy 2
permit (
	principal,
	action == Action::"GetList",
	resource
)
when {
	principal in resource.editors || principal in resource.readers
};

This policy states that any principal can read the contents of a task list (Action::"GetList") if that principal is in either the list’s readers group or its editors group. Here is a third policy:

// policy 3
forbid (
	principal in Team::"interns",
	action == Action::"CreateList",
	resource == Application::"TinyTodo"
);

This policy states that any principal who is an intern (in Team::"interns") is forbidden from creating a new task list (Action::"CreateList") using TinyTodo (Application::"TinyTodo").

Related content
Meet Amazon Science’s newest research area.

When the application needs to enforce access, as when a user of TinyTodo issues a command, it only needs to make a corresponding request to the Cedar authorization engine. The authorization engine evaluates the request in light of the Cedar policies and relevant application data. If it returns decision Allow, TinyTodo can proceed with the command. If it returns decision Deny, TinyTodo can report that the command is not permitted.

How do we build Cedar to be trustworthy?

Our work on Cedar uses a process we call verification-guided development to ensure that Cedar’s authorization engine makes the correct decisions. The process has two parts. First, we model Cedar’s authorization engine and validator in the Dafny verification-aware programming language. With Dafny, you can write code, and you can specify properties about what the code is meant to do under all circumstances. Using Dafny’s built-in automated-reasoning capabilities we have proved that the code satisfies a variety of safety and security properties.

Second, we use differential random testing (DRT) to confirm that Cedar’s production implementation, written in Rust, matches the Dafny model’s behavior. We generate millions of diverse inputs and feed them to both the Dafny model and the production code. If both versions always produce the same output, we have a high degree of confidence that the implementation matches the model.

Cedar figure.png
Building Cedar using automated reasoning and differential testing.

Proving properties about Cedar authorization

 Cedar’s authorization algorithm was designed to be secure by default, as exemplified by the following two properties:

  • explicit permit — permission is granted only by individual permit policies and is not gained by error or default;
  • forbid overrides permit — any applicable forbid policy always denies access, even if there is a permit policy that allows it.

With these properties, sets of policies are easier to understand. Policy authors know that permit policies are the only way access is granted, and forbid policies decline access regardless of whether it is explicitly permitted.

Related content
Distributing proof search, reasoning about distributed systems, and automating regulatory compliance are just three fruitful research areas.

Given an authorization request, the Cedar authorization engine takes each Cedar policy and evaluates it after substituting the application request parameters into the principal, action and resource variables. For example, for the request principal= User::”Alice”, action=Action::”GetList”, and resource=List::”AliceList”, substituting for the variables in policy 1 would produce the expression List::”AliceList” has owner && List::”AliceList”.owner == User::”Alice”. If this expression evaluates to true, we say the request satisfies the policy. The authorization engine collects the satisfied forbid and permit policies into distinct sets and then makes its decision.

We model the authorization engine as a Dafny function and use Dafny’s automated-reasoning capabilities to state and prove the explicit-permit and forbid-overrides-permit properties. To see how this helps uncover mistakes, let’s consider a buggy version of the authorization engine:

function method isAuthorized(): Response { // BUGGY VERSION
	var f := forbids();
	var p := permits();
	if f != {} then
		Response(Deny, f)
	else
		Response(Allow, p)
}

The logic states that if any forbid policy is applicable (set f is not the empty set {}), the result should be Deny, thus overriding any applicable permit policies (in set p). Otherwise, the result is Allow. While this logic correctly reflects the desired forbid-overrides-permit property, it does not correctly capture explicit permit. Just because there are no applicable forbid policies doesn’t mean there are any applicable permit policies. We can see this by specifying and attempting to prove explicit permit in Dafny:

// A request is explicitly permitted when a permit policy is satisfied
predicate IsExplicitlyPermitted(request: Request, store: Store) {
	exists p ::
		p in store.policies.policies.Keys &&
		store.policies.policies[p].effect == Permit &&
		Authorizer(request, store).satisfied(p)
}
lemma AllowedIfExplicitlyPermitted(request: Request, store: Store)
ensures // A request is allowed if it is explicitly permitted
	(Authorizer(request, store).isAuthorized().decision == Allow) ==>
	IsExplicitlyPermitted(request, store)
{ ... }

A Dafny predicate is a function that takes arguments and returns a logical condition, and a Dafny lemma is a property to be proved. The IsExplicitlyPermitted predicate defines the condition that there is an applicable permit policy for the given request. The AllowedIfExplicitlyPermitted lemma states that a decision of Allow necessarily means the request was explicitly permitted. This lemma does not hold for the isAuthorized definition above; Dafny complains that A postcondition might not hold on this return path and points to the ensures clause.

Here is the corrected code:

function method isAuthorized(): Response {
	var f := forbids();
	var p := permits();
	if f == {} && p != {} then
		Response(Allow, p)
	else
		Response(Deny, f)
}

Now a response is Allow only if there are no applicable forbid policies, and there is at least one applicable permit policy. With this change, Dafny automatically proves AllowedIfExplicitlyPermitted. It also proves forbid overrides permit (not shown).

Related content
To mark the occasion of the eighth Federated Logic Conference (FloC), Amazon’s Byron Cook, Daniel Kröning, and Marijn Heule discussed automated reasoning’s prospects.

We have used the Cedar Dafny models to prove a variety of properties. Our most significant proof is that the Cedar validator, which confirms that Cedar policies are consistent with the application’s data model, is sound: if the validator accepts a policy, evaluating the policy should never result in certain classes of error. When carrying out this proof in Dafny, we found a number of subtle bugs in the validator’s design that we were able to correct.

We note that Dafny models are useful not just for automated reasoning but for manual reasoning, too. The Dafny code is much easier to read than the Rust implementation. As one measure of this, at the time of this writing the Dafny model for the authorizer has about one-sixth as many lines of code as the production code. Both Cedar users and tool implementers can refer to the Dafny models to quickly understand precise details about how Cedar works.

Differential random testing

Once we have proved properties about the Cedar Dafny model, we want to provide evidence that they hold for the production code, too, which we can do by using DRT to show that the model and the production code behave the same. Using the cargo fuzz random-testing framework, we generate millions of inputs — access requests, accompanying data, and policies — and send them to both the Dafny model engine and the Rust production engine. If the two versions agree on the decision, then all is well. If they disagree, then we have found a bug.

The main challenge with using DRT effectively is to ensure the necessary code coverage by generating useful and diverse inputs. Randomly generated policies are unlikely to mention the same groups and attributes chosen in randomly generated requests and data. As a result, pure random generation will miss a lot of core evaluation logic and overindex on error-handling code. To resolve this, we wrote several input generators, including ones that take care to generate policies, data, and requests that are consistent with one another, while also producing policies that use Cedar’s key language constructs. As of this writing, we run DRT for six hours nightly and execute on the order of 100 million total tests.

Related content
Rungta had a promising career with NASA, but decided the stars aligned for her at Amazon.

The use of DRT during Cedar’s development has discovered corner cases where there were discrepancies between the model and the production code, making it an important tool in our toolkit. For example, there was a bug in a Rust package we were using for IP address operations; the Dafny model exposed an issue in how the package was parsing IP addresses. Since the bug is in an external package, we fixed the problem within our code while we wait for the upstream fix. We also found subtle bugs in the Cedar policy parser, in how the authorizer handles missing application data, and how namespace prefixes on application data (e.g., TinyTodo::List::”AliceList”) are interpreted.

Learn more

In this post we have discussed the verification-guided development process we have followed for the Cedar authorization policy language. In this process, we model Cedar language components in the Dafny programming language and use Dafny’s automated-reasoning capabilities to prove properties about them. We check that the Cedar production code matches the Dafny model through differential random testing. This process has revealed several interesting bugs during development and has given us greater confidence that Cedar’s authorization engine makes correct decisions.

To learn more, you can check out the Cedar Dafny models and differential-testing code on GitHub. You can also learn more about Dafny on the Dafny website and the Cedar service on the Cedar website.

Related content

US, CA, Sunnyvale
The Region Flexibility Engineering (RFE) team builds and leverages foundational infrastructure capabilities, tools, and datasets needed to support the rapid global expansion of Amazon's SOA infrastructure. Our team focuses on robust and scalable architecture patterns and engineering best practices, driving adoption of ever-evolving and AWS technologies. RFE is looking for a passionate, results-oriented, inventive Data Scientist to refine and execute experiments towards our grand vision, influence and implement technical solutions for regional placement automation, cross-region libraries, and tooling useful for teams across Amazon. As a Data Scientist in Region Flexibility, you will work to enable Amazon businesses to leverage new AWS regions and improve the efficiency and scale of our business. Our project spans across all of Amazon Stores, Digital and Others (SDO) Businesses and we work closely with AWS teams to advise them on SDO requirements. As innovators who embrace new technology, you will be empowered to choose the right highly scalable and available technology to solve complex problems and will directly influence product design. The end-state architecture will enable services to break region coupling while retaining the ability to keep critical business functions within a region. This architecture will improve customer latency through local affinity to compute resources and reduce the blast radius in case of region failures. We leverage off the sciences of data, information processing, machine learning, and generative AI to improve user experience, automation, service resilience, and operational efficiency. Key job responsibilities As an RFE Data Scientist, you will work closely with product and technical leaders throughout Amazon and will be responsible for influencing technical decisions and building data-driven automation capabilities in areas of development/modeling that you identify as critical future region flexibility offerings. You will identify both enablers and blockers of adoption for region flex, and build models to raise the bar in terms of understanding questions related to data set and service relationships and predict the impact of region changes and provide offerings to mitigate that impact. About the team The Regional Flexibility Engineering (RFE) organization supports the rapid global expansion of Amazon's infrastructure. Our projects support Amazon businesses like Stores, Alexa, Kindle, and Prime Video. We drive adoption of ever-evolving and AWS and non-AWS technologies, and work closely with AWS teams to improve AWS public offerings. Our organization focuses on robust and scalable solutions, simple to use, and delivered with engineering best practices. We leverage and build foundational infrastructure capabilities, tools, and datasets that enable Amazon teams to delight our customers. With millions of people using Amazon’s products every day, we appreciate the importance of making our solutions “just work”.
US, WA, Seattle
The Sponsored Products and Brands team at Amazon Ads is re-imagining the advertising landscape through 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. We are looking for an Applied Scientist to build the science that helps Amazon's advertisers grow — with a focus on Cross Border Sellers who face distinct barriers as they scale across multiple marketplaces, and this role is about understanding those pain points deeply and removing them: building intelligent, autonomous solutions that simplify advertising, act efficiently on the advertiser's behalf, and let advertisers accelerate their growth and success. We expect Scientist to think innovatively about how to reduce the effort and complexity of advertising for these advertisers. Working backwards from their needs — spanning hands-off sellers and global brands with cross-marketplace operations — you will take the lead on medium-to-large, ambiguous problems where neither the problem nor the solution is well defined, invent new methods, validate them through rigorous experimentation, and deliver customer-facing products with measurable business impact. This role combines science depth, product focus, and hands-on engineering: you will raise the science bar, build consensus on approach across product and engineering partners, and mentor scientists and engineers while remaining deeply hands-on with the hardest technical problems. Key job responsibilities As an Applied Scientist on this team you will: - Understand the pain points of Cross border advertisers as they scale across marketplaces, and build science-driven solutions that remove barriers and accelerate their growth and success. - Build agentic and ML systems that autonomously create, structure, and manage ad campaigns on advertisers' behalf, encoding auction and marketplace dynamics (bidding, budget pacing, targeting decisions) while balancing advertiser ROI, shopper experience, and marketplace health. - Innovate on new, simpler ways to advertise powered by GenAI, and push the frontier of existing autonomous programs (e.g., auto-targeting, global lift-and-shift) while proposing and prototyping the next generation of campaign automation. - Develop models across the campaign lifecycle — opportunity discovery, ranking, ad-readiness and demand prediction, and bid/budget optimization — and apply the right approach for each problem, from classical ML to LLM/reasoning methods. - Define and curate the datasets and signals needed to train and evaluate these systems — advertiser and campaign data, cross-marketplace performance, auction and bid/budget signals, impressions, clicks, conversions, and search-term/keyword performance. - Own core parts of the agentic architecture — planning, tool use and integration (e.g., MCP), reasoning frameworks (e.g., ReAct, CoT/ToT), and model customization — and define evaluation and safety methodology so that automated decisions are reliable and trustworthy. - Stay deeply hands-on: write production-quality, critical-path code and build core components that take systems from prototype to launch on large-scale pipelines (Spark/EMR, Airflow) and online serving. - Raise the science bar: review designs and experiment plans, and communicate results and tradeoffs clearly to technical and business leaders. About the team Autonomous SP drives growth and simplifies advertising for Amazon's hands-off advertisers by creating and enhancing autonomous campaign solutions. We lead existing successful programs, including auto-targeting and global lift-and-shift, and continually innovate by building new, simpler campaign constructs powered by GenAI to act efficiently on advertisers' behalf. Cross-border Seller Experience (CBSX) focuses on developing targeted solutions for domestic and global advertisers with multi-marketplace operations. By understanding and addressing their unique Seller Central needs, we optimize for cross-marketplace efficiency, improved performance, and streamlined advertising experiences. Our team operates horizontally, delivering impactful solutions that benefit both hands-on and hands-off advertisers globally. Together, we sit within Sponsored Products and Brands, which is re-imagining advertising through the latest generative AI — building responsible, intelligent systems that balance the needs of advertisers, the shopping experience, and marketplace health.
US, WA, Seattle
MULTIPLE POSITIONS AVAILABLE Employer: AMAZON WEB SERVICES, INC. Offered Position: Data Scientist III Job Location: Seattle, Washington Job Number: AMZ10593723 Position Responsibilities: Own the data science elements of various products to help with data-based decision making, product performance optimization, and product performance tracking. Work directly with product managers to help drive the design of the product. Work with Technical Product Managers to help drive the build planning. Translate business problems and products into data requirements and metrics. Initiate the design, development, and implementation of scientific analysis projects or deliverables. Own the analysis, modelling, system design, and development of data science solutions for products. Write documents and make presentations that explain model/analysis results to the business. Bridge the degree of uncertainty in both problem definition and data scientific solution approaches. Build consensus on data, metrics, and analysis to drive business and system strategy. Position Requirements: Master's degree or foreign equivalent degree in Statistics, Applied Mathematics, Economics, Engineering, Computer Science or a related field and two years of experience in the job offered or a related occupation. Employer will accept a Bachelor's degree or foreign equivalent degree in Statistics, Applied Mathematics, Economics, Engineering, Computer Science, or a related field and five years of progressive post-baccalaureate experience in the job offered or a related occupation as equivalent to the Master's degree and two years of experience. Must have one year of experience in the following skills: (1) building statistical models and machine learning models using large datasets from multiple resources; (2) building complex data analyses by leveraging scripting languages including Python, Java, or related scripting language; and (3) communicating with users, technical teams, and management to collect requirements, evaluate alternatives, and develop processes and tools to support the organization. Amazon.com is an Equal Opportunity-Affirmative Action Employer – Minority / Female / Disability / Veteran / Gender Identity / Sexual Orientation. 40 hours / week, 8:00am-5:00pm, Salary Range $166,036/year to $215,300/year. Amazon is a total compensation company. Dependent on the position offered, equity, sign-on payments, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits. For more information, visit: https://www.aboutamazon.com/workplace/employee-benefits.#0000
US, WA, Seattle
Are you excited about using economic reasoning to shape decisions that affect millions of customers? Do you want to tackle ambiguous, high-impact problems where your analysis directly influences strategy and investment? We are looking for a Senior Economist to join Amazon and drive economic solutions for complex business challenges. In this role, you will define and prioritize analytical approaches, build rigorous econometric models, and translate findings into actionable recommendations for leadership. You will partner with engineers, product managers, scientists, and business leaders to deliver measurable outcomes. If you thrive on turning unstructured problems into clear, data-driven strategies, this is the role for you. Key job responsibilities - Lead the design, implementation, and delivery of economic analyses for complex or ambiguous business problems, providing strategic direction that informs organizational goals and investment decisions. - Develop and apply econometric models—including causal inference, structural estimation, and forecasting methods—choosing the right approach for each problem and validating results through rigorous testing. - Collaborate with cross-functional partners including engineers, product managers, and applied scientists to implement scalable solutions and translate economic insights into product and business improvements. - Communicate findings through clear narratives and technical documents for audiences ranging from peer economists to senior leaders, building consensus and influencing key decisions. - Evaluate and integrate generative AI tools where appropriate to augment research productivity, while mentoring other economists and raising the bar on analytical best practices across the team. A day in the life You might start your morning reviewing model performance metrics and refining an econometric specification before a working session with engineers on data pipeline requirements. After lunch, you could present preliminary findings from a causal analysis to business stakeholders, fielding questions and aligning on next steps. Later in the afternoon, you join a peer review for a fellow economist's research design, offering constructive feedback. Throughout the day, you balance hands-on analytical work with strategic conversations that connect your research to real business outcomes. About the team Our team of economists partners across Amazon to solve some of the company's most consequential business questions. We combine deep expertise in economic theory and applied econometrics with access to rich, large-scale data to deliver insights that shape long-term strategy. We value intellectual curiosity, collaborative problem-solving, and a commitment to rigorous science. If you are looking for an environment where your economic thinking directly drives impact at scale, we would love to hear from you.
US, WA, Redmond
Amazon Leo is building a low Earth orbit satellite broadband network to bring fast, affordable connectivity to customers worldwide. We're looking for a Senior Applied Scientist to invent the machine learning that will let the network predict, explain and prevent its own failures. You'll work on open research problems at large scale. These include anomaly detection on non-stationary, high-dimensional telemetry, causal root-cause inference over constantly changing satellite and ground network graphs, and trustworthy ML for operators making decisions under pressure. You'll own the science agenda, from forming hypotheses and designing new models to putting them into production systems that protect customer connectivity. Export Control Requirement: Due to applicable export control laws and regulations, candidates must be a U.S. citizen or national, U.S. permanent resident (i.e., current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum. Key job responsibilities Define and lead a multi-year applied research agenda in network observability, anomaly prediction and availability modeling. Invent new time-series and spatio-temporal graph models, such as graph neural networks (GNNs), foundation models and dynamic baselining, to predict network and ground-segment failures before customers are affected. Develop causal inference and causal discovery methods for automated root-cause attribution across a large, interdependent event surface. Research probabilistic models that break availability and throughput into causal drivers (coverage, ground, network, terminal, payload, planning) and separate true signal from noise. Advance methods for alert correlation, deduplication, uncertainty quantification and metric-quality scoring. Explore large language models (LLMs) and agentic approaches for reasoning over telemetry, logs and incident narratives. Design rigorous offline and online evaluation, including backtesting against real closed incidents and gameday-based benchmarks. Take research into production on AWS (SageMaker, Bedrock), working with engineers on scalability, drift detection and explainability. Publish at top-tier venues, file patents and raise the scientific bar through mentoring and design reviews. A day in the life You might start the morning reading new literature on causal discovery and sketching how it applies to Leo's network graph. Later you could review a scientist's experiment design and debate the best evaluation methodology. During an event, you would test your attribution model live on the incident call. You might finish the day prototyping a new spatio-temporal anomaly detector and backtesting it against last quarter's incidents. About the team Amazon Leo Networking Software builds the software behind Leo's satellite and ground network. Our applied science team works on hard, open-ended problems with real-world impact. We value scientific rigor, curiosity and ownership, and we encourage publishing and contributing to the research community. As a Senior Applied Scientist, you'll help build this science function from the ground up and set the technical bar for the scientists who join after you.
US, WA, Bellevue
We are seeking a Senior Applied Scientist to push the state of the art in robot learning and help bring capable robots out of the lab and into everyday homes at Fauna Robotics. In this role, you will design novel algorithms across perception, manipulation, sim2real transfer, reinforcement learning, and multi-task learning, closing the gap between research and real-world deployment. You will work where robotics research meets production systems. You'll combine hands-on technical work with scientific leadership to guide the team toward the most promising directions. Working closely with software engineers and scientists, you will turn new ideas into robust solutions for dynamic, unstructured home environments. Homes bring challenges that structured settings like warehouses don't, and consumer-grade sensors and actuators have real limits, so this work calls for creative, out-of-the-box approaches. Key job responsibilities - Lead technical initiatives in areas such as robotics foundation models, reinforcement learning and manipulation - - Design experiments to identify the limitations of current state-of-the-art models and developing new models or techniques that can surpass these models - Design and implement novel deep learning architectures that push the boundaries of what robots can understand and accomplish - Mentor fellow scientists while maintaining strong individual technical contributions - Collaborate with engineering teams to optimize and scale models for real-world applications - Influence technical decisions and implementation strategies within your area of focus - Experienced in communicating complex technical work to a non-technical audience - The ability to work with minimal guidance, be proactive and to handle ambiguity and the challenge of quickly evolving goals About the team Fauna Robotics, an Amazon company, is building capable, safe, and genuinely delightful robots for everyday life. Our goal is simple: make robots people actually want to live and interact with in everyday human spaces. We believe that future won’t arrive until building for robotics becomes far more accessible. Today, too much effort is spent reinventing the fundamentals. We’re changing that by developing tightly integrated hardware and software systems that make it faster, safer, and more intuitive to create real-world robotic products. Our work spans the full stack: mechanical design, control systems, dynamic modeling, and intelligent software. The focus is not just functionality, but experience. We’re building robots that feel responsive, expressive, and genuinely useful. At Fauna, you’ll work at the frontier of this space, helping define how robots move, manipulate, and interact with people in natural environments. It’s an opportunity to solve hard problems across hardware and software with a team focused on making robotics accessible and joyful to build. If you care about making robotics real for everyone and building systems that are as delightful as they are capable, we’re interested in hearing from you.
US, WA, Seattle
MULTIPLE POSITIONS AVAILABLE Employer: AMAZON.COM SERVICES LLC Offered Position: Research Scientist II Job Location: Seattle, Washington Job Number: AMZ10564041 Position Responsibilities: Interact with various software and business groups to develop an understanding of their business requirements and operational processes. Utilize acquired knowledge and business judgment to build decision-supporting and operational tools to improve the bottom line. Build quantitative mathematical models to represent a wide range of supply chain, transportation and logistics systems. Implement these models and tools through the use of modeling languages and engineering code in software languages such as Java, C++, C# or C. Gather required data for analysis and mathematical model building by writing ad-hoc scripts and database queries. Perform quantitative, economic, and numerical performance analyses of these systems under uncertainty using statistical and optimization tools. Create computer simulations to support operational decision-making. Identify areas with potential for improvement and work with internal teams to generate requirements to realize improvements. Design optimal or near optimal solution methodologies to be used by in-house decision support tools and software. Create software prototypes to verify and validate the devised solutions methodologies. Integrate prototypes into production systems using standard software development tools and methodologies. 40 hours / week, 8:00am-5:00pm, Salary Range: $136,000/year to $184,000/year Amazon is a total compensation company. Dependent on the position offered, equity, sign-on payments, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits. For more information, visit: https://www.aboutamazon.com/workplace/employee-benefits. Amazon.com is an Equal Opportunity-Affirmative Action Employer – Minority / Female / Disability / Veteran / Gender Identity / Sexual Orientation.#0000
US, NY, New York
MULTIPLE POSITIONS AVAILABLE Employer: AMAZON.COM SERVICES LLC Offered Position: Applied Scientist II Job Location: New York, New York Job Number: AMZ10564066 Position Responsibilities: Participate in the design, development, evaluation, deployment and updating of data-driven models and analytical solutions for machine learning (ML) and/or natural language (NL) applications. Develop and/or apply statistical modeling techniques (e.g. Bayesian models and deep neural networks), optimization methods, and other ML techniques to different applications in business and engineering. Routinely build and deploy ML models on available data. Research and implement novel ML and statistical approaches to add value to the business. Mentor junior engineers and scientists. 40 hours / week, 8:00am-5:00pm, Salary Range: $172,400/year to $223,400/year. Amazon is a total compensation company. Dependent on the position offered, equity, sign-on payments, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits. For more information, visit: https://www.aboutamazon.com/workplace/employee-benefits. Amazon.com is an Equal Opportunity-Affirmative Action Employer – Minority / Female / Disability / Veteran / Gender Identity / Sexual Orientation.#0000
US, TX, Austin
MULTIPLE POSITIONS AVAILABLE Employer: AMAZON.COM SERVICES LLC Offered Position: Data Scientist III Job Location: Austin, Texas Job Number: AMZ10593703 Position Responsibilities: Own the data science elements of various products to help with data-based decision making, product performance optimization, and product performance tracking. Work directly with product managers to help drive the design of the product. Work with Technical Product Managers to help drive the build planning. Translate business problems and products into data requirements and metrics. Initiate the design, development, and implementation of scientific analysis projects or deliverables. Own the analysis, modelling, system design, and development of data science solutions for products. Write documents and make presentations that explain model/analysis results to the business. Bridge the degree of uncertainty in both problem definition and data scientific solution approaches. Build consensus on data, metrics, and analysis to drive business and system strategy. Position Requirements: Master's degree or foreign equivalent degree in Statistics, Applied Mathematics, Economics, Engineering, Computer Science or a related field and two years of experience in the job offered or a related occupation. Employer will accept a Bachelor's degree or foreign equivalent degree in Statistics, Applied Mathematics, Economics, Engineering, Computer Science, or a related field and five years of progressive post-baccalaureate experience in the job offered or a related occupation as equivalent to the Master's degree and two years of experience. Must have one year of experience in the following skills: (1) building statistical models and machine learning models using large datasets from multiple resources; (2) building complex data analyses by leveraging scripting languages including Python, Java, or related scripting language; and (3) communicating with users, technical teams, and management to collect requirements, evaluate alternatives, and develop processes and tools to support the organization. Amazon.com is an Equal Opportunity-Affirmative Action Employer – Minority / Female / Disability / Veteran / Gender Identity / Sexual Orientation. 40 hours / week, 8:00am-5:00pm, Salary Range $159,200/year to $215,300/year. Amazon is a total compensation company. Dependent on the position offered, equity, sign-on payments, and other forms of compensation may be provided as part of a total compensation package, in addition to a full range of medical, financial, and/or other benefits. For more information, visit: https://www.aboutamazon.com/workplace/employee-benefits. #0000
US, WA, Seattle
Amazon Ads is one of the fastest-growing advertising businesses in the world, connecting brands with hundreds of millions of customers across shopping, streaming, gaming, audio and the open web. Behind every ad that runs on Prime Video, Twitch, IMDb and thousands of external publisher apps and sites is a decisioning platform built by Amazon Ads Supply Tech. That platform makes X trillion ad decisions every day and supports $XB+ in annual publisher revenue across XX+ Amazon-owned publishers and X,000+ external publishers in streaming TV, audio, display, mobile and podcasts. Every one of those decisions is a science problem: which inventory qualifies for which buyers, how publisher commitments are paced and delivered, which ad wins among competing candidates, and what price maximizes long-term yield. Each must be solved in milliseconds, under strict latency and cost budgets, while balancing advertisers, publishers, viewers and Amazon. At this scale, a fraction-of-a-percent model improvement is worth $X millions. We are looking for a Principal Applied Scientist to set the science strategy for this platform. You will decide where machine learning creates the most value, bring intelligence into real-time runtime systems, and lead models from idea to production. Your work will directly shape three of Amazon Ads’ biggest priorities: growing Amazon-owned and third-party supply, enabling full-funnel advertising, and building agentic, AI-driven workflows for publishers and advertisers. As a principal, you will be a technical leader across the organization. You will raise the science bar, mentor senior scientists, and influence product and engineering leaders. You will work alongside excellent, driven scientists, engineers and product leaders who take on hard problems and invest in each other’s growth. Few places in the world operate at this scale. Key job responsibilities - Define the ML strategy for the ad decisioning platform. Set a multi-year science vision across pricing, yield optimization, forecasting, ad selection and commitment delivery, tied to measurable business outcomes. - Identify opportunities to deploy intelligence in runtime systems. Find where rules and heuristics in real-time serving paths can be replaced or improved by learned models, and partner with engineering to fit them within latency, compute and reliability budgets. - Build ML models that operate at X trillion decisions a day, drawing on approaches such as deep learning, reinforcement learning and bandits, causal inference, forecasting, and auction and mechanism design. - Evaluate ML models rigorously. Design offline, counterfactual and off-policy evaluations and online experiments. Define metrics that capture long-term value for advertisers, publishers and viewers, not just short-term lift. - Refine models for output quality and performance. Improve accuracy, calibration and robustness, cut serving latency and cost, and monitor models in production for drift and degradation. - Lead science across the organization. Set technical standards, review science designs and launches, and mentor and grow senior and principal-track scientists. - Push the frontier, including LLM and agentic approaches, and contribute to Amazon’s internal and external science community through papers, talks and patents. A day in the life Start the day reviewing off-policy evaluation results for a new pricing model that projects an X% yield lift, and deciding with your team whether it is ready for an online test. Next, you work with engineers on fitting a deeper model into a millisecond latency budget at X billion requests. At midday, you dig into why a forecasting model drifted during a live sports event, and sketch a fix. Later, you review a scientist’s paper draft and present the science roadmap to product leaders. Throughout, you work with brilliant, driven colleagues who sharpen your thinking and help you grow. About the team Ads Decisioning team brings together applied scientists and product managers to build the intelligence behind Amazon’s publisher business. We serve Amazon-owned publishers such as Prime Video, Twitch and IMDb, along with thousands of external publishers across streaming TV, audio and display. Our models decide, in milliseconds, which inventory qualifies for which buyers, how commitments are delivered, which ad wins and at what price, balancing advertisers, publishers, viewers and Amazon. We pair scientific rigor with a bias for production impact, learn from each other, and invest in each other’s growth. Come solve problems few teams anywhere get to work on.