Chief of Staff, VP of Product

Role Summary

Scale is building the infrastructure layer for institutional intelligence — the compounding asset that makes the world's most consequential organizations more capable over time. The Chief of Staff to the VP of Product sits at the center of that work.

This is not a chief of staff role in the traditional sense. This person is not a scheduler, a note-taker, or a communications coordinator. They are an extension of the VP of Product, absorbing context across every workstream, making real prioritization calls, and operating at a level of organized precision that makes the rest of the function run faster.

The right person for this role wants to grow into product leadership and understands that the fastest path there is to operate at close range with someone doing the job. They will be in every room, on every decision, and responsible for ensuring that nothing falls through the cracks, including the principal.

What You'll Do

• Prepare the VP for every significant meeting, external or internal: customer briefings, executive reviews, board-adjacent discussions with the right level of context and the right framing.
• Represent the VP in internal workstreams where her presence isn't required but her perspective is. This means you actually have the perspective, not just her notes.
• Drive follow-through on decisions made in meetings: own the action items, chase closures, and surface blockers before they become problems.
• Build and maintain the operational infrastructure that keeps the product org coordinated. Rhythms, comms, templates, and shared context without it becoming process for its own sake.
• Engage directly with engineering leads, PMs, and go-to-market partners with enough technical and product fluency to move things forward, not just relay information.
• Move people without authority. You will regularly need engineers, PMs, GTM leads, and customers to do things that aren't in their immediate interest to prioritize. You get there by being trusted, well-framed, and well-timed, not by invoking the principal's name.

What We're Looking For

Must-Have Qualifications

• 10 years of experience in product management, technical program management, strategy, or a role with real operational ownership - not coordination.
• Demonstrated record of managing complexity: multiple parallel workstreams, competing stakeholder demands, and ambiguous ownership  and keeping all of it moving without dropping threads.
• Extreme organizational precision. Their systems are legible to others, not just themselves.
• Enough technical fluency to hold a real conversation with a platform engineer. Not deep coding, but genuine comprehension of how systems work: APIs, infrastructure, deployment, architecture at a conceptual level and curiosity to learn.
• The judgment to act on behalf of the principal. 
• Strong, precise written communication. First drafts should be clean. Recaps, briefs, and async updates should require minimal editing.