ADE Maturity Assessment
Three teams starting this course at the same company might map to three different maturity levels — and need three different starting points. The assessment gives you precision that "roughly Level 2" doesn't. Five minutes. Immediate results. Personalized recommendations based on where your team actually operates, not where you think you should be.
Methodology
The assessment scores your team across four dimensions, each reflecting a distinct category of organizational readiness for agentic adoption. Scoring is designed to surface where you're strongest and where the gaps are largest — not to produce a single headline number that obscures the pattern.
The four dimensions
| Dimension | What it measures | Questions |
|---|---|---|
| Technology | Current tooling maturity and infrastructure programmability | 4 |
| Process | DataOps maturity, CI/CD disciplines, monitoring practices | 4 |
| Culture | Learning orientation, experimentation tolerance, cross-functional collaboration | 4 |
| Skills | Context engineering capability, systems thinking, critical AI evaluation | 3 |
Technology (4 questions) covers your current data stack's programmability: whether pipelines are code-defined or GUI-configured, whether environments are isolated, whether infrastructure supports the kind of hook-based triggering that makes agentic automation possible. A team on a fully code-defined, version-controlled stack with isolated environments starts from a much stronger position than a team on GUI-configured tools — not because the latter can't adopt agentic patterns, but because they have more infrastructure work to do first.
Process (4 questions) covers DataOps maturity: whether CI/CD is in place for data pipelines, whether data quality monitoring is systematic or reactive, whether there's a defined incident response process. Agentic systems plug into existing DataOps infrastructure — teams with mature DataOps practices have the hooks the agents need. Teams without them are building infrastructure and agents simultaneously, which is harder.
Each dimension score is independent. A high Technology score with a low Skills score points to a different adoption path than the reverse — look at the pattern, not just the total.
Culture (4 questions) covers the organizational dynamics that determine whether agentic adoption sustains. Does your team regularly experiment with new tooling? Are failures treated as learning opportunities or as evidence that the approach was wrong? Do data engineers collaborate closely with downstream consumers? Teams in experimental, learning-oriented cultures adopt agentic patterns faster — not because they're smarter, but because they iterate more.
Skills (3 questions) covers the specific capabilities that determine whether you can design and operate agentic systems well: the ability to reason about what context an agent needs (context engineering), the ability to think in systems rather than individual scripts, and the ability to critically evaluate AI outputs rather than treating them as ground truth. These are the skills that compound most in the agentic era.
How scoring works
Each question uses a 1–5 scale. Dimension scores are calculated as the average across that dimension's questions. The overall maturity level is determined by the pattern across dimensions — a team with high Technology scores and low Skills scores is in a different position than a team with the inverse pattern, even if the overall number is similar.
Confidence intervals are not provided because the assessment is designed as a diagnostic, not a benchmark.
The goal is direction, not precision.
What your score means
| Level | Description | Recommended starting point |
|---|---|---|
| Level 1 — Manual | Most pipeline work is manual and reactive. Automation is limited to basic scheduling. Team is new to AI tools. | Start with ADE 101 Module 1 and focus on Technology and Process dimensions first |
| Level 2 — Automated | Mature orchestration (Airflow, dbt) and CI/CD; AI-assisted but not agentic; good DataOps practices | ADE 101 — you have the foundation, now learn the agentic layer |
| Level 3 — AI-Assisted | Daily AI tool usage; some pipeline automation; beginning to think about workflow-level automation | ADE 101 Module 5+ (CTT framework) then ADE 201 |
| Level 4 — Agentic | Agents are deployed in your stack; solid DataOps foundation; governance and trust gradients defined | ADE 201 then ADE 301 — you're ready for systems design and production |
| Level 5 — Autonomous | Agents manage significant portions of your DataOps lifecycle with appropriate oversight and governance | ADE 301 — focus on observability, orchestration, and the adoption roadmap |
Teams at Level 2–3 typically see the highest value from ADE 101 and 201. Teams at Level 4–5 should focus on 201 and 301. If you're at Level 1, start with ADE 101 and use the Technology and Process modules as your infrastructure roadmap.
Start the learning path
ADE 101: Foundations → — Start here if you're at Level 1–3 or want to build the conceptual foundation before systems design.
ADE 201: Systems Design → — Start here if you're at Level 3–4 and ready to design multi-agent systems.
ADE 301: Production → — Start here if you're at Level 4–5 and focused on production, scaling, and org adoption.