All projects

Professional work

RATITEC · energy project backend

The Spring Boot backend of a platform that connects renewable-energy projects, field interventions and billing.

  • Delivered during the internship
  • In a pair
  • Confidential
Talk to me about it
Spring Boot REST APIs
12+
projects tracked on the platform
15+
links: project, intervention, invoice, payment
4
from design to delivery
2 months

01Starting point

Context & mission

The problem

In renewable energy, a company follows its projects, dispatches technicians to the field and bills its clients. These activities need to be connected and traceable, not scattered across separate tools.

The mission

During this summer internship, co-design and build the platform’s backend in a pair: projects, field interventions and billing, plus a few integration tasks on the React front end.

As a pair

My scope within the pair: the billing logic and the field-intervention module, plus small integration tasks on the React front end.

02Execution

What I did

  1. Layered REST APIs

    Controller, Service, Repository, DTO: each layer has one clear responsibility.

  2. Data model

    Projects, clients, technicians, interventions and invoices persisted with Spring Data JPA, Hibernate and MySQL, with operation traceability.

  3. Billing

    Validation rules, invoice generation, payment lifecycle and notification triggers.

  4. Field interventions

    Status management and operation history, exposed to the React front end through REST APIs.

  5. Teamwork

    Scrum (sprints, reviews, an evolving backlog) and Git day to day.

03Design

Architecture

A layered Spring Boot API: controllers expose DTOs, services hold the business rules (validation, billing, statuses), Spring Data JPA repositories persist entities in MySQL through Hibernate. The React front end consumes these APIs.

The business chain covered
  1. ProjectClients · technicians
  2. InterventionStatuses · history
  3. InvoiceValidation · generation
  4. PaymentLifecycle · notifications
API layers
  1. ReactFront end
  2. ControllerREST · DTOs
  3. ServiceBusiness rules
  4. RepositorySpring Data JPA
  5. MySQLHibernate

04Impact

Results

  • A backend covering the whole chain: project, intervention, invoice, payment.
  • Business rules enforced server-side, with a history for every intervention.
  • APIs consumed by the React front end, delivered within the two-month internship.

05Wrap-up

Takeaways

What this project proves

That I can turn a real business into reliable, traceable backend rules, as part of a team and on a short timeline.

Learnings and next steps

My first backend experience in a company. It gave me solid foundations in layered design and business-rule modelling, which I then pushed further on eBank and on the AI copilot at ALTEN.

06Technology

Full stack

  • Java
  • Spring Boot
  • Spring Data JPA
  • Hibernate
  • MySQL
  • React
  • JUnit
  • Mockito
  • Git
  • Scrum

Explore next

Professional work
  • Demonstrator qualified in internal staging
  • Confidential

Access-controlled AI copilot (RAG)

Final-year internship (PFE) · ALTEN Delivery Center Maroc · RabatMar → Sep 2026

An internal copilot that answers employees’ questions from company documentation, cites its sources, respects who may read what, and hands over to human support when needed.

Company knowledge was scattered across PDF and DOCX documents. Finding the right answer meant searching by hand or interrupting a colleague. A generic chatbot was not an option: it cannot say where an answer comes from, and it has no notion of who is allowed to read what.

correct answers (manual evaluation, 50 questions)
98%
to the first streamed token
< 1.5 s
PDF and DOCX documents indexed
50+
Scrum sprints
13
  • Java
  • Spring Boot
  • Spring Cloud Gateway
  • Python
  • FastAPI
  • LangChain
  • OpenAI
  • PostgreSQL
  • pgvector
  • Angular
  • +8
Read the case study : Access-controlled AI copilot (RAG)Confidential code