The opportunity
Lambda, The Superintelligence Cloud, is a leader in AI cloud infrastructure serving tens of thousands of customers. Our customers range from AI researchers to enterprises and hyperscalers.
What you'll do
Own the Whole Surface: Hold the product definition for the console as one product, decide what belongs in it and what does not, rank and sequence the work, and be honest about what Lambda is not doing this year and why.
Set the Patterns and Hold Them: Define the navigation, identity, permissions presentation, resource naming, states, errors, and empty screens that every service uses, write them down clearly enough that a team can build to them without asking you, then establish and run the review that console work passes before it ships.
Keep the Console Honest With the API: Make sure the console, the API, the command line, and infrastructure as code describe the same resources with the same names and the same rules, and treat a console-only capability as a problem to be fixed rather than a feature.
Fix the First Hour, Then Serve the Expert: Own what happens between signing up and running a first workload, instrument it well enough to know exactly where people stop, and keep the paths that operators and platform teams live in, like bulk actions, filtering, deep links, quotas, spend visibility, and access control, first class rather than an afterthought behind a wizard.
Find the Real Problem: Get close to customers, support tickets, escalations, and session data, and work out what is actually blocking people rather than what they asked for.
Write the Definition: Produce requirements, user stories, and acceptance criteria precise enough that engineering and design build from them without a translation layer.
What they're looking for
- Work as a Group: Partner with the product managers who own each service so their launches land inside your surface as one product, and agree the seams early rather than at launch review.
- Land the Launch: Set launch criteria that include documentation, in-product guidance, support readiness, and accessibility, and get them met before the surface goes live rather than after.
- Measure and Iterate: Define success before you ship, then go find out whether it happened, using completion rates, time to first result, and support load 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.