Skip to main content

DevOps / SRE Engineer (Kubernetes & Observability)

Posted 9 days ago

argyll infotechSeattle (WA)

SENIORITY

Senior

Apply (opens in a new tab)

About the role

Job Description: DevOps / SRE Engineer (Kubernetes & Observability)
About the Role: We are seeking an experienced DevOps / SRE Engineer with a strong background in migration, automation, and Kubernetes environments. In this role, you will play a key part in providing operational support for our telemetry and observability stacks, ensuring high availability, performance, and seamless monitoring across our infrastructure.
Duration: 12 Months Contract
Location: Seattle, WA 98109 (Hybrid)
Experience Required:
  • 12+ YearsKey Responsibilities
  • Provide robust operational support for enterprise telemetry and observability stacks within a Kubernetes environment.
  • Design, develop, and maintain Python scripts and automation tools to streamline monitoring, support, and operational workflows.
  • Configure, monitor, and troubleshoot core observability platforms including Grafana, Prometheus, Loki, and Tempo
  • Collaborate closely with DevOps, SRE, and cross-functional software development teams to guarantee optimal system performance and deep observability.
  • Manage containerized workloads using Docker and maintain efficient CI/CD pipelines
  • Utilize Git-based version control workflows within a Linux-based operating environment.
  • Required Skills & Qualifications
Experience: 5+ years of professional experience in DevOps, Site Reliability Engineering (SRE), and infrastructure migrations. Core Technologies: Strong hands-on expertise in Kubernetes (deployment, configuration, and advanced troubleshooting).Proficiency in Python for scripting, automation, and internal tool development. Solid working knowledge of AWS cloud environments. Observability: Hands-on configuration and troubleshooting experience with Prometheus Grafana, and log/trace aggregators such as Loki Environments & Tools: Containerization via Docker, Linux administration, and Git-based workflows.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this