Connectivity Systems Engineer

The Connectivity Systems Engineer designs and governs the passive physical-connectivity plant - the structured-cabling systems, the datacenter interconnect (DCI) and cross-connect architecture, the optical and copper transport media, the patch fields and meet-me-room, and the labeling and administration scheme - so the active network has a reliable, documented, and scalable physical layer to ride on. Core ownership is the connectivity design and the standard: the topology and media selection, the link and loss budgets the plant is engineered to, the cross-connect and patch-panel systems, the cabling bill of materials and port schedules, and the design records the field builds and certifies against. This is an individual-contributor engineering seat that sets the physical-layer standard and hands a buildable design to the crews and technicians who install it; it is not the person on the ladder with a splicer or the person configuring the switches. Performance is visible in plant reliability, how cleanly the design builds and certifies in the field, and how far the connectivity scales before it has to be re-engineered. This role is defined as much by its neighbors as by its remit. It is not the Fiber Technician who installs, splices, terminates, and certifies the fiber - the engineer designs the connectivity system and the standard the technician builds and certifies to (design-the-system versus build-to-the-design). It is not the Network Development Engineer who builds and automates the active switching / routing fabric - the engineer owns the passive plant and the transport media the fabric rides on (physical-connectivity-systems versus active-network-fabric). It is not the Fiber Superintendent who runs the construction crews and the field delivery - the engineer produces the design and the standard, not the crew schedule and the site management. And when SRE, cloud, or network operations configure the logical network, they are depending on the physical connectivity systems this seat engineers underneath them. What separates great from average is a connectivity design that builds clean, certifies to budget, and scales - not a diagram that looks right on paper. A great engineer designs the topology for the redundancy and diversity the service actually needs, selects media and transceivers against a real link / loss budget and reach, engineers cross-connects and patch fields that a technician can build and trace, writes a labeling and administration scheme the whole plant obeys, and hands the field a bill of materials and port schedule that construct without a hundred RFIs. A mediocre one draws a topology that ignores the loss budget, mixes media the transceivers cannot drive, invents a labeling scheme nobody follows, and hands the field a design so un-buildable that the plant that actually gets installed bears little resemblance to the drawing.