DevNet to CCIE Automation Rebrand: What It Means for Your Career in 2026

If you’ve been tracking Cisco’s certification ecosystem, you already know something big dropped in February 2026: DevNet Expert is now CCIE Automation. This isn’t just a name change — it’s a strategic signal from Cisco that automation has earned its place at the expert-level table alongside Enterprise Infrastructure, Security, Data Center, and Service Provider.

Let’s break down exactly what changed, what stayed the same, who should care, and how to position yourself for this new track.

Why Cisco Made the Move

For years, DevNet Expert lived in a weird liminal space. It was technically an expert-level certification — same tier as CCIE — but it carried different branding. The “DevNet” label attracted software developers and automation engineers, but it also confused traditional network engineers who didn’t see it as a “real” CCIE.

Cisco’s decision to rebrand addresses three realities:

1. Automation is no longer optional. Every CCIE track now includes automation components. Making it a standalone CCIE track acknowledges that automation expertise deserves the same recognition as routing/switching or security.

2. The talent market demands clarity. Hiring managers understand “CCIE.” They don’t always understand “DevNet Expert.” The rebrand instantly communicates expert-level credibility.

3. Convergence is happening. The line between “network engineer” and “network automation engineer” is dissolving. Cisco’s certification structure now reflects that reality.

What Actually Changed in the Exam

Here’s where it gets practical. The rebrand isn’t purely cosmetic — there are meaningful shifts in the exam blueprint.

Written Exam Updates

The qualifying written exam (formerly 350-901 DEVCOR) has been updated to reflect the CCIE Automation scope:

• Heavier emphasis on infrastructure automation — Expect more questions on IOS XE programmability, YANG models, NETCONF/RESTCONF, and gNMI/gNOI.
• Expanded Cisco platform coverage — DNA Center (now Catalyst Center), Meraki Dashboard API, ACI, and NSO now carry more weight.
• Reduced general software development content — Less emphasis on pure software engineering patterns (12-factor apps, microservices architecture) and more on network-specific automation workflows.

Lab Exam Evolution

The lab exam sees the most significant changes:

• Network infrastructure tasks are now included. Previously, the DevNet Expert lab was heavily API/code-focused. The CCIE Automation lab now includes configuring actual network devices alongside the automation code that manages them.
• Cisco NSO is a first-class citizen. NSO service development, device onboarding, and compliance checking are now core lab modules — not optional extras.
• Terraform and Ansible integration — The lab explicitly tests infrastructure-as-code workflows using these tools against Cisco platforms.

Here’s what a typical NSO service package skeleton looks like — you’ll need to be comfortable with this structure:

$ ncs-make-package --service-skeleton python my-l3vpn-service
$ tree my-l3vpn-service/
my-l3vpn-service/
├── package-meta-data.xml
├── python/
│   └── my_l3vpn_service/
│       └── main.py
├── src/
│   └── yang/
│       └── my-l3vpn-service.yang
└── templates/
    └── my-l3vpn-service-template.xml

And a basic YANG model for a service:

module my-l3vpn-service {
  namespace "http://example.com/my-l3vpn-service";
  prefix l3vpn;

  import ietf-inet-types { prefix inet; }
  import tailf-common { prefix tailf; }
  import tailf-ncs { prefix ncs; }

  list l3vpn {
    key name;
    uses ncs:service-data;
    ncs:servicepoint "my-l3vpn-service-servicepoint";

    leaf name {
      type string;
    }

    list endpoint {
      key device;
      leaf device {
        type leafref {
          path "/ncs:devices/ncs:device/ncs:name";
        }
      }
      leaf interface {
        type string;
      }
      leaf ip-address {
        type inet:ipv4-address;
      }
      leaf vrf-name {
        type string;
      }
    }
  }
}

Who Benefits Most from This Change

Current DevNet Expert Holders

If you already hold DevNet Expert, congratulations — your certification automatically transitions to CCIE Automation. No re-testing required. Your credential just got a significant perception upgrade in the job market.

Network Engineers Considering Automation

This is the biggest win. If you’re a CCNP-level engineer who’s been automating your network with Python scripts and Ansible playbooks, you now have a clear expert-level certification path that validates those skills in a networking context — not a software development context.

The old DevNet path felt like it was designed for developers who happened to work with network APIs. CCIE Automation is designed for network engineers who automate.

Career Changers and Multi-Track CCIE Holders

