🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Description Job Title: Software Engineer - Java Employment Type: Permanent Work Location: Chennai India - Hybrid About CloudBees CloudBees enables enterprises to deliver scalable, compliant, and secure software, empowering developers to do their best work. Seamlessly integrating into any hybrid and heterogeneous environment, CloudBees is more than a tool—it's a strategic partner in your cloud transformation journey, ensuring security, compliance, and operational efficiency while enhancing the developer experience across your entire software development lifecycle. It allows developers to bring and execute their code anywhere, providing greater flexibility and freedom through fast, self-serve, and secure workflows. CloudBees supports organizations at every step of their DevSecOps journey, whether using Jenkins on-premise or transitioning software delivery to the cloud. We're helping customers build the future, today. 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 in production codebases that weren't yours, in systems that mattered if they broke. 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 once. 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 one 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.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.