← All speakers

Bio, Work & Ideas

Merve Noyan

Conference affiliation: Hugging Face · 2026

Merve Noyan is a machine-learning engineer on Hugging Face’s ML advocacy engineering team, a coauthor of SmolVLM, and a coauthor of the O’Reilly book Vision Language Models. She develops open multimodal models and practical tooling that make image understanding, customization, and local deployment accessible with limited computing resources.

Earlier in her career, Noyan built natural-language-understanding systems for information retrieval and conversational agents. At Hugging Face, she expanded into computer vision, multimodal learning, and open-source developer infrastructure. Her work includes a 2024 guide to vision-language models and direct preference optimization for vision-language models in TRL, which trains multimodal systems using preferred and rejected responses without a separate reward model.

Noyan coauthored the SmolVLM release and research paper, examining how visual encoders, image tokenization, and training data affect the performance and memory demands of compact vision-language models. The family includes 500-million- and 256-million-parameter variants; the smallest requires less than one gigabyte of GPU memory for inference. Her smol-vision repository provides recipes for shrinking, optimizing, and customizing visual models, while her SigLIP projects explore image-text representations and their integration with Transformers.

  • Open weights do not guarantee open models. Noyan rejects the assumption that publishing weights on Hugging Face automatically makes a model fully open. Licensing, accessible implementation, and control over fine-tuning and deployment determine whether developers can adapt systems commercially, inspect their behavior, and protect sensitive data.
  • Small multimodal models demand deliberate design. SmolVLM treats architecture, visual tokenization, training data, memory, and throughput as connected engineering decisions. Quantization expands access to larger models, but quality and latency remain genuine tradeoffs; purpose-built smaller models can bring visual understanding to consumer devices.
  • Visual document retrieval preserves crucial context. Noyan advocates retrieving document pages as images with systems such as ColPali, then passing relevant pages to a vision-language model. This approach retains layouts, charts, tables, and images that brittle OCR-heavy pipelines can discard.
  • Agent-driven training should absorb operational complexity. Through agent skills and Model Context Protocol, coding assistants can discover models and datasets, estimate hardware requirements, launch fine-tuning jobs, and return trained models to Hugging Face Hub. Noyan has also developed computer-vision skills for object detection and segmentation, reducing setup problems such as incompatible bounding-box formats.

Her work on multimodal architectures and visual agents extends that trajectory toward systems that can understand documents, interpret screenshots, and operate closer to users’ devices and data.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Making a model fit is only the beginning: selective precision, architecture-aware evaluation and runtime compression determine whether local intelligence remains useful.

  • How much intelligence fits on your computer?
    0:21 ↗
  • From open reasoning to local agents
    4:41 ↗
  • Precision belongs where errors matter
    11:36 ↗
  • Benchmark the allocation, then examine the format
    14:46 ↗
  • A benchmark score does not describe the whole deployment
    17:51 ↗
  • A large quantized model or a small native model?
    21:41 ↗
  • Local demand changes what gets built
    24:21 ↗
  • Creating the checkpoint is the easy part
    28:54 ↗
  • New architectures invalidate old shortcuts
    32:30 ↗
  • The next compression targets are runtime state and computation
    37:27 ↗
  • How do you find a trustworthy modified model?
    43:22 ↗

Key ideas

Scroll to read ↓

Open models, agent traces, skills and managed compute turn a coding assistant into a tool for selecting models, launching training and processing research papers.

  • What would it take to put an AI engineer at your fingertips?
    0:00 ↗
  • Find a capable model, then choose how to serve it
    2:02 ↗
  • Narrow the choice with benchmarks and provider options
    4:21 ↗
  • Connect the Hub to a coding agent
    5:48 ↗
  • Hermes: setup, memory and a repaired Slack integration
    7:38 ↗
  • Turn saved sessions into inspectable training material
    9:17 ↗
  • Match a local model to the application and hardware
    10:15 ↗
  • From a training request to a model on the Hub
    12:03 ↗
  • Use MCP to discover resources and call AI applications
    15:00 ↗
  • Put the pieces together: OCR for research papers
    16:22 ↗

References