Hi, I’m Ulaş. I’m a network and systems engineer. This isn’t a résumé, it’s the part that doesn’t fit on one: how I got here, what I do now, and where I want to go.
Where I come from
I studied Computer Engineering at Erciyes University and graduated in 2025. I had software courses too, but what always pulled me in was how a packet travels from one end to the other. Why a switch can’t learn a MAC address, why a route doesn’t take: solving those has always felt like a puzzle. I built my foundation with Cisco Networking Academy courses: switching, routing and wireless.
My first real networking job happened while I was still studying. From autumn 2022 to late 2023 I worked part-time at the university’s IT department: getting end devices onto the network, IP/DHCP and domain settings, finding out why a user’s “no internet” really happened. It sounds small, but that’s where I saw how networks actually break.
What I do now
Since September 2024 I’ve been working as a network and systems engineer on enterprise and public-sector projects. In short:
- Built campus and data-center networks with Aruba, Cisco and HPE: redundancy with VSX and MC-LAG, VXLAN overlay, VRF traffic isolation, OSPF
- Built a factory network from scratch. In a live environment with no VLANs I did the segmentation and moved critical systems into a DMZ with FortiGate
- Took part in VMware ESXi to Hyper-V migration projects across dozens of provinces, thinking about the switch side together with the virtualization layer
- Deployed wireless networks of hundreds of APs, did controller replacements, and ran RF surveys with Ekahau
- Set up VPN and NAT with FortiGate and Sophos, monitoring with Zabbix and packet analysis with Wireshark
The most important thing I’ve learned: “it doesn’t work” is not a fault description. You first ask which layer, which end, and since when. Most problems don’t come from something complicated, they come from a simple thing you skipped. That’s why the “where I got stuck, how I solved it” posts on this blog exist.
The lab side
I built a solid foundation in enterprise networks, but one question kept nagging me: how does this traffic get carried across an operator’s backbone? The answer lives in telecom transport networks: MPLS, BGP, EVPN and Segment Routing.
So I spend my free time in the lab. In GNS3 I built a small service-provider network with Nokia SR OS: MPLS transport with OSPF and LDP, and a VPRN with MP-BGP between the PEs. I isolated two customers using the same IP blocks with RD/RT. Then I built the same service on Huawei in eNSP and put the two vendors’ commands side by side. Each vendor’s CLI works a little differently, commands I’m used to sometimes backfire and I get stuck on settings. I write about those here.
On certifications, I currently have HPE Aruba Certified Associate and Cisco Networking Academy courses. My next targets, in order, are CCNA, Nokia NRS 1 (November 2026) and Huawei HCIA-Datacom (February 2027).
Where I’m heading
My goal is clear: telecommunications. I want to work on the operator side, in transport and backbone networks, with vendors like Nokia and Huawei or in an operator’s network team, building and running networks at real scale. I don’t have professional experience in this field yet and I’m not hiding it. But I bring the habits from the enterprise field and the hours I’ve spent in the lab. This blog is the diary of that road.
Why this blog exists
Three reasons:
- I think if I can’t write something down, I haven’t really learned it. Writing makes it stick.
- I want something to exist for people on the same path. I couldn’t find a Turkish resource where I got stuck.
- I want to look back in six months and see how far I’ve come.
The posts only use examples from my own lab environment. I don’t share customer or organization information.
Roadmap
What I’ve finished and what’s next:
What’s on the blog
Highlights from the labs I built and wrote up:
Outside the screen
I work out regularly, play PC games and listen to rap and rock/metal. I practice English with those songs too, and I read and write technical documentation comfortably.
Contact
If you spotted a mistake in a post, you’re labbing the same topic, you’re looking for someone on a telecom team, or you just want to say hi: