BenchProofer: Formally verified coding benchmarks, on demand

New open-source tool turns existing test suites into sets of formal-verification tasks, which catch buggy solutions that tests alone would miss.

Key takeaways
  • BenchProofer is a new open-source Amazon tool that strengthens coding benchmarks by generating a formal specification, reference implementation, and machine-checked proof for each task — catching buggy fixes that pass tests but fail on untested inputs.
  • In testing, the audit flagged nearly one in three of Claude Opus 4.8's test-passing patches for behavior that differed from the reference fix. In a human-reviewed sample, about half of the flagged patches (21 of 41) had real bugs. Agents hit higher verified pass rates when given BenchProofer's specifications (Opus 4.8: 84.6%→93.6%; GPT-5.5: 79.6%→94.4%).
Was this answer helpful?

Today we measure coding agents by counting how many benchmark tasks they resolve, and we decide whether a task is resolved by running a suite of tests. But an agent can pass every test and still be wrong on inputs no test happens to check.

Worse, agents can learn to game the tests instead of learning to solve the underlying programming problems. This makes it harder to trust the agents when decisions matter most. Businesses may make roadmap decisions based on the outcome of a specific evaluation. And as more companies use reinforcement learning in their post-training processes, results on benchmarks are increasingly becoming the reward signal we use to train the agents. Inaccurate benchmarking poses the risk that agents will learn from results that are incorrect.

A new open-source tool from Amazon called BenchProofer uses automated reasoning to strengthen coding benchmarks. Benchproofer uses each task's reference solution to generate a formal specification; an implementation in a language amenable to formal verification; and a proof that the implementation satisfies the specification, under the stated assumptions. The proof is then checked by a verifier, and tests and audits check the implementation’s correspondence with the repository code.

Alongside the tool, we are releasing SWE-Proof, which adds these specifications, implementations, and proofs to all 500 tasks in the SWE-Bench Verified dataset.

What BenchProofer does

To get a sense of how BenchProofer works, consider a simple example. Someone files a bug report that says "the function that finds the largest number in a list returns the wrong answer on some inputs." The reference fix is a corrected find_max function. In an ordinary benchmark, an agent's fix is judged by running a few test cases; for example, find_max([3, 1, 2]) should return 3. If it passes those tests, the fix is counted as correct, even if it would return the wrong answer on some untested inputs.

The first artifact BenchProofer adds is a specification, which is a precise statement of what a correct answer must do, written so a machine can check it. For find_max, the specification would use a formal language such as Lean to express the following requirement: "For any nonempty list, the returned value must belong to the list, and no element may be larger than it".

The second artifact that BenchProofer adds is a reference implementation, an actual solution written in a language the verifier understands. The third is a proof, a step-by-step argument that the implementation satisfies the specification. A tool called a verifier — Lean’s proof checker is one example — checks the proof automatically, much the way a compiler checks types. If the proof goes through, we know the implementation meets the specification on every input it covers, as long as the proof’s assumptions hold.

BenchProofer schematic
BenchProofer builds a verified instance from a task with a known solution (top), and a coding agent is evaluated against the released formal specification (bottom).

Using the verified benchmark

Once BenchProofer has built these artifacts, we can use them to evaluate other fixes for the same task. An upgraded benchmark supports two evaluation modes. In audit mode, you run your coding agent through the benchmark's usual workflow and collect the repository patch it produces. The specification generated by BenchProofer guides additional tests that look for differences between the reference implementation and patches that pass the benchmark’s original tests.

In verified mode, the agent also receives the specification and a verification tool. Alongside its repository patch, the coding agent produces a separate implementation of the fix that the verifier can check against the specification. Once the verifier accepts the proof, we have a verified implementation. The repository patch must also pass the repository tests. The final audit checks whether the patch and the verified implementation describe the same behavior. A successful submission therefore pairs a test-passing repository patch with a verified implementation of the fix.

