Catalog / DEV-500

DEV-500

DevOps Engineering

Delivery-system design: pipeline architecture, DevSecOps controls, progressive release, and operating discipline.

Tuition
$5,500 USD
Duration
5 weeks
Commitment
5-6 hrs/week
Format
Live online cohort
Admissions
Rolling
Overview

About this program

Pipelines are systems, and most were never designed - they accreted. This program treats the delivery system as an engineering artifact: value-stream thinking, pipeline architecture on GitHub Actions or Azure DevOps, supply-chain security controls, progressive delivery with real rollback, and the operating metrics that show whether any of it is working.

Who this is for

  • Engineers responsible for CI/CD across multiple teams
  • Platform and DevOps leads formalizing delivery standards
  • Tech leads whose release process has become the bottleneck
Outcomes

What you will be able to do

  • Design pipeline architecture with clear stages, gates, and environment strategy
  • Implement supply-chain security: scanning, SBOMs, signing, and provenance
  • Ship with progressive delivery, feature flags, and rehearsed rollback
  • Operate delivery with DORA-style metrics and continuous improvement cadence
Curriculum

Program modules

Delivered over 5 weeks of live tutor-led sessions, applied work, and structured review.

M01

Delivery system design

  • Value-stream mapping your current path to production
  • Trunk-based development and branch strategy trade-offs
  • Environment strategy: how many, and what each is for
  • Build once, promote everywhere: artifact discipline
M02

Pipeline architecture

  • GitHub Actions and Azure DevOps: structural patterns
  • Reusable workflows, templates, and pipeline-as-code hygiene
  • Secrets, identities, and least-privilege pipeline access
  • Caching, parallelism, and pipeline performance
M03

DevSecOps and supply-chain security

  • Dependency scanning and vulnerability workflow design
  • SBOM generation and artifact signing in practice
  • Provenance and build integrity concepts
  • Policy gates without paralyzing delivery
M04

Release engineering

  • Progressive delivery: canary, blue-green, and ring models
  • Feature flags: architecture, hygiene, and cleanup debt
  • Rollback as a rehearsed, tested capability
  • Database and stateful-change release patterns
M05

Operating the delivery system

  • DORA metrics: measuring without gaming
  • Incident learning loops and blameless review practice
  • Delivery SLOs and the platform-team interface
  • Capstone: delivery-system design review with critique
Labs & applied work

Hands-on components

  • Guided pipeline build with security gates on a reference application
  • Progressive-delivery and rollback exercises in a lab environment
  • Delivery-system design capstone with structured review
Rolling admissions

Ready to apply?

Apply any time. Admissions reviews your fit, confirms the next available cohort, and issues an invoice. Your seat is confirmed on payment.