Scribd, Inc. is on a mission to advance human understanding. Our four products — Scribd, Slideshare, Everand, and Fable — help billions of people across the globe move beyond access and into insight, application, and expertise.
We support a culture where our employees can be real and be bold; where we debate and commit as we embrace plot twists; and where every employee is empowered to take action as we prioritize the customer.
We believe the best work happens when individual flexibility is balanced with meaningful community connection. Scribd Flex empowers employees to choose the workstyle and location that support their best performance, while committing to intentional in-person moments that strengthen collaboration and culture. Occasional in-person attendance is required for all Scribd, Inc. employees, regardless of location.
So what are we looking for in new team members? At Scribd, Inc., we hire for “GRIT.” Traditionally defined as the intersection of passion and perseverance toward long-term goals, GRIT reflects the mindset we expect from every employee. For us, it also serves as a practical framework for how we work: setting and achieving Goals, delivering Results within your role, contributing Innovative ideas and solutions, and strengthening the broader Team through collaboration and attitude.
This posting reflects an approved, open position within the organization.
We're changing how Scribd builds — and this role drives that forward. An agentic engineering stack is our competitive edge — turning AI leverage into real velocity: iterating fast to find the right direction, then moving with conviction. The foundations are taking shape — Claude Code in every engineer's hands, a plugin marketplace, an internal app platform in development, and the skills and conventions that make them effective in our codebases. The next chapter is making that stack the operating system every function at Scribd builds on top of.
In engineering, more than 80% of our engineers use Claude Code daily, and AI now writes more than half of our new code — roughly 3× the industry median. Across the company, teams are exploring agentic workflows and building their first internal apps and tooling. The deeper transformation is still just beginning: redesigning how software gets built as AI agents take on more of the work and engineers direct and steer — and extending that pattern to every other function. That's where this role comes in.
This is a foundational hire — Scribd's first product management role pointed inward, with the company itself as the customer. You'll lead Scribd's AI transformation, with the developer platform as the center of gravity: helping define the agentic engineering stack and shaping the evolution of the developer & agentic experience at Scribd. From that foundation, you'll extend the same thinking outward — partnering with Product, Design & Research, Data & Analytics, and TPM as they redesign their own work around AI agents, and guiding the internal app and agent platforms that every function depends on.
To do this well, you'll spend real time with developers and eng teams — understanding how they work today, where the friction lives, and what the next leap looks like for them. You'll lead the product strategy for developer experience and how we measure it — quantitatively and qualitatively. You'll bring the same lens to the parallel transitions in other functions at Scribd. Across all of it, your job is to help us adopt AI thoughtfully and prove its impact — not to scale AI generation for its own sake, but to make every function more capable and more confident in the outputs.
This role reports to the Director, Developer Platform, and partners closely with Engineering and Product leadership.
You are energized by hard, ambiguous, cross-functional problems where the technology landscape is moving faster than ever, adoption is uneven across functions, and the platform is actively evolving as it ships. You have spent enough time close to engineering to reason about platforms, APIs, and agent systems on their own terms — and enough time across functions to know that adoption is a people problem at least as much as a technical one. You are comfortable being the first PM in a new domain, defining the role as you go with no pre-existing playbook to inherit.
You are all-in on AI reshaping every kind of knowledge work across a company, and you have already been applying it to your own. You think in systems and feedback loops, and you see the difference between how work happens on paper and how it actually gets done. You prefer structural guardrails over non-enforced guidelines. You'd rather ship and learn than wait for perfect, reserving real caution for the rare decisions that you can't easily reverse.
Own the unified agentic enablement roadmap. Pull together the in-flight AI workstreams across Scribd into a cohesive, sequenced roadmap. Decide what is shared infrastructure and what stays function-specific. Make the tradeoffs visible to leadership.
Be the product owner for the internal app and agent platforms. Define and drive the product strategy for the platforms the company depends on — the internal app platform, the plugin marketplace, the agent runtime — and make sure they meet each function's real needs. You will partner with the Developer Platform and Data Platform engineering teams who build the underlying capabilities.
Translate between functions and the platform. Sit with different functions and their leaders to understand the workflows they are trying to redesign. Turn that into requirements we can build against, and turn the platform's capabilities into something every function can act on.
Drive cross-functional commitments to closure. Our AI Enablement strategy includes several load-bearing pieces of shared infrastructure — canonical context, the evaluation practice, the plugin marketplace, the internal app platform, and a coherent context ownership map. Each has named owners across functions. Your job is to keep them moving in lockstep and surface the seams before they fragment.
Make agentic enablement legible to the company. Define the metrics that matter — adoption, throughput, time recovered, evaluation quality, impact — and report against them. Build the narrative that gets every function bought in.
Partner on go-to-market for internal users. Plan and run the rollouts, education, and feedback loops that drive measurable adoption — capabilities aren't done when they ship, they're done when each function depends on them. Treat internal rollouts with the same rigor we would treat an external launch.
7+ years of product management experience, with notable focus owning developer tooling, AI platforms, or internal productivity tools
Demonstrated success owning ambiguous, cross-functional product surfaces end-to-end — defining the strategy, sequencing the work, and shipping with engineering partners — without a pre-existing playbook
Hands-on experience shipping real products with modern AI/LLM primitives — prompting, evals, tool use, agentic workflows, MCP, plugin or skill ecosystems, or comparable concepts. You have built things with these primitives, not just written PRDs about them
Strong technical fluency to match. You can hold your own with engineers on system design, API tradeoffs, evaluation methodology, and agent architectures
A track record of being a trusted technical-strategy partner to engineering leadership, with influence at the architecture and roadmap horizon
Exceptional written and verbal communication. You can move between an engineering deep-dive, a function lead's strategy review, and an exec narrative in the same week
Comfort and ability to move things forward when working in conditions where priorities, scope, and ownership are still being defined
A background that includes engineering, technical program management, or applied AI work in addition to product management — you have shipped production code at some point in your career
Experience as a PM, technical lead, or founder building internal-facing developer tools, AI platforms, or productivity products at scale
Direct experience with Claude Code, Codex, Cursor, or other agentic coding environments — as a power user, an enabler, or a builder
Familiarity with the operating realities of a multi-product subscription business and a software stack that spans Ruby, Go, TypeScript, Python, and the AWS/Databricks ecosystem
Prior experience standing up a new function or a new PM role in an organization
-
At Scribd, Inc., your base pay is one part of your total compensation package and is determined within a range. Our pay ranges are based on the local cost of labor benchmarks for each specific role, level, and geographic location. San Francisco is our highest geographic market in the United States.
In the state of California, the reasonably expected salary range is between $171,000 [minimum salary in our lowest geographic market within California] to $256,500 [maximum salary in our highest geographic market within California].
In the United States, outside of California, the reasonably expected salary range is between $141,000 [minimum salary in our lowest US geographic market outside of California] to $244,000 [maximum salary in our highest US geographic market outside of California].
In Canada, the reasonably expected salary range is between $179,000 CAD[minimum salary in our lowest geographic market] to $228,000 CAD[maximum salary in our highest geographic market].
We carefully consider a wide range of factors when determining compensation, including but not limited to experience; job-related skill sets; relevant education or training; and other business and organizational needs. The salary range listed is for the level at which this job has been scoped. In the event that you are considered for a different level, a higher or lower pay range would apply. This position is also eligible for a competitive equity ownership, and a comprehensive and generous benefits package.
Are you currently based in a location where Scribd, Inc. can employ you?
Employees must have their primary residence in or near one of the following cities. This includes surrounding metro areas or locations within a typical commuting distance:
United States:
Atlanta | Austin | Boston | Dallas | Denver | Chicago | Houston | Jacksonville | Los Angeles | Miami | New York City | Phoenix | Portland | Sacramento | Salt Lake City | San Diego | San Francisco | Seattle | Washington D.C.
Canada:
Ottawa | Toronto | Vancouver
Mexico:
Mexico City
Benefits at Scribd, Inc.
Scribd Flex (flexible work model)
Comprehensive health, dental, and vision coverage
Mental health support and disability coverage
Generous paid time off, including vacation, sick time, holidays, winter break, volunteer time, and sabbaticals
Paid parental leave and family support benefits
Retirement matching and employee equity
Learning and development programs and professional growth opportunities
Wellness and home office stipends
Complimentary access to the Scribd, Inc. suite of products
Enterprise access to leading AI tools
Get to Know Scribd, Inc.
About Scribd, Inc.
Life at Scribd, Inc.
We want our interview process to be accessible to everyone. You can inform us of any reasonable adjustments we can make to better accommodate your needs by emailing [email protected] about the need for adjustments at any point in the interview process.
If you apply for a job with Scribd or otherwise engage with us in connection with employment (including as an employee, contractor, or other personnel), the personal information we process in that context is subject to our Employee and Applicant Privacy Policy, which is available here.
Scribd, Inc. is committed to equal employment opportunity regardless of race, color, religion, national origin, gender, sexual orientation, age, marital status, veteran status, disability status, or any other characteristic protected by law. We encourage people of all backgrounds to apply, and believe that a diversity of perspectives and experiences create a foundation for the best ideas. Come join us in building something meaningful.
