← All speakers

Bio, Work & Ideas

Maxime Labonne

Conference affiliation: Liquid AI · 2026

Maxime Labonne is Head of Post-Training at Liquid AI and creator of the LLM Course, an open-source guide to developing and deploying language models. He builds small foundation models designed for the constraints of actual devices while making advanced training techniques accessible to other engineers.

From cybersecurity to foundation models

Labonne earned a doctorate in machine learning at the Institut Polytechnique de Paris, researching anomaly-based network intrusion detection with the French Alternative Energies and Atomic Energy Commission. He subsequently held machine-learning research positions at Airbus and JPMorgan Chase before joining Liquid AI.

His earlier work included graph neural networks and the book Hands-On Graph Neural Networks Using Python. He later created the LLM Course, combining learning roadmaps with practical notebooks, and co-wrote LLM Engineer’s Handbook with Paul Iusztin. His other open-source projects include llm-datasets, a curated collection of post-training datasets and tools, and LLM AutoEval, which automates model evaluation in Google Colab.

  • Evaluate before fine-tuning. Labonne recommends defining quality, cost, and latency metrics, then testing prompting before committing to customization. Effective post-training depends on accurate, diverse, challenging examples; deduplication, reward models, and model-based judging improve dataset quality. His preference-optimization tutorial demonstrates how these decisions translate into practice.
  • Model merging as open-source experimentation. His MergeKit work combines existing models through interpolation, parameter pruning, and layer recombination without repeating full training. His Beyonder experiment assembled specialized chat, code, role-playing, and mathematics models into a mixture of experts, initializing its router with representative prompts. He cautions that benchmark contamination can inflate apparent leaderboard gains.
  • Small models require hardware-aware design. Working on Liquid Foundation Models, Labonne emphasizes that oversized embedding layers can consume parameters needed for reasoning. LFM2 combines gated short convolutions with grouped-query attention, with architectural choices tested on target CPUs and smartphones. His account of small-model development prioritizes specific capabilities such as extraction and tool use over uniform competence across every benchmark.
  • Train against failure, then extend with tools. Small reasoning models can enter a doom loop, repeating text without producing an answer. Labonne addresses the problem with preference data that rejects looping responses, reinforcement learning with verifiable rewards, and repetition penalties. For on-device language models, he favors web search and Python tools to compensate for limited internal knowledge and long-context weaknesses. A browser-based vision-language demonstration reflects his interest in capable models that operate close to their users.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Memory limits, latency, and narrow tasks change how small models should be built—from embedding budgets and device profiling to preference training that suppresses repetitive loops.

  • What fits on a phone or in a car?
    0:15 ↗
  • Where the parameter budget goes
    2:28 ↗
  • Choose operators on the target hardware
    3:59 ↗
  • A 350M model trained on 28 trillion tokens
    6:07 ↗
  • Adapt the stages to limited capacity
    8:31 ↗
  • Make repetitive failures into rejected answers
    10:41 ↗
  • Reward completion, penalize repetition
    12:46 ↗
  • Move knowledge and context into tools
    15:28 ↗
  • When to deploy locally—and what distillation may miss
    17:59 ↗

Key ideas

Scroll to read ↓

A base model can continue a question without answering it. Fine-tuning changes that behavior; model merging offers another way to reuse capabilities already learned by other models.

  • From completing questions to answering them
    1:00 ↗
  • Establish whether prompting is enough
    1:54 ↗
  • Choose a training interface
    3:22 ↗
  • Separate context, answers and preferences
    4:06 ↗
  • Build data that teaches the intended behavior
    5:47 ↗
  • Decide which weights to train
    8:19 ↗
  • Find a stable learning rate and a workable memory budget
    9:30 ↗
  • Reuse training already embodied in model weights
    10:26 ↗
  • Interpolate two models or combine sparse updates
    12:01 ↗
  • Repeat layers without another training run
    13:17 ↗
  • Assemble experts and initialize a router from prompts
    14:26 ↗
  • Evaluate the assembly against its sources
    16:11 ↗

References