Search Results for "Jenkins"

A **Staff Release Engineer** is a senior individual contributor in the **Developer Platform** organization responsible for designing, scaling, and governing the systems and practices that reliably move software from source to production. This role ensures releases are **repeatable, secure, observable, and low-risk**, enabling product and service teams to ship faster without compromising quality or compliance.

The **Staff Developer Experience Engineer** is a senior individual contributor in the Developer Platform organization responsible for materially improving the productivity, reliability, and satisfaction of software engineers by building and evolving internal platforms, tooling, and “golden paths” that make software delivery faster, safer, and more repeatable. This role blends deep software engineering with platform thinking, operational excellence, and a strong internal customer orientation.

The Staff Deployment Engineer is a senior individual contributor in the Developer Platform organization responsible for designing, standardizing, and operating the systems and practices that reliably move software from source control to production. This role focuses on deployment automation, release orchestration, environment strategy, progressive delivery, and reliability controls—enabling product teams to ship frequently, safely, and compliantly with minimal friction.

A **Staff CI/CD Engineer** is a senior individual contributor in the **Developer Platform** organization responsible for designing, evolving, and operating the continuous integration and continuous delivery/deployment (CI/CD) capabilities that enable engineering teams to ship software safely, quickly, and repeatably. The role balances platform architecture, reliability engineering, security-by-design, and developer experience, turning delivery practices into scalable, self-service platform products.

The Staff Build Engineer is a senior individual contributor in the Developer Platform organization responsible for the reliability, speed, security, and scalability of the company’s build and continuous integration (CI) ecosystem. This role designs and evolves build systems, CI/CD primitives, and artifact/dependency workflows so that product engineering teams can ship code predictably with minimal friction.

The **Senior Release Engineer** is accountable for designing, operating, and continuously improving the software release lifecycle—turning validated code into reliable, repeatable, auditable production releases. This role sits in the **Developer Platform** organization and acts as a force multiplier for engineering teams by standardizing release processes, automating deployment pathways, reducing release risk, and increasing delivery throughput.

The **Senior Developer Experience Engineer** is a senior individual contributor in the **Developer Platform** department responsible for improving the day-to-day productivity, reliability, and satisfaction of software engineers across the organization. This role designs and operates “paved roads” (golden paths), developer tooling, CI/CD and build/test systems, and internal platform capabilities that reduce friction from idea to production.

The **Senior Deployment Engineer** is a senior individual contributor in the **Developer Platform** organization responsible for designing, implementing, and operating reliable, secure, and repeatable software deployment capabilities across environments (development, staging, production). The role focuses on enabling teams to ship changes frequently and safely through standardized pipelines, environment automation, release orchestration, and operational readiness practices.

The **Senior CI/CD Engineer** is a senior individual contributor in the **Developer Platform** department responsible for designing, building, operating, and continuously improving the continuous integration and continuous delivery/deployment (CI/CD) ecosystem that software teams rely on to ship changes safely and frequently. The role blends platform engineering, automation, reliability engineering, and secure software supply chain practices to ensure builds, tests, artifact management, and deployments are fast, repeatable, observable, and compliant.

A **Senior Build Engineer** designs, operates, and continuously improves the build and continuous integration (CI) systems that convert source code into reproducible, testable, and deployable artifacts at scale. The role sits within the **Developer Platform** department and focuses on accelerating engineering throughput while improving build reliability, security, and consistency across repositories, languages, and teams.

The Release Engineer designs, builds, and operates the mechanisms that convert source code into reliable, traceable, and repeatable releases across environments (dev/test/stage/prod). This role ensures that releases are automated where possible, controlled where necessary, and measurable end-to-end—spanning build, test, packaging, deployment, and post-release validation.

The Principal Release Engineer is a senior individual contributor in the Developer Platform organization responsible for designing, governing, and continuously improving the end-to-end software release lifecycle—spanning build, package, test, deploy, verification, and rollback—across multiple products and teams. This role ensures releases are repeatable, secure, observable, and low-risk, while enabling high deployment frequency and fast recovery through automation and standardized release patterns.

The Principal Developer Experience Engineer is a senior individual contributor in the Developer Platform organization responsible for materially improving the productivity, reliability, and satisfaction of software engineers through platform capabilities, workflow design, and developer tooling. This role identifies friction across the software delivery lifecycle, designs “golden paths,” and builds or influences platform products that enable fast, safe, and repeatable delivery at scale.

The **Principal Deployment Engineer** is a senior individual contributor (IC) in the **Developer Platform** organization responsible for designing, scaling, and governing deployment capabilities that enable engineering teams to ship software safely, repeatedly, and quickly. This role owns the technical strategy and execution for deployment orchestration, CI/CD and progressive delivery patterns, release reliability, and platform guardrails across multiple product lines and runtime environments.

The **Principal CI/CD Engineer** is a senior individual-contributor (IC) who architects, standardizes, and evolves the organization’s continuous integration and continuous delivery/deployment (CI/CD) capabilities as part of the **Developer Platform** department. This role designs secure, scalable, and developer-friendly pipelines and release systems that enable engineering teams to ship frequently with high confidence, low risk, and strong governance.

The Principal Build Engineer is the senior technical authority responsible for the performance, reliability, security, and scalability of the organization’s build and CI execution ecosystem—spanning build systems, dependency management, artifact generation, caching, and build/test orchestration. This role exists to ensure engineering teams can ship changes quickly and safely by making builds predictable, fast, reproducible, and cost-efficient across local development and CI.

The **Lead Release Engineer** is accountable for designing, operating, and continuously improving the release lifecycle that moves software from code complete to production safely, repeatably, and at high velocity. This role sits within the **Developer Platform** organization and owns the release “nervous system”: CI/CD orchestration patterns, release governance, deployment automation, environment readiness, and cross-team release coordination.

The **Lead Developer Experience Engineer** is a senior, hands-on engineering leader responsible for designing, building, and continuously improving the end-to-end experience of software developers across the organization—spanning local development, CI/CD, environments, golden paths, internal tooling, documentation, and enablement. The role exists to reduce friction, standardize high-quality delivery practices, and increase developer productivity and satisfaction while improving reliability and security outcomes.

The Lead Deployment Engineer is accountable for designing, operating, and continuously improving the deployment and release capabilities that move software from source control to production safely, repeatably, and at speed. This role sits within the Developer Platform organization and acts as the technical lead for deployment engineering—owning CI/CD workflows, release orchestration, environment promotion strategies, and the operational practices that keep deployments reliable.

The **Lead CI/CD Engineer** is a senior, hands-on platform engineer responsible for designing, operating, and evolving the organization’s continuous integration and continuous delivery/deployment capabilities as a core part of the **Developer Platform**. This role ensures that engineering teams can build, test, secure, and ship software reliably and quickly through standardized, observable, and scalable pipeline foundations.

The **Lead Build Engineer** is accountable for the design, reliability, performance, and security of the organization’s build and continuous integration (CI) capabilities, ensuring that engineering teams can compile, test, package, and publish software artifacts quickly and repeatably. This role sits within the **Developer Platform** department and typically acts as the technical lead for build systems and build infrastructure, driving standards and modernization across repositories, pipelines, tooling, and artifact flows.

A **Junior Release Engineer** supports the safe, repeatable, and observable delivery of software changes from source control to production. The role focuses on executing and improving release processes, maintaining CI/CD workflows, coordinating release activities across teams, and ensuring that releases meet basic quality, security, and operational readiness standards.