Experience

Experience connected to support, infrastructure and technical proof.

This page does not try to inflate the experience. It shows where I have been exposed to real environments, how I connect that exposure to technical projects, and what it says about my working method.

2025 — Present

Orange Business — technical support / service environment

Work-study experience in a customer service and support context

Exposure to ticket-based follow-up, service context and professional communication
Support mindset around checking environments, clarifying incidents and keeping trace of actions
Better understanding of operational expectations: accuracy, continuity, escalation and documentation
Experience that helps me present technical projects with more realistic constraints

2025

Private 5G / OpenAirInterface technical work

Hands-on setup, testing and troubleshooting around a 5G SA lab

Work around Core Network, gNodeB, UE logic and reproducible setup notes
Experimentation with RFSim, SDR-related configuration paths and attachment/session behavior
Troubleshooting based on logs, configuration checks, service state and documented observations
Documentation written so another person can continue or rebuild the environment later

2024 — 2026

Project-based network, cyber and telecom labs

University and personal technical projects reframed as professional case studies

Secure hospital network with VLAN, routing, redundancy, services, supervision and backup logic
Secure Java ChatApp with SSL/TLS validation, MySQL persistence and Wireshark evidence
SDR NOAA weather image workflow combining radio constraints, decoding tools and transmission logic
Caldera + ELK lab direction for attack simulation, logs, evidence and recommendations

Foundation

Bac Professionnel Systèmes Numériques and practical technical base

Earlier technical path focused on digital systems and operational habits

Hands-on comfort with equipment, services and step-by-step technical work
Early habits around following procedures, checking results and fixing basic technical issues
Foundation that made networking, systems and telecom projects easier to approach later

What this experience demonstrates

Operational awareness

I understand that technical work is not only configuration: it also includes follow-up, communication, clarity and traceability.

Troubleshooting discipline

The common thread across work and projects is evidence-based diagnosis: logs, captures, state checks and documented tests.

Documentation value

I treat documentation as part of the work, especially when a project has to be reviewed, continued or reproduced.

Realistic self-presentation

The portfolio should make the level clear: what I have done, what I can explain, and what still needs deeper validation.

See the projects behind the experience

The projects page is where the technical proof becomes concrete: architecture, tools, responsibilities, validation and limits.

View projects View skills