The engineering-conference landscape has consolidated in 2026. A handful of long-running events remain the durable choices; a small number of newer events deserve attention; and a large category of pay-to-speak conferences should be skipped. This is a curated list of conferences where the speaker selection is real, the attendance is substantive, and the conversations between sessions are as valuable as the sessions themselves.
LeadDev
The most consistently relevant engineering-leadership conference. Runs major events in London and New York, with smaller satellite events elsewhere. Talks are short (typically 20–25 minutes), practical, and unusually honest about what does not work.
Most useful in years when you are looking for fresh patterns. The hallway conversations and the "leadership-track" content are typically stronger than the technical-keynote content. LeadDev attracts a high concentration of director-and-above attendees relative to most engineering events.
SREcon
Not engineering-leadership-specific, but essential reading for managers in operations-heavy orgs. The cultural patterns at high-functioning SRE teams transfer to engineering management more directly than most realize, and SREcon's talks are unusually rigorous about what is actually being measured.
Most useful when your team owns operational systems or when you are building an SRE function. The "people, processes, and culture" track in particular is worth attending in person.
QCon
The InfoQ-organized conference series. Long-running, with strong technical content and an increasingly meaningful engineering-culture track. The track curation is what makes QCon work — attendees can deliberately construct a path through the conference rather than chase keynote names.
Most useful when your engineering org is at the stage of needing technical-leadership development for senior ICs as much as for managers.
Strange Loop (historical, but the archives matter)
Strange Loop concluded in 2023, but the archive of talks remains one of the strongest single sources of engineering thought-leadership content. Several of the most-cited engineering-management talks of the last decade originated at Strange Loop.
Most useful as a video library. Search the archive by topic when you encounter a problem; you will often find a 30-minute talk that is more useful than any current blog post.
Reading About the Problem Is Step One
Every resource on this list points at the same gap: distributed teams lose state between shifts. StandIn is the governance layer that closes it — handoffs, decisions, and authority captured from the tools your team already uses.
See the Workflow →Conferences worth attending for specific reasons
KubeCon and CloudNativeCon
Operationally focused but the engineering-organization content has grown each year. Most useful when you are evaluating platform-engineering investments or when your org is in a major platform-migration phase.
RSA (security)
Not engineering-leadership-focused, but the security-leadership content overlaps with engineering-leadership content more than the industry talks about. Most useful when your engineering org is building or refining security practices.
The CTO Summit (and similar invite-only events)
Several invite-only CTO-level events exist. The signal-to-noise depends entirely on the curation. Treat them transactionally — if the attendee list is published in advance and includes people you respect, attend; otherwise skip.
The Pragmatic Engineer events
A newer format built around the newsletter audience. Smaller, more focused, more peer-conversation-driven than the large conferences. Most useful when you want substantive hallway conversations with engineers from named companies.
Regional engineering-leadership conferences
Several regions have built durable engineering-leadership events — London's tech-leadership scene, Berlin's CTO summits, San Francisco's various invite-only gatherings, Singapore's regional events. The regional events often have higher signal-to-noise than the global conferences because the attendee base has overlapping context.
Most useful for building local networks. The cumulative effect of attending the same regional event annually for several years compounds in a way the one-off global-conference attendance does not.
Online and hybrid events
The pandemic-era online-conference experiment mostly failed for engineering-leadership content. The hallway track is too important. The exceptions are well-curated single-track online events with strong moderation — these can produce surprisingly substantive sessions when the content is right.
Most useful when the alternative is not attending at all. Treat online attendance as a fallback rather than a default.
Conferences to skip
Pay-to-speak conferences where the speaker selection is driven by sponsorship rather than substance. Vendor-organized conferences framed as community events. Conferences without published attendee composition. The signal-to-noise problem is solved at the gate; pick conferences whose gate-keepers you trust.
How to get the most out of attending
Pick three sessions you genuinely want to attend, and treat everything else as either a hallway opportunity or a rest break. The conference value-per-hour is usually highest in the hallway and dining conversations, not in the sessions. Schedule for serendipity, not for completeness.
Attend annually rather than rotating through different conferences. The compounding network effect of being known at a single event over several years is larger than the breadth of attending a different event each year.
Frequently asked questions
Which engineering-leadership conference is the most useful single choice?
LeadDev, in most cases. The combination of practical content, leadership-specific tracks, and high concentration of director-and-above attendees makes it the durable default.
Are smaller invite-only events worth pursuing?
Only if the attendee list is published in advance and includes people you respect. The signal-to-noise of invite-only events is entirely a function of curation.
How does StandIn relate to conference attendance?
Conferences surface the patterns; StandIn is where the patterns become practice. The structured handoff and decision-record discipline that recurs in the leadership-track talks is the operational layer StandIn provides.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.