layiq

/la·yiq/adjective

worthy; deserving; fitting; suitable.

A role, opportunity, or path that merits attention, time, and pursuit.

LAYIQ - Staff Product Manager - Compute at Lambda

Find the Real Problem: Get close to customers, deals, escalations, and support on On-Demand GPU Instances and 1-Click Clusters, and work out what is actually blocking them rather than what they asked for.
Decide What Matters: Rank the work and sequence it, and be honest about what Lambda is not doing this year and why.
Write the Definition: Produce requirements, user stories, and acceptance criteria precise enough that engineering builds from them without a translation layer.
Price and Package It: Decide how your part of compute is priced, packaged, and committed to across NVIDIA GPU generations, and how customers compare the options.
Deliver With Engineering: Work through the build with the compute and control plane teams, make the tradeoff calls that come up mid-flight, and keep scope honest against the date.
Land the Launch: Set launch criteria that cover the operational readiness an infrastructure product needs, and get documentation, pricing, sales, and support in place before it goes live rather than after.
Measure and Iterate: Define what success looks like before launch, then go find out whether it happened, using adoption and utilization rather than opinion.
Make the Call Stick: Take a position on contested tradeoffs, write it down well enough that people can disagree with it precisely, and keep owning the decision after it is made.
Work as a Group: Partner with the other product managers on compute and with the teams that own storage, networking, orchestration, and commerce, so the pieces land as one product.
You
Have 7+ years of product management experience, including time on a compute platform at a hyperscaler, neocloud, or comparable cloud provider.
Have shipped compute primitives that external customers used at scale, like instance types, capacity products, provisioning interfaces, or placement and isolation controls.
Understand GPU and CPU infrastructure well enough to reason with engineers about launch paths, hardware failure modes, placement, and performance.
Have owned a product where day two behavior mattered as much as launch, including failure handling, maintenance, and what customers are told when something breaks.
Have owned pricing, packaging, or commitment terms for an infrastructure product.
Can tell which parts of a hyperscaler playbook transfer to an AI cloud and which are cost without benefit.
Can reason about utilization and capacity economics, and make the call when customer flexibility and hardware utilization pull against each other.
Able to define iterative plans that move an organization from the current state towards the desired outcome.
Can turn ambiguous customer, technical, and commercial inputs into product definition that multiple teams execute against.
Communicate plainly, write well, and make decisions easier for people who do not all share the same context.
Nice to Have
Experience with interruptible or preemptible capacity, or with reservations and committed use products.
Experience with the surfaces customers automate against, like public APIs, infrastructure as code providers, machine images, or snapshots.
Experience with hardware failure handling across a large hardware footprint, like spare pools, node replacement, or fault containment.
Experience with performance isolation and placement on shared hardware, including what a provider can honestly guarantee.
Experience with bare metal or dedicated host products, including isolation between tenants.
Experience with distributed training or large-scale inference workloads and what they demand of the compute layer.

Staff Product Manager - Compute

Employer job description

About the Role

What You'll Do

Salary Range Information

About Lambda

Equal opportunity and accommodations

About this listing

Listing check

Similar jobs

Similar jobs