Getting Started Universe 2026

Your guide to submitting a session proposal

Whether you’re submitting a session proposal or nominating an inspiring speaker, now’s your chance to be a part of Universe 2026.

Get to know your audience

Based on Universe 2025 statistics

  • Attendees 3,400
  • Speakers 200+
  • Sessions 115
Sort by
  • Individual Contributor Senior
    28%
  • Individual Contributor
    17%
  • Director
    11%
  • Senior Manager
    8%
  • VP+
    8%
  • Manager
    7%
  • Senior Director
    7%
Results by category
  • 28%
    Individual Contributor Senior
  • 17%
    Individual Contributor
  • 11%
    Director
  • 8%
    Senior Manager
  • 8%
    VP+
  • 7%
    Manager
  • 7%
    Senior Director

Companies in Attendance

American Airlines Mercedes-Benz Spotify Adobe Shopify Intel
American Airlines Mercedes-Benz Spotify Adobe Shopify Intel

Pro tips for a winning submission

Practice makes perfect

Write and edit a couple of drafts of your session proposal using the offline form. Please note: You must enter your session information via the online submission form to formally apply to speak at GitHub Universe.

It's about the approach

Think about your session title as the subject line of an email. Keep it short, punchy, and persuasive, and ask yourself how it would get an attendee to add it to their schedule.

Get creative with your format

The best Universe sessions surprise and delight. Think beyond slides and talking points. Have you considered a live demo, an interactive exercise, a storytelling approach, or something completely unexpected? Some of our most memorable sessions have used unconventional formats — from live action activities to collaborative problem-solving. If you have an idea that breaks the mold, tell us about it. Creativity is a feature, not a bug.

Phone a friend

Have a friend outside of your industry review the proposal before you submit. They might not understand the technical language, but a fresh perspective is always helpful.

Kick the sales pitch

Sessions are intended to be educational, not salesy. When crafting your abstract, focus on sharing actionable insights, real-world examples, and best practices that deliver value to attendees. Avoid heavy product promotion, and instead engage your audience with ideas and lessons they can apply.

Follow our formula for your bio

Do you need some inspiration for your bio? Here's a formula that might help: Your name + something descriptive about what you do (vs. just stating your title and company) + why you are credible + your role and/or any previous roles that are relevant + any extracurricular professional accolades or organizations you're part of + something personal that both humanizes you and that you'd feel comfortable sharing during an icebreaker session.

Lights, camera, action

While it's optional for speakers to submit videos of previous talks, we strongly encourage you to do so, as it enhances our ability to assess your speaking style. If you don't have a video of a previous talk, you're welcome to provide a five-minute self-recorded video presenting on a topic of your choice. See this great example from Universe 2025 speaker Thomas Bissell (Sr. Associate, Digital Manufacturing Solution Engineering at Pfizer), who recorded a video on how the seven modes of the major scale work musically and how they create different emotional qualities ranging from bright to dark.

Speaking to the right audience

Universe brings together the people building the future of software development—developers shipping code, technical leaders making tooling decisions, and execs driving business impact. Each group has different goals, from solving tough engineering challenges to scaling teams and shaping strategies. Get to know who you’ll be speaking to as you write your session proposal.

Builders

  • Engineers
  • Developers
  • Maintainers
  • Founders

They build innovative software while finding ways to save time and quickly troubleshoot challenges. They know the value of open source and collaboration and are always looking for ways to acquire new skills to meet their personal and professional goals.

Drivers

  • Eng. leads
  • DevOps leads
  • Platform leads
  • Security teams
  • Founders

They source tools to meet business needs, ensure software meets security, privacy, and data compliance requirements, and work to increase developer productivity and satisfaction.

Leaders

  • CISOs
  • CTOs
  • CIOs
  • CxOs
  • Founders

They transform and establish their organization as a market leader, hire and retain valuable talent, and ensure financial and business goals are achieved.

Find your perfect session format

Ship & Tell (15 mins)

