Results for “pipeline-design”

Guides database design, implementation, optimization, migration, pipeline development, quality, and operations across SQL and NoSQL platforms.

Guides database design, implementation, optimization, migrations, data pipelines, and operations across SQL and NoSQL platforms.

Build synthetic datasets and data generation pipelines using the Data Designer library.

Designs and implements production-grade ML pipeline infrastructure: configures experiment tracking, creates orchestration DAGs, builds feature store schemas, deploys model registries, and automates retraining and validation workflows.

Define el enfoque, las herramientas y el pipeline de análisis antes de escribir código, eligiendo entre SQL, Python o un enfoque híbrido según la pregunta y los datos.

Cleans datasets, detects anomalies, generates reports, and creates visualizations using pandas, scikit-learn, and plotting libraries to turn raw data into client-ready deliverables.

Designs and implements big data architectures, processes large-scale datasets with distributed systems, and optimizes data pipelines for throughput using Hadoop, Spark, and cloud platforms.

Guides database design, implementation, optimization, migration, pipeline development, quality, and operations across SQL and NoSQL platforms.

Design and optimize revenue operations systems that connect marketing, sales, and customer success into a unified revenue engine.

Designs and implements RAG pipelines, covering document chunking, embedding strategies, hybrid search, answer synthesis with source attribution, and evaluation using RAGAS metrics.

Manage feature flags, experiments, and metrics in Eppo via its REST API, including flag configuration, experiment design, statistical analysis, and metric pipelines.

Designs and implements production-grade RAG systems by chunking documents, generating embeddings, configuring vector stores, building hybrid search pipelines, applying reranking, and evaluating retrieval quality.

Agent profile for design data pipelines, transformations, imports, exports, warehouse models, validation, and freshness checks. Use when Codex needs a specialist agent perspective for planning, implementation, review, debugging, validation, or handoff in this domain.

Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", or "LSM tree vs B-tree". Also trigger when choosing between SQL and NoSQL, designing data pipelines, or debugging distributed system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.