Software Engineer

About CloudBees:

CloudBees helps organizations build, run, and govern software factories, giving enterprises the confidence to ship software better and safer.

Writing code is no longer the bottleneck. Governing what reaches production and validating its impact is. As enterprises adopt agentic coding, software gets created faster than most teams can review, secure, and validate it. Without consistent governance, organizations end up shipping code they can't explain, audit, or trust.

CloudBees Unify is a governance layer that works with the tools a customer already runs, instead of asking them to replace them. It makes every change, human or AI, visible and accountable before it reaches production, and enforces the same policy across every tool, team, and workflow.

About the team:

Our department, internally called "Faster, Safer Releases," has three areas: CDRO Classic (CloudBees CD/RO), Unify Release Orchestration (Unify RO), and Unify FM (feature management). You'd help shape the technical direction of Unify RO alongside the engineers already building it.

You'll join a core team of experienced engineers. You won't manage anyone. You'll be a go-to technical contact for RO work happening outside the core team, and you'll share accountability for the codebase's long-term health, including bridging to CDRO Classic customers and pushing internal dogfooding alongside Unify FM.

What you'll do:

Help shape where Unify RO goes

• Learn the current RO architecture well enough to form an evidence-based view of what's solid, what's accumulating risk, and which ideas from CDRO Classic are worth carrying forward.
• Help sequence the technical roadmap so the team ships value every few weeks, working closely with the RO product manager.
• Stay hands-on with hard problems, especially ones that cross team boundaries and have no natural owner today.

Make the team stronger, not more dependent on you

• Work as a peer with strong engineers, as ready to be persuaded as to persuade.
• Bring context from across the department and from customers to make technical calls better informed.
• Give candid, useful design and code review, and expect the same back.

Build the bridge to CDRO Classic and the business

• Talk to CDRO Classic customers interested in Unify RO.
• Drive adoption of RO pipelines inside CloudBees itself, combining progressive delivery with feature flagging, in partnership with Unify FM.

Make quality the default, not an afterthought

• Keep testing, service boundaries, and release discipline strong as the team and roadmap evolve.
• Pay down tech debt as you go.
• Push observability toward finding root causes fast.
• Make it possible for other teams to move fast in the RO codebase through tooling, clear specs, onboarding, and code review.
• Write down architectural decisions and the reasoning behind them.

What we're looking for:

Must have

• 10+ years of experience, with principal or staff+ scope you can point to, including sequencing and trade-off calls on a complex, live system.
• You lead through influence and technical credibility, not formal authority.
• Strong opinions, loosely held.
• Comfortable talking directly to customers about technical trade-offs.
• Hands-on backend depth building and operating microservices on AWS, ideally in Go. Strong experience in a comparable backend language also works.
• Distributed-systems depth: concurrency, event-driven architectures, message buses, and what breaks in production.
• Hands-on use of AI coding agents (Claude Code, Cursor, Copilot, or similar) in your own work.
• A sense of humor.

Nice to have

• Experience with CI/CD systems, workflow/pipeline engines, or developer platforms.
• Experience with progressive delivery or feature flagging.
• Java.

Who this is for:

You like joining a system that's already moving, built by people who know it better than you will on day one. You'd rather improve what's working than rewrite it from scratch, and you're energized by a role that's equal parts deep technical work, customer conversations, and getting other CloudBees teams to use what the team builds. Sharp and a little irreverent beats technically flawless but humorless, as long as you still ship.