Mo Moosa

• Assumed full ownership of the iOS app post-restructure, overseeing development, weekly releases, and ongoing product maintenance.

• Collaborated directly with product, design, and backend teams to scope, develop, and deliver features end-to-end.

• Led the migration from hard-to-test Storyboards to a modular, dependency-injectable code base with 30% SwiftUI code that is easier to maintain and write automated tests for.

• Implemented several A/B tested features to quickly learn and improve the product in the most efficient way possible.

• Addressed serious quality issues by increasing test coverage from 0% to 25% via a combination of UI, unit, and snapshot tests, leading to reduced bugs in production.

• Participated in product workshop sessions to better understand our users and contribute to the needs of the business.

• Successfully migrated StoreKit 1 to StoreKit 2 without regressions, improving maintainability and UX.

• Led the effort to identify and plan the team's ideal technical roadmap, guided by regular proof of concept demos.

• Frequently monitored the app in Instruments to track down performance issues.

• Carefully planned the Objective-C to Swift migration and introduced SwiftUI to the project, improving maintainability and performance. Led the initiative of moving mobile developers to feature teams, which allowed the core mobile team to focus on platform improvements while improving collaboration.

• Helped translate Net Promoter Score feedback from our enterprise customers into meaningful ways to improve the product.

• Mentored an intern and worked with her to develop the mobile design system, which had not been attempted before and is now a valuable counterpart to the web design system.

• Introduced iterative prototyping to work around issues such as missing designs/specs.

• Stepped out of my comfort zone by introducing the Scrum agile approach to the team and managing the project.

• Promoted code reuse through encapsulation and modules and minimised third party framework dependencies that were slowing the development team down.

• Improved the poor designer-developer collaboration by organising regular play tests with the design team.