> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/pdi-developer-path-sandbox/pdi-developer/level-2-associate.md).

# Level 2 — Associate

Level 2 of the PDI Developer path. In development: the course outline is still being written.

{% hint style="warning" icon="eye" %}
**SANDBOX — draft page.** REPLACE-ME — this page is scaffolding, not authored content.
{% endhint %}

<h3 align="center">What's needed to complete this page</h3>

Same shape as Level 1, which is the reference:

<table data-search="false"><thead><tr><th width="230">Input</th><th>Notes</th></tr></thead><tbody><tr><td><strong>Positioning line</strong></td><td>One sentence — who steps up to this level, and what changes from Level 1</td></tr><tr><td><strong>Module list</strong></td><td>Module titles in order, each with its lesson count and description</td></tr><tr><td><strong>Lesson list</strong></td><td>Per module: titles, workshop-or-reading, and durations</td></tr><tr><td><strong>Skills you'll gain</strong></td><td>One card per skill area — icon, name, topics separated by dots — as on Level 1</td></tr><tr><td><strong>Duration</strong></td><td>Expected hours to complete</td></tr><tr><td><strong>Prerequisites</strong></td><td>Whether Level 1 is required first, or it can be entered directly</td></tr></tbody></table>

***

<h3 align="center">Skills you'll gain</h3>

REPLACE-ME

***

<h3 align="center">Course outline</h3>

REPLACE-ME

***

{% columns %}
{% column %}
{% hint style="warning" icon="file-certificate" %}
**Course accreditation**

Course accreditation applies to Levels 1 and 2. Finish the lessons and workshops and pass the exam embedded in the guide, and you'll automatically be able to download your course accreditation. It states your name, the course, and the Pentaho version you studied against. Unlike certification, this exam is self-paced and not proctored.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="warning" icon="award" %}
**Certification**

Certification is only available at Level 3 — Certified — not this level. It's a separate credential that organisations look for when engaging Pentaho consultants: all the mandatory courses plus a proctored exam — unlike the embedded exam for course accreditation.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

{% hint style="warning" icon="circle-question" %}
**REPLACE-ME** — confirm the pass mark for the embedded exam, and how many attempts a learner gets.
{% endhint %}

***

<p align="center"><a href="https://academy.pentaho.com/pdi-developer-path-sandbox/pdi-developer.md" class="button secondary" data-icon="arrow-left">Back to the PDI Developer path</a></p>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.pentaho.com/pdi-developer-path-sandbox/pdi-developer/level-2-associate.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
