12 semanas · intensivo
Para quien tiene plazo
Unas 8 horas por semana, en 1 ciclo centrados en las brechas que más pesan.
Carrera en 2026 y 2027
An Analytics Engineer turns raw warehouse data into tested, documented models that analysts and business teams can trust. The role sits between data engineering and analysis, applying software practices such as version control, testing and CI to SQL transformations.
Contenido revisado el 20 de octubre de 2026
Senior
Sets the modeling, testing and delivery standards of the analytics codebase and is accountable for its trustworthiness across teams.
You spend less time on individual models and more on the structure that lets others build safely: project conventions, CI, review of risky changes, and decisions about what to stream or sync. The change from mid-level is that your choices are inherited by every analyst who touches the project.
Puntuación media exigida: 74%
Staging/Intermediate/Marts Layers
Por qué: Lets you restructure a project that grew organically, set naming and materialization rules, and stop marts from referencing raw sources directly.
Dimensional Modeling in Practice
Por qué: Lets you design conformed dimensions shared by several business areas, so sales and marketing report the same customer count rather than two competing ones.
Data Testing (Generic & Custom)
Por qué: Lets you decide which custom tests guard business-critical models and which are noise, keeping the suite fast enough that people do not skip it.
Data Quality Assertions
Por qué: Lets you set anomaly and distribution checks with sensible thresholds and an owner for each alert, so a quality incident is handled rather than muted.
Snowflake/BigQuery/Redshift
Por qué: Lets you weigh a warehouse migration or a multi-platform setup against pricing, concurrency and lock-in, and defend the recommendation to engineering and finance.
Cloud Cost Optimization for Analytics
Por qué: Lets you set up resource monitors and per-team cost attribution, so a runaway query is capped automatically and the monthly bill is explainable.
CI/CD for Data Models
Por qué: Lets you build slim CI with deferred state so a pull request tests only the changed models, giving fast feedback and blocking a breaking change before merge.
Data Lineage & Impact Analysis
Por qué: Lets you trace a wrong dashboard figure back to its source model and list every downstream asset affected before renaming a column.
Reverse ETL Patterns
Por qué: Lets you sync a modeled customer segment into the CRM safely, handling duplicates, failed syncs and field mapping, so sales acts on warehouse data.
Real-Time Analytics Modeling
Por qué: Lets you decide which metrics truly need near-real-time freshness and model them with micro-batch or streaming, leaving the rest in cheaper daily batch.
Cada nivel de esta carrera corresponde a una ruta de estudio. Lee gratis el mapa completo de temas y luego mide tu nivel.
12 semanas · intensivo
Unas 8 horas por semana, en 1 ciclo centrados en las brechas que más pesan.
40 semanas · regular
Unas 4 horas por semana, en 3 ciclos. Cada ciclo lleva lo que quedó pendiente del anterior.
An Analytics Engineer turns raw warehouse data into tested, documented models that analysts and business teams can trust. The role sits between data engineering and analysis, applying software practices such as version control, testing and CI to SQL transformations.
Analytics Engineer está mapeado en 3 niveles: Mid-level, Senior y Expert. Abre cada nivel arriba para ver las habilidades que debe demostrar.
El plan tiene 2 ritmos: 12 semanas por nivel, con unas 8 horas por semana (intensivo) y 40 semanas por nivel, con unas 4 horas por semana (regular).
Una sesión de estudio para cada tema nuevo, a tu nivel.
Clases prácticas de uso de IA en el día a día de tu carrera.
Cada requisito se demuestra midiendo, no marcando una casilla.
Al final de cada ciclo ves qué avanzó y qué pasa al siguiente.
Un diagnóstico corto mide las habilidades que ya tienes. El recorrido empieza ahí.