2

Remote Gitops Engineer Jobs in Utah (NOW HIRING)

$56.50 - $75.25/hr

AWS EKS clusters managed as code, GitOps-driven delivery with the Argo suite, operator-managed data ... remote state on S3. * strong> CI/CD & automation: pipeline design in GitHub Actions or GitLab CI ...

Remote Gitops Engineer information

What is a Remote GitOps Engineer?

A Remote GitOps Engineer is a software professional who manages and automates infrastructure and application deployments using GitOps principles, typically while working from a remote location. GitOps is a methodology that uses Git repositories as the single source of truth for declarative infrastructure and applications. The engineer is responsible for implementing, maintaining, and troubleshooting continuous deployment pipelines, ensuring that changes are version-controlled and auditable. They often work with tools like Kubernetes, ArgoCD, and Flux, collaborating with development and operations teams to streamline DevOps workflows.

What are the key skills and qualifications needed to thrive as a Remote GitOps Engineer?

To thrive as a Remote GitOps Engineer, you need a strong background in software development, infrastructure-as-code, and experience with cloud platforms, often supported by a degree in computer science or a related field. Familiarity with tools like Kubernetes, Docker, Terraform, Git, and CI/CD systems, along with certifications such as CKA or AWS Certified DevOps Engineer, is highly valuable. Excellent problem-solving, communication, and self-motivation are key soft skills for collaborating remotely and managing complex workflows. These skills ensure efficient, reliable, and scalable deployment pipelines, enabling teams to deliver software securely and quickly in distributed environments.

How does a Remote GitOps Engineer typically collaborate with development and operations teams to ensure smooth deployment processes?

As a Remote GitOps Engineer, you'll frequently collaborate with both development and operations teams through tools like Git, Slack, and video conferencing. Your main responsibility is to ensure deployment pipelines are automated and transparent, often acting as a bridge between developers writing code and operations teams managing infrastructure. Regular communication and documentation are crucial to resolve issues quickly and keep everyone aligned. You will also participate in code reviews, incident response, and infrastructure improvements, ensuring deployments are reliable and reproducible across distributed teams.

What is the difference between Remote Gitops Engineer vs Cloud Engineer?

AspectRemote Gitops EngineerCloud Engineer
Required CredentialsCertifications like Kubernetes, Docker, GitOps toolsCloud platform certifications (AWS, Azure, GCP), Linux skills
Work EnvironmentRemote, DevOps teams, CI/CD pipelinesRemote or on-site, cloud infrastructure management
Industry UsageDevOps, software development, automationCloud services, infrastructure, application deployment
Search & Comparison IntentFocus on automation, deployment, CI/CDFocus on cloud infrastructure, architecture

The Remote Gitops Engineer specializes in automating deployment processes using GitOps tools and practices, primarily working remotely within DevOps teams. In contrast, a Cloud Engineer manages cloud infrastructure and services across platforms like AWS, Azure, or GCP. While both roles require cloud and automation skills, the Gitops Engineer emphasizes continuous deployment and automation pipelines, whereas the Cloud Engineer focuses on infrastructure setup and management.

What job categories do people searching Remote Gitops Engineer jobs in Utah look for? The top searched job categories for Remote Gitops Engineer jobs in Utah are:
What cities in Utah are hiring for Remote Gitops Engineer jobs? Cities in Utah with the most Remote Gitops Engineer job openings:

$56.50 - $75.25/hr

Full-time

Medical

Posted 13 days ago


Job description