Already hold CCIE EI or CCIE Security? Adding CCIE Automation creates a powerful combination. The market increasingly values engineers who can both design networks and automate their operation. A dual CCIE in EI + Automation signals exactly that. For a look at what the Automation track pays, see our CCIE Automation salary breakdown for 2026.

The Exam Blueprint: What to Study

Let’s get specific about where to focus your preparation.

Domain 1: Network Programmability Foundations (20%)

This is your baseline. You need solid fluency in:

• YANG data models — Read and write YANG, understand deviations and augmentations
• NETCONF/RESTCONF — Not just “what are they” but hands-on operational use
• gNMI/gNOI — The newer model-driven telemetry and operations interfaces
• Python for network automation — Nornir, Netmiko, NAPALM, pyATS

A quick pyATS testbed example — this is the kind of thing you should write from memory:

# testbed.yaml
testbed:
  name: ccie-automation-lab

devices:
  spine-01:
    os: iosxe
    type: router
    connections:
      defaults:
        class: unicon.Unicon
      cli:
        protocol: ssh
        ip: 10.0.0.1
        port: 22

  leaf-01:
    os: nxos
    type: switch
    connections:
      defaults:
        class: unicon.Unicon
      cli:
        protocol: ssh
        ip: 10.0.0.2
        port: 22

from pyats.topology import loader

testbed = loader.load('testbed.yaml')
device = testbed.devices['spine-01']
device.connect()

# Parse structured output - no regex needed
ospf = device.parse('show ip ospf neighbor')
for intf, data in ospf['interfaces'].items():
    for neighbor in data['neighbors']:
        print(f"Neighbor {neighbor} on {intf}: {data['neighbors'][neighbor]['state']}")

Domain 2: Cisco Platform Automation (25%)

The heaviest domain. You’ll need hands-on experience with:

• Catalyst Center (DNA Center) APIs — Template deployment, assurance, intent APIs
• ACI — Tenant provisioning via REST API and Terraform
• Meraki Dashboard API — Network provisioning and monitoring
• IOS XE RESTCONF — Direct device configuration via YANG-backed REST endpoints

Here’s a real-world Terraform example for ACI tenant provisioning:

resource "aci_tenant" "production" {
  name        = "PROD-TENANT"
  description = "Production network managed by CCIE Automation"
}

resource "aci_vrf" "prod_vrf" {
  tenant_dn = aci_tenant.production.id
  name      = "PROD-VRF"
}

resource "aci_bridge_domain" "web_bd" {
  tenant_dn          = aci_tenant.production.id
  name               = "WEB-BD"
  relation_fv_rs_ctx = aci_vrf.prod_vrf.id
}

resource "aci_subnet" "web_subnet" {
  parent_dn = aci_bridge_domain.web_bd.id
  ip        = "10.10.10.1/24"
  scope     = ["public"]
}

Domain 3: Automation Orchestration & CI/CD (25%)

This is where CCIE Automation diverges most from traditional CCIE tracks:

• Cisco NSO — Service development, device management, compliance
• Ansible for networking — Playbook design, roles, collections (cisco.ios, cisco.nxos)
• Git workflows — Branching strategies, merge requests for network changes
• CI/CD pipelines — GitLab CI or Jenkins for network config validation and deployment

An Ansible playbook you should be able to write cold:

---
- name: Configure OSPF across campus
  hosts: campus_routers
  gather_facts: false
  connection: network_cli

  vars:
    ospf_process_id: 1
    ospf_area: 0
    router_id_map:
      core-rtr-01: 1.1.1.1
      core-rtr-02: 2.2.2.2
      dist-rtr-01: 3.3.3.1

  tasks:
    - name: Deploy OSPF configuration
      cisco.ios.ios_ospfv2:
        config:
          processes:
            - process_id: "{{ ospf_process_id }}"
              router_id: "{{ router_id_map[inventory_hostname] }}"
              areas:
                - area_id: "{{ ospf_area }}"
                  ranges:
                    - address: 10.0.0.0
                      netmask: 0.0.255.255
        state: merged
      register: ospf_result

    - name: Validate OSPF neighbors formed
      cisco.ios.ios_command:
        commands:
          - show ip ospf neighbor
      register: ospf_neighbors
      until: ospf_neighbors.stdout[0] | regex_search('FULL')
      retries: 12
      delay: 10

Domain 4: Assurance & Monitoring (15%)

