New York

October 15–17, 2025

Berlin

November 3–4, 2025

London

June 16–17, 2025

Meetups

Videos

All our video highlights from webinars to live events

Latest videos

Highlights from our conferences

Measure for Change

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

View all videos from LeadDev London

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.

view all videos from LeadDev NEW YORK

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?

view all videos from LeadDev berlin

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.

view all videos from staffplus london

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.

view all videos from staffplus NEW YORK

All videos

  • Bridging the gap between engineering and customer success teams

    Investing in your customer success team is high leverage. The more knowledgeable your team is, the more effective it can be at investigating, diagnosing and triaging customer issues.

  • Using an ‘architectural North Star’ to align your engineering team with your organization

    In a fast-growing, agile organization, teams are usually encouraged to self-organize. Equipped with the guiding principles such as fast iteration and frequent feedback loop with the customers, we entrust the most valuable asset, people, to make informed decisions.

  • Transitioning from technical leadership to parenthood, and back again

    Navigating any new personal scenario while leading a team can be extremely challenging, but last summer I found myself nine months pregnant and leading our engineering organization through an acquisition while preparing for the birth of my son. On the day he was born, I got the news that the acquisition had been finalized.

  • Extended leave: how to manage the anxieties of returning to work

    As more companies offer longer parental leaves and other leaves of absence, managers and their teams are learning how to handle them successfully.

  • Driving architecture alignment across a fully-distributed engineering workforce

    InVision started as a small startup several years ago with tens of engineers, small teams working independently as velocity was paramount. But as InVision grew to hundreds of engineers, all fully remote, we realized that this independence was actually slowing us down – teams resolving the same problems, inconsistent metrics, etc.

  • How to hire remote junior developers

    You wouldn’t hire a senior developer without giving them any support or possibilities for growth, would you? Of course not!

  • Crafting effective 1:1s for distributed engineering teams

    Creating relationships with the individual humans on your distributed team is difficult since you rarely get to see them in person! But a team is much less likely to be effective and successful without a foundation of interpersonal relationships and trust.

  • Splitting the monolith

    After years—even decades—on the existing legacy mainframe, we pitched a plan to migrate a company to a new, microservices-based architecture. Convincing management seemed easy, but now we have to deliver: Take the years-old legacy system and break it apart into smaller services and systems we can actually maintain.

  • Solutions for creating and managing inclusive projects

    Corporate Culture is an ecosystem and diversity is the air we breathe. As such, how a project/delivery team cultivates its culture impacts the entire project, client relations and end-user experience.

  • Clear, concise and consistent: how to communicate and prioritize risks from the engineering team to the wider organization

    Communicating risks, particularly to our non-technical colleagues, is a challenge and by not doing it well we suffer pushback from the business. The risks are varied and at all different levels, but can include technical debt, skill gaps, team burnout, and more.

  • Lessons from flying for engineering leadership

    In October of 2008, I’d been unemployed for about four months. I was doing some consulting work, but still feeling entirely uncertain about my ability to make a living, so I did the obvious thing: I decided it was a good time to learn how to fly a plane.

  • Introduction to functional programming

    Expressions are the most basic form of human interaction! Programming languages are trending more towards using expressions rather than procedural statements, adopting the declarative paradigm.

  • Observability that matters (and avoiding the kind that doesn’t)

    The term observability has recently earned somewhat of a cult status — rapidly ascending to the ranks of “agile”, “digital transformation”, “microservices” and other such highly regarded (and perhaps often misused) labels. Suddenly every team wants to incorporate the pillars of observability into their ecosystem.

  • Unlocking success: the components of high-performing teams

    Do you have a great team & a great mission but don’t understand why the pace of delivery is so slow? Architecture & tech stack is only one part of the story.

  • The benefits of delivering imperfect software

    We all want to deploy the best software possible to delight our customers and please our product owners. There’s always one more feature, another performance improvement, and code we just wish we wrote better.

  • The race to Mach 2.0 at scale

    When Chuck Yeager became the first pilot to fly faster than the speed of sound, he set off a race around the world to do the same with a plane full of paying passengers. The United States, Russia, the UK, and France all wanted a piece of the inevitable fortune to be made building aircraft to cross oceans faster than sound itself.

  • Effective meeting facilitation techniques

    We’ve all had that experience where we’ve planned the perfect discussion only to have it hijacked by a passionate side-person, lose focus halfway through, or produce the exact same takeaways as you had before you began the discussion.

  • Navigating friction in your engineering team

    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.

  • The possibility of AI-powered Javascript apps

    There are many exciting things happening with AI, from which, until recently, JavaScript developers were largely shut out. But things are changing, if you can do `npm install @tensorflow/tfjs` or make an API call, you can now do AI.

  • Engaging your engineering team to achieve high performance faster

    When bootstrapping new teams, they need to go through the standard process of forming, storming, norming and performing. And in the context of fast-growing companies, with their own level of uncertainty, how can we achieve high performance when teams and goals are constantly changing?

  • Taking a fresh look at setting objectives and key results for your engineering team

    In 2013, Google famously published a leading reference for establishing Objectives and Key Results as a way to align teams and set short-term goals.

  • Identifying and articulating the role of AI in your software design process

    We’ve all read the articles and got excited by technologies such as machine learning, deep learning, Tensorflow, Panda and NumPy. A lot of us are also looking at how to incorporate these technologies into our toolset and in the software we are building.

  • Guiding your engineering team to self-organisation

    It’s all well and good for the agile manifesto to recommend self-organising teams, but what does that actually mean in practice? What’s the best way to do it, how far should you take it? Total anarchy is probably not the answer here… right?

  • How to create organizational change through compassionate leadership

    How many talks, articles, and podcasts have you seen about organizational change, and how to implement it? How many of them talked about what we can learn from non-human psychology? This is that talk.