Professional Machine Learning Engineer
Vertex AI Pipelines is a serverless orchestration service that executes machine learning workflows defined using either the Kubeflow Pipelines (KFP) or TensorFlow Extended (TFX) software development kits (SDKs). A developer writes the pipeline logic in Python and compiles the code into a pipeline definition file, which is then submitted to Vertex AI Pipelines for execution. The orchestration engine parses the directed acyclic graph (DAG) and executes tasks in strict dependency order, automatically provisioning the underlying compute resources for each step. Intermediate datasets, trained model weights, and metrics flow directly to Cloud Storage locations rather than remaining inside temporary compute containers.
+-------------------------------------------------------------+
| Pipeline Definition (KFP / TFX) -> Compiled Pipeline (YAML) |
+-------------------------------------------------------------+
|
v
+-------------------------------+
| Vertex AI Pipelines |
| (Serverless Engine) |
+-------------------------------+
|
+----------------------+----------------------+
| | |
v v v
+---------------+ +---------------+ +---------------+
| Ingestion & | ---> | Model | ---> | Model |
| Preprocessing | | Training | | Evaluation |
+---------------+ +---------------+ +---------------+
| | |
+----------------------+----------------------+
|
(Persists Artifacts & Lineage)
v
+----------------------------------+
| Cloud Storage & Vertex ML |
| Metadata |
+----------------------------------+
A pipeline component is a containerized, self-contained unit of computation that performs a single stage of the machine learning lifecycle, such as data extraction, transformation, training, or evaluation. Components accept inputs (such as parameters and artifact references), execute isolated tasks inside custom or prebuilt container images, and emit new output artifacts. Vertex ML Metadata automatically tracks the lineage and execution history of every component in the pipeline, recording exact code versions, input parameters, and output artifact locations. When an execution step encounters an error, the pipeline marks that task as failed, terminates dependent downstream tasks, and preserves all completed upstream outputs and lineage records for troubleshooting and auditing.
Automated model retraining is the automated execution of an end-to-end pipeline to refresh a model whenever underlying data distributions change or new training data arrives. Retraining workflows execute through three distinct trigger patterns:
Continuous training (CT) integrates model evaluation gates into the automated pipeline to ensure that newly trained models meet strict performance criteria before deployment. Once the training component produces a candidate model artifact, a downstream validation component calculates evaluation metrics—such as area under the curve (AUC), F1-score, or root mean squared error (RMSE)—against a dedicated evaluation dataset. If the candidate model's performance exceeds configured minimum thresholds and outscores the currently deployed baseline model, the pipeline marks the model as blessed and registers it in Vertex AI Model Registry. If the candidate fails the evaluation gate, the pipeline transitions to a rejected state, alerts the engineering team, and leaves the active serving endpoint unchanged.
Prepare and test your skills
Prepare and test your skills
Automated model retraining workflows are initiated through scheduled triggers using Cloud Scheduler, data-driven triggers using Cloud Storage notifications routed via Cloud Pub/Sub to Cloud Functions or Cloud Run, and metric-driven triggers from Vertex AI Model Monitoring alerts. These mechanisms execute pipelines on a recurring timetable, upon the arrival of new training data, or when feature skew, data drift, or concept drift exceed configured statistical thresholds.
When a candidate model exceeds configured minimum thresholds and outscores the currently deployed baseline model, the pipeline marks it as blessed and registers it in Vertex AI Model Registry. If the candidate fails the evaluation gate, the pipeline transitions to a rejected state, alerts the engineering team, and leaves the active serving endpoint unchanged.
Vertex ML Metadata automatically records the lineage, execution history, code versions, input parameters, and Cloud Storage artifact locations for every component in the pipeline. If an execution step encounters an error, the pipeline marks that task as failed and terminates downstream tasks while preserving all completed upstream outputs and lineage records for troubleshooting and auditing.