▶ Watch ↗AI Engineer World's Fair 202620:42
Conference affiliation: Adobe · 2026
Carlos Sanchez is a principal scientist at Adobe Experience Manager, the creator of the Jenkins Kubernetes plugin, and a member of the Apache Software Foundation. His work spans build automation, cloud infrastructure, and agentic applications: provisioning environments for software builds, investigating failed deployments, and assembling websites around a visitor’s intent.
Sanchez’s open-source work includes Apache Maven, Jenkins, and Kubernetes. In 2006, he co-authored Better Builds with Maven with John Casey, Vincent Massol, Brett Porter, and Jason van Zyl. His announcement of the freely released book identified its authors as Maven core developers. In his March 7, 2012 writing about DevOps, he described Maven’s goal of automating and standardizing build steps and the practical consequence: builds no longer had to depend on the person who knew every manual step, freeing engineers to work on continuous integration, quality checks, and useful metrics.
The Jenkins Kubernetes plugin applies that approach to build infrastructure. It provisions Jenkins agents in Kubernetes pods, with pipeline-defined templates specifying the containers and tools a build needs. Teams can allocate build environments on demand rather than maintain all their capacity as a fixed collection of machines.
CloudBees identified Sanchez as a principal software engineer in December 2018, working on scalable, cloud-native Jenkins deployments and explaining Jenkins X’s approach to continuous delivery for Kubernetes. By Adobe’s 2021 developer event, he was a senior cloud software engineer there. His subsequent resource-optimization work at Adobe Experience Manager includes autoscaling, workload hibernation, and automated resource management to use Kubernetes capacity more efficiently.
His work on Audience of One brings automation to website personalization. In his 2026 demonstration, Sanchez showed how browsing history, time spent on pages, and search queries can inform a page assembled for an individual visitor. Marketers define personas or intent groups in natural language; the system uses those groups and the visitor’s signals to choose content, recommendations, and the order of page blocks.
The team builds a retrieval corpus from the website’s own content and uses it to ground generation. Selected elements—such as hero text, product recommendations, blog feeds, navigation, and calls to action—can change while the site retains its design structure and brand constraints. This reduces the need for marketers to author thousands of variations while keeping generation tied to material the site already contains.
A coffee-shopping demonstration makes the mechanism concrete. A visitor searching for a coffee machine to use while camping receives a page combining suitable products with camping advice. A second demonstration uses AI Engineer’s site content to generate a side-by-side conference comparison for someone deciding between events. Both examples organize existing information around a decision the visitor is trying to make.
For Sanchez, accuracy and latency belong in the same evaluation. His team uses Promptfoo to compare prompts across models and providers, repeating evaluations because site size, subject matter, and commerce requirements affect which model works well. He targets page generation within roughly one or two seconds and argues that a model needs enough capability for the task without imposing an unacceptable wait. Recommendations can also be generated while someone browses and prefetched before they open the page. That relaxes the immediate latency requirement, but keeping recommendations current as intent changes adds inference cost.
His Kubernetes sandbox comparison takes the same care with infrastructure claims. Using Playwright and Chromium, he tested tenant routing, WebSocket connections, startup, and browser state. He distinguished preallocated warm pods from environments created on demand and examined claims about checkpoint restoration. Where a fast result reflected cached startup resources, he did not treat it as proof that browser memory had been restored. The comparison asks whether a sandbox supports the application’s actual lifecycle, including the state it must preserve, rather than judging it by startup speed alone.
▶ Watch ↗AI Engineer World's Fair 202620:42
Loading more talks and highlights…