> 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/partner-enablement-sandbox/the-practitioner-requirement.md).

# The Practitioner Requirement

Exactly what each partner engineer needs to hold, by role — and what they don't.

{% hint style="warning" icon="eye" %}
**SANDBOX — draft page.** A preview for review only. Nothing here is live. Role links point at the sandbox learning paths; pricing and the migration timeline are placeholders pending the commercial decisions in the Partner Enablement Programme proposal.
{% endhint %}

Partner compliance is a single course accreditation per engineer: **Level 1 — Practitioner** for the role they work in — PDI Developer, Business Analyst or Administrator. The Solution Architect and Solution Analyst paths are optional, open to partners who wish to get Pentaho certified. This page sets out the requirement role by role and links to the course each engineer will take.

***

### The four roles in scope

<table><thead><tr><th width="190">Role</th><th width="150">Requirement</th><th width="230">Who at your organisation</th><th>Course</th></tr></thead><tbody><tr><td><i class="fa-arrow-progress">:arrow-progress:</i> <strong>PDI Developer</strong></td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> <strong>Required</strong></td><td>Implementation engineers who build and operate pipelines on customer projects</td><td><a href="https://academy.pentaho.com/pdi-developer-path-sandbox/pdi-developer/level-1-practitioner.md">PDI Developer, Level 1 — Practitioner</a><br>53 lessons · 6 modules · capstone pipeline · ~14h 35m</td></tr><tr><td><i class="fa-chart-pie-simple">:chart-pie-simple:</i> <strong>Business Analyst</strong></td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> <strong>Required</strong></td><td>Analysts and reporting specialists who build reports, analyses and dashboards for customer business users</td><td><a href="https://academy.pentaho.com/business-analytics-path-sandbox/business-analytics/level-1-practitioner.md">Business Analyst, Level 1 — Practitioner</a><br>15 lessons · 6 modules · capstone APAC Sales Pack · ~6h 40m</td></tr><tr><td><i class="fa-shield-halved">:shield-halved:</i> <strong>Administrator</strong></td><td><i class="fa-circle-check" style="color:green;">:circle-check:</i> <strong>Required</strong></td><td>DevOps and platform engineers who install, secure and run Pentaho Server for customers</td><td><a href="https://academy.pentaho.com/administrator-path-sandbox/administrator/level-1-practitioner.md">Administrator, Level 1 — Practitioner</a><br>39 lessons · 6 modules · capstone server build · ~8h 30m</td></tr><tr><td><i class="fa-compass-drafting">:compass-drafting:</i> <strong>Solution Architect</strong></td><td><i class="fa-circle-plus" style="color:blue;">:circle-plus:</i> <strong>Optional</strong><br>for partners who wish to get Pentaho certified</td><td>Pre-sales and senior delivery leads who scope, design and sign off solutions</td><td><a href="https://academy.pentaho.com/solution-architect-path-sandbox/solution-architect/installation.md">Solution Architect, Installation</a><br>12 lessons · 4 modules · install the platform end to end · ~5h 10m</td></tr></tbody></table>

**Required** roles are the partner compliance bar: every engineer in one of those roles holds its Level 1 — Practitioner course accreditation. **Optional** is never a condition of compliance.

{% hint style="info" icon="calendar" %}
**Data Engineer** joins the partner requirement in Year Two, once that learning path exists for the wider catalogue. Until then there is nothing for that role to complete.
{% endhint %}

***

### What Practitioner involves

Every Practitioner course follows the same shape, whichever role:

* **Hosted lab, included.** A ready-made environment opens from the voucher; the Lab Guide is embedded and starts automatically.
* **Guided modules.** Between about 6h 40m and 14h 35m of effort, depending on the role, self-paced — pause and resume, no continuous week to block out.
* **A capstone project.** A real, deployable piece of work the engineer builds themselves and can show in a customer conversation.
* **An open-book exam.** No proctoring at this level. Pass it and the course accreditation is issued immediately, valid for two years.

The Solution Architect path is different, and optional. It has no levels: it is a set sequence of five courses — DI Developer, then Installation, then three Speciality courses, Containers, High Availability and Enterprise Security — leading to the Certified Solution Architect certification. Enterprise Security is the Integrating Authentication Mechanisms Speciality, the same course the Administrator path offers. It is open to any partner who wishes to get Pentaho certified, and never a condition of partner compliance. Installation, the course in the table, is 12 lessons, eight of them hands-on workshops, about 5h 10m in all: the engineer installs the whole Pentaho platform themselves on a Linux machine they prepare, rather than in a hosted lab, ending in an open-book exam.

***

### What is *not* required

{% hint style="success" icon="circle-check" %}
**Only the baseline is required.** Level 2 — Associate, Level 3 — Certified and the Speciality courses are part of the open Academy catalogue and available to any of your engineers who want to pursue them, but they are never a condition of partner compliance. Nor are the Solution Architect and Solution Analyst paths, which are open to partners who wish to get Pentaho certified. See [Beyond Practitioner](https://academy.pentaho.com/partner-enablement-sandbox/beyond-practitioner.md).
{% endhint %}

Nothing here is a headcount threshold either. How many engineers holding their role's baseline course accreditation your organisation needs, and whether that maps to a partner tier, is set by the Partner Programme — see [Your Organisation's Standing](https://academy.pentaho.com/partner-enablement-sandbox/your-organisations-standing.md).

***

### One course accreditation per engineer, not per role

An engineer holds Practitioner for the role they actually work in. Someone who both builds pipelines and runs the server for a small customer can hold both, but only one is required — pick the role that is most of their job.

<p align="center"><a href="https://academy.pentaho.com/partner-enablement-sandbox/how-enrolment-works.md" class="button primary" data-icon="building">Next: How Enrolment Works</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/partner-enablement-sandbox/the-practitioner-requirement.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.