Building your own benchmark

To build your own verified benchmark, give BenchProofer coding tasks from your own projects, such as bugs your team has already fixed.

How BenchProofer works

BenchProofer needs three things per task, all of which existing benchmarks already have. It needs a plain-English description of the problem, such as a GitHub issue. It needs a reference solution accepted as correct. And it needs a mechanical way to check candidate fixes, typically the existing test suite and its harness, the software that sets up the repository, applies a patch, runs the tests, and reports which ones pass.

Real codebases are far too large to verify end to end, so BenchProofer draws a boundary around newly written code and verifies only that. For each existing function the new code calls, BenchProofer generates a short contract that it tests — but does not verify — automatically.

Suppose, for instance, that the fix for find_max calls an existing function, smaller(a, b), which the codebase already includes. BenchProofer records a contract for it, such as "the value it returns is never larger than either input." Then it checks the contract by running the real smaller on many inputs. The proof of find_max relies on that contract, rather than on formal verification of smaller, which keeps verification tractable even inside a large repository.

Once we have the three artifacts and their contracts for all tasks in the benchmark, we put them through a battery of checks we call gates. Some gates are logic based. They confirm that verification of the reference proof succeeds, that verification of the pre-fix implementation against the same specification fails, that the corresponding patch passes the benchmark tests, that the specification rules out the original bug, or that the reference solution matches the real patch.

Other gates use adversarial agents to look for specifications that are too weak or too restrictive or that reveal the answer. A failure on either type of gate sends the task back for revision.

The verification options are Lean, Nagini for Python code with preconditions and postconditions, or Velvet for imperative programs written and verified within Lean.

BenchProofer workflow
The full BenchProofer workflow. (1) A real issue and repository become (2) a benchmark instance that must (3) pass mechanical and adversarial gates before release; at (4) evaluation, the solver sees only the issue, the repository, and the specification view.

Case study: SWE-Proof

We ran BenchProofer over all 500 tasks of SWE-Bench Verified, a benchmark that frontier models perform extremely well on — when their solutions are assessed by testing alone. For each task, the tool generated a specification, a reference implementation, a proof, and contracts for the unchanged functions called by the modified code.

We then checked the generated artifacts using repository tests, formal verification, and adversarial audits. We built each task for all three verification backends — Lean, Nagini, and Velvet — and released everything, including the verdict of every gate, so anyone can recheck the results independently.

We then compared Claude Opus 4.8 and GPT-5.5, the latest models from each provider when we ran the study, on both the standard SWE-Bench Verified benchmark and our verified version, SWE-Proof. (Applying the same methodology to later generations of Opus is a natural direction for future work.)

Finding 1: Tests can miss behavioral differences

Claude Opus 4.8 passes the standard SWE-Bench Verified tests on 425 of the 500 tasks (85.0%). But BenchProofer's audit agent uses the reference specifications to generate additional tests that look for behavior the original tests missed. On those tests, 134 of the 425 patches, nearly one in three, fail, while the reference patch passes.

Automated audit results

Opus 4.8

GPT-5.5

Pass benchmark tests

425 (85.0%)

406 (81.2%)

Flagged among the passing patches

134 (26.8%)

239 (47.8%)

Percentages are out of all 500 SWE-Bench Verified tasks. All flagged patches passed the benchmark tests.

With 291 of Opus 4.8’s patches (58.2% of all tasks), audit mode finds no difference between their behavior and those of the reference patches. However, the patches that do exhibit behavioral differences may still solve the original problem. To understand whether the flagged differences indicated actual bugs, human reviewers examined a random sample of 41 of the 134 flagged Opus patches. They identified 21 defects, including missed corner cases or incorrect behaviors. The other 20 were valid fixes.

Finding 2: Agents achieve higher verified pass rates when given formal specifications