Cloud Platform Engineer (AWS / EKS / Terraform)
Team: Infrastructure · Reports to Head of Infrastructure
About the role
You will build and operate TookiTaki's cloud platform: AWS EKS clusters managed as code, GitOps-driven delivery with the Argo suite, operator-managed data services running on Kubernetes, and a Terraform-based self-service layer that lets application teams request infrastructure through reviewed YAML instead of tickets. The job is platform engineering, not click-ops — everything ships through version control, automated pipelines, and policy gates.
Requirements
Education

  • R
  • equired: Bachelor's degree in Computer Science, Engineering, or a related field — or equivalent practical experience.
  • P
  • referred: Relevant certifications over a Master's — CKA (Certified Kubernetes Administrator), HashiCorp Terraform Associate, AWS Solutions Architect Associate or higher.
    Experience
  • 3
  • –5+ years in cloud, platform, or DevOps engineering.
  • P
  • roven track record running production Kubernetes on a managed cloud (EKS strongly preferred), including stateful workloads.
  • E
  • xperience operating infrastructure entirely through Infrastructure as Code — no console-driven change management.
    Technical expertise
  • <
  • strong>Kubernetes / EKS: cluster lifecycle and upgrades, autoscaling (Karpenter, KEDA, VPA), ingress and load balancing, IRSA/Pod Identity, core add-ons (cert-manager, external-dns, CoreDNS, node-local-dns).
  • <
  • strong>GitOps / Argo: ArgoCD for platform and application delivery (app-of-apps, Helm chart authoring, sync and rollback strategies), Argo Rollouts for progressive delivery, Argo Workflows/Events for automation.
  • <
  • strong>Databases and stateful services on Kubernetes: deploying and operating databases via Kubernetes operators — PostgreSQL and MySQL (Percona operators), ScyllaDB, Elasticsearch, Valkey/Redis, Kafka (Strimzi) — plus AWS RDS/Aurora where managed services fit better; backup/restore, upgrades, and capacity management for stateful workloads.
  • <
  • strong>Terraform: authoring reusable, versioned, tested modules (not just consuming them) — variable/output interface design, `terraform test`, semantic versioning, remote state on S3.
  • <
  • strong>CI/CD & automation: pipeline design in GitHub Actions or GitLab CI; plan/apply automation with Atlantis; policy-as-code gates (OPA/Conftest, checkov, tflint); pre-merge validation and drift detection.
  • <
  • strong>AWS core services: VPC and network design, Route 53, IAM (least-privilege roles and policies), S3, RDS/Aurora.
  • <
  • strong>Observability: Datadog, OpenTelemetry (collector and kube-stack), Grafana; alerting hygiene with low false-positive rates; log and event pipelines.
  • <
  • strong>Programming: solid scripting/tooling ability in Python or Go — enough to build renderers, validators, and pipeline tooling, not just glue scripts.
  • <
  • strong>Nice to have: data platform tooling (Airflow, Spark on Kubernetes, Temporal, StarRocks), identity and SSO (Keycloak, Dex, oauth2-proxy), load testing with k6, FinOps practices (tagging standards, cost allocation, rightsizing).
    Soft skills
  • S
  • trong problem-solving and analytical abilities; comfortable debugging across the stack (DNS → LB → cluster → workload → database).
  • C
  • lear written communication — design docs, runbooks, and PR descriptions are first-class deliverables here.
  • C
  • ollaborative mindset: infrastructure changes ship through peer review, and platform decisions are made with (not for) application teams.
    Key competencies
  • <
  • strong>Platform thinking: design paved roads that make the secure, cost-efficient path the easy path for application teams.
  • <
  • strong>Automation-first: if a task is done twice manually, the third time is a pipeline.
  • <
  • strong>Ownership: own services end to end — provisioning, upgrades, incidents, cost, and documentation.
  • <
  • strong>Cost awareness: treat cloud spend as an engineering metric; tag, measure, and optimize continuously.
  • <
  • strong>Adaptability: comfortable in a fast-moving environment where the platform itself is under active development.
    Success metrics (first 6–12 months)
  • A
  • pplication teams provision standard infrastructure through the self-service platform with no manual Terraform written by requesters.
  • E
  • KS cluster and node-group upgrades executed as routine, zero-downtime operations via blue/green rollout.
  • O
  • perator-managed data services (PostgreSQL, Kafka, Elasticsearch, etc.) run with tested backup/restore and rehearsed upgrade procedures.
  • 1
  • 00% of infrastructure changes delivered through reviewed, policy-gated pipelines — zero out-of-band console changes.
  • D
  • eployment lead time for platform changes reduced measurably (target: same-day merge-to-production for routine changes).
  • C
  • ost visibility established via tagging and dashboards, with identified savings executed (rightsizing, autoscaling, storage tiering).
  • A
  • ctionable alerting: on-call pages correspond to real incidents; false-positive alerts trend toward zero.
  • M
  • ean time to recovery for platform incidents under 30 minutes.
    Benefits
  • <
  • strong>Competitive salary aligned with industry standards and experience.
  • <
  • strong>Professional development: certification support (CKA, AWS, Terraform) and training across cloud, platform, and data engineering.
  • <
  • strong>Comprehensive benefits: health insurance and flexible working options.
  • <
  • strong>Growth opportunities: career progression within TookiTaki's expanding infrastructure and platform organization.

    Employment Type: FULL_TIME