The beginner pilot
Our first courses are written and reviewed. Now we need learners to take them, and to tell us every place where a beginner gets stuck.
The pilot courses
- AI Career Foundations: Roles, Skills and Roadmaps
- Python for Practical AI Engineering
- Essential Mathematics and Statistics for AI
- SQL and Data Preparation for AI
- Machine Learning: From Problem to Reliable Model
- Deep Learning and Transformers Explained
- LLMs: How They Work and How to Choose One
- Building Reliable Applications with LLM APIs
- RAG: Building AI That Uses Your Data
- AI Agents and Workflow Orchestration
- Evaluating and Testing AI Systems
- Fine-Tuning and Adapting AI Models
- Document and Multimodal AI
- Git and Team Development Essentials
- AI-Assisted Software Development
- Build and Deploy Your First API
- Deploying AI Models for Real Users
- Docker and Cloud Essentials for AI Developers
- CI/CD, Testing and Safe Releases
- Databases and Storage for AI Applications
- Scaling APIs and AI Workloads
- Frontend Architecture and Performance for AI Apps
- Authentication, Permissions and Multi-Tenant Applications
- AI Security, Privacy and Responsible Design
- MLOps and LLMOps: Operating AI in Production
- AI System Design and Cost Engineering
- Portfolio Capstone: Build, Evaluate and Ship an AI Product
- MCP: Connect AI Applications to Tools and Data
- Leading AI Products and Teams
Every course is free. You can take one course, or all of them. Python for Practical AI Engineering is the best start if you are new to programming.
How to take part
- Sign in with Google, GitHub, LinkedIn or your email address. The pilot needs an account, so that your reports belong to you and you can delete them.
- Enroll in a pilot course, and take the lessons in order. Do the practice on your own computer, as the lesson says.
- Report as you go. At the end of each lesson, open the form Something unclear or not working? Tell us every word that the lesson did not explain, every step that was missing or did not work, and every setup problem. Copy the error message if there is one. Small things count: they stop other beginners too.
- Tell us the time that each lesson took you, in the same form. It helps us to plan the courses honestly.
- Mark each lesson complete when you finish it, so that we can see where learners stop.
What a good report looks like
"In step 4, the lesson says activate the environment, but it does not say what to type on Windows. I typed source .venv/bin/activate and got The term 'source' is not recognized."
One problem per report is best. You can send as many reports as you want.
What happens to your feedback
- The course team reads every report, and fixes the lesson. You may see the change in the lesson a few days later.
- Your reports are saved with your account and the lesson, in the same database as your progress. They are not public.
- You can download them with the rest of your data, or delete them with your account, on your profile page.
- Do not put passwords, API keys or other personal data in a report. The privacy policy explains how we handle your data.