The same agents achieve more verified passes when given the formal specification. When Opus 4.8 writes its own specification — instead of using the one generated by BenchProofer — its verified pass rate is 84.6%, with Lean as the backend. When it uses BenchProofer’s specification, its pass rate rises to 93.6%. GPT-5.5 rises from 79.6% to 94.4%.

Specification used

Opus 4.8

GPT-5.5

Agent writes its own

423 (84.6%)

398 (79.6%)

Benchmark specification supplied

468 (93.6%)

472 (94.4%)

Verified passes using Lean. Percentages are out of all 500 SWE-Bench Verified tasks.

To count as a verified pass, the patch must meet three conditions: it must pass the repository tests; the Lean implementation of the fix must have a proof accepted by Lean's proof checker; and an audit must find no difference in behavior between the verified implementation and the patched code.

The specification points the agent to the relevant functions, so we tested how much that guidance alone helped. We found that the specification's faithfulness and the verified implementation's correspondence with the Python patch still require validation.

Finding 3: Agents struggle to generate faithful formal specifications

To isolate specification generation, we asked Opus to produce a formal specification and a Lean implementation that can be verified against it, without also producing a repository patch. It received only the bug report and the repository; as in the earlier experiments, the reference patch was hidden.

Only 61.4% of its generated Lean specifications passed automated review. Language model reviewers carried out an adversarial specification audit, looking for missing requirements, unnecessary restrictions, and incorrect assumptions about existing code. The main problem was that the specifications left out behavior that repairing the bug required.

What a verified instance actually looks like

The find_max function was a toy example. Here’s a more substantial one, a problem called matplotlib-24177, from SWE-Bench Verified. The problem calls for the generation of a histogram, where the shapes of the histogram’s bars are defined by anchor points, or vertices. The issue reads "[Bug]: ax.hist density not auto-scaled when using histtype='step'." That is, the histogram's density axis is not adjusted to fit the whole histogram when histtype="step". The root cause is that the plot's bounds were computed from a simplified set of vertices, so parts of the histogram were cut off.

This example, adapted from the bug report, plots the same random data as a bar histogram and a step histogram, which shows the overall contour of the bars:

import matplotlib.pyplot as plt
import numpy as np

samples = np.random.randn(100_000) * 1.2
_, (bar, step) = plt.subplots(ncols=2)
bar.hist(samples, bins=100, density=True, histtype="bar")
step.hist(samples, bins=100, density=True, histtype="step")
plt.show()

Both plots should show the full histogram. In the reported bug, the step plot could be cut off because its automatically chosen axis limits were too small.

The accompanying regression test uses a fixed set of points to make the check repeatable. It checks that the plot’s axis limits include every point. BenchProofer adds a specification describing the bounding-box calculation for every input it covers.

BenchProofer's specification describes the reference fix's output, namely the tight bounding box of all the points, so every vertex lies inside the box, and each side touches at least one vertex. Even if you do not read Lean, the shape of the statement is legible. It says the result is empty exactly when the input is empty, that every vertex sits within the returned bounds, and that each bound is actually achieved by some vertex.

-- Formal specification (Lean): what the fixed function must return
def problem_spec (verts : List (Rat × Rat))
    (result : Option (Rat×Rat×Rat×Rat)) : Prop :=
  match result with
  | none => verts = []
  | some (xmin, xmax, ymin, ymax) =>
    verts ≠ [] ∧
    (∀ v ∈ verts, xmin ≤ v.1 ∧ v.1 ≤ xmax ∧
                  ymin ≤ v.2 ∧ v.2 ≤ ymax) ∧
    (∃ a ∈ verts, a.1 = xmin) ∧ (∃ b ∈ verts, b.1 = xmax) ∧
    (∃ c ∈ verts, c.2 = ymin) ∧ (∃ d ∈ verts, d.2 = ymax)

