Principal Product Builder - AI & Agentic Products

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve substantive info. We need to parse the posting. Key sections: - About Amperity—Why This, Why Now: This is company description, not a required section heading. Could be placed under maybe "About the role"? Actually "About the role" is a heading we can use for description of role. The posting includes "The Role As a Principal Product Builder, AI and Agentic, you'll ensure customers adopt..." That's role description. So we can put that under

About the role

with paragraphs. - Then there is "Interesting Problems" with bullet points (Owning Outcomes Over Features, Judgment, Deepening Customer Connections, Crafting a Clear Narrative, Agent Optimized). Those are responsibilities? Could be under Responsibilities. - Then "About You" with bullet points (Customer Obsession, Technical Fluency, Systems Thinker, Thought Leadership, Collaborative and Humble, Always Learning Mindset, Navigating Ambiguity). Those are qualifications/requirements/skills. Could split into Requirements and Skills. - Then "Success Measures" with bullet points (AI product strategy, Customer adoption and value, Quality of execution, Trustworthy AI, Cross-platform leverage, Organizational influence, Market credibility). Those could be under maybe "Responsibilities" or "Success Measures"? Not a standard heading but we could treat as "Responsibilities" or maybe "Performance Expectations". But we only have allowed headings list. Could put under "Responsibilities" as they are success measures. - Location: Seattle, WA. Also schedule: "Amperity’s work model operates on four in-office days each week and one designated remote workday on Wednesdays." That's schedule info. So we can have Schedule section. - Compensation: Base Salary: $200,000-$280,000. Cash Incentives: Cash incentives are also available. Stock Options: opportunity for ownership... That's Pay section. - Benefits: paragraph about benefits. Thus we will create sections:

About the role

with paragraph(s) from The Role description.

Responsibilities

with list from Interesting Problems and Success Measures? Might be too many. Could separate: Responsibilities (Interesting Problems) and maybe "Success Measures" not a standard heading; but we could incorporate into Responsibilities as well. However we need to avoid thin sections. Could combine Interesting Problems and Success Measures into Responsibilities as a list. But we also have "About You" which could be Requirements (or Qualifications) and Skills. We need to decide: Use headings: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We must not create sections with placeholder/filler. Ensure each has real content. Let's extract content. About the role: "The Role As a Principal Product Builder, AI and Agentic, you'll ensure customers adopt and realize genuine value from what we build — often across multiple outcomes at once, connecting pain points to technical strategy and company growth. You'll stay connected with customers and stakeholders across their journey, including the highest-stakes conversations and escalations. That connection informs our most critical product decisions. You're a systems thinker who runs toward the most ambiguous problems — figuring out what's worth building, why, and for whom, often across more than one project. You bring real technical depth, including direct, hands-on experience building agentic systems yourself — that's what lets you help shape and elevate Amperity's own agentic strategy, not just advise on it from the sidelines. Backlog management and roadmap coordination are part of the job, but your focus is outcomes: building things that matter to customers." We can put that as paragraphs. Responsibilities: combine Interesting Problems bullet points and Success Measures bullet points. Interesting Problems bullet points: - Owning Outcomes Over Features: You own high-impact outcomes end-to-end rather than fixed feature sets—measuring success by real shifts in customer behavior, adoption, and value. - Navigating high-risk or ambiguous challenges across projects, you empower your team with clarity while defining and aligning with broader strategic goals. - Judgment: You know what to pursue or deprioritize and when to make decisions independently versus seeking alignment. You keep projects aligned with strategy, course-correcting as needed. Partners trust your clarity, and you proactively identify risks and help define future outcomes. - Deepening Customer Connections: Engaging customers and stakeholders directly to shape product direction. You set the tone for team engagement and lead high-stakes conversations with executives and technical architects, even during escalations or when requirements are ambiguous. - Crafting a Clear Narrative: You clearly explain what we are building, why customers need it, and how they benefit—making this narrative resonate internally and externally. You also connect individual capabilities to the broader system-level strategy. - Agent Optimized: You determine the best agentic approach for customer needs—whether via agents, workflows, or new interactions. You guide clients as a thought leader and help shape Amperity's strategic direction as technology evolves. Success Measures bullet points: - AI product strategy. Amperity has a clear, differentiated point of view on AI and agentic products, reflected in focused investment choices and a roadmap teams can act on. - Customer adoption and value. The capabilities you lead are adopted in real customer workflows and produce measurable improvements in time to value, product usage, retention, expansion, or other agreed business outcomes. - Quality of execution. High-risk ideas are tested early, teams make sound decisions with less ambiguity, and the work moves from discovery to reliable production outcomes without losing sight of the customer problem. - Trustworthy AI. Products meet practical standards for evaluation, explainability, privacy, safety, reliability, and human oversight, earning the confidence of enterprise customers and internal stakeholders. - Cross-platform leverage. The solutions and product decisions you shape strengthen multiple workflows, squads, or product surfaces rather than optimizing one feature in isolation. - Organizational influence. Product, Engineering, Design, and go-to-market leaders use your judgment to make better portfolio and customer decisions, and other Product Builders become more effective through your mentorship and example. - Market credibility. Customers, prospects, partners, and industry stakeholders understand Amperity’s AI advantage and increasingly look to the company for a practical point of view on agentic customer data products. We can combine these into a

