Overview
Cycleo runs bike-sharing fleets across three cities. Growth had outpaced its original monolith: deploys were scary, outages clustered at rush hour, and every new feature took longer than the last.
As product and technology lead, I set the technical direction, split the critical paths into independent services, and coached the in-house team to own the new architecture.
Challenge
A system that fails at peak demand, a team afraid to deploy, and a roadmap that couldn't wait for a full rewrite — the transformation had to happen while the bikes kept moving.
Approach
Strangler-fig migration: new services peeled off one boundary at a time behind the live system, each with its own deploys, dashboards, and rollback. No big-bang rewrite, no downtime windows.
- Client
- Cycleo Mobility
- Role
- Product & Tech Leadership
- Focus
- System Architecture
- Year
- 2025
- Engagement
- 6 months, embedded lead
- Outcome
- Independent deploys, calm rush hours
Deliverables
- Service boundaries, migration sequence, and architecture decision records
- Fleet-tracking and payments services extracted with zero downtime
- CI/CD, staging environments, and on-call rotation for the team
- Engineering mentorship: reviews, pairing, and hiring rubrics
Related work
System creaking under growth?
Get senior technical leadership that ships the fix and levels up your team at the same time.
Book a Consultation