Christophe Valentin

I joined the Architecture team to bring my historical knowledge of the stacks to more teams. As my first assignment, I elaborated a plan to extract from the monolith the call setup function that enables two participants to be connected. The proposed solution had to work alongside the legacy system and customers needed to be migrated smoothly without downtime. I joined my old team to help them kickstart the project in an AWS serverless environment. Once I had onboarded them and they were autonomous with the developments, I turned to my next project which was to be able to store a customer's assets in the region of their choice. This implied working deep into the Rails monolith, but also create a new service in an AWS serverless environment.

I took the technical leadership of the 4-engineer team. I was responsible for projects scoping, organizing the 2-week sprints and making sure the engineers could work efficiently. In coordination with the PM and EM, we regularly reviewed the processes and organization of the team to always try to improve. I was also the main point of contact for the other teams and needed to anticipate impacts of our developments on their projects.

I first joined the team responsible for handling calls, which is the core business of the company. We were tasked with developing new features leveraging the Twilio Programmable Voice API. We had to work in an ever increasing traffic, handling loads of concurrent requests.

We worked on extracting important systems from the Rails monolith into pure Ruby microservices. To that end we adopted the Domain Driven Design methodology to shape the new services while respecting bounded contexts. We made sure that the legacy and new systems could work alongside and allow for a smooth transition.

Our services had to be performant and handle an ever increasing traffic.