LLMs, calling an LLM API, rate limits (TPM/RPM)
An LLM client with retries, timeouts and a rate limiter; every call logged to a table; a domain config loader.
A burst of 50 calls finishes with no rate-limit errors.
18-week course roadmap for working data engineers
You already move, clean and model data. Learn to add retrieval, agents, guardrails and production serving by building one real product, one module a week.
Why this roadmap
Parsing documents, chunking, embedding, keeping an index fresh, controlling who sees what, and proving answers are right: that is your day job, with new tools. This course closes the gap without months of theory. Each week has one topic and one build, and nothing is thrown away.
One product, DataPilot, grows a module each week. You never start from a blank page.
Industry details live in config “packs”, so the same code runs on Lending, Retail and Telecom.
Tracing, evaluation, access control, load tests and failure drills are part of the plan.
How it works
About 10 hours a week. Only the topic changes.
Watch or read the week's free course module.
Reproduce the course example in a notebook.
Turn the notebook into a product module.
Run the week's test; fix until it passes.
Rerun on another industry. From week 10, add a 45-min incident drill.
Record results and what broke when you swapped.
One system-design interview question.
A pack is a folder with everything industry-specific: warehouse schema, sample data, documents, catalog, brand voice, compliance rules and test questions. The one rule: if switching domains needs a code change, that's a bug. Move it into the pack.
The roadmap
Pick a phase to see what you learn, build and test each week.
Learn how LLMs work and turn messy documents into clean, searchable data.
An LLM client with retries, timeouts and a rate limiter; every call logged to a table; a domain config loader.
A burst of 50 calls finishes with no rate-limit errors.
A document extractor that turns text into validated JSON, with a direct vs step-by-step comparison.
10 sample documents load, bad ones are rejected, accuracy recorded.
A warehouse built from a schema, plus search over column descriptions and cosine similarity written by hand.
“Where is the payment date?” finds the right column.
Ingestion of internal and customer documents into tables, with scan clean-up before OCR.
20 PDFs ingested two ways; OCR accuracy compared before and after clean-up.
Build a retrieval-augmented (RAG) assistant that answers from company documents with citations.
Four chunking strategies compared, including the recursive splitter.
10 questions pick a winning strategy.
A pgvector store with domain and audience filters.
Top-5 results are relevant; customer queries never return internal chunks.
Ask the Docs with page citations, keyword + vector fusion and diversity-aware retrieval.
10 answers cite the right file and page.
Incremental re-embedding by hash with an Airflow DAG per domain.
Re-running skips unchanged documents.
Build agents that use tools: query the warehouse, diagnose failures, respect roles, and measure quality.
Ask the Data: a LangGraph text-to-SQL agent (read-only, timeouts, self-correction) with end-to-end tracing.
15 questions answered correctly; every request has a complete trace.
Triage a Failure: classify seeded pipeline failures and suggest fixes from similar past incidents.
10 seeded failures classified correctly.
A persona-aware router, per-user rate limits, memory, approval before large queries, and an MCP server.
Each role reaches only its allowed capabilities and data.
An evaluation harness for every capability, plus a small LoRA fine-tuning notebook.
One command produces a full quality report.
Put agents in front of customers safely, and add generative content with compliance and human sign-off.
A public Customer Assistant on a separate endpoint, scoped to the logged-in customer, with input/output checks and human handoff.
20 customer questions answered; 15 attack prompts all refused.
Marketing Studio: pick a segment, write the brief and ad copy, optionally create images, check compliance, queue for approval.
A full campaign passes compliance; a rule-breaking draft is blocked.
Govern, serve, monitor and stress-test the platform, then certify.
Chunks in Delta tables under Unity Catalog, Vector Search, PII masking before embedding, grants per persona.
No raw PII in the index; grants enforced per role.
Agents logged and registered, served on Model Serving, with versioned prompts and an internal app.
The endpoint answers every capability with traces.
Custom scorers, AI Gateway limits, Docker Compose, Locust load tests, failure tests, circuit breaker and fallback model.
Under a 10x spike, error rate and latency stay within targets.
The production-readiness gate, a runbook, final evaluation, and the certification exam.
Every gate item is checked.
Free learning material
Tip: click any resource title to open it in a new tab. Some courses need a free account.
Sunday design hour books: Designing Data-Intensive Applications (Kleppmann), weeks 1–9; AI Engineering (Chip Huyen), weeks 10–18.
What you will build
DataPilot serves three audiences: the data team (everything), business users (answers and campaigns, never raw personal data) and customers (public info and their own account only). The customer assistant runs on a separate public endpoint, so it is never one prompt injection away from internal data.
Answers questions over company documents with page citations, kept fresh by a daily pipeline.
Turns a plain-language business question into safe, read-only SQL and returns an answer or chart.
Reads a failed pipeline log, classifies the failure, finds similar past incidents and suggests a fix.
A public assistant that answers from customer-safe documents and the customer's own account, and hands off to a human when unsure.
Picks a segment from the warehouse, writes the brief and ad copy, checks compliance, and waits for human approval.
Decides which capabilities and data each user can reach: data team, business user or customer.
Extract fields, search metadata, ingest PDFs
Ask the Docs with citations, fresh daily
Ask the Data, Triage, router, MCP, evals
Customer Assistant + Marketing Studio
Governed, served, load-tested, certified
Industry impact
The same capabilities apply across sectors. Only the data, documents and rules change.
Analysts are the bottleneck for every portfolio question.
Ask the Data lets loan officers ask “which loans are 30+ days past due by branch?” and get an answer without waiting.
Borrowers call to ask about balances and payment dates.
The Customer Assistant answers from public policies and the customer's own loan record, and hands off when unsure.
Ads and emails must carry required disclosures.
Marketing Studio checks every draft against compliance rules and blocks it until a person approves.
Policy documents are long and scattered.
Ask the Docs answers with the exact page it came from, which auditors can verify.
Returns and order questions flood support.
The Customer Assistant answers return policy and order status, and refuses to reveal other customers' data.
Merchandising can't easily see why products come back.
Ask the Data answers “which products had the highest returns last quarter?” with a chart.
Win-back campaigns take days to prepare.
Marketing Studio selects the segment, writes ad variants per channel, and queues them for approval.
Supplier invoices arrive as PDFs and scans.
The extractor and OpenCV clean-up turn them into validated, searchable data.
Plan and bill questions drive call volume.
The Customer Assistant explains plans and bills using the customer's own account data.
Billing pipelines fail overnight and teams scramble.
Triage a Failure classifies the log and suggests a fix from similar past incidents.
Churn needs targeted offers.
Marketing Studio builds a segment and an offer campaign with compliance checks.
Technical manuals are hard to search.
Ask the Docs gives cited answers to field and support teams.
One place decides who sees which data, so a new feature never opens a new leak.
One evaluation harness and tracing setup cover every capability.
A new industry is a new pack of config, documents and test questions: hours, not weeks.
Production ready
The product isn't “delivered” until every item passes.
From week 10, every Friday you break something on purpose and fix it the same way:
If 10% of 1 million users ask 5 questions a day:
The bottleneck is the LLM provider, not the web servers. Fixes: gateway quotas, autoscaling servers with Redis memory, an LLM gateway with fallback and caching, queues for slow work, and a protected warehouse.
Certify and interview
45 scored questions, 90 minutes, $200, online proctored. The product you build is your hands-on prep for all six sections: design, data preparation, application development, deployment, governance, and evaluation and monitoring.
FAQ
Working data engineers comfortable with SQL, Python and pipelines who want to add AI skills. No prior machine-learning experience is needed.
About 10 hours a week for 18 weeks: 1.5 hours each weekday, 2 hours on Saturday and 1 hour on Sunday.
All learning material is free. You pay for LLM API usage, which stays low with small models while building. The optional exam costs $200.
Weeks 1–14 run locally with Postgres, Airflow and Python. Databricks appears in weeks 15–18 for governance, serving and the exam.
Any. The provider lives in configuration, so you can use OpenAI, Gemini, Claude or an open-source model through Ollama.
Skip course videos, never the build. Always run Thursday's test and Friday's domain swap.
Start with week 1: an LLM client with retries, rate limiting and call logging.
Open the roadmap