IBM
Staff Software Engineer - Cloud Platform

How your CV stacks up
Upload your CV to see how well it fits this job role
?%
Introduction
At IBM Software, we transform client challenges into solutions. Building the world’s leading AI-powered, cloud-native products that shape the future of business and society. Our legacy of innovation creates endless opportunities for IBMers to learn, grow, and make an impact on a global scale. Working in Software means joining a team fueled by curiosity and collaboration. You’ll work with diverse technologies, partners, and industries to design, develop, and deliver solutions that power digital transformation. With a culture that values innovation, growth, and continuous learning, IBM Software places you at the heart of IBM’s product and technology landscape. Here, you’ll have the tools and opportunities to advance your career while creating software that changes the world.
Your Role And Responsibilities
About the role
We’re looking for a Staff Software Engineer I to lead the design and delivery of a foundational control plane platform that powers Confluent Cloud. In this role you will own highly technical projects across multiple services and teams, shaping the architecture and reliability of our cloud platform.
What You’ll Do
- Own end‑to‑end architecture and delivery of complex control‑plane systems (APIs, controllers, orchestration workflows, data models) that support Confluent Cloud products.
- Lead open‑ended technical initiatives: take ambiguous problems, clarify requirements, define the approach, and drive execution across teams and services.
- Raise the bar on reliability and operations by building resilient systems with strong observability, clear SLOs, runbooks, and safe rollout/rollback patterns.
- Collaborate across orgs (Cloud Platform, Kafka, Compute, Security, Traffic, SRE and others) to align on designs, trade‑offs, and long‑term platform direction.
- Mentor and unblock engineers at multiple levels; provide high-quality design and code reviews and help grow the broader engineering team.
- Continuously improve developer experience for our control‑plane stack (tooling, automation, CI/CD, test strategy) to remove toil and increase velocity.
- Influence technical strategy in your domain: identify high‑impact opportunities, propose roadmaps, and help prioritize work aligned with business goals.
- Contribute to engineering culture via documentation, design reviews, and knowledge sharing (internal talks, wikis, or external content where appropriate).
Reasons to use Rodeo
I’m in my final year doing Economics and I don’t know whether to apply for grad schemes now or do a masters first. What do you think?
Honest answer — it depends on where you want to end up. A lot of top grad schemes (Big 4, civil service, banking) don’t need a masters. Let’s look at the ones you’d be competitive for now, and we can decide if a masters actually adds anything.
Also worth knowing: most autumn 2026 applications are open now. Timing matters more than you think.
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet — that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
Graduate Consultant — 2026 Scheme
Why you're a good match
StrongYour economics background and your summer at a regional bank line up with what PwC looks for on the consulting scheme. Applications close in four weeks.
See breakdownIt searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Why you're a good match
You’ve got the grades and the economics background, and your bank internship is exactly the experience this scheme looks for. Apply soon — deadlines close within the month.
Experience fit
Your summer at the bank plus your econometrics coursework map directly to the day-one responsibilities on this scheme — client modelling, market briefings, and deal support.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right — and where to focus when applying.
Preferred Education
Master's Degree
Required Technical And Professional Expertise
- Experienced builder: Typically, 8+ years of software engineering experience, with a strong track record of delivering complex backend or distributed systems to production.
- Distributed systems & cloud expert: Deep hands‑on experience with at least some of:
- Distributed systems design (consistency models, failure modes, data modeling, scalability).
- Cloud platforms (AWS, GCP, or Azure) and cloud‑native architectures.
- Kubernetes or similar orchestration platforms.
- Strong systems and coding skills: Proficiency in one or more of Go, Java or Scala, and comfort working across services, infrastructure, and automation.
- Architect & executor: Able to define end‑to‑end designs, break them into milestones, de‑risk early, and land them on time with high quality.
- Operationally rigorous: You think in terms of SLOs, failure modes, observability, and incident response; you design for safe change and graceful degradation.
- Great communicator: You write clear design docs, explain trade‑offs crisply, and can lead technical discussions with diverse stakeholders (engineers, PMs, leadership).
- Leader without authority: You’ve successfully led cross‑team projects, influenced technical direction beyond your immediate code, and helped others level up.
- Values‑aligned: You care about customer impact, reliability, long‑term maintainability, and helping the team win, not just shipping features.


Get help with your application
Your very own career expert that helps elevate your application to the next level.
Preferred Technical And Professional Experience
Nice to have
- Experience building control‑plane systems (APIs, operators/controllers, metadata services, provisioning/orchestration workflows).
- Background with Apache Kafka or other streaming/data systems.
- Prior work on multi‑region, high‑availability, or disaster‑recovery architectures.
- Experience in security‑sensitive infrastructure (identity, certificates, secrets, mTLS, policy) or compliance‑driven environments.
- Contributions to open source projects, public talks, or technical blogs in relevant areas.
Why join Confluent and Cloud Platform Control Plane
- Work on mission‑critical infrastructure at global scale, used by thousands of customers in production.
- Partner with a strong group of senior and staff engineers across Cloud Platform, Kafka, and Compute.
- Help define the next generation of Confluent Cloud’s control plane, with real influence on architecture, reliability, and developer experience.
- Join a culture that values ownership, operational excellence, and one‑team collaboration.
“It took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what I’ve been looking for.”
Jessica, London
Skills
Location