Share the cool thing you shipped. Whether you're maintaining an open source project, building an internal tool that scales a workflow, or creating something that solves a real developer problem, this is your stage. Tell us what you built, why it matters, and what you learned along the way. Inspire other developers to build and contribute. Plan for Q&A so attendees can engage with your work.

Breakout session (40 minutes)

Whether you're a product leader announcing what's new, a customer sharing how you scaled developer tools across your business, or an industry voice discussing emerging trends, these sessions deliver insights grounded in real experience.

Product demo (15 minutes)

Share tips, tricks, and best practices that help users get more out of a specific product. Perfect for showing what's possible and inspiring people to try something new.

Workshop (90 minutes)

Interactive exercises where you guide attendees through practical learning. Participants actively apply concepts in a collaborative setting and walk away with skills they can implement immediately. The immersive format delivers the kind of depth that justifies the investment.

Sandbox session (45 minutes)

A session that combines demo and workshop. You'll demonstrate how you solved a specific challenge, then guide attendees through interactive exercises to apply what they learned.

Panel discussion (40 minutes)

A moderated conversation where a diverse group of experts discuss timely topics shaping the industry. Panels work best when they challenge conventional thinking and spark new ideas. Plan for significant Q&A and audience interaction.

Fireside chat (40 minutes)

A moderated one-on-one conversation. Think panel discussion, but with a single speaker instead of multiple experts.

Session Levels

From fundamentals to deep dives

To help attendees get the most value from your session, we ask you to indicate the depth of experience your talk assumes. Choosing the right level helps set expectations and ensures your session reaches the right audience. Rather than focusing on features or tooling, we encourage speakers to think about how deeply their session explores real decisions, tradeoffs, and outcomes.

Level 100 : Introductory

Designed for attendees who are new to a topic or approach. These sessions focus on foundational concepts and mental models, helping attendees understand why a problem exists and how teams typically approach it.

See examples Close examples
  • Developers: What slows feedback loops, and how teams fix it. Understanding where time is lost between writing, reviewing, and shipping code.
  • Engineering leaders: What changes when teams adopt AI-assisted development. How roles, expectations, and collaboration shift once AI becomes part of daily work.
  • Security professionals: Why supply chain issues keep surprising teams. Common dependency risks and how teams typically surface them.

Level 200 : Intermediate

Best suited for attendees with a working understanding of the topic. These sessions focus on how ideas show up in real workflows, including practical decisions, tradeoffs, and lessons learned from day-to-day use.

See examples Close examples
  • Developers: Designing CI/CD pipelines developers actually trust. Lessons learned from evolving pipelines to surface the right signals earlier.
  • Engineering leaders: What AI-assisted development changes, and what it doesn't. Evaluating impact on productivity, quality, and collaboration in real teams.
  • Security professionals: Moving from findings to fixes without slowing teams down. Integrating detection and remediation into everyday development work.

Level 300 : Advanced

Intended for experienced practitioners, these sessions dive into complex, real-world challenges that cover scale, failure modes, and the consequences of decisions made earlier in the lifecycle.

See examples Close examples
  • Developers: When automation breaks down: Lessons from scaling developer workflows. Failure modes, recovery strategies, and what teams would do differently.
  • Engineering leaders: Designing delivery systems that scale without fragmenting ownership. Align automation, metrics, and accountability across teams.
  • Security professionals: Governing at scale without turning security into a bottleneck. Designing security programs developers actually follow.

The anatomy of a great submission

A great session proposal stands out because it's clear, creative, and speaks directly to what developers need. In this section, we'll break down what makes a strong submission using an accepted example from Universe 2025 by Pillippa Pérez Pons, director at Niñas Pro (a nonprofit supporting girls in STEM across Latin America) and organizer of JSConf Chile. Her session title, abstract, and detailed outline show how creativity, clarity, and genuine passion come together.

Title

Git's nine lives: Taming frontend chaos with Git's hidden features

Why it works

The title is creative and memorable, using a cat metaphor to make a technical topic approachable. It's specific enough that developers immediately understand the session is about practical Git skills, yet playful enough to spark curiosity.

Abstract

