The **Principal DevOps Engineer** is a senior individual contributor (IC) responsible for designing, evolving, and governing the company’s cloud infrastructure and delivery platforms so engineering teams can ship software **safely, quickly, and reliably**. This role operates at “system level,” connecting product engineering needs with platform capabilities across environments (dev/test/stage/prod), and turning reliability, security, and scalability requirements into durable automation and standards.

The **Principal Cloud Native Engineer** is a senior individual contributor who designs, evolves, and governs the organization’s cloud-native engineering standards and enabling platforms (e.g., Kubernetes, service networking, CI/CD, observability, and infrastructure-as-code). This role accelerates product delivery by providing secure, reliable, scalable “paved roads” that reduce cognitive load for application teams while improving operational resilience and cost efficiency.

The Principal Cloud Engineer is a senior individual contributor (IC) who leads the design, evolution, and operational excellence of the organization’s cloud platforms and foundational infrastructure services. This role exists to ensure cloud environments are secure, reliable, cost-efficient, and scalable—enabling product engineering teams to ship features quickly without compromising resilience, compliance, or governance.

The Observability Engineer designs, builds, and continuously improves the telemetry, tooling, and practices that enable engineering teams to understand system behavior in production. The role establishes reliable signals (metrics, logs, traces, events), actionable alerting, and service-level indicators/objectives (SLIs/SLOs) so teams can detect, diagnose, and prevent customer-impacting issues efficiently.

The Network Engineer designs, implements, and operates the network connectivity that enables secure, reliable communication between applications, users, and infrastructure across data centers, cloud environments, and office/remote sites. This role ensures the company’s platforms and internal systems can move traffic predictably—at the required performance, availability, and security levels—while supporting rapid change through automation and disciplined operational practices.

The Network Automation Engineer designs, builds, and operates automation that makes enterprise network changes repeatable, testable, and safe at scale. This role exists to reduce manual configuration work, shorten change lead times, improve network reliability, and create auditable, version-controlled network operations aligned to modern engineering practices. The business value is improved uptime, faster delivery of infrastructure capabilities, reduced operational risk, and higher efficiency for NetOps and Cloud & Infrastructure teams. This is a **Current** role with accelerating importance as networks become more software-defined and integrated with CI/CD, IaC, and platform operating models.

A **Monitoring Engineer** designs, implements, and continuously improves the monitoring and observability capabilities that keep cloud and infrastructure platforms reliable, diagnosable, and cost-effective. The role ensures that teams can detect issues early, understand system behavior, respond to incidents efficiently, and measure reliability against agreed service objectives.

A **Linux Systems Engineer** designs, builds, operates, and continuously improves Linux-based infrastructure that supports product engineering and internal business systems. The role focuses on **reliability, security hardening, performance, automation, and lifecycle management** of Linux servers and services across on-prem, cloud, and hybrid environments.

The Lead Systems Reliability Engineer (Lead SRE) is responsible for ensuring the reliability, scalability, performance, and operational excellence of production systems and the cloud infrastructure that runs them. This role combines deep systems engineering expertise with a reliability-focused operating model: establishing service level objectives (SLOs), reducing toil through automation, and building resilient architectures and operational practices that enable rapid, safe change.

The **Lead Storage Engineer** designs, delivers, and operates resilient, secure, and high-performance storage platforms that underpin production applications, data platforms, and cloud infrastructure. This role serves as the technical authority for block, file, object, and backup/DR storage services across hybrid environments, balancing reliability, performance, cost, and compliance.

The **Lead SRE Engineer** is accountable for the reliability, availability, performance, and operational scalability of production systems, translating business expectations into measurable reliability targets (SLOs/SLIs) and building the engineering capabilities to meet them. This role leads the design and continuous improvement of observability, incident response, resilience, and automation practices across cloud and infrastructure platforms and the services running on them.

The **Lead Site Reliability Engineer (Lead SRE)** is a senior, hands-on technical leader responsible for ensuring the reliability, availability, performance, and operational excellence of customer-facing production systems. This role blends deep systems engineering with software engineering practices to reduce toil, improve observability, harden platforms, and embed reliability into the software delivery lifecycle.

The Lead Reliability Engineer is accountable for ensuring that the company’s production services meet defined reliability, performance, and availability targets while enabling rapid and safe delivery of product changes. This role leads reliability engineering practices across one or more critical service areas, balancing incident leadership and operational excellence with proactive engineering work that reduces risk and toil.

A **Lead Production Engineer** is a senior individual contributor who owns the reliability, operability, and day-2 excellence of production systems across cloud and infrastructure. The role ensures services are observable, scalable, secure-by-default, and resilient under real-world failure conditions, while reducing operational toil through automation and strong engineering practices.

The **Lead Observability Engineer** designs, implements, and governs the observability capabilities that enable reliable, secure, and high-performing cloud services at scale. This role ensures engineering teams can detect, understand, and resolve production issues quickly by building standardized telemetry (metrics, logs, traces, profiling) and turning it into actionable insights (SLOs, dashboards, alerts, incident context).

