The **QA Analyst** is an individual contributor within **Quality Engineering** responsible for validating that software products meet defined requirements, are fit for purpose, and perform reliably in real-world conditions. The role focuses on planning and executing testing, identifying defects early, improving test coverage, and providing clear quality signals to enable safe, predictable releases.
The Principal QA Analyst is a senior individual contributor in Quality Engineering who owns end-to-end quality outcomes for one or more critical product areas, with particular emphasis on test strategy, risk-based coverage, and quality signals across the SDLC. This role designs and governs pragmatic test approaches that improve customer outcomes (fewer defects, faster recovery, predictable releases) while enabling engineering teams to deliver at speed.
The **Lead QA Analyst** is a senior quality engineering practitioner who ensures software releases meet defined standards for **functional correctness, reliability, usability, and risk posture**. This role leads testing strategy and execution across one or more product areas, balancing hands-on test analysis with team leadership, cross-functional coordination, and quality governance.
The Junior QA Analyst supports the Quality Engineering function by executing test activities that validate software changes before release, helping the organization deliver reliable, user-ready products. This role focuses on hands-on testing (primarily manual with foundational automation exposure), clear defect reporting, and tight collaboration with engineers and product teams to ensure requirements are met and regressions are prevented.
The **Associate QA Analyst** is an early-career quality professional responsible for validating software changes through structured testing, clear defect reporting, and disciplined follow-through. The role supports the delivery of reliable, user-ready product increments by executing test cases, identifying risks, and helping the team maintain quality standards across releases.
The Lead FinOps Analyst is a senior individual contributor (and often a functional lead) within the Cloud Economics function, accountable for translating cloud usage and billing data into actionable financial and engineering decisions. The role builds and runs the operating mechanisms that make cloud spend measurable, attributable, forecastable, and optimizable—without slowing delivery.
The **Cost Optimization Analyst** is an individual contributor within **Cloud Economics** responsible for identifying, quantifying, prioritizing, and driving actions that reduce cloud and adjacent technology costs without degrading reliability, security, or delivery velocity. The role blends data analysis, financial acumen, and cloud platform fundamentals to translate usage and engineering decisions into measurable unit-cost and efficiency improvements.
The Senior Observability Analyst is a senior individual contributor within the Cloud & Infrastructure organization responsible for turning telemetry (metrics, logs, traces, events) into actionable operational insight. This role designs and continuously improves the company’s observability practices so that engineering and operations teams can detect, diagnose, and prevent service degradation with speed and confidence.
The Senior Capacity Planning Analyst ensures that cloud and infrastructure platforms have the right amount of compute, storage, network, and supporting service capacity to meet product demand—without chronic overprovisioning or capacity-related outages. This role translates business and engineering signals into quantitative forecasts, actionable capacity plans, and prioritized investments across cloud spend, reservations/commitments, and infrastructure roadmaps.
The **Principal Observability Analyst** is a senior individual contributor in **Cloud & Infrastructure** responsible for designing, governing, and continuously improving the organization’s observability capability—turning telemetry (metrics, logs, traces, events, profiles) into reliable detection, faster diagnosis, and measurable service health outcomes. This role acts as the analytical authority for how the enterprise measures reliability and performance, and ensures observability investments translate into operational resilience and product experience improvements.
The Observability Analyst is an individual contributor in the Cloud & Infrastructure department responsible for turning telemetry (metrics, logs, traces, events, and dependency signals) into actionable insights that improve service reliability, performance, and operational efficiency. The role focuses on operational analysis, detection quality, dashboarding standards, alert tuning, and incident learning—bridging the gap between platform tooling and the teams who run production services.
The **Lead Observability Analyst** is a senior, hands-on analytics and operational leader within **Cloud & Infrastructure** responsible for ensuring that engineering and operations teams can *see*, *understand*, and *act on* the health and performance of production systems. This role turns telemetry (metrics, logs, traces, events, and profiles) into actionable insights, reliable alerting, and measurable service outcomes (SLOs/SLIs) that reduce downtime, accelerate incident resolution, and improve customer experience.
The **Junior Observability Analyst** supports the reliability and performance of cloud-based systems by monitoring telemetry (metrics, logs, traces), triaging alerts, and producing clear operational insights for engineering and infrastructure teams. The role focuses on **detecting issues early, reducing noise in monitoring, and improving the quality and usability of dashboards and alerting**, under the guidance of senior observability, SRE, or platform engineering leaders.
The **Associate Observability Analyst** is an early-career role within **Cloud & Infrastructure** responsible for helping the organization detect, understand, and respond to system behavior through **metrics, logs, traces, and events**. The role focuses on operational visibility: building and maintaining dashboards, improving alert quality, supporting incident triage, and ensuring teams can reliably answer “what’s happening?” and “why?” across cloud services and applications.
The **Associate Responsible AI Analyst** helps ensure that AI-enabled products and internal ML systems are designed, evaluated, documented, and monitored in ways that are **fair, reliable, safe, privacy-preserving, secure, transparent, and accountable**. The role supports Responsible AI (RAI) governance by performing structured assessments, maintaining evidence artifacts, executing repeatable evaluation workflows, and partnering with engineering and product teams to reduce user and business risk.
The Scrum Master is a servant-leader and delivery facilitator who enables one or more cross-functional product teams to consistently deliver valuable software increments using Scrum and complementary Agile practices. This role exists in software and IT organizations to increase delivery predictability, improve flow efficiency, strengthen team health, and remove organizational impediments that slow down execution.
The **Release Train Engineer (RTE)** is the servant-leader and chief facilitator for an **Agile Release Train (ART)**—a long-lived, cross-functional “team of teams” that delivers value through a shared cadence and synchronized planning and execution. The RTE enables predictable delivery outcomes by orchestrating program-level (and often portfolio-adjacent) planning, execution, dependency management, and continuous improvement across multiple Agile teams.
The Agile Coach enables teams and leaders to improve delivery outcomes by strengthening Agile ways of working, accelerating learning loops, and embedding continuous improvement across product and engineering. The role focuses on coaching people, refining delivery systems, and making work visible and measurable so teams can reliably deliver valuable software with sustainable pace.
The **Junior Identity Administrator** supports the secure, reliable, and auditable operation of the company’s identity and access management (IAM) services across employees, contractors, and (where applicable) customer or partner identities. The role focuses on executing standardized access processes (joiner–mover–leaver), maintaining identity directory hygiene, supporting single sign-on (SSO) and multi-factor authentication (MFA) operations, and ensuring access requests and approvals are handled accurately and on time.
The **Senior Linux Administrator** is a senior individual contributor within **Enterprise IT** responsible for the reliability, security, and performance of Linux-based infrastructure that underpins internal services and business-critical production platforms. The role designs and operates standardized Linux environments, automates repeatable operations, and leads complex incident resolution while ensuring adherence to enterprise security and compliance controls.
The Senior Kubernetes Administrator is a senior individual contributor responsible for the reliability, security, scalability, and operability of Kubernetes clusters used by enterprise engineering teams to run production workloads. This role designs and runs the Kubernetes platform “as a product” within Enterprise IT—ensuring clusters are correctly configured, monitored, upgraded, and governed while enabling developers to ship safely and quickly.
The **Principal Virtualization Administrator** is the senior-most individual contributor accountable for the reliability, performance, security, and lifecycle of the organization’s virtualization platforms that underpin critical enterprise workloads. This role ensures virtualization is engineered and operated as a resilient product/platform—standardized, automated, cost-effective, and audit-ready—while enabling application teams to consume compute, storage, and network capacity with predictable service levels.
The **Principal Systems Administrator** is the senior-most individual contributor responsible for the reliability, security, and operational excellence of enterprise systems that underpin employee productivity and internal service delivery (identity, endpoints, core infrastructure, virtualization, server OS platforms, foundational cloud services, and adjacent operational tooling). This role acts as a technical authority for systems administration practices, sets standards for build/patch/configuration, and drives automation to reduce operational toil while improving uptime and audit readiness.
The Principal Linux Administrator is the enterprise technical authority for Linux platforms within Enterprise IT, accountable for the reliability, security, standardization, and automation of Linux-based infrastructure that underpins business-critical applications and services. This is a senior individual contributor (IC) role with broad decision influence, responsible for setting Linux engineering standards, guiding platform roadmaps, and solving high-severity or high-complexity problems that span teams and domains.
The **Principal Kubernetes Administrator** is the senior individual-contributor authority responsible for the reliability, security, scalability, and operational excellence of Kubernetes platforms used across Enterprise IT. This role owns the “last mile” of Kubernetes production readiness—ensuring clusters, add-ons, networking, storage, identity, and operational processes meet enterprise standards while enabling product and application teams to ship safely and quickly.
The Linux Administrator is responsible for the reliability, security, and day-to-day operational health of Linux-based infrastructure that supports enterprise applications, internal developer platforms, and shared IT services. This role ensures Linux systems are consistently configured, patched, monitored, backed up, and recoverable—while meeting organizational standards for availability, performance, and compliance.
The **Lead Linux Administrator** owns the reliability, security, and operational excellence of an organization’s Linux server estate across on-premises and cloud environments. This role provides senior technical stewardship for core Linux platforms (compute, storage, identity integration, patching, monitoring, backups, and automation) while coordinating day-to-day operations, escalations, and continuous improvement across the Linux administration function.
The Lead Kubernetes Administrator is accountable for the reliability, security, and operational excellence of the organization’s Kubernetes platforms used to run production workloads across enterprise IT environments. This role exists to ensure Kubernetes clusters and supporting services (networking, storage, ingress, identity, observability, and backup/DR) are engineered and operated to meet uptime, performance, compliance, and cost targets while enabling application teams to ship safely and quickly.
The Kubernetes Administrator is responsible for the reliability, security, and operational excellence of Kubernetes clusters that run business-critical applications in an Enterprise IT environment. This role ensures clusters are correctly provisioned, upgraded, monitored, and governed so that internal engineering teams and platform consumers can deploy and operate workloads safely and efficiently.
The **Junior Linux Administrator** supports the availability, security, and day-to-day operability of Linux-based infrastructure used by an enterprise IT organization to run internal services and business-critical applications. The role focuses on executing standard administration tasks, responding to tickets and alerts, performing routine maintenance, and following established runbooks under the guidance of senior administrators and SRE/Platform teams.