ADK made agent building code-first and portable
ADK is open-source, model-agnostic and deployment-independent, with support for Python, Go, Java and TypeScript.
Google’s stack is the most code-first of the three hyperscalers: ADK is an open-source, model-agnostic framework, Agent Engine is the managed runtime beneath it, and the data gravity of BigQuery is usually why the customer chose it. Play to that — grounding on governed data is where this stack wins.
Part 1 is the delivery lifecycle and what each stage means on Google Cloud.
Six stages. Select one to see what it means on this stack.
Choose the workflow, the model family and whether the work belongs in ADK code or Agent Studio.
Ground agents on BigQuery, Vertex AI Search and enterprise content.
Build agents in ADK, compose multi-agent systems and expose tools via MCP.
Build eval sets, baseline them and gate releases in a normal CI pipeline.
IAM, VPC Service Controls, safety settings and data governance across the agent estate.
Deploy to Agent Engine or GKE, trace, monitor cost and hand over.
On Google engagements, the data team is usually the most important relationship. Select one to light the stages they own.
The 2026 read on Google’s agent platform.
ADK is open-source, model-agnostic and deployment-independent, with support for Python, Go, Java and TypeScript.
Managed autoscaling, sub-second cold starts, session management and long-running execution mean teams stop building runtime infrastructure.
200+ models including Gemini, Gemma, Claude and Llama, with LiteLLM integration for the rest.
Agent2Agent was donated to the Linux Foundation with broad industry backing, making cross-vendor agent delegation a standards question rather than a vendor one.
Gemma gives a genuine open-weight option inside the same tooling, which changes the cost profile of high-volume, narrow tasks.
Most Google agent deployments exist because the enterprise data already lives in BigQuery. Grounding quality on governed structured data is the differentiator.
Consulted when this program was written, in July 2026. Each entry names the claim on this page that it backs, so the pairing stays checkable if the copy is later edited.
Part 2 is the Google stack in concrete terms — and the governed-query discipline that separates a demo from a deployment here.
Six building blocks you will use on almost every engagement.
Gemini for frontier reasoning, Gemma for open-weight and edge, plus partner models.
Gemini, Gemma, Model GardenCode-first agent development with multi-agent primitives.
ADK (Python, Go, Java, TypeScript)Managed deployment, scaling, sessions and memory.
Vertex AI Agent Engine, GKEUnstructured search plus governed structured querying.
Vertex AI Search, BigQueryIAM conditions, perimeters and safety configuration.
IAM, VPC Service Controls, safety settingsEvaluation, tracing, monitoring and cost management.
Vertex AI evaluation, Cloud Trace, Cloud MonitoringThe layers a deployment needs, what each one holds, and what the engineer owns there.
Six layers. Click one to see components and SCDAI engineer responsibilities.
BigQuery as the governed analytical estate plus unstructured enterprise content.
Enterprise data and documents in place, with their existing governance.
A governed, classified corpus with column and row policies retrieval must respect.
The analytical estate, with column-level policy tags and row-access policies enforced in the engine rather than in your query.
The document corpus, and layout-aware parsing that preserves the structure a citation later depends on.
Catalogue, lineage, quality and the data-governance surface across the estate.
Discovery, classification and de-identification of sensitive fields before they are indexed or embedded.
Working through governed tables and metrics rather than raw table access.
Embedding a column you were not permitted to read. Policy tags govern the query and not the vector, so de-identification has to happen before the embedding, not after.
Vertex AI Search for documents, governed SQL for structured questions.
A governed, classified corpus from the data layer.
Grounded, attributed results whose access checks were enforced by the engine.
Managed retrieval over the corpus with grounding and source attribution.
Low-latency approximate nearest neighbour at scale for the custom path.
A public-web grounding source for questions the enterprise corpus genuinely cannot answer, kept explicitly separate from it.
Text-to-SQL against BigQuery through the semantic layer, with policy tags doing the trimming.
Preventing free-text SQL from becoming the architecture by accident.
Mixing enterprise and web grounding in one answer without saying which sentence came from where. It is the fastest way to lose a reader’s trust permanently.
Model selection across Gemini and Gemma, context caching and structured outputs.
Grounded, attributed results from retrieval.
Schema-conformant output from the tier that meets the task’s quality bar.
The frontier tier, with long context and native multimodal input.
Open-weight models for the workloads that must run in your own boundary or at your own unit cost.
Explicit caching of a large stable context, priced accordingly.
Response schemas enforced by the API so downstream code parses a contract.
Using small models where they are sufficient, measured rather than assumed.
Filling a long context because it is available. Recall degrades in the middle of a very long prompt, and retrieval quality beats context length nearly every time.
ADK agents, multi-agent composition, MCP tools and A2A delegation.
Schema-conformant model output and its permitted tool surface.
Executed or proposed actions with session state and a trace.
The framework for building, composing and testing agents as code.
Managed runtime and scaling for deployed agents, with state and tracing.
Agent-to-agent delegation and typed tool servers, each with a declared scope.
Write-back into the operational systems, under a service identity with its own trail.
Keeping topology as simple as the problem allows.
Multi-agent designs adopted before a single agent has been measured. Each hop adds latency, cost and a new place for the task to be misunderstood.
Service account scoping, VPC Service Controls, safety settings and data governance.
Proposed actions and drafted responses from the agent layer.
Permitted, perimeter-contained, logged output attributable to a principal.
Least-privilege identity plus a service perimeter that stops data leaving it, however the request is shaped.
Prompt-injection and content screening on both directions of the exchange.
Safety settings, citation checking and the model-governance record for each deployment.
Admin and data-access logging across model, retrieval and tool calls.
Keeping the agent and its data inside a defensible perimeter.
A perimeter around the data and not around the model endpoint. Exfiltration follows the path you left open, and inference is a path.
Evaluation in CI, Agent Engine deployment, tracing and cost control.
Permitted, logged output from the governance layer.
Measured quality, latency and cost, and a gate that can block a release.
Automatic and model-based grading against held-out sets, wired into CI.
End-to-end spans across retrieval, inference and tools.
Quality, latency and error dashboards with alerting on user-visible thresholds.
Cost per task against quota and provisioned throughput.
Regression gating and cost per task on a platform that scales easily.
Model-based grading with no human-labelled anchor. The judge drifts with the model, and your quality metric drifts with it.
An agent generating free-text SQL against raw tables will eventually produce two different answers to the same question. Query through governed metrics.
VPC Service Controls perimeters are how enterprises prevent exfiltration here. Design inside them from the start.
Gemma or a small Gemini tier is often sufficient for narrow, high-volume tasks. Measure before defaulting to frontier.
ADK makes multi-agent easy, which makes premature multi-agent common. Start with one agent and split only when evidence demands it.
Part 3 is the patterns you will build repeatedly on Google Cloud, then the modules, labs and capstones that prove you can run them.
Filter by lifecycle stage or by earned autonomy. Selecting a use case jumps the value chain and the architecture to the stage and layer it depends on.
No use cases match that combination.
How a Google Cloud engagement actually runs.
Land inside the perimeter with a scoped service account. Retrofitting a perimeter is painful.
Agree the query path with the data team. Free-text SQL against raw tables is the mistake that ends these engagements.
Build a single ADK agent with tests and evals. Resist multi-agent until the evidence demands it.
Test whether Gemma or a smaller tier holds quality, and take IAM conditions and perimeter design to security.
Deploy to Agent Engine, wire tracing and cost telemetry, hand over runbook and eval suite.
4 modules, 60 taught hours, 20 hands-on labs and 4 assessments — every lab provisioned and graded by the SCIKIQ Agentic AI Playground. Open a module to see its labs.
End-to-end agent design, development, deployment and testing, 10 hours each. Reviewed by a Senior SCDAI Engineer against a published rubric.
Build an ADK agent that answers analytical questions through governed BigQuery queries with citations, deployed on Agent Engine inside a perimeter, with an eval baseline.
Build a coordinator and specialised sub-agents, delegate one task over A2A, and gate the whole system on CI-enforced evals with full tracing and a measured cost per task.
Every lab in this program follows the shape below. This is lab 02 in full — the brief you are given, the environment that is provisioned for you, the code you start from and the assertions that decide whether you passed.
Stop free-text SQL becoming the architecture by accident.
Expose BigQuery to an ADK agent through validated, parameterised query tools built on governed metrics. Then attempt to make it issue an unbounded or ungoverned query.
@tool
def revenue_by(dimension: str, period: str, filters: dict) -> QueryResult:
"""Parameterised and validated. The agent chooses arguments,
never SQL text."""
raise NotImplementedError
Every module ends with a timed, randomised assessment delivered through the SCIKIQ Agentic AI Playground. The certificate requires a pass on all of them plus two reviewed capstones.
What each test covers, how long it runs, and how many items are currently in the versioned bank behind it.
| # | Assessment & coverage | Items | Time | In bank |
|---|---|---|---|---|
| 01 | Platform foundationsModel selectionADK fundamentalsAgent EngineCost per task | 30 | 45 min | 4 |
| 02 | Grounding & governed queryingVertex AI SearchBigQuery groundingQuery governanceRetrieval metrics | 30 | 45 min | 4 |
| 03 | Agents, tools & multi-agentADK patternsTool designMulti-agent and A2AContainment | 30 | 45 min | 4 |
| 04 | Evaluation, security & operationsEval design and gatingIAM and perimetersTracingCost management | 35 | 50 min | 4 |
Real items, drawn from 16 in this program's bank — weighted toward the scenario and diagnosis types, because those are the ones that predict field performance. Instant feedback, nothing saved.
Four sample items — one attempt each, then the reasoning is shown.
Q1When should you use Agent Studio rather than ADK?
Low-code prototypes that cannot be productionised are a common trap. Use them deliberately, for shaping.
Q2An agent generates free-text SQL against raw BigQuery tables. What is the problem?
Consistency is the issue. Governed, parameterised query tools are what keep the answer stable and the data team supportive.
Q3ADK makes multi-agent composition easy. What is the associated risk?
Ease of use invites unnecessary complexity. Start with one agent and split when evidence demands it.
Q4What is a VPC Service Controls perimeter for?
It is an exfiltration control, complementary to IAM. Together they answer the security question that blocks data-adjacent agents.
The same ladder whichever specialisation you enter through — what changes is the domain you go deep in. Below: how the program is delivered, the skills it moves, the roles it leads to, and the specialisations closest to this one.
The same labs, assessments and capstones, delivered to an enterprise cohort or to individual professionals.
Cohorts of 20 to 2,000+ on your own tenancy, with your data patterns and your cloud. Skill-gap baselining up front, per-team mastery reporting throughout, and capstones scoped against your real backlog so the output is deployable work.
The same labs, assessments and capstones for individual engineers and analysts, run on shared infrastructure with a fixed cohort calendar. You leave with a graded portfolio, not a certificate of attendance.
Find your row and aim one column right. The Playground scores you against this after every module.
| Skill | Beginner | Intermediate | Advanced |
|---|---|---|---|
| Google Cloud platform | Calls Gemini. | Builds ADK agents on Agent Engine. | Designs an agent estate with perimeters and cost control. |
| Governed grounding | Generates SQL. | Uses validated, parameterised query tools. | Designs a governed query path the data team trusts. |
| Model right-sizing | Uses the frontier model. | Tests smaller models on the task. | Designs tiering that holds quality at a fraction of cost. |
| Context engineering | Writes clear prompts. | Structures retrieval, tools and state deliberately. | Designs context strategy for reliability and cost at scale. |
| Retrieval & grounding | Builds basic vector search. | Tunes chunking, hybrid search and reranking. | Designs graph + vector grounding with measured recall. |
| Agent orchestration | Runs a single tool-calling agent. | Builds supervised multi-step and multi-agent flows. | Designs autonomy boundaries and failure containment. |
| Tool & system integration | Calls a documented API. | Writes an MCP server over a system of record. | Designs a least-privilege tool estate across systems. |
| Evaluation | Eyeballs outputs. | Builds labelled eval sets and regression gates. | Runs online evals with drift and judge calibration. |
| Observability & cost | Reads logs. | Traces runs, tracks tokens and latency. | Owns cost per task and capacity planning in production. |
| Security & guardrails | Adds output filters. | Mitigates the OWASP LLM Top 10 in a build. | Threat-models an agent estate and proves controls. |
| Client delivery | Takes notes in a workshop. | Runs discovery and scopes a thin slice. | Owns the account technically, from scope to handover. |
The SCDAI ladder is the same whichever specialisation you enter through — what changes is the domain you go deep in.
Skill a team, or join a cohort
B2B cohorts run on your tenancy with capstones scoped to your backlog. B2C cohorts run on a fixed calendar.
Stated plainly enough to rule yourself in or out without a sales call: the prerequisites, how the program runs, exactly what the credential is worth, and the questions everyone asks.
Stated plainly so you can rule yourself in or out without a sales call. Nothing here is a formal qualification — it is what the first lab assumes you can already do.
You should already be able to do these
What we assume, and what we teach
What the program asks of your week
Cohort dates and pricing are confirmed on enquiry rather than printed here, because both move with the intake.
The credential is awarded per specialisation, so it names the domain or stack you were assessed in rather than claiming general competence. On this program the badge reads SCDAI — Google (GCP, Gemini & Gemma, ADK).
A certificate that cannot be checked is decoration. Every award resolves to a record showing the specialisation, the award date and the assessments passed.
This is the credential the program awards, shown exactly as it is issued — with the specialisation named, the assessment record attached and a verification link anyone can check without an account.
This is to certify that
Your name
has been assessed and certified as
SCIKIQ Certified Data and AI Engineer
Google (GCP, Gemini & Gemma, ADK)
Not “Data and AI Engineer” but the domain or stack you were actually assessed in. A general claim would be a weaker one.
Modules passed, labs graded and both capstones reviewed — so the credential states what was measured rather than that you attended.
The credential ID resolves to a public record showing the specialisation, the award date and the assessments passed.
Add it to your LinkedIn profile in one step. The link pre-fills the certification fields from the credential record, so the entry on your profile matches the record a reader can check.
Add to LinkedIn profile The button is live on your real certificate; here it opens LinkedIn pre-filled with this specialisation so you can see exactly what the profile entry will say.A certificate that cannot be checked is decoration. Every award resolves to a record showing the specialisation, the award date and the assessments passed.
The objections that come up in every conversation about this program, answered without the brochure voice.
Both, and the second is the point. Eight timed assessments and two reviewed capstones stand between you and the credential, so a pass means someone measured the skill rather than recorded your attendance.
Every lab is provisioned, graded and unblocked by the Playground rather than by an instructor. That is what lets a cohort of 2,000 cost the same faculty time as a cohort of 20 — and why you are never waiting on someone to mark your work.
Two retakes are included per assessment, each drawing a fresh item set from the bank, so a retake is a genuinely new paper rather than the same questions again.
For the domain specialisations, no — labs run in provisioned sandboxes. For the four tech-stack programs you will want access to that platform, since deploying into a real subscription is much of the point.
Yes. B2B cohorts run on your own tenancy with your data patterns, a skills baseline before kick-off, per-team mastery reporting, and capstones scoped against your actual backlog so the output is deployable work rather than an exercise.
Take the domain you deploy into. If you move across industries, take a tech-stack program instead and pick up domain context on the engagement. The chooser on the programs page will narrow it.
The trends, platform capabilities and regulatory positions are reviewed each quarter, and every external claim on these pages links to its source so you can check the date yourself.
A graded portfolio: forty machine-graded labs, two reviewed end-to-end agent builds with measured evaluation and cost per task, and a verifiable credential naming your specialisation.
Still deciding?
Tell us the systems you deploy into and we will say plainly whether this specialisation is the right one — or which of the 21 is.