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
A DevOps engineer builds and runs the automation that takes code from a commit to production: pipelines, infrastructure as code, containers and the telemetry around them. The role grows from following established workflows to designing the platform and reliability practices other teams build on.
Contenido revisado el 20 de octubre de 2026
Mid-level
Owns the build, infrastructure and container setup of a service end to end, including how it is observed in production.
You write the Terraform, Ansible and Dockerfiles for a service yourself and answer for them when they misbehave. You also set up the dashboards and logs that tell you something is wrong. Compared with junior, you design the change instead of only applying it.
Puntuación media exigida: 69%
Terraform Basics
Por qué: You manage remote state and split a stack safely, so two engineers applying at once or a manual console edit does not corrupt the environment.
Configuration Management
Por qué: You write idempotent playbooks and detect drift, so a server patched by hand during an incident is brought back to the declared state instead of staying a snowflake.
Docker Fundamentals
Por qué: You build small images with sensible volumes and networks and compose a local stack, so a service behaves the same on a laptop and in the cluster.
Container Security
Por qué: You scan images, drop root and keep secrets out of layers, so a vulnerable base image found in a scan is fixed before it reaches production.
Metrics & Dashboards
Por qué: You expose service metrics and build a RED dashboard, so you can see error rate and latency rising after a deploy rather than hearing about it from users.
Log Aggregation
Por qué: You ship structured logs to a central store, so during an outage you search one place by request id instead of logging into each host.
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.
A DevOps engineer builds and runs the automation that takes code from a commit to production: pipelines, infrastructure as code, containers and the telemetry around them. The role grows from following established workflows to designing the platform and reliability practices other teams build on.
DevOps Engineer está mapeado en 4 niveles: Junior, 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í.