Senior Software Engineer, CloudBees

• You have 5+ years of backend software engineering experience, with a track record of shipping and operating production services in a B2B SaaS environment
• You have strong proficiency in Golang — you understand the language deeply, not just the syntax
• You have hands-on experience with distributed systems: microservices, event-driven architecture, service mesh, and the failure modes that come with them
• You have 3+ years working with our tech stack or equivalent: Kubernetes, NATs, REST/gRPC/GraphQL APIs, AWS and/or GCP, and relational or NoSQL databases (PostgreSQL, Cassandra)
• You have experience with identity and access management at a systems level — authentication flows, authorization models, JWTs, SAML, OIDC, multi-tenancy patterns
• You think holistically about how your work fits into the larger system — and you actively seek to understand the customer, product, and business context around what you build
• You have a product engineering instinct: you're not satisfied shipping something that works technically if it doesn't serve the people using it well
• You are comfortable with ambiguity and can navigate competing priorities, make sound technical decisions with incomplete information, and communicate your reasoning clearly
• You care about the developer experience your platform creates — clean APIs, predictable behavior, fast onboarding, and minimal surprise
• You take ownership seriously. You don't wait to be asked to fix things, improve documentation, or flag risks
• Experience with IdP solutions such as Keycloak

Desirable

• The CloudBees platform is the foundation everything else is built on. When it works well, engineers ship faster, customers trust us more, and the product compounds. When it doesn't, every team feels it. This is that team — and this role matters
• We are looking for a Senior Software Engineer to join the Platform Engineering team. You will be part of an engineering team comprising front-end, back-end, and full-stack software engineers doing agile development
• You bring deep back-end engineering expertise and, just as importantly, a product mindset — you understand that platform is a product, and the quality of your abstractions directly determines what everyone else can build
• You are past the point of needing your work scoped for you. You write production-quality code, you design systems that others will build on for years, and you have the judgment to know when to optimize for speed and when to optimize for correctness. You are fluent in the tradeoffs of distributed systems, curious about how the platform affects the full software delivery lifecycle, and committed to leaving things better than you found them
• Design, build, and maintain high-throughput, resilient backend services and APIs that power the CloudBees platform across cloud and hybrid environments
• Develop and own microservices using Golang, ensuring they are performant, observable, and built for long-term maintainability
• Partner with frontend engineers and platform architects to define and implement clean API contracts (REST, gRPC, GraphQL) that enable great developer experiences
• Contribute to the design and evolution of our data layer — including relational (PostgreSQL), NoSQL (Cassandra), and streaming (Kafka/NATs) systems
• Be the voice of the customer in every technical discussion. Understand how they use the platform, what slows them down, and what would unlock the most value — then build it
• Bring a product lens to your technical work: participate in roadmap discussions, question assumptions, and advocate for platform investments that have outsized downstream leverage
• Collaborate with product managers and engineers across the org to understand how platform decisions ripple outward — into CI/CD behavior, developer experience, compliance posture, and customer outcomes
• Write documentation, runbooks, and internal guides that make the platform understandable and self-serviceable for the teams that depend on it
• Write clean, testable, well-documented code. Set the standard for what good looks like on your team
• Instrument your services from day one — meaningful metrics, structured logging, distributed tracing — and use observability data to drive continuous improvement
• Lead and participate in design reviews, architecture decisions, and code review with rigor and constructive honesty
• Mentor peers and contribute to a culture of shared ownership, psychological safety, and engineering craftsmanship