Frontend development at scale can feel like herding cats — messy rebases, oversized monorepos, and disappearing commits at every turn. But Git has some hidden tricks that can help you land on your feet.

In this fast-paced, story-driven session, we'll use the metaphor of a cat's nine lives to explore Git's lesser-known features: sparse checkouts, partial clones, commit-graph optimizations, reflog, and more. Along the way, you'll pick up practical tips (and a few laughs) to help you tame Git chaos and keep your projects running smoothly.

Why it works

The abstract opens with a relatable problem that resonates with frontend developers, then immediately offers concrete solutions. It's specific about what attendees will learn while keeping a conversational tone that promises both practical value and genuine engagement.

Detailed outline

Frontend development at scale is beautiful chaos — like trying to herd cats. You start with clean branches and good intentions, but then here come the rebases, the CI pipelines that never finish, and the monorepo that just keeps growing. This session is a story — told through the metaphor of a cat with nine lives — about surviving (and thriving) in complex Git workflows.

We begin with a moment of overwhelm: too many contributors, too many folders, and a rebase gone horribly wrong. That's when the Git Cat appears — a symbol of resilience, agility, and unapologetic independence — and shows us how to land on our feet.

  • Life 1 – Rebase Like a Cat: Elegance in motion. Learn how git rebase -i and rerere can bring back control and confidence during conflict resolution.
  • Life 2 – Clean Commits, Clear Minds: Like a cat grooming its fur — tidy up your history with squashing and thoughtful commits for better code review and collaboration.
  • Life 3 – Sparse Checkouts, Focused Flow: Cats don't need the whole house to nap. Why should developers clone the whole repo? Focus only on what you need with sparse checkout.
  • Life 4 – Partial Clones, Full Speed: Not every journey needs to carry the full load. We'll explore partial clones to accelerate onboarding and local performance.
  • Life 5 – Pouncing with Performance: Tap into Git's hidden speed boosts — commit-graph, bitmap indices, and MIDX — to move with cat-like efficiency.
  • Life 6 – Reflog to the Rescue: Falling off the branch? Git reflog can bring back that precious lost commit. Like a cat, there's always a way back up.
  • Life 7 – Smarter Fetches, Less Meowing: Learn how Git's improved fetch negotiation protocol reduces noise and boosts sync speeds — no extra setup needed.
  • Life 8 – Teaching with Curiosity: Git can be confusing. That's why we'll use visual metaphors, humor, and a little cat magic to explain complex internals simply.
  • Life 9 – GitHub-Native Living: Tie it all together with GitHub-hosted repos, Codespaces, and frontend team habits that make collaboration feel smooth and natural.

We'll bring these lives to life with illustrated slides, cat metaphors, short terminal clips, and a playful audience poll: "What Git cat are you?" No live coding — just clear, focused moments of storytelling.

We'll wrap with a gentle nudge: Git doesn't have to be a source of fear. It can be a graceful, powerful part of your workflow — if you learn its rhythm. You'll leave with a cheat sheet, a smile, and maybe a little more curiosity about what Git can do for you.

Why it works

Rather than listing Git features, Pillippa structures the session around a metaphor that makes complex concepts memorable. The outline shows creativity through illustrated slides, cat metaphors, and audience interaction while ensuring attendees leave with techniques they can use right away.

Explore the 2026 content tracks

GitHub Universe sessions are grounded in real experience with a focus on what teams built, learned, and changed as work moved from idea to code to review and release. Each track below includes themes and starter questions to help you shape a proposal that’s a strong fit for what we’re programming this year. We’re especially interested in talks that surface tradeoffs, lessons learned, and concrete changes teams made (along with what worked, what didn’t, and why).

Build faster, stay in flow

For:

  • Engineers
  • Developers
  • Maintainers
  • Founders

This track focuses on how developers move work forward across the full software lifecycle from writing and reviewing code to testing, automating, and shipping it. Sessions should show how individuals and teams use modern AI and agentic workflows to speed up reviews, make CI more actionable, reduce rework, and keep code clear, reviewable, and ready to ship. Key themes:

