Principal Engineer - Software Engineering in London

Hybrid - Chennai/London, IND •

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

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.

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

Founded in 2010, Cloud Bees is backed by Goldman Sachs, Morgan Stanley, Bridgepoint Capital, HSBC, Golub Capital, Delta-v Capital, Matrix Partners, and Lightspeed Venture Partners.

CDRO Classic (Cloud Bees CD/RO, our established, self-managed release orchestration product, still very much serving customers today), Unify Release Orchestration (Unify RO, its newer sibling, delivered as a Saa S), and Unify FM (feature management).

You'd help shape the technical direction of Unify RO alongside the engineers already building it, who are rethinking what release orchestration can look like rather than porting CDRO Classic.

You'll be a go-to technical contact for RO work happening outside the core team, and you'll share accountability with the core team for the codebase's long-term health, including bridging to CDRO Classic customers curious about Unify RO and pushing internal dogfooding so Cloud Bees' own teams ship their own PRs faster and safer, alongside Unify FM.

Help shape where Unify RO goes Learn the current RO architecture from the people who built it, well enough to form an evidence-based view: 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, not a multi-quarter rewrite.

You'll work closely with the RO product manager, as a conversation with the whole team rather than a two-person channel: product owns what and why, engineering owns how and in what order.

Drive adoption of RO pipelines inside Cloud Bees itself: help other teams ship PRs from dev to production faster and safer, 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.

Make it possible for other teams to move fast in the RO codebase without breaking it: through tooling, clear specs (including for AI-written changes), onboarding, and code review.

Hands-on backend depth building and operating microservices on AWS, ideally in Go. Strong experience in a comparable backend language, with appetite to go deep in Go, also works.

The distributed-systems depth that goes with it: concurrency, event-driven architectures, message buses, and what actually breaks in each of them in production.

Hands-on use of AI coding agents (Claude Code, Cursor, Copilot, or similar) in your own work, not secondhand opinions.

You'll need one some days, and it'll help on the good ones too.

Java. CDRO Classic is written in Java, and knowing it shortens the ramp on deciding what to keep.

Sharp and a little irreverent beats technically flawless but humorless, as long as you still ship.