← All jobs

Python Container Images Software Engineer at Canonical

Confirmed open

Build and secure container images and their CI/CD pipelines using Python and Go in a remote role spanning Americas, APAC and EMEA.

Canonical logoCanonical

Search jobs by company: Canonical

Location
Remote
Advertised region
Home Based - Americas; Home Based - APAC; Home based - EMEA
Work arrangement
remote
Technologies
Python, Kubernetes, Docker, Linux
See how to apply

Save job — free account Saved jobs

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.

We’ll email you a sign-in code. Upload your CV after sign-in.

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

Role overview

Canonical’s container image team builds images and the automation that tests and publishes them. The source lists remote locations in the Americas, APAC and EMEA, with company travel up to 15 percent of working time.

Responsibilities

  • Build scalable container images and automate their build, test and publication workflows.
  • Create tools and tests for security compliance and cloud-native compatibility.
  • Improve Python- and Go-based image tooling through code and architecture review.
  • Document solutions, engage with the open-source community and support team mentoring.

Qualifications

  • Experience building container images, programming in Python and administering Linux systems or packages.
  • Hands-on CI/CD such as Jenkins, GitHub Actions or Concourse, plus GitOps workflows.
  • Proficiency with at least one container management or orchestration tool such as Docker or Kubernetes.
  • Ability to deliver quality software on time and explain technical tradeoffs clearly.

Technology in this role

  • Python: Python Kubernetes Docker .
  • Kubernetes: Python Kubernetes Docker .
  • Docker: Python Kubernetes Docker .
  • Linux: Python Kubernetes Docker .
  • Go: Improve Python- and Go-based image tooling through code and architecture .
  • GitHub Actions: Hands-on CI/CD such as Jenkins, GitHub Actions or Concourse, plus GitOps .
  • Jenkins: Hands-on CI/CD such as Jenkins, GitHub Actions or Concourse, plus GitOps .
  • CI/CD: Hands-on CI/CD such as Jenkins, GitHub Actions or Concourse, plus GitOps .

Role-specific candidate guide

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

Understanding the scope. This Software Engineer - Python - Container Images 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: “Canonical’s container image team builds images and the automation that tests and publishes them. The source lists remote locations in the Americas, APAC and EMEA, with company travel up to 15 percent of working time.” 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 software engineering 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 “Build scalable container images and automate their build, test and publication workflows.”; “Create tools and tests for security compliance and cloud-native compatibility.”; “Improve Python- and Go-based image tooling through code and architecture review.”. 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 “Experience building container images, programming in Python and administering Linux systems or packages.”; “Hands-on CI/CD such as Jenkins, GitHub Actions or Concourse, plus GitOps workflows.”; “Proficiency with at least one container management or orchestration tool such as Docker or Kubernetes.”. 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, Kubernetes, Docker, 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.

Benefits

  • We consider geographical location, experience, and performance in shaping compensation worldwide. We revisit compensation annually (and more often for graduates and associates) to ensure we recognize outstanding performance. In addition to base pay, we offer a performance-driven annual bonus or commission. We provide all team members with additional benefits which reflect our values and ideals. We balance our programs to meet local needs and ensure fairness globally.
  • Distributed work environment with twice-yearly team sprints in person
  • Personal learning and development budget of USD 2,000 per year
  • Team Member Assistance Program & Wellness Platform
  • Opportunity to travel to new locations to meet colleagues
  • Priority Pass and travel upgrades for long-haul company events

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

Related jobs