Network Engineer with Automation

Job Role - Network Engineer

Location - Round Rock, TX (hybrid)

Duration: 12 months + Contract

Job Description:

Network Engineer (x12 openings)

Business Requirement:

The meeting centered on qualifying multiple network engineering openings tied to a broader infrastructure modernization effort. Manager explained that his team, along with another managers team, has similar requirements and is hiring because Client has a large volume of end-of-life network gear across data center and remote site environments, including MDF/IDF closet-type locations. He said many of these devices are already at the end of life or have been for several years, which is creating instability and limiting Dell's ability to support newer AI-driven initiatives.

Manager framed the business need around modernization, stability, vulnerability remediation, and automation. He noted that Dell cannot fully support "modern things" or the AI wave unless the infrastructure, hardware, and software are current. He also acknowledged vulnerabilities as an important factor, but emphasized that operational stability and faster remediation through automation are equally important drivers

From a role perspective, manager repeatedly stressed that Client is looking for a network engineer who also has automation expertise, not an automation engineer who happens to know some networking. He said prior hires with strong software or automation backgrounds but weak networking knowledge took too long to ramp because they had to rely on other network experts. Dell does not have time for that learning curve on this effort

The work mix is expected to be roughly 60% automation and 40% network engineering/design, although manager said it could swing to 70/30 or 80/20 depending on the project phase. The automation will support provisioning, refreshes, software/hardware modernization, and APIs such as CMDB-related integrations.

This role is not simply a network automation opening. Manager was clear that Client needs a true senior network engineer first, with strong automation capability layered on top. We are prioritize deep infrastructure/networking credibility first, then validate automation experience and openness to SDD/AI-agent-enabled development

Identify the main technical pillars as CCNP-level network engineering, network design, automation, and spec-driven development/SDD. He clarified that the first three are critical must-haves, while SDD is newer and can be learned if the candidate has the right attitude and aptitude.

TECHNICAL REQUIREMENTS:

1. Senior Network Engineering Background

• The strongest must-have is deep, hands-on network engineering experience. Manager specifically said Client wants someone who is a network engineer first and has operated at a CCNP-level. He described this as someone who understands infrastructure, security, and how to design data center environments.

2. CCNP-Level Knowledge, Can get away with CCNA Preferably Certification

• Manager called out CCNP-level knowledge as the first key requirement. He said a CCNP certification is preferred because it signals that the candidate understands networking, infrastructure, security, and data center design concepts. He also said CCNA may be acceptable as a starting point if the candidate checks the other major boxes, but a lack of networking knowledge would be a major concern

3. Layer 2 / Layer 3 Design Experience

• Manager emphasized that candidates need to understand how access switches, distribution switches, Layer 2, Layer 3, and switching technologies fit together in a broader architecture. He specifically tied this to designing sites, data centers, and edge environments.

4. Automation Experience in a Networking Context

• Automation is a critical requirement. Manager said the ideal split is around 60% automation and 40% networking/design, and he described automation as central to software upgrades, provisioning, hardware/software refreshes, faster remediation, and improved reliability.

5. Python, Ansible, Terraform, or Comparable Automation Frameworks

• Manager mentioned Python and Ansible but said Client is not locked into only those tools. He said candidates may have used Python, Ansible, Terraform, similar scripting, cloud-based tooling, or AI-assisted approaches, and that any infrastructure automation framework could be relevant if it produced the right outcomes.

6. API Integration Experience

• Manager confirmed that REST API knowledge is part of the automation requirement. He specifically mentioned using APIs to call existing infrastructure systems and referenced CMDB APIs or similar sources to fetch information during provisioning or automation workflows.

7. Experience with Large-Scale Refresh or Modernization Efforts

• Manager gave examples of strong success criteria, including candidates who have stood up a data center, architected or delivered successful infrastructure work, or helped refresh thousands of devices using automation in the background.

8. Troubleshooting as Part of Design and Deployment

• Manager clarified that this is not an operational NOC-style role and the person will not spend their time on bridges. However, troubleshooting is still important when issues arise during provisioning, deployment, refresh activity, or when something the engineering team deploys causes a problem.

9. Change Management and Ability to Push Through Red Tape

• Manager said he does not have a strict preference on company size. Candidates can come from large companies or startups, but he emphasized attitude and the ability to work through red tape, change management, and organizational friction. He specifically said he does not want someone who will become frustrated in that type of environment.

10. Openness to Spec-Driven Development / AI-Assisted Development

• Manager identified spec-driven development, or SDD, as a newer requirement. He said it is a plus if candidates have recent experience with it, but it is not a hard blocker as long as they have the right attitude and can learn how to work with AI agents or tools like Devin/Claude-type environments.

Best-Fit Candidate

The ideal candidate is a senior network engineer with roughly 10 years of real infrastructure experience, CCNP-level knowledge, strong Layer 2/Layer 3 design skills, and hands-on automation experience tied to network provisioning, refreshes, or infrastructure modernization. They should be comfortable with Python, Ansible, Terraform, APIs, or comparable tools, and open to using AI-assisted/spec-driven development methods.

Acceptable Candidate

A strong CCNA-level candidate may be acceptable if they have deep practical networking experience, meaningful automation experience, and can clearly demonstrate that they have designed, deployed, or refreshed enterprise network infrastructure. Manager said CCNA can be a starting point if the candidate checks the other boxes.

Quick Pass / Fail Scorecard