← All speakers

Bio, Work & Ideas

Philipp Schmid

Conference affiliation: Staff Engineer · Google DeepMind · 2026

Philipp Schmid is a Staff Engineer at Google DeepMind building the organization’s AI developer-experience and developer-relations team. He helps developers turn Gemini, Gemma, and other advanced models into usable software, with particular attention to agent reliability, practical tooling, and evaluation.

At Hugging Face, Schmid became a technical lead overseeing strategic partnerships with AWS, Google Cloud, and Azure. His work helped bring open-source models into managed cloud environments: he authored an early guide to the Hugging Face–Amazon SageMaker partnership, introduced large-language-model inference containers, and contributed to deployment infrastructure supporting AWS Inferentia2 and Hugging Face Inference Endpoints.

He joined Google DeepMind in 2025. His current work encompasses Gemini and Gemma across cloud and on-device environments, combining developer education with the engineering questions involved in building useful agents: conversation state, multimodal inputs, tool integration, inference costs, and reliable execution.

  • Context is application state. Agents operate on user intent, preferences, previous decisions, and changing instructions that cannot always be reduced to predefined flags. Schmid argues that developers should specify goals and constraints while allowing models latitude in how they achieve them. His account of why experienced engineers struggle with agents emphasizes preserving semantic context and designing tools whose descriptions expose assumptions human programmers might leave implicit.
  • Reliability requires repeated evaluation. A single successful demonstration cannot establish whether a nondeterministic agent works consistently. Schmid favors repeated trials, execution traces, outcome-based grading, and human or model-assisted assessment. His analysis of multi-turn coding evaluation extends that concern to changing requirements and earlier architectural decisions that can compromise later work.
  • Skills need evals and an expiration date. Schmid distinguishes temporary capability skills, which compensate for current model limitations, from durable preference skills encoding organization-specific practices. He recommends precise triggering instructions, negative test cases, progressive disclosure of references, and with-and-without-skill ablation tests. His Gemini Interactions API evaluation example demonstrates how trace inspection and lightweight validators can establish whether specialized guidance improves performance or should be retired.
  • Errors are inputs, not dead ends. Failed tool calls should inform an agent’s next action instead of automatically restarting lengthy workflows and discarding accumulated context. Schmid also treats interoperability pragmatically: the Model Context Protocol can reduce duplicated integration work, but models still select tools through ordinary function calling. His public analysis of multi-agent handoffs similarly concentrates on explicit coordination and stateless interaction.

Schmid maintains practical open-source examples through deep-learning-pytorch-huggingface, gemini-samples, and mcp-cli, a lightweight interface for interacting with MCP servers.

Read the topics behind these talks

4 conference talks

AI Engineer World's Fair 20251:44:51

AI Engineering with the Google Gemini 2.5 Model Family

Google DeepMind developer-relations engineer Philipp Schmid leads a hands-on Gemini 2.5 workshop covering Flash and Pro models, API authentication, the accompanying GitHub notebooks, multimodal inputs, conversational state management, and agent tooling. Demonstrations and audience questions explore local and remote MCP servers, DeepWiki repository access,…

Philipp Schmid

APIs, MCP, and protocols · RAG, context, and search · Developer workflows and testing

AI Engineer Europe 20261:47:34

Building Conversational Agents

Google DeepMind presenters Thor Schaeff and Philipp Schmid lead a hands-on workshop on building conversational agents with Gemini. They contrast generateContent with the Interactions API, demonstrate Python coding-agent tool calls and persistent conversational state, then build real-time voice experiences with the Live API, generated music, configurable…

Thor Schaeff · Philipp Schmid

Speech and audio · APIs, MCP, and protocols · Enterprise

AI Engineer Europe 202610:40

Why (Senior) Engineers Struggle to Build AI Agents

Google DeepMind’s Philipp Schmid explains why experienced software engineers can struggle with AI agents: agent development depends on natural-language context and semantic interpretation rather than strictly deterministic state. He discusses preserving execution by treating errors as inputs, evaluating outputs with traces, human experts, or LLM judges,…

Philipp Schmid

Evals · APIs, MCP, and protocols · Coding and developer tools

References