Everything for DevOps & SRE Engineers
DevOps and SRE engineers live in incident channels, postmortems, and infrastructure-as-code reviews. This hub braids together the CI/CD, cloud, and reliability vocabulary, the grammar patterns used in incident writing, and every relevant interview and blog resource in one place.
Vocabulary sets
Grammar & writing
Interview prep
Related deep-dive hub
Blog articles (10)
- Capacity Planning English: Forecasting and Resource Vocabulary
Learn the English vocabulary for IT capacity planning — headroom, utilisation, forecasting, scaling triggers, and resource allocation terms explained in context.
- DevSecOps English: Security Shift-Left and Threat Vocabulary
Learn the English vocabulary for DevSecOps — shift-left security, threat modelling, SAST/DAST, secrets management, and supply chain security terms explained.
- Green Software English: Sustainability and Carbon-Aware Computing Vocabulary
Learn the English vocabulary for green software engineering — carbon intensity, carbon-aware computing, software carbon intensity, energy proportionality, and sustainability terms.
- On-Call Handoff English: Phrases for Shift Transitions
Learn the vocabulary and phrases for on-call handoffs — verbal and written shift transitions, what to include, what to flag urgently, and handoff templates.
- Pulumi English: Infrastructure as Code in Any Language
Master the English vocabulary of Pulumi — stacks, resources, state, providers, and the key differences from Terraform explained for IT professionals.
- Cloud Migration Strategy Vocabulary: The 6Rs, CAF, and Migration Waves Explained
Master the vocabulary of cloud migration for IT professionals. The 6Rs framework, Cloud Adoption Framework, landing zones, migration waves, TCO analysis, and the language of migration planning discussions.
- Cloud Computing Vocabulary: 30 Essential Terms Explained
The 30 most important cloud computing terms every developer needs to know: regions, availability zones, serverless, IaC, IAM, auto-scaling, managed services, SLA, and more — with real examples.
- English for SRE Engineers: SLO, SLA, Error Budget, and Incident Language
The professional English vocabulary and communication patterns for Site Reliability Engineers: SLI/SLO/SLA, error budgets, incident command, post-mortems, and reliability reporting.
- How to Write a Post-Mortem / Incident Report in English
Templates, phrases, and structure for writing blameless post-mortem reports in English: timeline, root cause analysis, impact statement, and action items. With real examples for DevOps and SRE engineers.
- DevOps Vocabulary: 40 Must-Know Terms Explained
A practical guide to the 40 most essential DevOps terms — from CI/CD pipelines and containers to monitoring, IaC, and deployment strategies. With example sentences for each term.
Other role hubs
Explore more
Browse every exercise category, or search the full site.
Frequently Asked Questions
What's the difference between Infrastructure as Code (IaC) using Terraform and Ansible for a DevOps environment?
Terraform primarily focuses on provisioning infrastructure resources – servers, networks, databases – in declarative manner across multiple cloud providers. Ansible, conversely, is an agent-based configuration management tool focusing on configuring existing systems and deploying applications, often within a single environment. Terraform excels at creating repeatable, scalable infrastructure, while Ansible handles the ongoing maintenance and application setup.
How do SREs utilize SLOs (Service Level Objectives) versus SLAs (Service Level Agreements)?
SLOs define what a service should *achieve* in terms of performance and availability, setting targets based on user needs and business impact. SLAs are contractual promises made to customers regarding service levels, typically focused on uptime or response time guarantees. SREs use SLOs for continuous improvement and proactively addressing potential issues before they impact users, while SLAs primarily dictate legal obligations.
Explain the concept of 'Chaos Engineering' and why it's important in an SRE context.
Chaos engineering involves deliberately injecting failures into a production system to identify weaknesses and build resilience. This isn't about causing outages, but rather controlled experiments like randomly terminating processes or simulating network latency to test how the system responds under stress. The goal is to proactively discover vulnerabilities before they become real problems during an actual incident.
What's 'Observability' in DevOps, and what tools are commonly used?
Observability refers to the ability to understand the internal state of a system based on its external outputs – logs, metrics, and traces. It moves beyond traditional monitoring by allowing you to proactively diagnose problems and gain insights into complex systems using tools like Prometheus, Grafana, ELK stack (Elasticsearch, Logstash, Kibana), and Jaeger.
How do you implement canary deployments effectively for minimizing risk?
Canary deployments involve releasing a new version of an application to a small subset of users before rolling it out to the entire population. This allows you to monitor performance and identify any issues in a controlled environment, mitigating risks associated with large-scale releases using tools like Kubernetes or feature flags.
What is 'Automation as Code' (Aac) and how does it relate to DevOps practices?
Automation as Code means treating automated tasks—like deployments, scaling, or remediation—as code itself, typically using configuration management tools or infrastructure-as-code. This allows you to version control automation workflows, test them thoroughly, and integrate them seamlessly into your CI/CD pipelines for greater efficiency and reliability.
Describe the role of a Service Mesh (e.g., Istio) in an SRE's toolkit.
A service mesh is a dedicated infrastructure layer that manages communication between microservices, providing features like traffic management, security, and observability without requiring changes to application code. It abstracts away complex networking concerns, allowing developers to focus on business logic while SREs can leverage its metrics for deeper insights into service interactions.
What is a 'Post-mortem' analysis, and why are they essential in SRE operations?
A post-mortem analysis is a structured investigation of an incident after it has occurred to identify root causes, contributing factors, and preventative measures. It's not about assigning blame but about learning from mistakes to improve future system design and operational processes, documenting the entire event for knowledge sharing.
Explain how SLIs (Service Level Indicators) differ from SLOs and their role in monitoring.
SLIs are measurable metrics that track progress towards an SLO, such as request latency or error rates. They provide granular data for monitoring and alerting, while SLOs represent the desired level of performance or availability. Monitoring SLIs allows SREs to proactively identify when an SLO is at risk.
What are 'GitOps' principles and how do they align with DevOps workflows?
GitOps advocates treating Git as the single source of truth for infrastructure and application configurations. Changes are made in Git, and automated processes (e.g., using ArgoCD or Flux) continuously synchronize those changes to the target environment, ensuring consistency and auditability throughout the entire system.