Reme Juan Le Hane

I joined Loop shortly after the product was brought in-house to provide structure and momentum to the engineering team. At that time, it was a small group of junior and mid-level engineers. When I requested my job description at the end of my first week, my lead simply replied, “We were hoping you’d tell us.”

So, I began by learning the products, understanding the people, and identifying where things were slowing down My initial focus was on reducing friction—both for engineers and for the overall delivery process. I introduced TypeScript to the frontend (which was already in use on the backend), implemented documentation standards, initiated a proper code review process, and collaborated with the team to integrate unit testing into our workflow as an essential part of our definition of done.

One of our my successes was unifying the mobile apps. We had two, one for Logistics and one for On-Demand, split across separate codebases that were nearly identical. Fixes and features had to be duplicated manually, often introducing bugs and delays. To address this, I merged the codebases, introduced build flavors to accommodate different configurations, and set up CI pipelines to automate builds and distributions for internal testing using App Tester and TestFlight.

Over time, I began shifting away from day-to-day coding and more toward team and culture development. I introduced structured 1:1s, helped formalize how we give and receive feedback, and now oversee the company’s 360° review process.

Additionally, I maintain close collaboration with Product, Marketing, Sales, and Support teams to ensure alignment and minimize communication gaps across departments.

I’ve taken ownership of cost management efforts, starting with a 15% reduction in our GCP expenses. I’ve also setup reporting to track costs and assess the impact of feature development more intentionally.

From an architectural standpoint, we rebuilt our frontend and backend systems, previously scattered across multiple repos, into a unified NX monorepo using Next.js and NestJS. This eliminated duplication, improved reusability, and allowed us to share logic and utilities across services, most of which now sit at or near 100% test coverage.

Our testing stack includes Cypress for user journey tests and Postman for API testing, with scheduled and post-deployment runs fully automated.

The mobile apps now support over-the-air updates for emergency hotfixes, and test coverage has increased from 0% to ~70%. Our release cadence is now predictable and consistent on a monthly basis.

Ultimately, I co-lead engineering for a platform that supports ~5 million deliveries per month. I mentor six engineers directly and help shape technical direction, product strategy, and cross-functional execution. It’s a role that blends deep technical involvement with team growth and cultural leadership and that’s exactly the kind of impact I enjoy.

Technologies used:

• Node
• ReactJS
• Flutter
• Next.js
• Google Cloud Platform (GCP)
• Firebase

Technologies used:

• Flutter
• BLoC
• GoLang
• AWS

I was brought into Wyzetalk for my React experience as the company had some older projects that needed to be updated. The plan was to replace the existing AngularJS management tool as well as the Ionic 1 mobile application with React and React-Native versions respectively.

While everything went as planned for the configuration tool which I rebuilt using React with Redux and Typescript, React Native as well as Native Script and Ionic 4 proved not suitable for the businesses needs.

Initially I built the replacement configuration tool using React with Redux, Typescript and Webpack, the team has since grown with an additional 2 developers.

React-Native proved to not be suitable for the mobile application and after prototyping with NativeScript, Ionic 4 and Flutter, I landed on Flutter as the most suitable tool for the job. Myself and my 3 team members built the mobile application using both TDD and DDD on top of the BLoC architecture for state management.

During my time I also improved upon a number of the internal processes, including developer onboarding and deployments.

We had no formal onboarding process and most of it was done by sitting with someone to talk you through it and slack you the various configuration files that were needed for the roughly 6 codebases you needed to work on the projects, and it was usually about 2 weeks before you were fully up and running.

I replaced with a Dockerized development environment as we had developers working on Windows Mac and LInux and different node versions were required for different projects. I also setup a CLI script to clone all the repos and generate the required configurations. We now onboard developers in about 45 minutes.

Some of what was done for onboarding also made it possible for us to replace the manual deployment process to a dedicated server to an automated one using Azure Cloud and build pipelines.

For the original app, deployments were also manual and time consuming taking upwards of a few hours to complete, for the new application I also setup a series of CI scripts which were used for configuration of the various client versions as well as app store deployments with Fastlane which usually completes in under 20 minutes.

Technologies used:

• Flutter
• BLoC
• ReactJS
• Redux
• Typescript
• NodeJS
• Webpack
• Docker
• NestJS
• Express

I was initially brought on to scaffold and spear head the Web Application side of a new project the company was going to be developing, and to help with the architectural decisions to ensure proper alignment between the back and front ends.

Within a few months, we had grown into a 7 man team of UX, UI and Functional developers on the Web Application side, of which I am the Team/Technical Lead. Much of my focus is spent is working on the core application components and working with the team on their feature developments, helping with the understanding of the very complex system we are building and attending regular meeting with the back end team so that we can ensure everything stays aligned and deal with any shared challenges being faced.

The project itself is a React based Progressive Web Application aimed at the insurance industry with an initial focus on the day to day management from the perspective of brokers and brokerages.

Technologies used:

• ReactJS
• Redux
• NodeJS
• Webpack
• Docker

Working in a fast paced and dynamic Fintech environment focused on developing stable and secure Hybrid Mobile and Web Applications using some of the latest and greatest available technologies such as AngularJS, Node.js and ReactJS.

Responsibilities:

• General Agile/Scrum tasks
• Maintenance of existing internal and external products and applications.
• Project research and staying up-to-date with modern web standards, trends and technologies.

Technologies used:

• ReactJS
• Redux
• AngularJS
• NodeJS
• Webpack
• Docker

Working in a fast paced, dynamic environment and being responsible for assessing and estimating work required as well as developing and investigating new features, client’s requests and cost-to-serve enhancements to the existing infrastructure..

Responsibilities:

• Day-to-day management of the V4 Front-end team.
• Responsible for maintenance and updates to clients access portals.
• Development of new client portal and portal features.
• Project research and staying up-to-date with modern web standards, trends and technologies.

Achievements:

• Promoted to V4 discipline lead after 4 months, making me responsible for both SA and India Front-end teams.
• Assisted in developing and enhancing existing client infrastructure with an estimated cost saving of over £200, 000 per annum.
• Key developer involved in new Finance Billing section with an estimated saving of 60 hours per month for the Product Support team.

Technologies used:

• jQuery
• Backbone
• Bootstrap 3
• NodeJS