wagey.ggwagey.ggv1.0-4558734-20-Apr
Browse Tech JobsCompaniesFeaturesPricingFAQs
Log InGet Started Free
Jobs/Chef Role/ecoATM | Gazelle - Sr. DevOps Engineer
Pro members applied to this job 36 hours before you saw itGet Pro ›
ecoATM | Gazelle

ecoATM | Gazelle - Sr. DevOps Engineer

Remote - USA$302k+3d ago
RemoteSeniorNACloud ComputingLogisticsChefDevOps EngineerBashPythonAWSAzureGCPTerraformDockerLinuxKubernetesJenkinsPuppetChefAnsibleNode.js.NETPulumiMoveCross-functional Collaboration

Upload My Resume

Drop here or click to browse · PDF, DOCX, DOC, RTF, TXT

Apply in One Click

Requirements

• 8–12+ years experience in DevOps, SRE, or platform engineering • Strong experience with: • Cloud platforms (AWS, GCP, Azure) • Infrastructure as Code (Terraform, CloudFormation, etc.) • CI/CD systems (GitHub Actions, GitLab CI, Jenkins, ArgoCD) • Containers and orchestration (Docker, Kubernetes) • Windows and Linux Operating Systems • Configuration Management Tooling (Chef, Ansible, Salt, Puppet) • Proficiency in scripting or programming (Python, Nodejs, Bash, etc.) • Deep understanding of distributed systems and cloud architecture • Experience operating platforms at scale (100+ services, high deployment frequency) • Experience building internal developer platforms (IDP) • Knowledge of GitOps and modern deployment patterns • Strong understanding of networking, security, and observability systems • Business Travel (How much will you travel?) • Location (Where will you be working?) • Remote within the United States

Responsibilities

• Platform & Infrastructure Engineering: • Design and operate scalable, secure cloud infrastructure (AWS, GCP, Azure) • Build and maintain Infrastructure as Code (Terraform, Pulumi, CloudFormation) • Own runtime platforms (Kubernetes, serverless, container platforms) • Containerization of .NET and Windows workloads • Evolve system architecture, scaling strategies, and failure handling to align with distributed, elastic environments • Shift mindset from static provisioning to dynamic, API-driven infrastructure • What success looks like: A platform that behaves cloud-native by design, not just cloud-hosted • What success looks like: • CI/CD & Release Engineering: • Design and implement robust CI/CD pipelines for multiple services and teams • Standardize build, test, and deployment workflows • Enable safe, fast releases through automation, testing, and progressive delivery strategies • Improve deployment frequency while reducing change failure rates • Move from primarily rolling deployments to more advanced deployment strategies • Build platform capabilities that make safe deployment strategies the default for engineering teams • What success looks like: Frequent, low-risk deployments with measurable reductions in change failure rate • Automation & Developer Productivity: • Eliminate manual processes through automation and self-service tooling • Build internal developer tooling that reduce friction and cognitive load • Improve developer workflows across build, test, deploy, and operate phases • Drive adoption of platform capabilities across engineering teams • What success looks like: A streamlined platform with fewer tools, clearer patterns, and lower cognitive load for engineers • Security &DevSecOps: • Integrate security into CI/CD pipelines and infrastructure workflows • Implement identity, secrets management, and secure supply chain practices • Ensure compliance with standards (SOC2, HIPAA, etc. where applicable) • Partner with security teams to embed controls into platform tooling • Redefine RBAC strategies across infrastructure, CI/CD, and Kubernetes environments • What success looks like: A secure minimal permission setup with clear ownership and auditing capability that drives responsiveness to unexpected changes. • Technical Leadership: • Act as a technical authority across DevOps, SRE, and platform engineering • Drive architectural decisions and long-term technical strategy • Mentor engineers and influence best practices across teams • Lead cross-team initiatives and platform adoption efforts • What success looks like: Clear, consistent architectural direction that reduces ambiguity and rework, with engineering teams independently making high-quality decisions aligned to platform standards. Measurable uplift in engineering quality, with fewer escalations, stronger design reviews, and increased delivery confidence across teams. • Cross-Functional Collaboration: • Partner with product engineering to improve delivery workflows • Work with SRE, security, and data teams to align platform capabilities • Collaborate with leadership on roadmap, priorities, and tradeoffs • Influence engineering culture toward automation and reliability • What success looks like: Strong alignment across engineering, security, and leadership, resulting in faster delivery with fewer friction points. Platform capabilities are widely adopted because they solve real problems, not because they are mandated. Cross-team initiatives execute predictably, with clear ownership, minimal duplication, and shared accountability for outcomes.

Benefits

• This position may also be eligible for short-term and long-term incentives based on individual and company performance. • Base pay offered may vary depending on job-related knowledge, skills, and experience. This information is provided per CA SB 1162 (“CA Pay Transparency Law”). Base pay information is based on market location. Learn more about ecoATM benefits here. • This job description is not intended to be all-inclusive. Employee may perform other related duties as assigned to meet the ongoing needs of the organization.

Get Started Free

No credit card. Takes 10 seconds.

Privacy·Terms··Contact·FAQ·Wagey on X
Loading...