Product Manager, AI Enablement

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to parse the job posting. The posting includes: - Who We Are (company description) - What you’ll do (responsibilities) - Who you are (qualifications/requirements) - Your skill-set (must-haves, nice-to-haves) - What’s in it for you (benefits? maybe includes travel, base pay range) - Travel: approx 6 trips per year - US Base Pay Range: $130k - $150k - Also AI - A Transformative Force (maybe not needed) - Equal Opportunity Employer (boilerplate to remove) - Also mention "Please note that the base pay range is a general guideline only." etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "AI - A Transformative Force" maybe not needed? It's not a standard heading; but could be considered part of About the role? It's more like company values. Might be considered part of About the role? But we have no explicit "About the role" heading; we have "Who We Are" which is about company. Could map to "About the role"? Actually "About the role" is typical heading for role description. But we have "What you’ll do" which is responsibilities. "Who you are" is qualifications/requirements. "Your skill-set" is skills/must-haves/nice-to-haves. "What’s in it for you" is benefits/pay etc. Travel and base pay range could be under Benefits or Pay. We must not repeat job title as heading. No Job ID. We need to output only HTML fragment, no markdown fences. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. We need to include a section ONLY when posting has real specific content for it — never emit heading followed by filler/placeholder text. Thus we need to decide which sections to include: - About the role? Could be "Who We Are" but that's about company, not role. However we could treat "Who We Are" as About the role? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content. We have: - About the role: maybe we can combine "Who We Are" and "What you’ll do"? But "Who We Are" is company description, not role. Could still be considered "About the role"? Might be okay but maybe better to have "About the role" as a short paragraph describing the role's purpose: The role fixes AI enablement across internal teams. That is in "What you’ll do" first paragraph. So we could create About the role section with that prose. - Responsibilities: list of duties from "More specifically, you will:" bullet points. - Requirements: maybe "Who you are" includes builder, process mapper, frontier-fluent, translator, rigorously skeptical. Could be considered qualifications. - Qualifications: maybe overlapping with Requirements. Could combine. - Skills: must-haves and nice-to-haves. - Benefits: What’s in it for you includes travel, base pay range, maybe other intangibles (direct line to leaders, peer, mandate, etc). Also "Travel: This role requires approximately 6 trips per year". Also "US Base Pay Range : $130,000 USD - $150,000 USD". Also maybe "Fair warning: the first 60 days will feel exhilarating..." etc. That's more descriptive. - Pay: we could separate Pay section with base pay range. - Schedule: maybe not present; no schedule info. So we should not create Schedule section. We must not create sections with filler like "commensurate with experience". We have actual pay range, so we can include Pay. We need to avoid duplication: The "What’s in it for you" includes travel and base pay range; we could split into Benefits (travel, etc) and Pay (salary range). Or we could keep Benefits section that includes travel and maybe other intangibles, and Pay section for salary. We must not repeat content. So we need to parse and allocate. Let's extract sections: Company description (Who We Are) - could be part of About the role? Might be better to have About the role as a brief description of the role's purpose, not company. But we have no explicit company description heading; we could include it as a paragraph under About the role? The instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't forbid including company description under About the role. So we can put the "Who We Are" paragraph(s) under About the role. Responsibilities: the bullet list after "More specifically, you will:" plus maybe the preceding paragraph about first 50% time etc. That's responsibilities. Requirements/Qualifications: "Who you are" bullet-ish paragraphs: builder, process mapper, frontier-fluent, translator, rigorously skeptical. Could be under Requirements. Skills: Must-haves and Nice-to-haves list. Benefits: What’s in it for you paragraph(s) about impact, working with sharp teams, etc. Also Travel. Pay: Base pay range. We must not include EEO etc. Now we need to format with

  headings and appropriate

  or

  • . We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep the substance but not necessarily verbatim; but better to keep close. We need to avoid duplication: ensure each piece appears once. Let's draft. First, About the role: combine Who We Are and maybe the introductory sentence about role fixing AI enablement. Who We Are paragraph: "Pindrop is the Real Human + Right Human® Identity Trust Platform for the AI era. As AI-driven fraud and deepfakes erode trust in digital communication, Pindrop delivers continuous identity verification and deepfake detection across voice, video, and digital interactions in real time. Enterprises rely on Pindrop to secure billions of high-risk customer interactions each year, including top U.S. banks, as well as leading insurers and healthcare providers. Powered by models trained on more than 1.5 billion real-world interactions annually and protected by 300+ patents, Pindrop restores trust while reducing fraud, lowering operational costs, and improving customer experience. Recognized by TIME as one of the Top 10 Most Influential Software Companies of 2026 and by Inc. for Best in Business for Innovation, Pindrop is backed by leading investors including Andreessen Horowitz, IVP, and CapitalG." Then maybe add a sentence about the role: "As Product Manager, AI Enablement, you will own the product experience that turns Pindrop's AI capabilities into practical, repeatable workflows across Finance, RevOps, People, Recruiting, Customer Success, Marketing, and Legal." That's from What you’ll do first sentence. We can include that in About the role or Responsibilities. Probably better to put role description in About the role. Now Responsibilities: list of duties from "More specifically, you will:" bullet points. We need to capture each bullet as
  • . The bullets: - Map processes before touching AI. Sit with stakeholders, document current-state workflows end to end, extract the context and tools involved, and identify precisely where AI can reduce friction — not the other way around. - Build and manage a portfolio of internal AI tools, agentic workflows, and prompt-based copilots that solve discrete, measurable problems — and push every project past prototype into production. - Audit AI capabilities already built into tools Pindrop has purchased (e.g., Greenhouse, ERP) before standing up new solutions; use what we've paid for first. - Extend Pindrop's shared AI platform and agent infrastructure to new use cases rather than creating parallel stacks. - Design and implement the operating process that moves AI concepts from prototype to production, including evaluation, human-in-the-loop review, rollout criteria, and post-launch monitoring. - Consolidate learnings across functions — what worked in Finance should be usable in People; what worked in People should be accessible to CS — and build the tooling and documentation that makes reuse real. - Make the ROI case. Define success metrics, instrument usage, track adoption, and be able to explain clearly what the company is getting for its AI investment. - Drive adoption through practical enablement — workshops, onboarding paths, office hours, and coaching — focused on giving teams the guardrails they need to use AI well, not just permissively. Also there is earlier sentence: "The first 50% of your time will focus on Finance and RevOps; the rest goes where the highest-value problems are." That's also a responsibility. Could include as a bullet or paragraph. We'll include that as a bullet. Now Requirements/Qualifications: "Who you are" paragraphs: - A builder, not just a user. You've gone past prompting and into building — you have a GitHub (or equivalent) with projects that prove it. You've shipped agentic systems that solve real problems, and you know how different it feels when the last 20% actually works. - A process mapper first. Before you touch a tool, you understand the workflow. You can sit with a stakeholder, draw out what actually happens today, and find the leverage point — because you know you can't automate a process you haven't mapped. - Frontier-fluent and self-directed. You track what's happening at the edge of AI tooling because you're genuinely curious, not because it's required. You know the difference between AI theater and AI value, and you're allergic to the former. - A translator and teacher. You can walk into a Finance or HR meeting without owning their domain and still build credibility — through preparation, curiosity, and practical results. You get energy from turning a skeptic into a confident user. - Rigorously skeptical. You stress-test outputs, understand where models break down, and hold a high bar before recommending a workflow to a real team. You know what an eval is and why it matters. We could treat these as Requirements (or Qualifications). We'll make a section

    Requirements

    with
    • each. Now Skills: Must-haves and Nice-to-haves. Must-haves list: - Process mapping. This is the number-one requirement. You must be able to document a current-state workflow end to end, extract the tools and context involved, and use that map as the foundation for any AI solution. No map, no AI advantage. - 3+ years in product management, product operations, AI enablement, or a closely related role at a technology company — with PM-level ownership of scope, requirements, delivery, and metrics. - Hands-on experience with frontier AI CLIs and coding tools, including Codex, Claude Code, Anti-Gravity, and/or SuperGrok. We will ask to see what you've built. - Demonstrated ability to build agentic systems that solve a discrete, measurable problem — not a demo, a shipped solution. A GitHub profile showing 3–4 built projects is a strong signal; candidates without one will be asked to walk through their work in detail. - Fluency in context engineering and ontology design — ability to speak to both concepts and apply them in practice. - Conceptual command of test-driven development and eval-driven development for AI systems; must understand why evals matter and how to define them, even if you're not writing them by hand. - Proven ability to define success metrics, track adoption, and make the ROI case for AI investments to a skeptical stakeholder. Nice-to-haves list: - Experience with meta harnesses and multi