New York

October 15–17, 2025

Berlin

November 3–4, 2025

London

June 2–3, 2026

All our video highlights from webinars to live events

Highlights from our conferences

Measure for Change

Picking metrics is one thing. But the harder decisions lie in what to do with them afterward.

Drive product gaps as an engineering leader talk by Emily Thomas in LeadDev New York 2024 Conference

Drive product gaps as an engineering leader

Discover practical strategies for engineering leaders to influence product development effectively, even in the absence of strong product management and a clear company vision.

Smruti Patel

Growth in a downturn

In this talk, Smruti Patel asks, if hyper-growth is marked by spending more to make more, what does building for enduring growth look like?

Idea to Innovation

Join me as we embark on a journey to dissect the anatomy of innovation, uncover strategies to unlock the full potential of ideas, and transform them into impactful realities. Let’s build a strong culture of innovation, and make sure that it is not just a buzzword but a tangible outcome.

Slack enterprise key management: Senior to staff lessons

Explore the key lessons and skills Audrei gained during their first Staff+ project, Slack Enterprise Key Management. This talk offers insights for anyone growing in their Staff+ career.

  • Being a customer-focused engineering leader

    Most software engineers don’t realize that an outage is more than keeping the TTR low (yes, TTR is very important); it’s also about managing the expectations of your customers.

  • Vault and Security as a Service

    Over the past ten years, we’ve seen a dramatic shift in the architecture of service-oriented systems.

  • Tackling Big, Impossible Projects

    Big, Impossible projects are exciting, transformative, and begin with an overwhelming number of unanswered questions.

  • Reclaiming the Spirit of Agile

    Do you follow Agile processes like Scrum, Kanban or XP… and yet struggling to deliver on time, under budget and without last-minute heroics? Why aren’t these supposedly best practices working for you?

  • Transitioning to a lead dev

    The transition from a developer to a Lead Developer can be a rocky one. Yesterday, you were working as a developer and today, suddenly, you find yourself in the role of the Lead Developer.

  • Building Engineering Teams Under Pressure

    Why do some teams ship features rapidly, support each other, and effectively communicate while others struggle?

  • Do the Most Good

    Mina shares reflections from the campaign trail and explores strategies to use your time and skills to affect social change.

  • Eiffel’s tower

    When Gustave Eiffel built his namesake tower, it was nearly twice as tall as the tallest structure on Earth.

  • Storytelling patterns for engineering leaders

    In most forms of entertainment, it all comes down to the story.

  • Navigating engineering team friction

    Friction is a common, and necessary, part of team growth—but when left unchecked, team friction is unhealthy for you, your coworkers, your company, and ultimately your end users.

  • Is Kotlin right for you?

    Kotlin sure has been receiving a lot of buzz lately, is there something to it?

  • Crafting fun and productive Sprint retrospectives

    What do Stairway to Heaven, air balloons, and the 3 Little Pigs have in common? They’re all fun formats for sprint retrospectives!

  • Bootstrapping inclusion in engineering organisations

    Diversity and Inclusion are hot topics right now. But, year after year, our industry fails to move the numbers significantly. It seems everyone is talking about it, but how do you actually bring about change?

  • Creating code reviews that reflect your team’s culture

    Our engineering workflow revolves around our code review process. Code reviews are more than just a way to make sure we don’t introduce new bugs into the codebase.

  • Building and scaling distributed teams

    Remote work is the number one desired workplace setup for developers. As a lead dev, you’re able to hire from a global talent pool, and your team’s productivity, engagement and retention can soar as everyone works in the way that’s best for them.

  • A tour of Apache Pulsar

    Apache Pulsar is a distributed pub/sub system develop at Yahoo! This talk covers Apache Pulsar’s underlying design and protocol level semantics.

  • Creating learning workshops for developers

    Interactive workshops are the best way to engage teams and individuals and help everyone remember lessons learned.

  • Building a data infrastructure

    Your team needs data so they can make the right decisions. Unless they have the right data in the right place, they’re left to act on intuition, opinions and hunches.

  • Planning, executing, and landing refactoring

    Slack is the leading global collaboration hub that makes people’s working lives simpler, more pleasant and more productive.

  • Why GraphQL?

    If you don’t know much about GraphQL, you probably just identify it as the hip, shiny new thing companies are adopting to replace their RESTful APIs.

  • Everything You Need to Know About OpenAPI 3.0 in Ten Minutes or Less

    The OpenAPI spec (formerly known as Swagger Spec) is now in version 3.0 … but what does that mean to you?

  • How to Design Systems and Processes Teams Actually Follow

    When we work alone, it’s easy to make sure things come out the way we think is best. But what happens when we need to get an entire team to agree on — and actually use — best practices? What if we have to convince an entire company?

  • How to hold career path conversations with developers

    Our industry is not the best at preparing developers to grow their careers when they reach the critical point when they have to decide between continuing to work as an individual contributor or moving into management.

  • Strategies for reducing the fragility of your systems

    Have you ever worked on a computer system that was so fragile it was frightening to make changes to? Maybe it was challenging to deploy, difficult to delete code, or changing one piece would cause surprising cascading failures.