Kerdoud Tahar

FARITAS

Lead Java / Spring Backend Developer

Joined the FARITAS project team (declaration and control of tourist taxes collected by rental platforms — Airbnb, Booking, Gîtes de France, Abritel...), initially as a backend developer, then as lead since Sept. 2024 and functional referent since Sept. 2025.

Responsibilities:

• Java/Spring Boot backend design and development (REST API, data modeling)

Lead developer: deliverable quality, code reviews, team technical coordination

• Functional support after the departure of the PO: requirements gathering, arbitration, business liaison

• Skill development for two developers, including one transitioning to Java

• Migration from Java 11 to 17

• Redesign of file processing to handle increased load from large platforms

• DevOps collaboration: Grafana dashboards, formalizing dev roles in release and deployment processes (dev, testing)

• Implementation of unit and integration tests

• Technical and functional documentation writing

Achievements:

• Complete redesign of processing (full in-memory loading → batches of 10,000 lines): throughput x20 — a 400,000-line file previously took 10 hours, the application now handles 5 million lines (Booking, Gîtes de France) in 6 hours

• Improved reliability of analysis file restitution: generation at the end of processing, one-month retention storage, automated purging (Java cron), and on-demand regeneration endpoint — end of server crashes during mass retrieval

• Reduced database load through caching for repetitive calls (tax period calculation)

• Ensured technical and functional continuity despite the departure of the lead dev and PO

JAVA 11/17, SPRING BOOT, VUE.JS (PINIA), REST, GIT, MAVEN, POSTGRESQL, JERSEY, JENKINS, SONAR, JUNIT

Office and Calendar

Java Backend Engineer

Joined the Calendar team (5 developers), responsible for time management tools for bank advisors and their clients (Agenda, Office Agenda, Client Agenda), marketed to several banks — with a major delivery expected on January 1st.

Responsibilities:

• Evolutionary and corrective maintenance of legacy applications (ticket processing, bug fixes)

• In-depth refactoring of legacy code: writing/recovering unit tests beforehand, non-regression tests, then secure code redesign

• Systematic reduction of class and method size for readability and code control

• Multi-client versioning: one Git branch per bank in addition to the Arkéa branch, feature arbitration based on the client (selective merges, cherry-picks, consistency between branches)

• Build and dependencies on a legacy toolchain (Ivy for run/build, Ant for dependencies)

• Preparation of deliveries to client banks, then maintenance and processing of post-delivery feedback

• Incident analysis and management with the PO/BA

• Technical and functional documentation writing

Achievements:

• Delivery of the entire application suite on time for the January 1st deadline, zero blocking incidents post-delivery

• Improved reliability of legacy code through refactoring systematically secured by tests (unit + non-regression), with no regressions introduced

• Maintained functional consistency between client branches despite differentiated scopes per bank

• Rapid mastery of a legacy build chain (Ivy/Ant) outside current standards, strong adaptability to atypical technical environments

// JAVA 8 & 11, UBUNTU, INTELLIJ, JIRA, CONFLUENCE, IVY, GRADLE, ANT, THRIFT, REST, SWAGGER, MAPSTRUCT, SONARQUBE, JENKINS, POSTMAN, SOAP-UI, NEXUS, GITHUB, GIT //

Retirement

Lead Java / Spring Backend Developer

Joined a team of 6 (3 developers, 1 tech lead, 1 technical-functional referent, 1 project manager) to build a shared information system from scratch between Caisse des Dépôts (CDC) and the Service des Retraites de l'État (SRE): address changes, pension cancellations, declarations and cancellations of death. Following the departure of the tech lead, took over the role of lead developer and continued the project autonomously with the team.

Responsibilities:

• Architecture definition with the architect: micro-services breakdown (back API + front, 4-5 Kafka modules, a batch)

• Design and development of REST APIs for retirement file management

• Development of Kafka modules for exchanges between CDC and SRE information systems, after autonomous upskilling in the technology

• Skill development for two team members (one developer, the tech lead) on the technical foundation

• Data modeling and technical design (diagrams, documentation)

• Unit, integration, and functional testing (Postman collections + test scripts)

• Code reviews (Sonar + Merge Request)

• Leading technical meetings and agile ceremonies

Achievements:

• Build phase completed and application delivered to the run team, despite the tech lead's departure early in the project

• Took on the de facto lead developer role from the first month: thorough note-taking upon arrival enabled supporting the skill development of others

• Autonomous upskilling in Kafka (one week during inter-contract period) immediately reinvested in exchange modules

• Test coverage > 80% and SonarQube quality gate level A maintained across all modules

JAVA 11, SPRING BOOT 2.5.6, ANGULAR 13, REST, APACHE KAFKA, APACHE AVRO, BATCH, POSTGRESQL, LOMBOK, MAPSTRUCT, SWAGGER, JIRA, SONARQUBE, JENKINS, POSTMAN, CONFLUENCE, NEXUS, MAVEN, GIT