← All speakers

Bio, Work & Ideas

Cormac Brick

Conference affiliation: Google · 2026

On this page

Cormac Brick is a principal engineer at Google AI Edge developing the software and hardware techniques that bring capable AI to phones, laptops, embedded computers, and robots. His work focuses on making models small, fast, private, and reliable enough to operate locally on affordable devices.

From specialized processors to on-device AI

At Movidius, Brick worked on low-power machine intelligence and demonstrated the Movidius Fathom Neural Compute Stick at NeurIPS 2016: a USB accelerator that ran neural-network inference directly on a Raspberry Pi. After Intel acquired Movidius, he served as a director of machine intelligence in its Movidius group and later led architecture work on laptop neural processing units.

At Google, he became a technical lead for the on-device stack encompassing MediaPipe, LiteRT, and the open-source LiteRT-LM inference framework. In 2024, he coauthored Google’s introduction of the AI Edge Torch Generative API, which helps developers deploy PyTorch-built language models through Google’s mobile runtime. He also contributed to technical reports for Gemma 3, Gemma 4, and EmbeddingGemma, collaborating with Gemma developers to make their models run effectively across many devices.

How he makes small models useful

  • Choose the right deployment model. Brick distinguishes operating-system models such as Gemini Nano, shared through Android’s AI Core, from models packaged inside individual applications. Shared models avoid duplicating large downloads; application-specific models offer greater customization and broader hardware reach, at the cost of additional engineering.
  • Train tiny models for specific jobs. His team applies synthetic-data fine-tuning to FunctionGemma, a 270-million-parameter model, for mobile function calling. Targeted training improved an example workflow from roughly 46 percent accuracy to the mid-80s overall, with most individual functions exceeding 90 percent. The result depends on narrowly defined tasks and rigorous evaluation, not generalized intelligence.
  • Keep agent context lean and actions predictable. For on-device agent skills, Brick favors loading detailed instructions only after a model selects a relevant capability. This progressive disclosure reduces context and computation; constrained decoding further improves reliability by limiting tool calls to permitted operations. The open-source Google AI Edge Gallery demonstrates this architecture across mobile applications.
  • Design around real hardware constraints. Available memory, quantization, latency, and component cost determine whether a model can reach older phones, Raspberry Pi boards, or inexpensive robots. LiteRT supports portable deployment across CPUs and GPUs, while neural processing units require specialized, vendor-specific compilation.
  • Combine focused models into complete products. Brick’s team built AI Edge Eloquent, an offline dictation application that combines separate Gemma-derived models for speech recognition and text polishing. The system removes verbal fillers, adapts to specialized vocabulary and unfamiliar names, and illustrates how compact, inspectable model pipelines can deliver practical on-device products.

Read the topics behind these talks

3 conference talks

Key ideas

Scroll to read ↓

An on-device agent can load skills into a system model or run a specialized model inside the app. Cormac Brick walks through both paths, from JavaScript interfaces to synthetic-data fine-tuning.

  • What if the device’s built-in AI does not do your task?
    0:15 ↗
  • Where local inference runs
    1:37 ↗
  • Use system intelligence or ship your own
    2:58 ↗
  • A restaurant picker in Google AI Edge Gallery
    5:06 ↗
  • Load skill details only when needed
    7:43 ↗
  • Create, test, and distribute a skill
    8:59 ↗
  • Package and deploy a tiny model
    10:18 ↗
  • Teach a small model the app’s functions
    13:13 ↗
  • Chain specialized models for offline transcription
    15:52 ↗
  • Selecting a skill is easier than coordinating several
    17:41 ↗
  • What changes from MediaPipe, and where to find benchmarks
    18:59 ↗

Key ideas

Scroll to read ↓

From live translation to JavaScript skills and offline dictation, building useful edge AI depends on matching model size, customization, and runtime to the device.

  • What should run on the device?
    0:16 ↗
  • Shared system models and specialized app models
    7:05 ↗
  • Effective size is about resident memory
    11:29 ↗
  • Package once, measure on the target device
    16:14 ↗
  • A journal that can act, retrieve, and render
    18:32 ↗
  • Load the instructions only when they are needed
    23:42 ↗
  • From a virtual piano to restaurant roulette
    29:18 ↗
  • Generate a skill, then test it on a phone
    35:03 ↗
  • From Transformers to an edge artifact
    41:57 ↗
  • Measure the model, then choose the specialization
    46:09 ↗
  • Offline dictation with a separate polishing model
    55:36 ↗
  • Train the behavior, supply the vocabulary
    1:02:39 ↗
  • What fine-tuning changes—and what was available
    1:04:30 ↗
  • Safety boundaries and multi-skill requests
    1:09:38 ↗
  • Keep the context bounded and the base model shared
    1:15:51 ↗

Key ideas

Scroll to read ↓

Local intelligence depends on more than fitting weights in memory: the task, runtime, hardware and training data determine whether a small device can respond usefully.

  • Intelligence beyond expensive robots
    0:17 ↗
  • Local inference trades cloud costs for a memory budget
    2:28 ↗
  • Small models are often ready to prompt
    4:42 ↗
  • Compressed weights are only part of the footprint
    6:06 ↗
  • The same model produces different interaction budgets
    7:27 ↗
  • Test the interaction, not just whether the model runs
    9:28 ↗
  • Tiny models narrow the task to widen device reach
    12:39 ↗
  • From a spoken request to a device function
    14:24 ↗
  • Spend the training effort on one task
    16:17 ↗
  • Offline dictation combines two specialized models
    17:47 ↗
  • Make specialization easier, and perception faster
    19:33 ↗

References