DevOps Engineer mock test

About the role

A DevOps engineer owns the path from a commit to running software: the build, the pipeline, the container images and the runtime they deploy to. The job is to make releases boring, fast and repeatable, and to keep production healthy once the code is there.

In most teams that means CI/CD, Docker and Kubernetes, infrastructure as code on a public cloud, and a share of on-call and troubleshooting across the whole stack.

What you will do

• Build and maintain CI/CD pipelines in GitLab CI, GitHub Actions or Azure DevOps, and fix them when they stall or fail.
• Write efficient Dockerfiles and keep images small, cacheable and secure.
• Deploy and run workloads on Kubernetes with Helm, including probes, resource limits and autoscaling.
• Provision cloud infrastructure with Terraform and manage configuration with tools such as Ansible.
• Set up logging, metrics and alerting, and debug performance problems from the application down to the network.
• Take part in on-call, incident response and postmortems, and document what you build.

What we look for

• Several years in a DevOps, platform or infrastructure role.
• Hands-on experience with Kubernetes and Helm, and an understanding of why pods restart, fail probes or get evicted.
• Container build knowledge: image layers, build cache, multi-stage builds.
• Experience with Git, CI/CD systems and at least one cloud platform (AWS, GCP or Azure).
• Linux and networking fundamentals, and scripting in Bash or Python.

Nice to have

• GitLab CI specifically, including runners and caching.
• Observability with OpenTelemetry, Prometheus and Grafana.
• Willingness to read application code (Python, Node.js or similar) when the problem is not in the infrastructure.

About this mock test

One hour on a real Linux machine, in a terminal in your browser. You get a stuck GitLab pipeline running, stabilise a Kubernetes pod that keeps failing and speed up a slow Docker build, then answer short written questions on probes and image layers.

This is practice. There is no job at the end of it. It is the same interview format employers run on EasyEnv, so you can measure yourself against what companies hiring for this role ask for, and see where you need more work.