Principal Software Engineer, CBCI

Job Title: Principal Software Engineer, CBCIJob Type: Full-timeLocation: Hybrid - Denver, CO (3 days on-site per week)About CloudBeesCloudBees helps organizations build, run, and govern software factories, giving enterprises the confidence to ship software better, faster, and safer.Writing code is no longer the bottleneck. Governing what reaches production and validating its impact is. As enterprises adopt agentic coding, software is created faster than most teams can review, secure, and validate. Without consistent governance, organizations risk shipping code they cannot explain, audit, or trust.CloudBees addresses this challenge without asking teams to replace the tools they already use. Across every toolchain a customer runs, CloudBees makes each change, human or AI, visible, auditable, and accountable before it reaches production. CloudBees Unify is the product behind this: a governance layer, with context and control-plane capabilities, that enforces consistent policy and evidence across every tool, team, and workflow.Founded in 2010, CloudBees is backed by Goldman Sachs, Morgan Stanley, Bridgepoint Capital, HSBC, Golub Capital, Delta-v Capital, Matrix Partners, and Lightspeed Venture Partners.Visit us at www.cloudbees.com.About the RoleCloudBees CI helps enterprises build and deliver software with confidence. Built on Jenkins, with a core written in Java and deployments running on Kubernetes, it brings together the challenges of distributed systems, an extensible plugin ecosystem, and the reliability customers expect from critical delivery infrastructure.We are looking for a Principal Software Engineer to set technical direction for the CloudBees CI product area and turn that direction into working software. You will lead architecture and execution across teams while staying close to the code: solving the hardest engineering problems, improving an established codebase, and helping other engineers do their best work.You bring deep expertise in Java, Kubernetes, and distributed systems, together with a product mindset. You understand that an architectural decision is only valuable if it improves the customer's experience. You know when to simplify, when to invest in a deeper change, and how to move an established product forward without compromising the workflows customers depend on.