> 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/speciality-courses.md).

# Speciality Courses

The advanced tier of the PDI Developer path. Standalone courses for experienced pipeline developers, some counting towards Level 3 — Professional.

The advanced tier, for experienced pipeline developers who want to push beyond standard ETL into machine learning, streaming and AI workloads.

{% columns %}
{% column %}
{% hint style="success" icon="cube" %}
**Each one stands alone**

Take a single speciality on its own. You don't need to work through Levels 1 to 3 first — just the hands-on experience to keep up.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="info" icon="award" %}
**Some count towards Level 3**

Certain specialities form part of the **Level 3 — Professional** certification, so the work counts twice if you're heading that way.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

<h3 align="center">Who these are for</h3>

{% columns %}
{% column %}
{% hint style="success" icon="circle-check" %}
**You're ready — if you**

* Already build and run PDI pipelines day to day
* Are comfortable with transformations, jobs, parameters and variables
* Want to go beyond standard ETL into machine learning, streaming and AI workloads
  {% endhint %}
  {% endcolumn %}

{% column %}
{% hint style="info" icon="signs-post" %}
**Start with the levels if you**

* Are new to Pentaho Data Integration
* Haven't yet built a pipeline end to end
* Prefer a guided curriculum over figuring out gaps in your PDI knowledge on your own

**Level 1 — Practitioner** takes you from your first transformation to a production-shaped pipeline.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

<h3 align="center">Choose a speciality</h3>

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-brain-circuit">:brain-circuit:</i> <strong>Machine Learning</strong></td><td>REPLACE-ME — one line on what this course covers and who it's for.</td><td><em>REPLACE-ME</em></td><td></td></tr><tr><td><i class="fa-wave-pulse">:wave-pulse:</i> <strong>Streaming Data</strong></td><td>REPLACE-ME — one line on what this course covers and who it's for.</td><td><em>REPLACE-ME</em></td><td></td></tr><tr><td><i class="fa-robot">:robot:</i> <strong>AI Pipelines</strong></td><td>REPLACE-ME — one line on what this course covers and who it's for.</td><td><em>REPLACE-ME</em></td><td></td></tr></tbody></table>

{% hint style="warning" icon="circle-question" %}
**REPLACE-ME** — mark which of the three count towards Level 3 — Professional, so a buyer can see it on the card rather than in the small print. Also confirm whether the entry bar is real-world experience or a formal PDI Developer level.
{% endhint %}

***

<p align="center"><a 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.pentaho.com/pdi-developer-path-sandbox/speciality-courses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.