Introducing Physical Engineering S Last Exam Ple With Google Cloud Ai Research
- Source
- mercor.com
- Author
- Mercor research blog
- Date

Context
Physical-Engineering's Last Exam, or PLE, is a new benchmark from Mercor, a company that builds AI evaluations with a network of domain experts, and the AI and infrastructure research team at Google. It tests whether AI agents can do the design work engineers sign off on, and its headline result is that they cannot yet be fully trusted to. According to Mercor's announcement, the best configuration, Claude Opus 5.5 running in Claude Code, scored 48.3% on the hidden test set. Its designs met 91% of individual constraints on average, but only 41% cleared every hard safety and feasibility check.
That gap is what the benchmark is built to expose. An engineering design that gets most things right still fails review if one load calculation or code requirement is wrong, so PLE awards points for cost efficiency only after a design passes every hard check. The 85 tasks span mechanical, electrical, civil and structural work, such as sizing a switchboard and its cables, designing a cooling loop or checking a roof deck. Licensed engineers wrote 44 of them end to end. Google generated the other 41 with an adversarial loop in which one agent drafts a task, a second agent tries to break it and the first hardens it, and engineers validated all 85. Each task runs in a project folder of about 61 files, including drawings, 3D building models, client emails and outdated revisions planted as traps. The agent has no internet access and up to six hours, and much of the difficulty is working out which requirements actually govern the design.
Mercor and Google ran 14 frontier models across seven agent harnesses, the software that gives a model tools and runs its work loop. The model mattered far more than the . Scores across models spanned up to 50 points, while moving the same model to a different harness changed its score by a median of about 3. Claude Opus 5.5 led, followed by GPT 6 Astra at 45.8% and Gemini 4 Argon at 40.6%. The top configuration used an average of 27 million and 63 minutes per task. The benchmark extends Mercor's APEX-Agents work on office tasks such as banking and legal analysis. Google has released 29 public tasks, the grading tools and the evaluation container, while scored competition runs on the hidden set. The announcement does not give per-discipline scores or the full scoring formula. This explanation draws on the announcement alone, not on the accompanying paper or Google's companion post.
- PLE gives cost-efficiency credit only after a design clears every hard safety and feasibility check. The top agent's designs met 91% of individual constraints on average, but only 41% cleared every hard check.
- Across 14 frontier models and seven agent harnesses, model choice mattered far more than harness: scores across models spanned up to 50 points, while the same model on different harnesses moved a median of about 3 points.
- Each task runs in a containerized project folder of about 61 files, including PDFs, spreadsheets, emails, 2D CAD drawings, 3D BIM models and outdated revisions planted as traps, with no internet access and up to six hours.
- The 85 tasks span mechanical (30), electrical (27), civil (18) and structural (10) work. Licensed engineers authored 44; Google built 41 with an adversarial Creator and Solver , and engineers validated every task.
- Google released 29 public tasks, the grading tools and the evaluation container. An open competition runs on the hidden test set, and thirteen Google-sponsored models can be run for free.
- AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
- agent harness — The scaffolding around a model that turns it into a working agent — the loop, the tools it can call, and the rules for when to stop.
- token — The chunk of text a model reads and writes in — roughly three-quarters of a word — and the unit AI usage is billed in.
- agentic loop — The cycle an agent runs in: decide, call a tool, read the result, decide again — repeating until the goal is met or a stop condition fires.
Checking sign-in…
Loading comments…





