Overview
SONiC Programmatic Iterative Configuration (gnmi/yang, Swss) Experience Required. SONiC base configuration (L2, mclag, lag/portchannel, bgp, bfd, etc) experience preferred. Position Overview: Looking for a network engineer with experience in data center environments and at least light programming experience. FRR Experience Preferred (OSPF). OpenGear experience nice to have. Light systems programming language (C, C++, Golang, Rust, etc) experience preferred. Scripting Language (Python, Bash, Etc) Experience Required. Linux administration (Bash, systemd units, general system navigation) experience preferred. Virtual Networking (VXLAN) Experience Preferred. AWS networking (VPC, Direct Connect) nice to have.
Responsibilities
- Programmatic Iterative Configuration of SONiC Switches (yang/gnmi, swss, etc.).
- Base Configuration of SONiC Switches (Inband and OOB configurations as described).
- Implement and demonstrate CRUD/CRD-style interfaces for constructs such as Physical and sub interfaces, VXLAN/VNI, VRF, and ACL.
- Provide correctly functioning examples and document interface functionality for the SingleStore team to implement; Golang implementation of the core functionality is expected but not required for the role.
- Coordinate with DevOps on switch integration with monitoring and transition from ad-hoc to code-driven base configuration.
- Coordinate with DevOps on switch provisioning (ZTP or otherwise) and on the SONiC build pipeline.
- Contribute to network engineering efforts to free up the storage team to focus on storage implementation.
Additional Configuration & Topology
- Inband Configuration: L2, mclag, lag/portchannel, bgp, bfd; set up anycast addresses for metadata service IP, SAG, etc.
- Bifurcated Spine-Leaf Topology (Inband): details on spine/ToR connections and private AS per side.
- Spine-Leaf Topology (Out Of Band): 1x spine per side; private AS considerations; current L3 hardcoding may be present.
- Coordination with DevOps on firewall integration, monitoring, and code-driven configuration changes.
Requirements & Experience
- FRR experience required; OpenGear experience bonus.
- Direct experience with OpenGear and related network gear is favorable.
- Requirements include FRR experience and ability to work with in- and out-of-band network configurations.
Tasks & Challenges
- Transition from ad-hoc to code-driven configuration; multi-path and traffic handling considerations such as egress/ingress behavior and multipath reliability.
- Direct Connect multipath verification; ensure security features do not hinder legitimate traffic; address issues like DNSSEC where applicable.
- Setup tasks: direct-to-end-device serial console via SSH; standardized OS versions for devices; standardized credentials.
- Cellular requirements for emergency access and recovery scenarios; minimum expectations for data plans.
Topology & Hardware
- Physical Topology: 2x OpenGear OM2224 spines, 16x OpenGear IM7248 ToRs.
- Current State: spines routable; ToRs lack ethernet routing; end-device access via nested console sessions.
Coordination
Coordinate with colocation vendors and DevOps on antenna extension installation, monitoring integration, and network provisioning.