OpenAI Says AI Cut a Chipmaker’s Test-Writing Time by ~48%

OpenAI says its engineers and models cut the time a large chipmaker spent writing verification tests by about 48%. In a 22 October 2026 post on its forward deployed engineering (FDE) team, OpenAI listed “~48% time saved through AI-based directed test generation” for an unnamed semiconductor customer, and set it against an industry where, it wrote, “Verification can account for ~70% of a project’s effort.”

The post says around 15 FDEs worked with the customer on more than 10 use cases from mid-2025, and that all of them reached production within three to six months. OpenAI does not name the company. As we read it, the post shows where AI was pointed first in chip design: at checking the work, the step OpenAI says takes most of the effort.

Business Pill · VERIFICATION COST

A one-minute explainer of verification cost: what it takes to check something, however cheap it was to make. It teaches the general idea only and says nothing about any company in this piece.

The key insight: As we read it, the new element is where the time went: OpenAI says AI cut about 48% of the time spent on directed test generation, a step inside verification, which it says can account for ~70% of a chip project’s effort.

What OpenAI Built for the Chipmaker

OpenAI wrote that the ambition was to “make their verification process AI-native”. The post names three areas of work.

  • Directed test generation. Writing the targeted tests that check whether a chip design behaves as intended.
  • Root cause analysis and debugging. Diagnosing why a design failed a test.
  • An architecture assistant. Help for the engineers who plan the design.

The team did not start as chip experts. “Some FDEs had joined OpenAI just days earlier and had never worked in semiconductors,” the post says. They embedded with the customer’s verification team and “built evals with the engineers to test whether the AI could generate useful tests and correctly diagnose chip failures.” OpenAI adds that “we built custom harnesses for the individual use cases.”

OpenAI says AI-based directed test generation saved about 48% of the time for one unnamed large semiconductor
OpenAI says AI-based directed test generation saved about 48% of the time for one unnamed large semiconductor customer. The index (before = 100, with AI about 52) is our illustration of that figure; OpenAI also says verification can account for about 70% of a chip project’s effort.

The Numbers OpenAI Gives

ItemFigureWhat OpenAI wrote
TeamAround 15 FDEs“In mid-2025, we had around 15 FDEs working with a large semiconductor customer on 10+ use cases.”
Use cases10+Directed test generation, root cause analysis and debugging, and an architecture assistant
Time to production3 to 6 months“Over the first 3-6 months, all of them reached production and early user adoption.”
Test generation~48% time saved“~48% time saved through AI-based directed test generation”
Kernels22% median gain“22% median performance improvement through kernel optimisation”
DebuggingWeeks to hours“Weeks of debugging compressed into hours”
Industry context~70% of effort“Verification can account for ~70% of a project’s effort in this industry.”

All figures are from OpenAI’s 22 October 2026 post and describe one unnamed customer. The grouping into rows is ours.

When the results were played back, the post says, the customer’s Chief Hardware Officer asked: “Did you guys work as chip designers before coming here?”

The Arithmetic

  • About 1.9 times the tests in the same time. If writing a set of tests takes about 48% less time, the same set takes about 52% of the old time, which is roughly 1.9 times as many tests per hour, by our arithmetic. That assumes the work itself stayed the same; OpenAI does not say.
  • Not 48% of the whole project. OpenAI gives the ~70% figure for verification as a whole and the ~48% for one step inside it, test generation. The post does not say what share of verification that step takes, so the two numbers cannot be multiplied into a project-wide saving.

From Custom Code to a Common Harness

The first versions were built one use case at a time. Later, OpenAI wrote, the team moved them onto a common harness with Codex at its core: “Custom applications became plugins and skills built on common Codex primitives.” It adds: “We were able to remove roughly 90% of the custom code from each project.”

OpenAI’s lesson for its own hiring is that domain knowledge is learned on the job: the FDEs need not know the industry on day one, but “it is their responsibility to learn it.”

Connecting the Coverage

The Structural Read

As we read it, the gains sit in checking work rather than designing it: two of the three areas OpenAI names, test generation and debugging, are about finding faults in a design.

As we read it, the post treats domain knowledge as something the engineers acquire on the job. OpenAI says some of its FDEs had never worked in semiconductors when the engagement began.

As we read it, the second step mattered as much as the first. OpenAI says moving the use cases onto a common Codex harness removed roughly 90% of the custom code from each project.

The customer’s Chief Hardware Officer, as quoted in OpenAI’s post, 22 October 2026

“Did you guys work as chip designers before coming here?”

Three Implications

FOR CHIP-DESIGN TEAMS OpenAI says the work covered directed test generation, root cause analysis and debugging, and an architecture assistant, and that all the use cases reached production within three to six months.

FOR AI VENDORS OpenAI says its FDEs built evals with the customer’s engineers to test whether the AI could generate useful tests and correctly diagnose chip failures.

FOR BUYERS MEASURING RETURNS OpenAI gives time-saved and performance figures but no cost or headcount figures, so the post does not state the financial return on the engagement.

The Business Engineer Lens

This story maps onto the Business Engineer framework AI & The Harness Theory.

The framework says the next professional jump “is an operating system that wraps your AI โ€” a harness that compresses your thinking, your team’s feedback, and the model’s raw capability into something replicable.” It adds: “Without it, AI works for you. With it, AI works for your team.”

As we read it, OpenAI’s account follows that path: custom harnesses for each use case first, then one common harness that, OpenAI says, removed roughly 90% of the custom code. The framework was published in April 2026 and does not discuss OpenAI or this customer.

What Is Not Established

The figures are OpenAI’s own account of one engagement, and OpenAI does not name the semiconductor customer or the chips involved. The ~48% describes time saved on directed test generation, not on verification as a whole or on the chip project. The ~70% is OpenAI’s statement about the industry, without a source in the post. The post gives no cost, headcount saving or revenue figure for the work. The 1.9 times is our arithmetic.

Business Engineer Framework

AI & The Harness Theory

A Business Engineer framework on the operating system that wraps an AI model and makes its results replicable.

Read the Map of AI →

More from OpenAI’s FDE post

The Bottom Line

OpenAI’s 22 October 2026 post says around 15 of its forward deployed engineers worked with an unnamed large semiconductor customer on more than 10 use cases, all in production within three to six months. It lists about 48% time saved on AI-based directed test generation, a 22% median kernel performance gain and weeks of debugging compressed into hours, in an industry where it says verification can be about 70% of a project’s effort.

95,000+ executives read Business Engineer for the AI strategy frameworks cited by ChatGPT, Claude, and Perplexity.

A note on sourcing. This piece is based on OpenAI’s 22 October 2026 post on its forward deployed engineering team, read in full, and our own earlier pieces. OpenAI does not name the semiconductor customer and we have not identified it. The 1.9 times and the chart index are our arithmetic and illustration. Nothing here is investment advice.

Sources: OpenAI: What FDE means at OpenAI (22 Oct 2026)

Scroll to Top

Discover more from FourWeekMBA

Subscribe now to keep reading and get access to the full archive.

Continue reading

FourWeekMBA