• Model-driven telemetry — gNMI subscriptions, TIG stack (Telegraf, InfluxDB, Grafana)
• pyATS/Genie — Automated testing and network state validation
• Catalyst Center Assurance APIs — Health scores, issue correlation

Domain 5: Security & Infrastructure Automation (15%)

• Secure API practices — Token management, certificate-based auth, RBAC
• Zero-trust principles in automation — Least privilege for service accounts
• Automated compliance — NSO compliance reporting, custom checks

Study Timeline: A Realistic 6-Month Plan

Assuming you’re already at CCNP level with some automation experience:

How CCIE Automation Compares to Other Tracks

Here’s how the new track stacks up:

• CCIE EI focuses on designing and troubleshooting complex enterprise networks. Automation is a component. See how real network engineers actually use OSPF and BGP daily for what that looks like in practice.
• CCIE Automation focuses on automating those networks. Infrastructure knowledge is a prerequisite, but the exam tests your ability to manage networks through code.
• CCIE Security and CCIE DC have their own automation elements, but they’re domain-specific. CCIE Automation is cross-domain by design.

Think of it this way: CCIE EI proves you can build the network. CCIE Automation proves you can make the network run itself.

The Job Market Impact

The timing of this rebrand isn’t accidental. Here’s what we’re seeing in the market:

• Network Automation Engineer roles have grown 340% on LinkedIn since 2023
• Salaries for automation-skilled CCIEs are commanding $180K–$250K+ base at major enterprises and service providers
• Companies like JPMorgan Chase, Goldman Sachs, and major cloud providers are specifically requesting CCIE-level automation skills in job postings

The CCIE Automation credential gives you a standardized way to prove these skills to employers who already understand the CCIE brand.

What This Means for FirstPassLab Students

We’ve been preparing for this shift. Our training programs have always emphasized the convergence of networking fundamentals and automation — because that’s how modern networks actually work.

If you’re considering the CCIE Automation track, here’s what matters:

1. Don’t skip the networking fundamentals. Automating something you don’t understand is a recipe for disaster. Make sure your routing, switching, and infrastructure knowledge is solid before diving into automation tooling.

2. Get hands-on with NSO early. It’s the single biggest differentiator in the new lab exam. Many candidates underestimate the learning curve.

3. Build a home lab that includes automation. A CML instance with a GitLab CI pipeline pushing configs via Ansible or Terraform is worth more than 100 hours of video courses. Our CML vs INE vs GNS3 comparison covers which platform to pick for your lab setup.

4. Practice writing code under pressure. The lab is timed. You need to write functional Python, YANG, and Ansible from memory — not copy-paste from Stack Overflow.

Key Takeaways

• DevNet Expert → CCIE Automation is more than a rebrand. The exam blueprint now includes infrastructure configuration tasks alongside automation code.
• Network engineers who automate are the primary beneficiaries. This track finally validates the hybrid skillset the market demands.
• NSO, pyATS, Terraform, and Ansible are your core tools. Master them in a network context.
• The content gap is real — few training providers have dedicated CCIE Automation prep yet. Getting ahead now gives you a 12-month advantage.

Frequently Asked Questions

Is DevNet Expert now CCIE Automation?

Yes. Cisco rebranded DevNet Expert to CCIE Automation in February 2026. Existing DevNet Expert holders automatically transition to CCIE Automation with no re-testing required.

What changed in the CCIE Automation exam vs DevNet Expert?

The lab now includes configuring actual network devices alongside automation code, NSO is a first-class citizen, and Terraform/Ansible integration is explicitly tested. The written exam shifted toward infrastructure automation and reduced pure software development content.

How much do CCIE Automation engineers earn in 2026?

Automation-skilled CCIEs command $180K-$250K+ base salary at major enterprises and service providers. Network Automation Engineer roles have grown 340% on LinkedIn since 2023.

How long does it take to prepare for CCIE Automation?

With CCNP-level knowledge and existing automation experience, plan for approximately 6 months of focused study covering YANG/NETCONF, Cisco NSO, platform APIs, CI/CD pipelines, pyATS, and timed mock labs.

Is CCIE Automation worth it for network engineers?

Yes, especially for network engineers who already automate with Python and Ansible. The certification validates hybrid networking-plus-automation skills in a networking context — not a software development context — which is exactly what the market demands.

Ready to fast-track your CCIE journey? Contact us on Telegram @phil66xx for a free assessment.