I had a Beatport network diagram that could help me get a job. Sending it was the uncomfortable part.
A New York recruiter sent a long list of requirements for a systems and network role. Layer 2 and Layer 3 networking. BGP and OSPF. Firewalls, VPNs, Linux, DNS, mail, monitoring, data-center wiring, Windows integration, and enough troubleshooting to deal with all of it when the clean diagram stopped matching reality.
I answered every item.
The environment I managed had more than 300 active nodes. I described the work as about 15 percent troubleshooting and 85 percent growth and expansion. Beatport had grown nearly twenty times over three years, so most days were about adding capacity before the old design became the limit.
The written answers were detailed, but a real network map would make the scope obvious in seconds.
I had one that showed the routing protocols, VLANs, BGP relationships, internet providers, and load balancing. I removed security information and hardware details. The sanitized version was already useful in vendor conversations.
I still did not attach it.
Instead, I asked the recruiter whether it would help and whether the company would be comfortable receiving it. I did not want a useful work sample to make me look careless with my employer's information.
That mattered more than squeezing another page of proof into the application. Anybody hiring an infrastructure person should care how that person handles a network diagram from the last job.
The point was to show that I knew the environment without showing the environment.