Bird · 2018 – 2025
My story at Bird
Eight years helping Bird grow from a Santa Monica WeWork startup into a global mobility platform — Habitat, developer platforms, micro-frontends, and systems across the stack.
Role: Senior Staff Software Engineer
- Platform engineering
- Distributed systems
- Global operations
Origin
The story
Andrew Arrow was one of the first people to show me the Bird app before it launched. He kept pinging me to take a serious look at the company, which eventually led to a scooter ride with Justin Balthrop in Santa Monica and the start of my Bird chapter.
I joined Bird in early 2018 when the company was still operating out of a small WeWork office in Santa Monica, just after the first scooters appeared on the streets. Over the next eight years I had the opportunity to help grow the company from a small startup into a global mobility platform operating in hundreds of cities.
During Bird’s period of hypergrowth, I played an active role in scaling the engineering organization by interviewing, hiring, onboarding, and mentoring engineers across multiple teams. As the company’s needs evolved, I moved fluidly between individual contributor and engineering management roles, choosing the position where I could have the greatest impact rather than following a traditional management track.
Throughout my time at Bird, I contributed across nearly every layer of the technology stack. I worked on both Product and Systems Engineering, backend services powering the mobile applications, integrations with external partners, internal operational platforms used by support and business teams, developer tooling, security infrastructure, and engineering productivity initiatives. I was often brought into projects that crossed organizational boundaries because of my broad understanding of the platform and ability to connect technical decisions with business needs.
One of the contributions I’m most proud of was leading the design and implementation of Habitat, Bird’s proprietary geospatial configuration platform. I conceived the system shortly after joining the company and led its architecture and development from an idea into one of the foundational platforms that powers Bird’s business today. Habitat became the central control plane for every market in which Bird operates, both domestic and international, allowing business teams to configure market behavior without engineering deployments.
Beyond traditional configuration management, Habitat evolved into Bird’s experimentation platform. It enabled teams to safely launch new markets, roll out products, perform A/B experiments, configure pricing, define riding and parking zones, enforce speed limits, and customize mobile application behavior on a market-by-market basis. The platform significantly accelerated product development by allowing operational and product teams to iterate independently while maintaining a single, consistent system of record.
Collaboration
People I built this with
The people behind this chapter—and the part each of them played in shaping the work.
CTO & Co-Founder, Triangle Health · Former CTO, Bird and Geni
Justin recruited me to Bird and served as CTO during its fastest years of growth. We worked together as the company expanded from a small Santa Monica startup into a global mobility platform.
Founder, Spartan · Early Bird engineer
Chan and I joined Bird on the same day. He helped lay the company's original technical foundation using then-emerging tools such as Kotlin and Dropwizard, and his instincts for performance and scale influenced many of the systems we built as Bird grew.
Software Engineer at Bird · Full-stack product engineer
Vlad and I formed Bird's original core backend team. We worked together across charger tools, an early multilayer map-management system for scooters, chargers, nests, and field operations, the RBAC authorization system that remains foundational to Bird's administration tools, agreement management, and many other operational platforms. Our pattern was consistent: take a sprawling problem, break it into manageable pieces, and build the system Bird needed to operate.
Full-stack Engineer at Triangle Health · Former iOS engineer, Bird and Snap
Jason fundamentally restructured and rebuilt Bird's iOS application, transforming it from a mostly prototype experience into a fast, responsive mobile platform. He also led the Bluetooth integration and app-to-scooter communication that connected the rider experience directly to Bird's vehicles.
Staff Software Engineer at Airbnb · Former VP of Engineering, Bird
Datadog was Michael's daily instrument, and his dashboards were masterpieces. For nearly every question, he could pull up an existing dashboard or build a new one in seconds. His attention to p99 performance, reliability, and anything the team could instrument and improve helped keep Bird's systems grounded in evidence as he led the engineering organization.
Principal Engineer, Andrew Arrow Dev · Early Geni, Yammer, and Bird engineer
Andrew was one of the first people to show me the Bird app before it launched. He kept pinging me to take a closer look at the company, which eventually led to my scooter ride with Justin Balthrop in Santa Monica and the start of my Bird chapter. We later worked together there as Bird grew.
Senior Director, Product at Bird
Björn and I partnered across years of Bird product work, including integrations that brought Forest and Lyft into Bird's broader mobility ecosystem. When he joined, he kept reminding me how impressed he was by Habitat. By then I thought of Habitat as simply the operating system we ran on, so his perspective was a valuable reminder to step back and recognize what the team had built.
Director, Product at Bird · Engineer turned product leader
Prat joined Bird as an engineer after I interviewed and vouched for him in 2018. He worked on my team building internal administration systems and later GovTech products during the early Culver City years, then successfully transitioned into product management as the company evolved.
Co-Founder & CEO, Triangle Health · Former Senior Director of Product, Bird
Jonathan led or contributed to more Bird initiatives than a short list can capture. His scope included government compliance products and strategy, rider and operator experiences, international expansion, payments and fintech, and retail and consumer products. We partnered across a number of those efforts as Bird's platform expanded rapidly.
Context
The problem and my role
Problem
Hypergrowth required platforms that let hundreds of markets launch and iterate without waiting on engineering deployments — while the org, stack, and product surface kept expanding.
Role
Moved fluidly between IC and engineering management, hiring and mentoring across teams, and contributing across product, systems, backend, partner integrations, ops platforms, security, and developer productivity.
Constraints
- Global expansion across 300+ cities with local policy and product differences
- Business teams needing to configure markets without engineering releases
- Monolith-era systems under hypergrowth pressure
- Cross-org work that required connecting technical decisions to business needs
System
Architecture
System map
Habitat as the global market control plane
Business and product teams configure market behavior once, then a shared platform distributes those decisions to services and applications across Bird’s markets.
- 01
Market and product teams
Define launches, pricing, zones, speed limits, experiments, and app behavior
- 02
Habitat control plane
Maintains a consistent, geospatial system of record
- 03
Configuration and experiments
Versions regional policy and controlled product rollouts
- 04
Product services and apps
Consume shared market configuration without bespoke deployments
- 05
Global markets
Apply localized behavior across 300+ cities
Execution
What I built
- Architected Bird’s global geospatial configuration platform (Habitat) powering operations across 300+ cities, enabling business teams to launch new markets, configure regional policies, manage pricing, and safely roll out product features without engineering deployments.
- Worked with Jason Fieldman as he transformed Bird’s early iOS prototype into a fast, durable mobile platform with Bluetooth vehicle integration, app-to-scooter communication, and Habitat-controlled product behavior.
- Built the company’s internal developer platform providing unified visibility into microservices, deployments, dependency graphs, APIs, libraries, and database schemas, improving developer productivity and operational efficiency.
- Established Bird’s React micro-frontend architecture, enabling independent teams to build and deploy applications autonomously while sharing common infrastructure, authentication, and design systems.
- Led the modernization of Bird’s backend architecture by decomposing a large monolithic application into independently deployable Kubernetes-based microservices running on AWS.
- Designed centralized authorization infrastructure integrating Okta, JWT, RBAC, and custom Dropwizard extensions, allowing security teams to manage fine-grained permissions across internal platforms.
- Developed operational platforms used daily to manage fleets, vehicles, partners, riders, markets, and payment operations across Bird’s global business.
- Partnered with product leadership to build third-party mobility integrations with Forest and Lyft, enabling riders to access Forest bikes through Bird and Bird vehicles through Lyft.
- Built a global legal content management platform enabling attorneys to author, version, translate, and publish localized user agreements across hundreds of international markets without engineering support.
Tradeoffs
Technical decisions
A control plane instead of market-specific releases
- Decision
- Model regional product and policy differences as versioned geospatial configuration in Habitat.
- Why
- Business teams needed to launch and adapt markets without waiting for an engineering deployment for every local change.
- Tradeoff
- A flexible control plane becomes critical infrastructure and requires strong validation, auditability, and a carefully governed schema.
Team autonomy through shared foundations
- Decision
- Adopt React micro-frontends with common authentication, infrastructure, and design systems.
- Why
- Independent teams could ship their own operational surfaces while users still experienced one coherent platform.
- Tradeoff
- Deployment autonomy shifts complexity into contracts, dependency management, and shared platform standards.
Decompose around operational boundaries
- Decision
- Move monolithic backend responsibilities toward independently deployable Kubernetes services on AWS.
- Why
- Hypergrowth increased the need for independent scaling, ownership, and release cycles across a widening product surface.
- Tradeoff
- Distributed systems improve autonomy but introduce network, observability, and operational complexity.
Value
Product impact
User impact
Gave operational and product teams direct, governed control over launches, policy, pricing, experiments, and localized app behavior.
Business impact
Reduced dependence on engineering releases for market changes while creating shared developer, authorization, and service foundations for a growing organization.
Results
Outcomes
- Habitat became a foundational control plane and experimentation platform for Bird’s global markets.
- Developer platform and micro-frontend foundations improved autonomy and visibility across engineering teams.
- Monolith-to-microservices migration and centralized auth raised the ceiling for scale and security.
Notes
Notes from the system
Habitat deserves its own story
Habitat is the centerpiece of my Bird work — a geospatial operating system for policy, pricing, geofences, experiments, and market launches. The dedicated Habitat case study covers its seven architectural phases in depth.
Reflection
Lessons learned
- “The highest-leverage platform work gives other teams safe autonomy rather than centralizing every decision with engineers.”
- “Architecture must evolve with the organization: shared contracts, visibility, and ownership become as important as service boundaries.”
Tools
Stack
Next case study
Translation Exchange — language as structured meaning →