Principal Software Engineer
CloudBees, Inc. (company site, opens in a new tab)10+ yrsOn-siteDirect career pageEst. 35–55 LPA
Posted 1d ago
Reach people at CloudBees, Inc.
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at CloudBees, Inc. you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Lead technical direction and roadmap sequencing for Unify Release Orchestration (RO), balancing architectural risk and iterative value delivery every few weeks.
- Act as a key technical liaison across internal teams and CDRO Classic customers, driving adoption of RO pipelines and ensuring codebase health and quality standards.
- Own complex cross-team problems, code reviews, architectural documentation, and enhance observability and tech debt management to enable fast, safe code shipping.
Minimum Requirements
- 10+ years software engineering experience with principal or staff-level technical leadership in complex, live systems.
- Hands-on backend development and operation of microservices on AWS, ideally with Go or comparable language experience.
- Strong distributed systems knowledge including concurrency, event-driven architectures, and message buses with production troubleshooting experience.
- Experience directly using AI coding agents (e.g., Claude Code, Copilot) in development work.
Ideal Candidate Profile
- Experienced in improving existing complex systems through influence and collaboration rather than formal authority or top-down decision making.
- Comfortable engaging directly with customers to discuss technical trade-offs and incorporate feedback into product and architecture.
- Engineers who prefer iterative improvements over large rewrites, balancing deep technical work with cross-team coordination and adoption efforts.