Fleetbase
Senior engineering work on logistics, React Native migration, and TypeScript SDK development.
- Role
- Senior Software Engineer
- Year
- 2023–2024
- Status
- shipped
- Stack
- React Native · TypeScript · Node.js +2
Problem
Logistics platforms age. Native iOS/Android codebases block velocity, and untyped SDKs make integration painful for downstream teams.
Solution
Led the React Native migration, rebuilt the JavaScript SDK in TypeScript, supported architecture decisions, mentored engineers, and shipped across the modular supply-chain system.
Highlights
- React Native migration of mobile clients
- JavaScript SDK → TypeScript with full type surface
- Architecture support across modular services
- Team leadership and developer mentoring
- Cross-functional work with product and design
Stack
01
React Native migration
The mobile clients were native iOS and Android, both aging out of velocity. The decision was a full React Native migration — not a hybrid shell, not a webview wrapper, but a proper shared codebase.
The hardest part was not the rewrite. It was the rewrite alongside a logistics platform that could not pause for three months. Migration had to ship in slices, with feature parity preserved at every step.
02
JavaScript SDK → TypeScript
The public JS SDK was used by downstream integrators. It was also untyped, which meant every integration partner wrote their own informal type definitions, and the support load reflected that.
The rebuild to TypeScript was a real cost, but it cut support time dramatically and made the SDK a product surface instead of a liability. Downstream integrators got proper types, and the codebase got the kind of refactor confidence that strict typing enables.
03
Architecture & mentoring
Beyond the two headline projects: I supported architecture decisions across the modular supply-chain system, ran technical reviews, and mentored engineers. The senior engineering work is less visible than the launches, but it is what compounds.
What I brought
- Pragmatic modular monolith patterns over premature microservices.
- Strong opinions on testing strategy that the team could actually run.
- Cross-functional clarity with product and design.
Links