GenAI Data Engineering
Build RAG data pipelines for ingestion, chunking, embedding, and indexing. Manage vector store operations and embedding model lifecycle.
8 courses, each building on the last. The bar shows each course's share of the curriculum. 7 goals are unlocked for preview.
Python Essentials for Agent Builders11.2%
LLM Foundations for Agent Builders10.8%
Kubernetes Essentials for GenAI Engineers10.8%
Web APIs & Services for GenAI Engineers9.7%
Data Infrastructure Essentials for GenAI10.8%
Enterprise LLM Customization20.6%
GenAI Data Pipelines19.5%
GenAI Operations6.5%
Core responsibilities this discipline prepares you for. Open one to see how you build it.
Build embedding pipelines — ingest, chunk, embed, and store in vector databases
- Select and benchmark embedding models across OpenAI and Gemini for domain-specific accuracy
- Implement chunking strategies (fixed, semantic, recursive) with batch embedding generation
- Build complete pipelines processing thousands of documents into pgvector with HNSW indexing
Design RAG data infrastructure — hybrid search and reranking
- Build BM25 + semantic hybrid search with LLM-as-reranker patterns using Gemini
- Implement semantic caching for throughput optimization and query result deduplication
- Construct hybrid search pipelines and benchmark retrieval quality with RAGAS precision-recall metrics
Build knowledge graph pipelines using Neo4j
- Extract entities from unstructured text and construct knowledge graphs with relationship typing
- Implement GraphRAG patterns and agentic Graph-RAG with MCP tool integration for graph traversal
- Build knowledge graphs from document corpora and query them with graph-aware retrieval agents
Process documents at scale — parsing, chunking, and quality filtering
- Process multi-format documents with Docling across PDF, HTML, and Office formats
- Apply intelligent context-preserving chunking and GPU-accelerated curation with NeMo Curator
- Build document processing pipelines that handle real-world messy data with quality filtering
Implement data quality controls — PII, dedup, compliance filtering
- Integrate Presidio for PII detection with custom entity recognizers and deduplication strategies
- Build compliance pipelines with content classification for regulated industries
- Construct quality gates that block non-compliant documents from entering the embedding pipeline
Orchestrate data pipelines with scheduling and failure recovery
- Use Argo Workflows for Kubernetes-native pipeline orchestration with DVC data versioning
- Build quality gates between pipeline stages with dead-letter queues and failure recovery patterns
- Wire multi-stage pipelines with automatic retry, checkpoint recovery, and quality validation gates
Monitor pipeline health — freshness, quality scores, embedding drift
- Instrument pipeline stages with OpenTelemetry and build Grafana dashboards for freshness and quality
- Monitor retrieval quality continuously with RAGAS evaluation and embedding drift detection
- Build monitoring for live pipelines that detects data quality degradation and triggers remediation
Design multi-tenant data isolation for enterprise RAG
- Build tenant-aware embedding pipelines with pgvector namespace isolation per customer
- Implement row-level security for vector search with per-tenant quality monitoring
- Verify tenant data isolation under concurrent multi-tenant queries with cross-tenant leakage tests
Each group becomes a signed node on your public skill graph — a recruiter-auditable record of the labs you actually passed. Share the URL; they see the discipline, the labs, and the signature.
Run the embedding pipeline at corpus scale: batch generation, and the senior signal — re-embedding the whole corpus to a new model with zero downtime (dual-write, backfill, cutover), plus dimensionality/quantization and cost trade-offs.
Get heterogeneous sources in cleanly — where the job actually bleeds time: PDF/HTML/table/multimodal parsing, cleaning and normalization, dedup, and incremental/CDC sync with freshness handling.
Operate the index as a lifecycle: vector-DB ops, index construction and tuning (HNSW/IVF/PQ), reindex/rebuild/compaction/backup, sharding, and recall-vs-latency tuning at build time.
Is the index good? precision@k / recall@k / MRR / nDCG, golden-retrieval-set construction, chunking-strategy tuning (tuned against these metrics), drift detection, and retrieval regression — measuring the index, not the answer.
Build the graph when vectors aren't enough: entity/relation extraction, ontology and graph construction (Neo4j), GraphRAG retrieval, and graph+vector hybrid.
Build and tune the retrieval stage offline: dense+sparse/BM25 fusion, reciprocal rank fusion, and cross-encoder reranking — tuned against a golden set, not per-request in a feature.
Close the loop: feedback capture, re-embedding/re-index triggers, active learning, corpus expansion, and continuous retrieval eval.
Keep the corpus compliant: PII detection/redaction, lineage, access governance, and the hard problem — right-to-be-forgotten deletion from the index and every derived artifact.
Run the pipeline as a system: orchestration (Airflow/Dagster/Prefect), batch-vs-streaming, scheduling and backfills, data versioning, deployment/CI-CD for pipeline jobs, and monitoring/scaling.
Baseline provider access in pipeline code: embedding and LLM SDK calls, auth, batching, and retries.
Production Python for pipeline code: async, Pydantic, data libraries, typing, and error handling.