Skip to main content

Platform Engineering Maturity Assessment

Answer 20 questions across 5 dimensions to score your platform maturity. Get a radar chart, an overall level (1–4), and targeted improvement recommendations for your weakest areas.

✓ 5 dimensions, 20 questions ✓ SVG radar chart — no external libs ✓ Level 1–4: Reactive → Optimizing ✓ Top 3 recommendations

DX Developer Experience

How easy is it for a new engineer to go from zero to first deployment?

Is there a central Internal Developer Portal (catalog, docs, self-service)?

How consistently are Golden Path templates adopted across teams?

Is developer satisfaction (DX NPS or similar) measured and acted on?

AU Automation

How mature is your CI/CD pipeline (test coverage, gates, speed)?

How automated is infrastructure provisioning (IaC coverage)?

How reliably can you perform rollback without manual steps?

Are database migrations and config changes automated in the pipeline?

OB Observability

Do all production services emit metrics, structured logs, and traces?

Are SLOs defined and error budgets actively tracked per service?

How fast can you detect and diagnose a P1 incident end-to-end?

Is alerting actionable (low noise, clear ownership, runbooks linked)?

SE Security

Is SAST / dependency scanning integrated in the default CI pipeline?

How consistently are secrets managed via a vault / secret manager (no plain-text secrets)?

Is RBAC enforced across platform tooling (IDP, CI/CD, cloud console)?

Are container images scanned for CVEs before production deployment?

SS Self-Service

Can engineers create a new service without filing a ticket (scaffolding, repo, CI/CD)?

Can engineers spin up a dev or staging environment on demand?

Can engineers request and rotate secrets without platform team involvement?

What percentage of platform features are available as self-service APIs or UI actions?

Maturity Radar

0%
Level 1 — Reactive
Developer Experience0/12
Automation0/12
Observability0/12
Security0/12
Self-Service0/12

Top 3 Recommendations

Answer the questions to see tailored recommendations.

Share this tool: X / Twitter LinkedIn
✓ 60,000+ developers use DevPlaybook ★★★★★ 4.8 / 5 on Gumroad ✓ MIT licensed · Instant download ✓ No login required

Related Products

on Gumroad

You Might Also Need

More Free Tools

Enjoying this tool? Get more like it.

Weekly developer tool guides, productivity playbooks & AI tricks. Free. No spam.

DevPlaybook Pro 7 days free

Unlock AI-Powered Dev Tools

  • ⚡ AI Code Review, Doc Generator & SQL Builder
  • ⚡ All premium templates & early access
  • ⚡ Member discounts on Gumroad products
Start Free Trial →

$9/mo after trial · Cancel anytime

Want the full toolkit?

Get DevPlaybook Pro

Every template, guide, boilerplate, and automation script in one bundle. 13 premium products — grab them all at once and save big.

$79
$241 separately Save $162 (67% off)
Get DevPlaybook Pro — $79 →

MIT licensed · Instant download · No subscription

See what's included → Browse all deals →

Frequently Asked Questions

What are the 5 dimensions of platform engineering maturity?▼

Developer Experience (DX): How well the platform reduces cognitive load and friction for product engineers. Automation: How much of the software delivery lifecycle is automated — builds, tests, deployments, rollbacks. Observability: How well teams can understand what their systems are doing in production (metrics, logs, traces, alerting). Security: How early and consistently security controls are applied across the platform. Self-Service: How much teams can provision infrastructure, environments, and services without opening tickets or waiting for platform team help.

What do the 4 maturity levels mean?▼

Level 1 — Reactive: Platform engineering is ad-hoc. Individuals heroically solve problems but there is no standardization. Level 2 — Repeatable: Core practices exist and are documented but adoption is inconsistent. Level 3 — Scalable: Practices are standardized, enforced, and adopted across most teams. Platform team focuses on enablement. Level 4 — Optimizing: Continuous improvement loops, data-driven decision making, and developer experience metrics drive all platform investments.

How often should I run this assessment?▼

Run the assessment at the start of each quarter to track progress, before and after major platform initiatives to measure impact, and when onboarding new leadership to establish a baseline. Share results with your engineering leaders to align on investment priorities. A good target cadence is quarterly with a full team retrospective twice a year.

What should I do after getting my score?▼

Focus on the top 3 recommendations shown after the assessment. Each recommendation targets your lowest-scoring dimensions. Start with one concrete initiative per quarter — trying to improve all dimensions simultaneously rarely works. Common first steps: if DX is weak, start a developer satisfaction survey and internal developer portal; if Automation is weak, standardize your CI pipeline with a golden path template; if Security is weak, implement SAST in your default CI workflow.

How does the radar chart work?▼

The radar (spider) chart shows your score for each of the 5 dimensions on a 0–3 scale (matching the Not Started / Basic / Intermediate / Advanced radio options). Each axis represents one dimension. A perfectly balanced, fully filled pentagon means Advanced on all dimensions. Gaps in the chart reveal which dimensions lag behind. The chart is drawn with SVG and updates in real-time as you answer questions — no external libraries required.