Software Engineer - Java

• Job Title: Software Engineer - Java

• Employment Type: Permanent

• Work Location: Chennai India - Hybrid

About CloudBees

CloudBees 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 .

About the Role

We use Claude Code every day and are pushing agentic AI further into how we work. If you want to be on a team figuring out what AI-assisted engineering actually looks like on a real, complex product (not a sandbox), this is it.

CDRO (Continuous Delivery & Release Orchestration) is CloudBees' enterprise CD product. It's been running in production at some of the world's largest engineering orgs for over a decade. Hundreds of engineers depend on it to ship software safely and on schedule.

We're a team of about 10, distributed across India, France, Spain, and the US. We're not chasing the next hype cycle feature. We operate a product real customers depend on, modernize it while keeping it stable, and do it with a small team that takes ownership seriously.

Key Responsibilities

Most teams try AI coding tools on greenfield work. We're doing something harder: applying them to a decade-old enterprise codebase with real customers depending on it. CDRO's core is Java 21 with a significant Groovy layer. The work is a mix of internal cleanup that makes the codebase easier to evolve, and direct improvements that make customers' lives better.

• Concretely:

• Own Java work across the core: REST API, pipeline execution engine, persistence layer
• Continuously reduce complexity: modernize older subsystems, shrink the product surface area where it makes sense, improve test coverage, and leave the codebase easier than you found it
• Use Claude Code as a normal part of your workflow, to move faster without skipping thought
• Write tests that prove things work. Shift-left, not "QA will catch it."
• Document what you build. We're async across timezones. If you know something the team needs to know, write it down.
• Actively avoid being a single point of failure for anything you own

Qualifications

• Required:

• Solid Java. You've worked

professionally at least 4 years developing Java software

, in production codebases that weren't yours, in systems that mattered if they broke.

• Strong AI awareness: you know what Claude Code, or Cursor, etc. do. You've played with some of them at least.
• Relational database experience: SQL, JPA/Hibernate, schema migrations. Oracle or PostgreSQL background is a strong advantage.
• Comfort in large, mature codebases. You can navigate unfamiliar code, form a hypothesis, test it, and stay functional when you don't understand everything at.
• Testing discipline. You write unit and integration tests as part of the work, not after.
• Honest communication. If something is blocked or broken, we need to know. We're async and distributed.

• Strong plus:

• Active use of Claude Code to ship real work, not just tab completion

• Bonus: you want to push it much further than you do today.

• Groovy. Willingness to pick it up fast matters more than prior credentials.
• Kubernetes/Helm: deploying and debugging workloads, not just using them.
• Experience evolving established systems: migrations, incremental rewrites, dependency upgrades.

• Preferred (not mandatory):

• Jenkins or CI/CD internals
• Distributed systems infrastructure: message brokers (ActiveMQ, Artemis, RabbitMQ), coordination (Zookeeper)
• React/TypeScript: the UI is adjacent and not your main domain, but not being afraid of it helps

Who this is for

• You're a Java engineer who finds large, evolved codebases interesting rather than off-putting. You've seen what breaks when systems are poorly documented and owned by person. You build the opposite.
• You want hard engineering problems, real ownership, and a team that says what's true. With ~10 people on the team, you'll touch meaningful parts of the system fast. You'd rather evolve a product real enterprises depend on than build a greenfield service nobody's relying on yet.

Working Conditions

• Standard working hours: 9:30 a.m. – 6:30 p.m., Mon–Fri, or as per business needs
• Work location / travel expectations: Hybrid
• Reasonable accommodations will be considered in line with the Rights of Persons with Disabilities Act, 2016.

Equal Opportunity Statement

CloudBees is an Equal Opportunity Employer. We do not discriminate on the basis of caste, religion, color, gender, sexual orientation, age, marital status, disability, or any other status protected under applicable law. We are committed to creating an inclusive workplace where everyone can thrive.

Data Protection Statement

All personal information collected during the recruitment process will be handled in accordance with applicable Indian data protection laws and CloudBees privacy policy.

Disclaimer

This job description is intended to provide a summary of the position and its responsibilities. It is not an exhaustive list of duties. Responsibilities and activities may evolve as per organisational requirements.

• Solid Java. You've worked professionally at least 4 years developing Java software, in production codebases that weren't yours, in systems that mattered if they broke.
• Strong AI awareness: you know what Claude Code, or Cursor, etc. do. You've played with some of them at least.
• Relational database experience: SQL, JPA/Hibernate, schema migrations. Oracle or PostgreSQL background is a strong advantage.
• Comfort in large, mature codebases. You can navigate unfamiliar code, form a hypothesis, test it, and stay functional when you don't understand everything at.
• Testing discipline. You write unit and integration tests as part of the work, not after.
• Honest communication. If something is blocked or broken, we need to know. We're async and distributed.