Bac Professionnel Systèmes Numériques
Practical base around digital systems, equipment, services, and operational discipline.
A practical technical profile built from labs, support work, and documented troubleshooting.
My direction is clear: networking, systems, cybersecurity, telecom and technical support. I am not trying to look like an expert in everything. I want the portfolio to show how I work: configure, test, observe, fix, document, and explain the result.
Core directionNetworks, systems, cybersecurity, telecom
Work methodSetup → test → troubleshoot → document
Portfolio ruleProof first, no fake claims
What defines my profile
I come from a Bac Professionnel Systèmes Numériques background and continued in Networks & Telecommunications. That path shaped the way I learn: I understand better when I can touch the environment, run commands, break things carefully, and verify the result.
The projects in this portfolio are not presented as perfect products. They are technical case studies: what was built, what tools were used, what evidence exists, what limits remain, and what the project proves about my way of working.
The strongest line in my profile is the connection between networking, systems, cybersecurity visibility, telecom experimentation, and documentation. That mix is what makes the portfolio more serious than a simple academic showcase.
- Infrastructure and service-oriented thinking
- Hands-on troubleshooting with logs, captures and repeatable tests
- Clear documentation for handoff, review and future reuse
Technical path
Networks & Telecommunications studies
Structured work around switching, routing, systems, telecom, cybersecurity labs, and project reports.
Technical support and infrastructure environments
Work-study and practical exposure that connect lab knowledge with tickets, service expectations, communication and follow-up.
Proof-oriented technical portfolio
The portfolio is being rebuilt around serious case studies, clean pages, and honest proof instead of generic descriptions.
How I work
I prefer useful technical progress over vague presentation. A strong project should be readable by someone else: context, setup, tests, evidence, result, and limits.
Start from the environment
Before presenting a result, I try to understand the topology, services, dependencies, configuration files and expected behavior.
Validate with evidence
Logs, Wireshark captures, terminal output, screenshots and controlled tests are stronger than assumptions.
Keep the explanation reusable
I write steps, notes and limitations so another person can understand what was done and continue later.
Be honest about limits
If a part is unfinished or only partially validated, I prefer saying it clearly instead of pretending the project is production-ready.
Professional qualities
Structured execution
I work best when the task is divided into setup, configuration, validation, troubleshooting and documentation.
Technical curiosity
I like understanding why a service fails, why a packet is visible, why a signal is noisy, or why a configuration mismatch blocks the result.
Persistence without pretending
When something does not work, I keep the trace of what was tested and I separate confirmed facts from guesses.
Documentation mindset
A project is not really finished for me if the next person cannot understand the steps, the evidence, and the remaining limits.
Soft skills shown through projects
Clarity
I try to explain technical work in a way that is readable by both technical reviewers and people who need the big picture.
Autonomy
I can move forward from a technical objective, inspect the environment, test options, and build a documented path.
Patience in troubleshooting
I am comfortable working step by step when the answer is not immediate, especially in labs involving network, system or telecom behavior.
Team handoff
I pay attention to notes, structure and reusable commands because technical work often continues after the first person leaves.
What I want to deepen next
Network and service operations
Routing, segmentation, services, monitoring, troubleshooting, and production-style follow-up.
Cybersecurity visibility
Better work around logs, SIEM analysis, attack simulation, indicators, evidence and recommendations.
Telecom and private 5G
More reproducible work around OAI, SDR-related environments, UE testing, RFSim, and technical reporting.
Prepared profile sections
Certifications
Kept honest for now: only verified certifications should appear, with issuer and date.
Interests
Used to make the profile human without moving away from the technical direction.
CV snapshot
A compact web CV view is prepared to summarize the profile without replacing a formal PDF later.
Profile extensions
Certifications
Intentionally honest section: only verified certifications should appear, with issuer, date and proof when available.
Interests
Interests used to make the profile more human while staying aligned with networking, cybersecurity, telecom and creation.
CV snapshot
A concise web view designed to quickly read the positioning, experience, skills, projects and contact path.
See the work behind the profile
The projects page is the strongest proof layer: each main project should explain context, tools, evidence, results and limits.