Will AI Replace DevOps? Promote Us to Shepherds

Written by Matt Bailey | Aug 23, 2025 10:30:57 PM

AI is racing into software delivery. Tools accelerate boilerplate work, teams push faster, leadership expects more. The fear is simple, AI replaces us. The reality is different. AI shifts our work. We become the people who set guardrails, verify outputs, and turn speed into safe delivery at scale.

The upside you can bank today

  • Faster task completion. Studies report developers finish coding tasks about 55% faster with AI assistants. (GitHub Resources, MIT)
  • Broad adoption. 76% of respondents use or plan to use AI. Current usage at 62%. (Stack Overflow 2024)
  • Platform engineering compounds gains. Reduced lead time, more stable releases, lower cognitive load when teams standardise self-service and automation.
  • CI and CD maturity rising. 60% use CI and CD in production for most or all apps, with automated releases increasing year on year.

The risks you must govern

  • Security debt is the headline risk. A 2025 study found vulnerabilities in 45% of AI-generated code across common CWE classes. Java was most affected. XSS and log injection were frequent failures. (Veracode)
  • Package hallucinations fuel supply chain attacks. LLMs invent libraries that attackers can register and poison, known as slopsquatting. (arXiv, Trend Micro)
  • New attack surfaces need new controls. OWASP Top 10 for LLM apps highlights prompt injection and data leakage that classic web threat models miss. (OWASP)

IoT makes the stakes higher

Connected estates are exploding. Cellular IoT alone is forecast to exceed 7 billion connections by 2030. More devices, more events, more automation. More room for AI to help and to harm if unguided. Expect demand for AIOps to rise as signal volumes outgrow human triage. (Ericsson)

The role shift, from implementer to AI shepherd

What changes

  • Define prompts, patterns, and policy, then codify them in reusable templates.
  • Verify AI outputs with tests, static analysis, and production evidence.
  • Measure flow and quality, then tune models and guardrails.
  • Curate golden paths in the internal developer platform, so safe by default beats fast by accident.

What stays the same

  • Ownership of outcomes.
  • SRE discipline, change control, and incident learning.
  • DORA-aligned flow metrics and quality gates.

Emerging job shapes

  • AI platform engineer builds AI-aware golden paths and SDKs on the platform.
  • AI reliability engineer adds observability, evaluation, and rollback to agentic workflows.
  • Secure-by-prompt engineer bakes compliance and security into prompt patterns and runners.
  • Evidence engineer captures tamper-proof traces of changes, models, and decisions for audit.

Platform engineering is mainstream. It is the right home for this work. Surveys show multi-year adoption and clear developer benefits when platforms standardise automation and security.

A minimal control stack you can deploy now

  1. Guardrails in the pipeline

    Block risky diffs and enforce review on AI-touched code.

    Insert your examples here.

  2. Policy as code

    Stop unsafe infrastructure before it ships.

    Insert your Rego or policy snippets here.

  3. Prompt patterns that encode security

    Make secure defaults the path of least resistance.

    System: You are a senior engineer who writes production-grade code.
    Always include input validation, parameterised queries, and safe logging.
    Never invent package names. Only use libraries from this allow-list: <org list>.
    Cite each import with a link to its docs in comments.
    Return unit tests first, then implementation.
  4. Evidence capture

    Record what changed, who approved, which model helped, and what tests passed.

    Insert your Git notes or evidence pattern here.

What to measure

  • Flow, lead time for changes, deployment frequency, and change failure rate.
  • Percent of releases fully automated. Target the top automation bracket reported in industry surveys.
  • Percent of code that passes security checks on first pass. Trend by model and team.
  • MTTR for incidents related to AI-assisted changes.
  • Cost per unit of delivery, including AI inference costs.

Bottom line

AI changes the work, not the need for engineers. The winners will standardise AI use inside platforms, verify everything, and turn speed into safe, observable flow.