Shortening feedback loops across the SDLC

  • What specific changes helped your team shorten feedback loops or stay in flow?
  • Where did speed gains come from simplifying workflows or removing steps, rather than adding more tooling?
  • What tradeoffs did you make to move faster without hurting readability or maintainability?

CI/CD that developers trust

  • How have you evolved CI/CD to surface the right signals earlier?
  • What made checks, tests, or automation feel actionable instead of noisy?
  • If you rebuilt your pipeline today, what would you remove, simplify, or design differently?

AI in the loop, with guardrails

  • How are you using AI to assist development without breaking review, ownership, or accountability?
  • What made AI-generated changes easier or harder to understand and trust?
  • What surprised you once AI became part of daily development work, especially as changes moved from code generation and review, to merge?

Onboarding, learning, and developer growth

  • How have you improved onboarding or skill development without slowing teams down?
  • What practices helped new contributors become productive faster?
  • How do you balance speed with mentorship and knowledge sharing?

Secure every commit

For:

  • Eng. leads
  • DevOps leads
  • Platform leads
  • Security teams
  • Founders

This track is for sessions that explore how teams build high-quality software, secure by default. From developer-first workflows and automated remediation to identity, guardrails, and supply chain integrity, share real-world strategies for securing the entire lifecycle without slowing developers down. Key themes:

Security for AI-powered development and AI systems

  • How does AI change the way teams think about security, code quality, and trust across the development lifecycle?
  • How are teams embedding guardrails, validation, and remediation directly into AI-assisted workflows, coding agents, and pull requests? What lessons have emerged as AI-generated code moves from experimentation into real production systems?

Identity, access, and trust at scale

  • How are modern teams redefining least-privilege access as automation, ephemeral credentials, and distributed workflows grow?
  • What practices help organizations replace static credentials with scalable, auditable identity models across CI/CD and developer platforms?
  • Where do identity strategies break down at scale — and how have teams adapted to keep developers moving while maintaining control?

Designing guardrails, not gates

  • Why do traditional detect-and-alert approaches struggle as development velocity increases?
  • How are teams using secure defaults, automated remediation, and verification to reduce noise while improving both security and code quality?
  • What trade-offs emerge when guardrails fail — and how do teams design workflows that stay resilient without slowing developers down?

Supply chain integrity from source to production

  • How are teams managing open source risk, provenance, and integrity across increasingly complex software ecosystems?
  • What practical approaches help organizations secure builds, manage dependency risk, and enforce policy without disrupting developer workflows?
  • What real-world challenges appear when operating supply chain security continuously across large codebases — and what has actually worked?

Automate and scale with confidence

For:

  • Eng. leads
  • Platform leads
  • CISOs
  • CTOs
  • CIOs
  • CxOs
  • Founders

This track is for anyone responsible for scaling software delivery across teams and systems. Sessions should focus on automation, AI-assisted delivery, and the practices that help organizations move faster at scale without risking security, context, or reliability. Key themes:

Automation that earns trust

  • What automation meaningfully reduced toil for developers?
  • Where did automation introduce new risks or failure modes?
  • How did you decide what to automate, and what to keep manual?

Scaling CI/CD and delivery systems

  • How have you scaled pipelines across teams, environments, or products?
  • What lessons did you learn the hard way while growing delivery systems?
  • How do you keep systems understandable, observable, and operable as they grow?

Measuring what matters

  • Which metrics actually reflect developer productivity and code health?
  • Which metrics looked useful but didn't improve outcomes, and why?
  • How do teams use data to guide improvements rather than enforce control?

AI adoption at organizational scale

  • What changed once AI became part of your ways of working?
  • How do you enable your teams to get the most out of AI?
  • What guardrails helped maintain consistency, quality, and trust?
Submit your session proposal

We hope the guidance above helps you craft a winning session proposal for GitHub Universe 2026. And don’t forget—the deadline is Friday, May 1, at 11:59 pm PT.

Got questions?

We're here to help! Reach out at speakersupport@github.com.