Hyperscalers offer managed vision, speech, language, and custom training platforms. Cloud AI accelerates prototypes but requires governance: IAM, cost caps, data residency, and logging.
Service categories
- Pretrained APIs — OCR, translation, moderation
- Custom training — AutoML tabular, fine-tuning jobs
- Serving — managed endpoints with autoscaling
- Data labeling — workforce or assisted labeling tools
Integration pattern
# Pseudocode: call a hosted model API
import json
payload = {"inputs": "Summarize this ticket in one sentence."}
print(json.dumps(payload)[:50], "...")
# Real apps: auth headers, retries, timeouts, redact PII firstPractice: Optional Python pseudocode—pair with Python and data science tracks for hands-on depth.
Governance checklist
- Separate dev/staging/prod projects and keys
- Budget alerts on token and GPU spend
- Log prompts/responses with retention policy
- Region selection for data sovereignty
Important interview questions and answers
- Q: Managed vs self-host?
A: Managed reduces ops; self-host for air-gap or strict cost at scale. - Q: API key leak?
A: Rotate keys, scope IAM, never commit secrets to git.
Self-check
- List three cloud AI service categories.
- Name two governance controls.
Pitfall: API keys in git—use secrets manager and separate dev/prod projects.
Interview prep
- Governance basics?
- IAM-scoped keys, budget alerts, regional data residency, prompt/response logging policy.
- Managed API trade-off?
- Less ops burden; vendor terms and lock-in must be acceptable.