The Lead Network Engineer is the technical lead accountable for designing, scaling, and operating resilient, secure, and observable network connectivity across cloud and on-prem environments that underpin software delivery and digital services. This role owns network architecture decisions within defined guardrails, drives automation and reliability practices for network operations, and mentors other engineers while partnering closely with Security, SRE, Platform Engineering, and Application teams.

The Lead Network Automation Engineer designs, builds, and operationalizes automation for network and cloud connectivity across enterprise environments—turning traditionally manual, ticket-driven networking tasks into reliable, version-controlled, testable software delivery. The role exists to increase network delivery speed and safety (changes, provisioning, upgrades), reduce outages caused by configuration drift and human error, and create scalable network operations that keep pace with product and platform growth.

The **Lead Monitoring Engineer** is responsible for designing, operating, and continuously improving the organization’s monitoring and observability capabilities across cloud infrastructure and production applications. The role ensures that engineering teams can reliably detect, diagnose, and resolve issues using high-quality telemetry (metrics, logs, traces, events) and actionable alerting aligned to service health and business impact.

The **Lead Linux Systems Engineer** is the technical lead accountable for designing, operating, and continuously improving Linux-based infrastructure services that underpin production workloads across cloud and/or data center environments. This role ensures Linux platforms are secure, resilient, performant, and automatable—enabling product engineering teams to ship reliably while meeting availability, compliance, and cost objectives.

The Lead Kubernetes Engineer is the technical lead responsible for designing, operating, securing, and continuously improving the organization’s Kubernetes platform(s) used to run production services. This role ensures clusters are reliable, scalable, cost-efficient, and standardized so that product and engineering teams can ship software quickly without compromising availability or security.

The **Lead Infrastructure Engineer** designs, builds, and operates the core infrastructure platforms that enable reliable, secure, and scalable delivery of software services. This role provides senior technical leadership across cloud, compute, networking, storage, observability, and infrastructure automation—ensuring that engineering teams can ship product safely and efficiently.

The Lead DevOps Engineer is a senior, hands-on technical leader responsible for designing, building, and operating reliable delivery and runtime platforms that enable product teams to ship software safely, quickly, and repeatedly. This role bridges software engineering and cloud/infrastructure operations by standardizing CI/CD, infrastructure as code, observability, release engineering, and operational practices across multiple services and teams.

The **Lead Cloud Native Engineer** is a senior individual contributor and technical leader within the **Cloud & Infrastructure** department, responsible for designing, building, and evolving the company’s cloud-native platform capabilities (containers, Kubernetes, CI/CD enablement, IaC, observability, and runtime security) so product engineering teams can ship reliably and securely at scale. The role balances hands-on engineering with architecture, standards, and enablement—turning platform strategy into operational reality.

The **Lead Cloud Engineer** is a senior, hands-on technical leader responsible for designing, building, and continuously improving the cloud infrastructure, platform services, and operational capabilities that enable software teams to deliver reliable, secure, and scalable products. This role typically blends deep engineering execution with architecture-level decision-making, cross-team influence, and operational ownership.

The Kubernetes Engineer is an individual contributor in the Cloud & Infrastructure department responsible for building, operating, securing, and continuously improving Kubernetes platforms that run production workloads. This role ensures clusters are reliable, scalable, cost-efficient, and developer-friendly, with strong guardrails for security, compliance, and operational excellence.

The **Junior Systems Reliability Engineer (Junior SRE)** is an early-career reliability-focused engineer responsible for improving the availability, performance, and operational health of production systems through disciplined incident response, observability, automation, and continuous improvement. This role works within the **Cloud & Infrastructure** organization to reduce toil, strengthen operational practices, and help engineering teams ship changes safely.

The **Junior Storage Engineer** is an early-career infrastructure engineer responsible for provisioning, operating, and supporting enterprise storage services across on-prem and/or cloud environments. The role focuses on reliable day-to-day execution—handling service requests, participating in incident response, monitoring capacity/performance, and maintaining runbooks and automation under guidance of senior engineers.

A Junior Site Reliability Engineer (SRE) helps ensure that customer-facing services and internal platforms are reliable, observable, performant, and cost-efficient. This role focuses on learning and applying SRE practices—monitoring, incident response, automation, and production hygiene—under the guidance of more senior SREs and reliability leadership.

The **Junior Reliability Engineer** helps keep customer-facing services and internal platforms **available, performant, and recoverable** by supporting observability, incident response, and reliability improvements across cloud infrastructure and production systems. This role focuses on **executing reliability practices consistently**—monitoring, alert tuning, runbook upkeep, change hygiene, and automation—under the guidance of senior Reliability Engineers / SREs.

The **Junior Production Engineer** helps keep customer-facing systems reliable, observable, secure, and cost-effective in day-to-day operation. The role focuses on operational execution—monitoring, incident response support, runbook usage and improvement, small-to-medium automation tasks, and safe change management—under the guidance of senior Production Engineers/SREs.