In the Lean code below, sampledVertices represents the sampling operation used by the fix. Its second argument selects the sampling mode; false means keeping every input point. As in the find_max example, BenchProofer records the property the fix relies on as an axiom. It then tests whether the axiom holds through “fuzzing”, or randomly generating a large volume of inputs that are irregular in some way, so that they’re likely to elicit unusual behaviors.

-- Axiom: an assumption about the sampling operation, tested by fuzzing
-- Sampling takes a list of points and a mode flag.
opaque sampledVertices :
    List (Rat × Rat) → Bool → List (Rat × Rat)
-- false selects keep-all mode: return every point in order.
axiom sampledVertices_keepall : ∀ verts,
    sampledVertices verts false = verts

The reference implementation loops over the vertices and widens the box whenever a vertex falls outside the current bounds.

-- Reference implementation (Lean): the fix, in the verifier's language
def implementation (verts : List (Rat × Rat)) :
    Option (Rat×Rat×Rat×Rat) := Id.run do
  match (sampledVertices verts false) with
  | [] => return none
  | p0 :: rest =>
    let mut xmin := p0.1; let mut xmax := p0.1
    let mut ymin := p0.2; let mut ymax := p0.2
    for v in rest do
      if v.1 < xmin then xmin := v.1
      if v.1 > xmax then xmax := v.1
      if v.2 < ymin then ymin := v.2
      if v.2 > ymax then ymax := v.2
    return some (xmin, xmax, ymin, ymax)

Finally, a proof shows that the implementation meets the specification on every input in its domain, and Lean’s proof checker verifies that proof mechanically. The proof relies on the stated sampledVertices axiom. Fuzzing can find violations of that axiom, but passing the fuzzing checks does not prove it universally.

-- Proof: the implementation meets the specification on every input
theorem correct : ∀ verts,
    problem_spec verts (implementation verts) := by
  intro verts
  cases hs : sampledVertices verts false with
  | nil  =>
    rw [none_branch verts hs]
    simp only [problem_spec]
    exact (sampledVertices_keepall_nil verts).mp hs
  | cons p0 rest =>
    rw [impl_some_char verts p0 rest hs]
    simp only [problem_spec]
    exact ⟨verts_ne_nil .., bounds_all ..,
           coord_attained ..)

Getting started

BenchProofer is open source. Clone the BenchProofer repository on GitHub, which links to the SWE-Proof dataset and the full paper. If you build or evaluate coding agents, run yours on SWE-Proof and tell us what you find, or bring your own benchmark, since the adapter is one short class. If you work on verification, add a backend for another verifier, contribute a new gate (the most valuable ones test whether a specification faithfully captures the chosen reference behavior), or audit an instance. Every task ships with its artifacts and verdicts, and a single counterexample reopens it. Whether you bring a benchmark or a backend, we would love your issues and pull requests.

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, 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, 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, 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, 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, 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, WA, Seattle
MULTIPLE POSITIONS AVAILABLE Employer: AMAZON.COM SERVICES LLC Offered Position: Applied Scientist III Job Location: Seattle, Washington Job Number: AMZ10037670 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, and run and analyze experiments in a production environment. Identify new opportunities for research in order to meet business goals. Research and implement novel ML and statistical approaches to add value to the business. Mentor junior engineers and scientists. Position Requirements: Master’s degree or foreign equivalent degree in Computer Science, Machine Learning, Engineering, or a related field and two years of research or work experience in the job offered, or as a Research Scientist, Research Assistant, Software Engineer, or a related occupation. Employer will accept a Bachelor’s degree or foreign equivalent degree in Computer Science, Machine Learning, Engineering, or a related field and five years of progressive post-baccalaureate research or work experience in the job offered or a related occupation as equivalent to the Master’s degree and two years of research or work experience. Must have one year of research or work experience in the following skill(s): (1) programming in Java, C++, Python, or equivalent programming language; and (2) conducting the analysis and development of various supervised and unsupervised machine learning models for moderately complex projects in business, science, or engineering. 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 $167,100/year to $226,100/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