Robert Lehmann
Staff SRE, Google
Zürich, Switzerland
Actions
Robert has spent the past decade with Google SRE, building the tools that a majority of Google's incident response uses for production monitoring. In a previous life, he was a Python aficionado and otherwise enjoys teaching.
Links
Area of Expertise
Topics
Why You (too) Need an (API) Style Guide
You’ve probably been in this situation: You thought long and hard about this new API of yours, but now it comes to naming — shock, horror, what will you do? Or, worse, you’re a reviewer and you’re not sure if the proposed API quite aligns with the status quo. That’s where API Style Guides come in and can eliminate (some of the) bikeshedding.
In this talk, we will explore:
- What is an API Style Guide, and why could you possibly need one?
- What are the characteristics of a good style guide, and what constitutes a bad one?
- Some exemplary style guides for your to be inspired by (e.g. AIP, AEP)
- Where else can style guides help (it’s 2026, do I need to spell it out: AI)
Robert will draw on his decade+ at Google where he was one of 3% of the company allowed to perform API reviews. His team maintained multiple style guides in order to scale reviews.
The Migration Cookbook
Enterprise migrations are hard: The new platform is usually not quite ready yet, nobody fully knows what the old tool did, management wants everything to be done by yesterday, and your users don’t want their favorite toys taken away.
That’s why there is an entire scientific field devoted to “change management.” In this talk, we will explore how its lessons apply to the real world:
- Why are migrations so painful, and what are some common patterns?
- What are some of the proven techniques to avoid (or at least: limit) tears during migrations?
- Which technical approaches can power our wonderful migration plans?
- What are some of the policies and governance models to streamline these processes?
- How to not lose the fun while doing all of this?
Robert draws on a decade of shepherding tens of thousands of internal users from a fragmented tool landscape, through multiple sunsets and deprecations, to a unified monitoring platform at Google SRE.
OpenTeleme-what: Disentangling the maze of modern observability
OpenTelemetry has “decisively won the instrumentation wars,” titled ClickHouse in 2025. Yet, 3 out of 4 developers never even use as much as a debugger (FlouState 2025), let alone sophisticated observability for debugging.
In this talk, we will hopefully bring those numbers up. We will explore:
- Why OpenTelemetry, and how does it compare to other solutions (e.g. Prometheus, Fluent)
- What is OpenTelemetry, and what’s the difference between API, SDK, OTLP, BBQ, OpAmp, and OTEP (one of which is a made up acronym)
- How to deploy all of this, and how does it fit into the bigger picture of DevOps?
Robert will feed off his decade+ of experience at Google SRE, most recently as Uber Technical Lead for its Planet-Scale Dashboards and working closely with OpenTelemetry.
Planet-Scale Dashboards
Google runs hundreds of thousands of services globally, often interdependent and with shared concerns. At that scale, classical Federated Observability — a platform team providing foundations and/or building blocks for each team to assemble on their own — does not scale anymore.
In this talk, we will demonstrate how Google managed to cut toil dramatically while providing best-in-class monitoring out-of-the-box:
- What are the unique circumstances that contributed to Google’s scaling problem?
- A data model for re-usable dashboards
- Impact on both configuration overhead and incident response
- Looking beyond dashboards, how such re-use can be facilitated in the broader observability space
Robert will draw on Google’s research paper on Planet-Scale Dashboards (to be published mid 2025) and more than a decade of experience in SRE.
BaselOne 2026 Sessionize Event
WeAreDevelopers World Congress 2026 - Europe Sessionize Event
WeAreDevelopers World Congress 2025 Sessionize Event
DevOpsDays Zurich 2025 Sessionize Event
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top