Skip to content

Delivery & Platform 90 days 2-3 hours/day updated 2026-06-01

DevEx 90-Day Learning Path

Master DevEx in 90 days — developer experience measurement, toolchain optimization, feedback loops, and cognitive load reduction. Turn developer satisfaction into a strategic advantage.

What DevEx means

Developer Experience (DevEx) is the discipline of measuring and systematically improving the conditions under which software engineers work. It draws on the SPACE and DORA frameworks to quantify productivity, flow, and satisfaction. DevEx practitioners identify friction points in toolchains, onboarding, and deployment workflows and drive improvements that compound into significant velocity gains.

Who should follow this path

  • Platform engineers owning developer tooling
  • Engineering managers measuring team health
  • DevOps engineers reducing developer friction
  • Developer advocates improving internal toolchains

Prerequisites

  • Experience working within a software delivery team
  • Basic understanding of CI/CD and deployment pipelines
  • Familiarity with survey and data analysis techniques
  • Knowledge of platform engineering concepts

The 90-day plan

Daily study recommendation: 2-3 hours/day, six days a week. Consistency beats intensity — block the time in your calendar like a meeting.

Days 1–15: Foundation

  • DevEx definition and the SPACE framework
  • DORA metrics: deployment frequency and lead time
  • Developer cognitive load and flow state
  • Toil identification and categorization
  • Developer satisfaction surveys and NPS

Outcome: Establish a DevEx measurement baseline using SPACE and DORA frameworks.

Days 16–30: Core concepts

  • Developer journey mapping and pain point analysis
  • Onboarding time-to-first-commit measurement
  • Local development environment standardization
  • Dev container and Codespaces setup
  • Toolchain audit and consolidation

Outcome: Reduce time-to-first-commit for new engineers by 50 percent through environment standardization.

Days 31–45: Tools and workflows

  • Internal developer portal with Backstage
  • Self-service scaffolding and golden paths
  • Documentation-as-code and API catalog
  • Reducing context switching with unified portals
  • Developer feedback collection loops

Outcome: Deploy a developer portal that consolidates tooling, docs, and service discovery.

Days 46–60: Hands-on projects

  • CI pipeline speed and flakiness reduction
  • IDE and editor tooling standardization
  • Code review latency measurement and improvement
  • Automated code quality feedback in PR workflows
  • Build cache and incremental test strategies

Outcome: Cut CI pipeline times and code review latency with automated quality feedback loops.

Days 61–75: Advanced practices

  • Engineering productivity analytics platforms
  • Custom dashboards for DORA and SPACE metrics
  • A/B testing toolchain improvements
  • ROI calculation for DevEx investments
  • Executive reporting on developer productivity

Outcome: Build an engineering analytics dashboard and present ROI for DevEx initiatives.

Days 76–90: Portfolio, interview & certification prep

  • Portfolio: DevEx improvement case study
  • DevEx interview preparation
  • Building a DevEx team charter and roadmap
  • Communicating DevEx value to leadership
  • Open-source contributions to Backstage plugins

Outcome: Present a measurable DevEx improvement portfolio and lead DevEx strategy discussions.

Weekly outcomes at a glance

PhaseOutcome
Days 1–15Establish a DevEx measurement baseline using SPACE and DORA frameworks.
Days 16–30Reduce time-to-first-commit for new engineers by 50 percent through environment standardization.
Days 31–45Deploy a developer portal that consolidates tooling, docs, and service discovery.
Days 46–60Cut CI pipeline times and code review latency with automated quality feedback loops.
Days 61–75Build an engineering analytics dashboard and present ROI for DevEx initiatives.
Days 76–90Present a measurable DevEx improvement portfolio and lead DevEx strategy discussions.

Tools to learn

  • Backstage
  • LinearB
  • Swarmia
  • Jellyfish
  • GitHub Codespaces
  • Dev Containers
  • Grafana
  • Datadog
  • PagerDuty
  • Slack

Labs to practice

Mini projects

  • Conduct a full developer journey audit and publish a DevEx improvement roadmap
  • Build a DORA metrics dashboard from CI/CD and incident data
  • Implement dev container standards reducing onboarding from days to hours

Interview questions to prepare

  1. What is the SPACE framework and how does it differ from DORA metrics?
  2. How do you measure developer cognitive load?
  3. What is the difference between developer experience and developer productivity?
  4. How would you prioritize a DevEx improvement backlog?
  5. Describe a successful DevEx initiative you drove and how you measured its impact.
  6. How do you get developer buy-in for toolchain changes?
  7. What role does documentation quality play in developer experience?

Certification suggestions

  • Certified Kubernetes Administrator (CKA) — CNCF
  • AWS Certified DevOps Engineer – Professional — AWS
  • Google Professional DevOps Engineer — Google Cloud

Browse the full certification registry for exam details and official links.

Free resources

// instructor-led option

Prefer live, guided training with mentors and certification support? DevOpsSchool.com runs paid instructor-led programs that pair well with this free path.

Explore paid training on DevOpsSchool.com ↗