Site Reliability Engineer mock test
EasyEnv, Remote, World Wide, 6 questions
Sign in to applyAbout the role
A site reliability engineer keeps production services available, fast and predictable, and treats operations as an engineering problem. Instead of fixing the same outage twice, an SRE automates the fix, measures reliability against agreed objectives, and works with developers so that new services are built to be run.
The role sits between software development and operations. It usually includes an on-call rotation, and much of the day is spent on observability, capacity and the slow work of removing the causes of incidents.
What you will do
- Run and improve services on Linux, containers and Kubernetes, on cloud or bare metal.
- Build and maintain monitoring, logging and alerting with tools such as Prometheus, Grafana, the ELK stack or Datadog.
- Define SLIs and SLOs with service owners and use error budgets to decide between reliability work and new features.
- Respond to incidents on call, lead root cause analysis and write blameless postmortems with follow-up actions.
- Tune load balancing, proxies, DNS and failover so that a single fault does not become an outage.
- Automate provisioning and remediation with infrastructure as code and scripts.
What we look for
- Several years in SRE, DevOps or Linux systems engineering, with real on-call experience.
- Deep Linux knowledge: processes, memory, file systems, systemd, and reading logs and metrics under pressure.
- Networking fundamentals: TCP/IP, DNS resolution, HTTP, TLS, and reverse proxies such as Nginx or HAProxy.
- Hands-on experience with Docker, Kubernetes and Helm, and with Terraform or a similar tool.
- Programming in Python, Go or Bash well enough to automate your own toil.
Nice to have
- Capacity planning and performance tuning, including kernel and disk I/O.
- Running a relational database such as PostgreSQL in production.
- Chaos testing, disaster recovery drills, and incident management frameworks.
About this mock test
One hour on a real Linux machine, in a terminal in your browser. You debug a Kubernetes service, an Nginx proxy and a name resolution problem, then answer short written questions on incident response, SLOs and memory.
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.
Applying needs a free EasyEnv account, so the company knows who applied and you can follow your application. The interview runs on a real machine, so it needs a desktop browser.
