Mobility & Navigation Systems Engineer
I build mobility platforms, booking systems, routing engines, geospatial products,
and map-driven software for African cities.
|
Crowdsourced transit data for Nairobi's matatu network, a community-maintained successor to the 2014 Digital Matatus GTFS dataset.
|
Bus mobility platform for reservations and recurring travel. Includes Mova Pass, a subscription service for students and professionals who rely on daily bus rides.
|
|
Multi-tenant platform for operators to manage routes, fleets, and network data.
|
Internal operations platform used by Mova to manage its mobility products, business operations, and the wider Mova app ecosystem.
|
Most of my work sits at the intersection of mobility platforms, geospatial data, routing, and interfaces people use to plan and book journeys.
- Mobility & routing, OpenTripPlanner, GTFS pipelines, PostGIS, trip planning
- Platform architecture, multi-tenant Laravel backends, clean boundaries, versioned APIs
- Booking & mobility products, reservation systems, subscription platforms, operational tooling
- Map-driven UX, Mapbox GL, offline-tolerant mobile clients, low-bandwidth-first design
- Shipping, Docker, CI/CD, and the unglamorous production work that keeps things up
How I think about building
- Constraints first. African mobility runs on informal networks, patchy data, and constrained devices. The architecture follows from that, not from a Bay Area reference stack.
- Data before features. A routing product is only as good as its underlying mobility data. Most of the hard work is upstream of the UI.
- Boring infrastructure, interesting products. I'd rather spend novelty budget on the user-facing experience than on the deploy pipeline.
Backend
Frontend
Mobility & Geo
Infrastructure
I'm interested in mobility platforms, transit data, routing problems, and the software that makes everyday journeys easier to plan and book. If you're working on something in that space, or you want to build on Navigo's data, reach out.
