Aidan Legaspi

Engineering manager for product and platform teams. Nearly nine years at Eventbrite took me from frontend engineer to staff engineer to managing teams in the US and Spain.

Career

Five chapters, from writing the shared code to leading the people who build it.

  1. Software Engineer I & II, Frontend Platform2017–2020

    Building shared foundations

    I worked on the layer other teams built on: the first-generation design system, developer tooling, and the organization permissions UI. For the 2018 IPO rebrand, I led engineering, partnering with design on the new type and color system while keeping other engineers current as it changed.

    The rebrand shipped across the web and earned a Quarterly Engineering Award.

  2. Senior Software Engineer / Tech Lead, Multi-Event Management, Design Ops2020–2022

    Leading a team to ship

    As tech lead for six engineers, I led the React frontend for Creator Collections, delivered in about three months, and refined a calendar workflow for managing up to 900 recurring events.

    As Scrum Master, I helped the team ship smaller increments and made bug fixes part of sprint planning, improving cycle time and bringing the bug backlog down to a sustainable level.

    Read the full story: Leading a team to ship
  3. Staff Engineer, Design Ops2022–2023

    Making systems people adopt

    I co-created Marmalade, Eventbrite’s new design system, and worked to make it something teams chose. We piloted it with Checkout, Marketing Tools, and Help Center, paired with design on composable pieces like Card Anatomy, and I owned the move to federated contribution so teams could extend it themselves.

    Contributors grew 5x, and Marmalade won Best Documentation and Jury’s Choice at the 2023 Design System Awards.

    Later managed Design Systems (2025–2026) alongside Creator Growth, and hired Eventbrite’s first Design Engineer.

    Read the full story: Card Anatomy
    One set of primitives, two card compositionsFour abstract primitives (media, heading, text and action) are reused to build a vertical card and a horizontal card.PrimitivesCompositionAnother composition

    Concept diagram, not a product artifact.

  4. Engineering Manager, Frontend Enablement2023–2024

    Giving teams a paved path

    I built Frontend Enablement in a quarter to deliver a paved path off the Django monolith. Rather than spend the team on one flagship migration, I pushed for capabilities every team could reuse, and treated adoption as a product: demos each sprint, an internal blog, office hours, and early adopters as a feedback loop.

    Standing up a backend-for-frontend went from six weeks to two days, and the paved path became the standard for new web projects.

    Read the full story: Giving teams a paved path
    From the monolith to team-owned apps on a paved pathBefore: three product teams all ship through one shared monolith. After: each team owns its own app, and all three apps sit on a shared paved path for CI/CD, infrastructure, and monitoring.BeforePaved pathTeamTeamTeamMonolithTeamTeamTeamAppAppAppShared paved pathCI/CD, infrastructure, monitoring

    Concept diagram, not a product artifact.

  5. Engineering Manager, Creator Growth & Monetization2024–2026

    Leading through change

    An August 2024 reorg merged Monetization’s services and frontends into my new team with only two transferring engineers. I started with transition 1:1s, clarified ownership, and reset priorities to capacity, then gave engineers more ownership of planning and stakeholder communication, with coaching along the way. We went on to co-own engineering for the Free Tier relaunch.

    I kept all eight engineers for 20 months after the reorg and promoted two to Senior.

    Also managed Design Systems from January 2025.

    Read the full story: Leading through change

About

I like building leverage, and I care about what it does for the people using it. I’m at my best helping engineers grow into larger scopes while staying close enough to the work to help shape it.

More about me