Site Reliability and GitOps Engineer at Canonical

Confirmed open

Automate Canonical core services and cloud infrastructure with infrastructure as code, Python, CI/CD and observability.

Canonical

Location: Remote
Advertised region: Home based - Worldwide
Work arrangement: remote
Technologies: Python, Linux

Create a free application profile — Keep your skills and projects in a reusable profile. Private by default; you choose when to share. Apply for this job directly with the employer.

By continuing, you agree to processing needed to manage your account and profile. Privacy policy

Role overview

This remote engineering role operates Canonical’s services, networks and infrastructure across private and public clouds. The posting emphasises reusable automation, resilient containers and observability with Prometheus, Grafana and Elasticsearch.

Responsibilities

Expand infrastructure-as-code and automate operations across cloud environments.
Improve resilience and scalability of cloud and container services while maintaining operational responsibility for core systems.
Investigate incidents, capacity and performance using monitoring and tracing tools.
Coordinate architecture, documentation and runbooks with globally distributed development, operations and support teams.

Qualifications

Strong Python and Linux operations experience, including networking, routing, firewalls and storage.
Practical infrastructure-as-code, version control, peer review, testing and CI/CD for application and infrastructure changes.
Experience with cloud services, enterprise Linux administration and troubleshooting across the software stack.
Clear English communication in distributed teams and a computer science or related engineering degree.

Technology in this role

Python: Strong Python and Linux operations experience, including networking, routing, firewalls and .
Linux: Strong Python and Linux operations experience, including networking, routing, firewalls and .
Elasticsearch: The posting emphasises reusable automation, resilient containers and observability with Prometheus, Grafana and .
CI/CD: Practical infrastructure-as-code, version control, peer review, testing and CI/CD for application and infrastructure .
Prometheus: The posting emphasises reusable automation, resilient containers and observability with Prometheus, Grafana and .
Grafana: The posting emphasises reusable automation, resilient containers and observability with Prometheus, Grafana and .

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This Site Reliability / Gitops Engineer position at Canonical is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “This remote engineering role operates Canonical’s services, networks and infrastructure across private and public clouds. The posting emphasises reusable automation, resilient containers and observability with…” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the platform and infrastructure area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Expand infrastructure-as-code and automate operations across cloud environments.”; “Improve resilience and scalability of cloud and container services while maintaining operational responsibility for core systems.”; “Investigate incidents, capacity and performance using monitoring and tracing tools.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “Strong Python and Linux operations experience, including networking, routing, firewalls and storage.”; “Practical infrastructure-as-code, version control, peer review, testing and CI/CD for application and infrastructure changes.”; “Experience with cloud services, enterprise Linux administration and troubleshooting across the software stack.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are Python, Linux. Treat this as a set of posting-derived signals, not a guarantee that every tool is used daily or that the list is complete. For each term relevant to your experience, prepare one concrete example: the system or workflow, the part you owned, the alternatives considered, and how you tested reliability, security, performance or usability as appropriate. If you have not used a named tool, explain the closest related system you have worked with and how you would ramp up; do not relabel that experience as direct production use. If the source describes technologies beyond this list, prioritize its exact wording.

Evidence to put in the application. Tailor the first half of your CV to the named work instead of using a generic summary. Lead with two or three outcomes that match the responsibilities, and include enough context to show complexity, scope and your role. Add technical detail.

About Canonical

Canonical publishes Ubuntu and develops open-source software for cloud, connected devices and enterprise infrastructure. Its teams work across countries.

Employer website

How to apply

Review the original posting and apply through the employer’s careers page.

View source and apply

Source checked: 2026-11-08

Browse job categories

Python