Product Manager, Enterprise Core Platform

The shape of it

In the posting’s own words

Scale is building the agentic operating system that powers AI deployment across the world's most important organizations. The Platform PM is the person who determines what that foundation needs to be — and holds the bar on how well it gets built.

What it asks for · 6

• 6+ years in product management with meaningful time owning platform, infrastructure, or developer-facing products at production bar.
• Demonstrated record of defining and shipping platform capabilities — not features on top of a platform someone else built. You can describe the architectural decisions you made, what production required, and what you learned.
• Strong sequencing judgment: can prioritize across competing customer commitments and team velocity needs with incomplete information, without thrashing.
• Technical fluency sufficient to hold real conversations with platform engineers about architectural tradeoffs across infra, auth, observability, deployment, and agent runtime. Not deep coding, but genuine comprehension of how production systems work.
• Extreme ownership and follow-through: closes loops without reminders, drives outcomes across teams without formal authority, holds self and others to commitments.
• Clear, precise communication: adjusts for audience (platform engineer vs. FD PM vs. executive); writes and speaks at the right level of detail.

What the job covers

• Define the foundation. Determine what needs to be true at the core platform layer — across each capability pillar — before anything reliable can be built on top of it.
• Sequence it. Prioritize and order platform work given customer commitments, FD team velocity needs, and what is actually blocking progress today. Getting this wrong means building on an unstable base or building the right things in the wrong order and paying for it in rework and FD team drag.
• Identify patterns and graduate capabilities. Watch what FD teams are building across the application layer, determine what is genuinely repeating, and make the call on what moves to core — and when. Do not rush graduation or delay it out of caution.
• Hold the quality bar. Every capability on the platform roadmap earns its place twice: once by being necessary, and again by being done well enough that customers trust it without thinking about it. Keep the platform from becoming a graveyard of half-built capabilities.
• Unlock delivery team time to value. Forward deployed delivery teams should spend their time solving the hardest customer problems, not rebuilding plumbing on every engagement. That requires a platform that is secure by default, deployable anywhere, observable in production, and equipped with the agentic primitives, eval infrastructure, expert judgment capture, and data reasoning capabilities that every agent workload needs.
• Partner across the organization. Work closely with platform engineering, forward deployed PMs, and BU leads to surface signal, resolve sequencing tradeoffs, and keep the roadmap grounded in what is actually blocking work.

Tools and skills named

Words the posting leans on

• platform21×
• core7×
• customer7×
• production7×
• every6×
• infrastructure6×
• bar5×
• built5×
• capabilities5×
• sequencing5×
• build4×
• building4×
• customer commitments4×
• foundation4×
• hold4×
• layer4×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

More open at Scale AI

• AI Advisory ConsultantSan Francisco, CA; New York, NY
• AI Advisory PrincipalSan Francisco, CA; New York, NY
• AI Applications Ops Manager, GPSDoha, Qatar
• AI Builder InternSan Francisco, CA
• AI Infrastructure Engineer, Model Serving PlatformSan Francisco, CA; New York, NY
• AI Infrastructure Engineer, Sandbox PlatformSan Francisco, CA; Seattle, WA; New York, NY