Search Results for "Jenkins"

The **Principal SRE Engineer** is a senior individual contributor (IC) responsible for shaping, scaling, and continuously improving the reliability, performance, and operational excellence of cloud-hosted products and core infrastructure. This role drives enterprise-grade Site Reliability Engineering practices—particularly SLO-based reliability management, resilient architectures, high-quality observability, and automated operations—across multiple teams and services.

The Principal Site Reliability Engineer (SRE) is a senior individual contributor responsible for ensuring that critical cloud services are reliable, scalable, secure, and cost-efficient, while enabling rapid product delivery. This role designs and governs reliability engineering practices (SLOs/SLIs, error budgets, incident management, observability, resilience testing) and drives cross-team execution of reliability improvements across the platform.

The **Principal Reliability Engineer** is a senior individual-contributor (IC) role responsible for **setting reliability strategy and technical direction** across critical cloud infrastructure and production services, while directly improving **availability, latency, scalability, incident response maturity, and operational efficiency**. This role exists to ensure that engineering teams can ship changes quickly **without compromising production stability**, and that reliability is designed, measured, and governed as a first-class product attribute.

The Principal Production Engineer is a senior individual contributor in the Cloud & Infrastructure organization responsible for ensuring that customer-facing and internal production systems are reliable, scalable, secure, and cost-efficient. This role blends deep systems engineering with operational excellence and influences architecture and engineering practices across multiple teams and services.

The Principal Observability Engineer is a senior individual contributor (IC) in the Cloud & Infrastructure organization accountable for the end-to-end observability strategy, platform architecture, and operational outcomes across distributed systems. This role builds and evolves the telemetry foundations (metrics, logs, traces, profiling, synthetics) that enable engineering teams to detect, understand, and remediate reliability, performance, and customer-impacting issues quickly and safely.

The Principal Network Engineer is the senior-most individual contributor (IC) network specialist responsible for designing, governing, and continuously improving the network foundations that power reliable, secure, and scalable cloud and infrastructure services. This role sets technical direction for enterprise networking across data center, cloud, and edge environments, while partnering closely with platform, security, SRE, and application engineering to ensure the network enables product delivery—not blocks it.

The **Principal Network Automation Engineer** is a senior individual contributor responsible for designing, delivering, and operationalizing network automation capabilities that improve reliability, security, speed, and consistency across cloud and infrastructure networks. This role builds the automation “platform” and engineering practices that enable network changes to be delivered safely through code, testing, and CI/CD—at enterprise scale.

The **Principal Monitoring Engineer** is the technical authority responsible for designing, standardizing, and continuously improving the organization’s monitoring and observability capabilities across cloud infrastructure, platforms, and production services. This role ensures that engineering teams can detect, diagnose, and resolve issues quickly through high-quality telemetry (metrics, logs, traces, events) and reliable alerting, aligned to customer-impacting outcomes and SLOs.

The **Principal Linux Systems Engineer** is the senior-most (or among the senior-most) individual contributor responsible for the reliability, security, performance, and lifecycle of Linux-based infrastructure that underpins production services. This role designs and governs the Linux platform “golden path” across bare metal, virtualized, and cloud environments, ensuring systems are automated, observable, compliant, and cost-effective at scale.

The Principal Kubernetes Engineer is a senior individual contributor (IC) responsible for designing, evolving, and governing the organization’s Kubernetes platform(s) to deliver secure, reliable, scalable, and cost-effective container orchestration capabilities. This role combines deep Kubernetes expertise with platform engineering practices, reliability engineering, and a strong operating-model mindset to enable product teams to ship faster with fewer incidents.

The Principal Infrastructure Engineer is a senior individual contributor (IC) responsible for designing, evolving, and governing the company’s cloud and infrastructure foundations so product engineering teams can deliver secure, reliable, scalable software quickly. This role owns high-impact technical decisions across compute, networking, storage, identity, observability, and automation, and drives the infrastructure operating model (standards, patterns, self-service, and reliability practices) across multiple teams.

The **Principal Engineer – Cloud and Reliability** is the senior individual-contributor authority responsible for designing, evolving, and governing the cloud platform and reliability practices that keep production services **available, performant, secure, and cost-effective at scale**. This role blends deep cloud engineering with SRE-style reliability leadership, establishing technical direction across teams while remaining hands-on in critical systems, incidents, and platform improvements.

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 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.