The problem
Jocata’s DIY Journeys platform was being run out of a third-party vendor’s repositories, with no dedicated in-house team of Jocata’s own to own its codebase, release process, or roadmap.
My role
Led the migration as Associate Engineering Manager, COE UI, in my first year at Jocata — moving the codebase in-house and building the team that would take it over.
Approach
Migrated the DIY Journeys platform’s repositories from the vendor’s infrastructure into Jocata’s own source control, and built a new in-house team from the ground up to own the platform going forward — recruiting, onboarding, and ramping engineers on a codebase they hadn’t built. A related migration soon after brought the team’s mobile apps in-house from another vendor the same way.
Outcome
DIY Journeys became a fully in-house Jocata platform with its own dedicated team, removing the dependency on the vendor and laying the groundwork for the mobile-apps migration that followed the same pattern.