Senior Product Manager

<h1>Senior Product Manager, Cluster Scalability</h1> <p>Location: Dublin</p> <h2>About the Role</h2> <p>MongoDB is hiring a Senior Product Manager to own scalability for the Atlas data platform. Atlas is how the world’s most demanding applications run on MongoDB — from real-time gaming and financial transactions to AI workloads with unpredictable traffic patterns. When those applications grow, slow down, spike, or contract, scalability is the layer that decides whether the customer trusts us to keep running their business.</p> <p>This role owns the end-to-end product experience for how customers scale up, scale down, and horizontally scale their Atlas deployments. That includes vertical scaling (instance tier changes), autoscaling, horizontal scaling (sharding and shard key strategy), and the operational workflows around all of them. You will set the strategy, drive execution with engineering, and be accountable for measurable year-over-year improvements in how reliably and predictably customers scale.</p> <p>We care less about whether you’ve worked on databases before and more about whether you’re the kind of PM who can ramp fast on a hard technical domain, form a clear opinion about what needs to happen, and defend that opinion to senior engineers, field partners, and enterprise CTOs, especially when they disagree with you. Database and scaling concepts are teachable. Judgment, conviction, and crispness are not.</p> <h2>Responsibilities</h2> <ul> <li>&nbsp; &nbsp; &nbsp; Set a clear, opinionated vision and strategy for Atlas cluster scalability and translate it into concrete, prioritized bets each release.</li> <li>&nbsp; &nbsp; &nbsp; Own the end-to-end roadmap for vertical scaling, autoscaling, and horizontal scaling, including the operational and observability surfaces customers rely on during scaling events.</li> <li>&nbsp; &nbsp; &nbsp; Make hard prioritization calls, including saying no to things with real customer or leadership support, and own those decisions and their consequences.</li> <li>&nbsp; &nbsp; &nbsp; Build deep technical understanding of Atlas scaling internals (instance tier mechanics, autoscaler logic, sharding, balancer behavior, capacity headroom) and use it to shape requirements and tradeoffs with engineering. You don’t need to know this on day one. You do need to know it deeply by month two.</li> <li>&nbsp; &nbsp; &nbsp; Represent product direction with conviction to senior engineering leaders, field partners, and enterprise customers, especially when they disagree.</li> <li>&nbsp; &nbsp; &nbsp; Stay close to customers and field partners to deeply understand scaling pain points, failure patterns, and the moments where trust is won or lost.</li> <li>&nbsp; &nbsp; &nbsp; De