Product Manager, Enterprise Core Platform

Benefits

Parental leave

Not verified

Non-birth-parent leave

Not verified

Family-building benefits

• Fertility benefits: Not verified
• Adoption assistance: Not verified
• Surrogacy assistance: Not verified

Mental health support

Not verified

Relocation assistance

Not verified

Childcare support

Not verified

Learning budget

Not verified

Verification

Not verified

Salary

$206K-$300K not verified - source not recorded; timestamp not recorded

401(k) match

Not verified

Was this benefit information wrong? Tell us.

Market context

U.S. role benchmark (BLS OEWS)

$102,662 U.S. median for this role

Projected growth (BLS Employment Projections)

+5.4% - Faster than average

146% above the BLS role benchmark for product management aggregate.

Matched to SOC 11-1021 - Product Management aggregate by role bucket.

Source: U.S. Bureau of Labor Statistics, OEWS, May 2024 and Employment Projections, 2024-2034.

Schedule

Shift type

Not verified

Weekend work

Not verified

Application

Cover letter

Not verified

Assessment

Not verified

Deadline

Not stated

Where they hire

State eligibility is not yet verified.

About this role

Product Manager, Enterprise Core Platform New York, NY Role Summary 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. This is not a roadmap PM, a program manager, or a feature tracker. The Platform PM owns the core infrastructure that every FD team builds on top of: defining the foundation before anything else can be built reliably, sequencing work against real customer commitments and FD team velocity, identifying which FD-built patterns are ready to graduate to core, and ensuring that every capability that ships does so at a bar customers can trust without thinking about it. The best Platform PMs have defined platform capabilities at production bar in high-stakes environments and understand the difference between what is necessary to build, what is interesting to build, and what should never be built at all. What You'll Do - 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.

Read the full description at job-boards.greenhouse.io. FewerJobs shows a source-linked preview and links to the original posting.