Staff Product Manager, Cloud Networking
Confluent
- Pay
- $232k–$272k
- Workplace
- Remote
- Location
- Remote, United States · United States
- First seen
- 6 days ago
- Last seen
- 26 minutes ago
- Board
- Ashby
Summary
We’re not just building better tech. We’re rewriting how data moves and what the world can do with it.
- react
- aws
- gcp
- azure
- kafka
Posting
We’re not just building better tech. We’re rewriting how data moves and what the world can do with it. With Confluent, data doesn’t sit still. Our platform puts information in motion, streaming in near real-time so companies can react faster, build smarter, and deliver experiences as dynamic as the world around them. It takes a certain kind of person to join this team. Those who ask hard questions, give honest feedback, and show up for each other. No egos, no solo acts. Just smart, curious humans pushing toward something bigger, together. One Confluent. One Team. One Data Streaming Platform. ABOUT THE ROLE: Confluent's Cloud Networking team is responsible for making connectivity to and from Confluent Cloud reliable, scalable, secure, cost-efficient, and simple to use — across Kafka, Flink, Connectors, Data Governance, and Tableflow, on AWS, Azure, and GCP. As Staff PM for Cloud Networking, you will own the platform strategy for how enterprises connect to Confluent Cloud. This is not a feature-level role — you will define the architecture of our networking product surface across all clouds and connection models, set the multi-year roadmap, and operate as a co-decision-maker alongside engineering leadership on the technical direction of the platform. You will work across all networking connection types — PrivateLink, VNet peering, Transit Gateway, Private Service Connect, and egress optimization — and drive alignment across engineering, field, and executive stakeholders on what we build and why. WHAT YOU WILL DO: - Own the platform strategy for Confluent Cloud Networking across AWS, Azure, and GCP — defining the north star, multi-year roadmap, and sequencing of bets that balance customer connectivity needs, cost efficiency, security posture, and engineering leverage - Define frameworks and standards that other PMs, designers, and engineers use to evaluate networking decisions — connection model selection criteria, cost attribution models, security control frameworks, and launch readiness standards - Drive architectural decisions in partnership with engineering leadership — weighing trade-offs between user experience, cost, and operational complexity - Expand scope and create optionality — identify adjacencies the team should move into (network observability, cost transparency tooling, next-generation isolation models) and build the business case for them - Develop the product team — mentor Senior PMs on the team, provide feedback on produ