• list. Requirements: from About You bullet points that are more like qualifications: Customer Obsession, Technical Fluency, Systems Thinker, Thought Leadership, Collaborative and Humble, Always Learning Mindset, Navigating Ambiguity. Could be Requirements. Skills: maybe we could separate technical skills: "You prototype quickly using AI tools and low-code integrations, and can test ideas directly in a codebase. While engineering owns production architecture, hands-on experience with agentic frameworks, tool use, and context engineering is required." That's from Technical Fluency bullet. Could be Skills. But we need to avoid duplication. Let's assign: Requirements: list of the bullet points under About You (Customer Obsession, Technical Fluency, Systems Thinker, Thought Leadership, Collaborative and Humble, Always Learning Mindset, Navigating Ambiguity). Each as
• . Skills: maybe we can extract "hands-on experience with agentic frameworks, tool use, and context engineering" as a skill. Also "prototype quickly using AI tools and low-code integrations". Could be separate. But we might combine Requirements and Skills into one section? The instruction says we can have sections for Requirements, Skills, etc. We'll create both if we have distinct content. Let's extract: From About You: - Customer Obsession: You focus on customer value over novelty. You understand their true goals, validate ideas directly through prototypes or feedback before shipping, and actively support internal teams to ensure real impact. - Technical Fluency: You prototype quickly using AI tools and low-code integrations, and can test ideas directly in a codebase. While engineering owns production architecture, hands-on experience with agentic frameworks, tool use, and context engineering is required. - Systems Thinker: You continuously deepen your understanding of Amperity's end-to-end architecture and data flows to make informed product decisions. You understand the broader ecosystem to complement, integrate, or differentiate effectively, navigating complex use cases and integrations. - Thought Leadership: You are a customer data expert who understands the value and challenges of brand data. You proactively propose forward-thinking ideas, serving as a key driver of innovation for Amperity. This includes building for end users, AI agents using Amperity as infrastructure, and shaping context engineering to deliver maximum agent value. - Collaborative and Humble: You build cross-functional trust, seek help when needed, and actively mentor and onboard fellow Product Builders. - Always Learning Mindset: You don't assume you already know the answer — you validate and expand what you believe through your own research and by leaning on others, and you're ready to adjust when the evidence points somewhere new. - Navigating Ambiguity: You're comfortable without a fixed playbook — what customers need next, and how to build it, keeps shifting. You're handed outcomes, not features, often without a defined path, and you figure it out alongside your team. You're just as comfortable walking into a customer conversation without every answer, making good use of whatever context you have. We could treat each as requirement. Skills: maybe we can pull out "hands-on experience with agentic frameworks, tool use, and context engineering" and "prototype quickly using AI tools and low-code integrations". But those are already in Technical Fluency bullet. Could still list as skills. But to avoid duplication, we could make Requirements be the list of the bullet points (excluding the technical fluency details) and Skills be the specific technical abilities: "Prototyping with AI tools and low-code integrations; hands-on experience with agentic frameworks, tool use, and context engineering." Let's craft. Benefits: paragraph: "We offer all the benefits you'd expect from a great place to work: comprehensive healthcare coverage with a choice of medical plan options, transportation subsidies, a comfortable work environment with plenty of snacks, and employee experience programs and perks. We also offer self-managed PTO and the flexibility to do your best work in the way that works for you. We provide an inclusive environment where you'll be challenged to find and unlock your full potential, surrounded by a team of world-class people driving for excellence." Pay: Base Salary: $200,000-$280,000. Cash Incentives: Cash incentives are also available. Stock Options: The opportunity for ownership is an exciting part of Amperity’s total compensation package. Every employee at Amperity receives a new-hire equity grant, commensurate with the scope of their position. Schedule: Location Seattle, WA and work model: four in-office days each week and one designated remote workday on Wednesdays. We should not include location as separate heading; we can include location in Schedule section or maybe a short paragraph. Since we have Schedule heading, we can include both location and schedule. Now produce HTML:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  ...

  Pay

  ...

  Schedule

  ...

  Make sure no extra sections like About Amperity etc. Check for any boilerplate: we removed EEO etc. Now craft content precisely. About the role paragraph: we can keep as two sentences maybe. Let's write:

  As a Principal Product Builder, AI and Agentic, you'll ensure customers adopt and realize genuine value