GCP Prep
ProfessionalAI/MLData

Professional Machine Learning Engineer

Professional Machine Learning Engineer covers designing, building and productionising machine learning models on Google Cloud. It is far more about MLOps than about model theory — the exam cares whether your model survives contact with production.

Overview

The most common misconception about this exam is that it is a data science exam. It is not. It is an operations exam that happens to be about models.

Expect the balance of questions to sit in pipelines, serving, monitoring and automation rather than algorithm selection. Training–serving skew, feature stores, drift detection and continuous training carry real weight.

You do need enough modelling fluency to reason about evaluation metrics, class imbalance, overfitting and when a simpler approach is the correct answer. But you will not be asked to derive anything.

Generative AI has grown into a meaningful portion of the exam. Prompt design, grounding, tuning approaches and evaluating generative output now appear alongside classical ML.

The other recurring theme is knowing when not to build. A pre-trained API that meets the requirement usually beats a custom model, and the exam rewards recognising that.

Level
Professional
Exam length
120 minutes
Questions
50–60 multiple choice and multiple select
Registration fee
USD $200 (plus tax where applicable)
Valid for
2 years
Delivery
Online proctored, or onsite at a test centre
Recommended experience (official)
Google recommends 3+ years of industry experience, including 1+ year designing and managing ML solutions on Google Cloud.

Our difficulty rating

5/5

Our recommended preparation

1016weeks

Difficulty and preparation time are GCP Prep's own editorial assessments, not official figures.

Who Should Take This Certification?

  • Machine learning engineers productionising models
  • Data scientists moving towards deployment and operations
  • Data engineers taking on ML platform work
  • Software engineers specialising in AI systems

Skills Covered

  • Framing a business problem as a machine learning problem
  • Choosing between low-code, pre-trained and custom model approaches
  • Data preparation, feature engineering and feature stores
  • Training at scale, distributed training and hyperparameter tuning
  • Serving models: online, batch, and edge deployment
  • ML pipelines, orchestration and continuous training
  • Monitoring for drift, skew and degradation in production
  • Responsible AI, explainability and fairness

Exam Topics

Weightings are shown only where they are officially published — we do not estimate them.

1.Architecting low-code AI solutions

~13%
  • Using pre-trained APIs and low-code tooling to meet a requirement
  • In-warehouse machine learning for tabular problems
  • Deciding when a managed solution is sufficient

2.Collaborating within and across teams to manage data and models

~14%
  • Exploring and preparing data for modelling
  • Feature engineering and managing features consistently
  • Model and dataset versioning, metadata and lineage
  • Working with data engineering and application teams

3.Scaling prototypes into ML models

~18%
  • Moving from notebook experiments to reproducible training
  • Distributed training and hardware accelerator selection
  • Hyperparameter tuning strategies
  • Evaluation metrics appropriate to the problem

4.Serving and scaling models

~20%
  • Online prediction, batch prediction and edge deployment
  • Latency, throughput and cost trade-offs in serving
  • Traffic splitting and safe model rollout
  • Scaling endpoints and managing capacity

5.Automating and orchestrating ML pipelines

~22%
  • Designing end-to-end training and deployment pipelines
  • Continuous training triggers and retraining strategy
  • CI/CD applied to machine learning artefacts
  • Pipeline components, reuse and parameterisation

6.Monitoring AI solutions

~13%
  • Detecting data drift, concept drift and training–serving skew
  • Monitoring prediction quality and business metrics together
  • Explainability and debugging model behaviour
  • Responsible AI, fairness and bias assessment

Preparation Roadmap

Our suggested order of study. Tick steps as you complete them — progress is saved in this browser.

Loading your progress…

Progress is saved in this browser

  1. Machine learning fundamentals

    Enough theory to reason well: supervised versus unsupervised, over- and underfitting, and metric selection.

  2. Problem framing

    Turning a business problem into an ML problem — and recognising when it should not be one.

  3. Data preparation and features

    Feature engineering, feature stores and keeping training and serving features consistent.

  4. Training at scale

    Custom training, distributed strategies, accelerator choice and hyperparameter tuning.

  5. Serving models

    Online versus batch, latency and cost trade-offs, and rolling out a new model version safely.

  6. ML pipelines and automation

    The heaviest domain. Orchestration, continuous training, and CI/CD applied to models.

  7. Generative AI

    Prompting, grounding, retrieval augmentation, tuning approaches and evaluating generative output.

  8. Monitoring and responsible AI

    Drift, skew, explainability, fairness and the operational response when a model degrades.

  9. Practice questions and mock exams

    Prioritise pipeline, serving and monitoring questions — together they dominate the exam.

Certification ready

Study Resources

Learning-hub topics that cover this certification's material, written by us.

Official documentation and training remain the authoritative source for exam content. Our material explains concepts in our own words and is designed to sit alongside it, not replace it.

Practice Questions & Mock Exam

We have 6 original questions relevant to this certification, each with an explanation of why the correct answer is correct and why every distractor is not.

Career Opportunities

Machine Learning Engineer

Build and operate production ML systems end to end.

MLOps Engineer

Own the platform, pipelines and monitoring that ML teams depend on.

AI Engineer

Build applications on top of foundation models, with grounding and evaluation.

Data Scientist (production-focused)

Bridge the gap between experiments and systems that actually run.

Explore career resources

Frequently Asked Questions

Do I need a data science background?
You need working ML literacy — metrics, overfitting, class imbalance, feature engineering — but not research depth. Software and data engineers pass this regularly. Pure data scientists sometimes struggle with the operations and pipeline material, which is the larger part.
How much mathematics is involved?
Very little. You should understand what an evaluation metric means and when precision matters more than recall, but you will not be asked to derive anything.
Should I take Professional Data Engineer first?
It is a strong pairing. Most production ML problems are data problems, and the pipeline and storage knowledge transfers directly. If you have to choose one, pick the one closer to your actual role.
How much generative AI is on the exam?
A meaningful and growing portion. Grounding, retrieval augmentation, tuning approaches and evaluation of generative output are all fair game alongside classical ML.