Philippe L.

First developer and now backend lead for the startup. I established the foundation of the project's architecture for managing companies' non-financial data, enabling executives to link non-financial and financial aspects to better manage their company KPIs.

Technically, the backend was broken down into several asynchronous microservices (~15) in Java 21 / Springboot (Kafka) and monitored via the Datadog solution. All within an AWS cloud on a Kubernetes / Karpenter infrastructure (Traefik, Helm, ALB, etc.). Infrastructure as Code with Terraform.

I am committed to clean code principles and hexagonal architecture to place business logic at the heart of developers' concerns and ensure a real separation of responsibilities between different technical and application components.

8 months after joining Prismea as a Backend Developer, I had the honor of being offered a Lead Backend Developer position. My role thus evolved, adding to the backend developer tasks:

- Management of a small team of 3 to 5 people (internal organization in feature teams)

- Discussion with POs and UI designers on functional needs and technical feasibility

- Study and creation of functional and technical tasks to be performed

- Estimation of features

- Guarantee of clean code principles adherence

- Ownership of the team's backlog and task assignments

- Facilitation of meetings on complex technical tasks

- Support for developers and pair programming when necessary

- Recruitment of new developers

As a Java developer, I participated in discussions and grooming around new features as well as their development. Organization in feature teams, code reviews, adherence to clean code principles, CI/CD with dozens of production deployments per day. Technical exchanges with external partners (API providers). A project rich in technologies where tests are not optional, a constant search for improvement, and a competent team composed entirely of seniors. Increased rigor in respecting API contracts.

Technologies:

- Continuous Integration / Continuous Deployment (CI/CD)

- Microservices

- Apache Kafka

- Java 17+, SpringBoot 2+

- Hibernate, Liquibase, PostgreSQL, DynamoDB

- Test Driven Development (TDD), BDD, End To End (E2E)

- Slack, Gitlab, SonarQube, Miro

- Monitoring (APM + logs + profiling + watcher)

- Adherence to SOLID principles

- Hexagonal Architecture

- Domain Driven Design (DDD)

- Scrum Ceremonial (daily, weekly, retrospective, issue board)

- AWS