profile:
role: "Computer Engineering Student @ ESPRIT"
location: "Tunis, Tunisia"
track: "Network Engineering / IT Infrastructure / Linux Systems"
certification: "Cisco CCNA 200-301 — in progress"
current_focus:
- "CCNA switching and routing labs"
- "Enterprise-style GNS3 topologies"
- "Linux service deployment and monitoring"
- "Structured troubleshooting and validation"I build network infrastructure labs, stress them, break them, and bring them back to a working state.
My strongest focus is network engineering and Linux-based infrastructure: routing, switching, subnetting, VLANs, OSPF, NAT, VPN concepts, DHCP/DNS, Linux services, monitoring, packet analysis, and documentation.
I am currently preparing for Cisco CCNA 200-301, with a practical learning style built around labs, failure scenarios, show commands, Wireshark captures, and reproducible validation.
|
A browser-based exam simulator I built while preparing for CCNA switching topics. It focuses on STP, PVST+, Rapid PVST+, root election, port roles/states, guard features, IOS commands, topology analysis, and 
|
A multi-zone GNS3 infrastructure project with Cisco IOS routers, segmented networks, OSPF routing, NAT, VPN concepts, Linux service VMs, and monitoring. Final validation involved tracing issues across OSPF adjacencies, route propagation, UDP tunnels, DHCP gateways, VM IP settings, and Linux service status. 
|
|
Full-stack HR and talent management platform built with Symfony 6.4, PHP, MySQL, Doctrine, Groq/OpenRouter APIs, face-api.js, and TensorFlow.js. Worked on AI scoring workflows, profile enrichment, authentication flows, skills categorization, and client-side face validation. 
|
Integrated academic project for secure exam-box assignment and tracking. Built with Qt/C++, Arduino, QR scanning, RFID, GPS tracking, and serial communication to support operational tracking workflows. 
|
|
|
|
|
|
design the topology
↓
build the addressing plan
↓
configure routing / switching / services
↓
break something intentionally or hit a real failure
↓
isolate the layer
↓
verify with commands + captures
↓
document the fix
I care about the part most people skip: validation.
A network is not working because the diagram looks clean.
It is working when routes propagate correctly, hosts receive the right gateways, services respond, captures prove the traffic path, and the failure can be reproduced and fixed again.
Jul 2024 – Aug 2024 · Tunis, Tunisia
- Designed VLSM-based IPv4 addressing plans for segmented lab networks.
- Configured and validated VLANs, trunks, inter-VLAN routing, DHCP/DNS, OSPF/RIP, and static routes.
- Used traceroute, routing-table checks, and Wireshark captures to verify reachability.
- Implemented ACL-based segmentation and SSH hardening.
- Documented configurations, validation checks, and failure/fix evidence.
2026 target:
- complete CCNA 200-301 preparation
- keep building infrastructure-focused projects
- strengthen Linux administration and monitoring
- move toward network engineering / infrastructure reliability / security foundations
I am especially interested in internships or junior opportunities around:
Network Engineering · IT Infrastructure · Linux Systems · Monitoring · Security Foundations · Operations
ESPRIT — Ecole Supérieure Privée d'Ingénierie et de Technologie
Cycle Ingénieur, Computer Engineering · Expected 2028
Relevant coursework: Computer Networks, Operating Systems, Databases, Object-Oriented Programming, Software Engineering, Data Structures.
build → break → inspect → fix → document