Senior DevOps Engineer

This is infrastructure work at the point of consequence. You will move between architecture, implementation, incidents, and customer teams without throwing the hard part over a wall.

WEBRIOT gets called when infrastructure has become a constraint. Sometimes the job is a platform build. Sometimes it is a failing delivery path, an edge fleet that cannot recover cleanly, or an AI workload that escaped the prototype without operational controls.

Your job is to find the real failure mode, make the tradeoffs visible, and ship the smallest durable system that changes the outcome. You will write code, shape architecture, improve operations, and teach the customer how to own what remains.

Make production less surprising and the team less dependent on outside help.

The work changes with the system. The standard does not.

• Design and implement platform capabilities across cloud, Kubernetes, edge, and AI workloads.
• Trace delivery and reliability failures through code, infrastructure, telemetry, and team boundaries.
• Build automation, deployment paths, observability, recovery controls, and operational documentation.
• Lead technical conversations with engineers and executives without hiding tradeoffs behind jargon.
• Pair with customer teams so ownership transfers with the system instead of after it.

We care more about production judgment than a perfect inventory of vendor badges. You should be able to explain what you changed, why it mattered, and what the system taught you after deployment.

• Deep experience operating production infrastructure and debugging failure across multiple layers.
• Strong Infrastructure as Code, CI/CD, Linux, networking, containers, and Kubernetes fundamentals.
• The ability to write maintainable software or automation in at least one general-purpose language.
• Clear technical writing and direct communication under uncertainty.
• A record of simplifying systems, improving recovery, or materially changing delivery outcomes.

Your first 90 days should leave evidence in the system and in the team operating it.

• 01
  
  Days 01-30 / Read the system

  Understand the architecture, delivery path, operating signals, and the humans carrying the risk.

• 02
  
  Days 31-60 / Change the constraint

  Ship a material improvement with measurable evidence and an explicit rollback path.

• 03
  
  Days 61-90 / Transfer ownership

  Leave the customer able to operate, extend, and challenge what was built.

Tools are context. Outcomes are the job. You should be fluent in modern infrastructure patterns and able to learn unfamiliar systems quickly.

Kubernetes Terraform / Open Tofu AWS / Azure / GCP Git Hub Actions / Git Lab CI Argo CD / Flux Open Telemetry Prometheus / Grafana Go / Python / Type Script

Real systems, direct technical conversation, and a working session built around judgment instead of trivia.