Staff Product Manager: Agentic Discovery

We need to output HTML fragment with sections: About Us? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Include a section only when posting has real, specific content. We need to extract content: About Us (company description) maybe as "About the role"? Actually "About Us" is company description. Could map to "About the role"? But we have "Job Summary". Could treat as "About the role". The instruction examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose headings that match content. We have sections: About Us (company overview), Job Summary (role description), What You'll Do (responsibilities), What Success Looks Like (maybe outcomes), What We're Looking For (requirements/qualifications/skills), Benefits. We should not include Pay or Schedule as not present. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need
  • . For requirements list also
    • . For benefits list also
      • . For prose use

        . We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: Diversity, EEO, data handling, etc. Also remove application instructions (none). Remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, maybe a short

        for metadata like location? Not needed. We'll start with

        About the role

        containing the About Us and Job Summary? Actually About the role could include company overview and job summary. But we might split: About Us as a paragraph, Job Summary as another paragraph. Both under same heading? Could be separate headings: About the role (company overview) and Job Summary (role description). But instruction says use headings for those specific examples; we can use multiple. Let's decide: -

        About the role

        : include company overview (About Us) and Job Summary (maybe combine). Could be two paragraphs. -

        Responsibilities

        : list of What You'll Do items. -

        Qualifications

        : What We're Looking For (experience, track record, etc.) Could also split into Requirements and Skills but we can combine. -

        Benefits

        : list of benefits. We must not include empty sections. Let's extract content precisely. About Us paragraph: "Constructor powers product search and discovery for some of the largest retailers in the world. We serve billions of requests every week, and you've probably seen our results somewhere and used our product without knowing it. We differentiate ourselves by focusing on metrics over features, and reinventing search and discovery from the ground up as a machine learning challenge with the specific goal of improving metrics like revenue. We're approximately doubling year over year despite the market slowing down and have customers in every eCommerce vertical. We're a passionate team of technologists who love solving problems and want to make our customers' and coworkers' lives better. We value empathy, openness, curiosity, continuous improvement, and are excited by metrics that matter. We believe that empowering everyone in a company to do what they think is best can lead to great things." Job Summary paragraph: "We're looking for a systems-minded, AI-native Staff Product Manager to help lead the next chapter of Constructor: Agentic Discovery. As commerce shifts toward agentic experiences, we're investing heavily in a portfolio of AI-powered surfaces — our AI Shopping Assistant, Product Insights Agent, Prism recommendations, and more to come — that change how shoppers discover products and how businesses run discovery. This is a high-leverage, high-ambiguity role. You'll own two things at once: helping our agentic experiences scale from promising experiments into a repeatable, reliable engine, and giving the business teams who depend on them the same transparency and control over agentic experiences that they have today over traditional search. You'll start by owning the business tooling and dashboards for agentic discovery — the experiences that let business teams see what our agents are doing, why, and to what effect, so they can execute faster and steer with confidence. Over time, your mandate grows to setting direction for the entire Agentic Discovery chapter: the on-site agentic experiences, the offsite/agentic surfaces, the integrations that connect them, and the agentic tooling underneath. This is a Staff role today with a clear path to Director as you take on chapter-wide leadership. Agentic discovery at Constructor is fundamentally an AI and machine learning problem, so this role lives and breathes it. You'll partner closely with ML, engineering, design, and go-to-market to turn new agentic capabilities into experiences that ship, prove value, and stay under our customers' control — and serve as the connective tissue that aligns multiple teams behind one coherent vision for agentic discovery. If you're excited about defining a brand-new category, being held to real usage and business outcomes, and giving businesses control over the AI experiences shaping their storefronts, this role is for you." Responsibilities list (What You'll Do): bullet points: - Own business impact, not features. Drive measurable lift in usage and business outcomes — conversion, revenue, engagement — across Constructor's agentic experiences. - Give businesses transparency and control. Build the dashboards and tooling that let business teams see what agentic experiences are doing, understand why, and steer them — closing the gap to the control they have in traditional search. - Scale experimentation. Turn one-off agentic experiments into a repeatable, scalable way to launch, measure, and improve new agentic interfaces — cutting time-to-launch. - Set chapter vision and strategy. Define the multi-quarter direction for Agentic Discovery — where we're heading and why — tie it to customer business outcomes, and rally teams behind it. - Lead the business-tooling and dashboard experience first. Own its strategy and roadmap, and make agentic behavior and impact visible and actionable for business users. - Orchestrate across surfaces. Unite on-site agentic experiences, offsite/agentic surfaces, and integrations behind one definition of agentic discovery success, so improvements compound instead of colliding. - Turn AI capability into shipped experiences. Partner with ML and engineering to take agentic and LLM-powered experiences from idea to production, balancing quality, latency, cost, and reliability. - Make success measurable. Define and instrument the metrics — go-live velocity, usage, engagement, business outcomes — that tell us whether agentic discovery is working. - Keep it trustworthy. Treat explainability, control, and guardrails as first-class requirements so customers trust and adopt agentic experiences. - Grow the mandate. Expand from business tooling into chapter-wide leadership across the full agentic portfolio and the integrations beneath it. We need to keep each as
      • . What Success Looks Like: Could be considered as part of responsibilities or outcomes; but we might not need separate section if not heading. Could incorporate into responsibilities? But it's separate content. Could make a section "What Success Looks Like" but not in allowed headings list. The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

        for section headings (e.g. ...)". Likely they expect only those headings. Safer to map Success Looks Like into Responsibilities or maybe Qualifications? But it's distinct. Could treat as part of Responsibilities (outcomes). However we must preserve all substantive information; we can include it as a

        under Responsibilities heading, or as a separate

        maybe "What Success Looks Like" but not in list; risk. Better to incorporate as a paragraph under Responsibilities after the list? Or as a separate

        "What Success Looks Like" but maybe acceptable. The instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. So we can use other headings as long as they are

        . I'd include a section for What Success Looks Like. Similarly, What We're Looking For could be Requirements/Qualifications/Skills. We'll split maybe into Requirements and Skills. Let's parse What We're Looking For bullet-like sentences: - Extensive product management experience (typically 8+ years) in AI/ML, agentic, search, or discovery products, including time operating at a senior or staff level. - A track record of moving business metrics at scale — usage, conversion, revenue, engagement — not just shipping features, and of setting strategy across multiple teams. - Experience building for business users/operators (merchandisers, category managers, or similar) — especially the tooling, dashboards, and controls they rely on. - Strong AI/ML/LLM product depth — understands how agentic and LLM-powered experiences work and can reason about their tradeoffs (quality, latency, cost, reliability). - Comfort with zero-to-one ambiguity and with scaling — able to experiment on brand-new interfaces and to build the repeatable process that turns them into a portfolio. - A rigorous, measurement-first mindset that ties every experience back to usage and business outcomes. - Excellent cross-functional leadership — able to align teams with different goals behind a shared definition of success, working shoulder-to-shoulder with ML, engineering, design, and go-to-market. - A strong instinct for trust — treating transparency, control, and guardrails as core to whether agentic experiences succeed. - Comfort setting direction where none exists yet, and leading through clarity and credibility rather than the org chart. We can treat these as Requirements (maybe also Skills). Could split into Requirements (experience, track record) and Skills (AI/ML depth, cross-functional leadership, etc.). But we can just have one section "Requirements" with list. Benefits list: - Unlimited vacation time — we strongly encourage all of our employees to take at least 3 weeks per year. - A competitive compensation package including stock options. - Company-sponsored US health coverage (100% paid for employee). - Fully remote team — choose where you live. - Work-from-home stipend! We want you to have the resources you need to set up your home office. - Apple laptops provided for new employees. - Training and development budget for every employee, refreshed each year. - Parental leave for qualified employees. - Work with smart people who will help you grow and make a meaningful impact. - This position is fully remote — Constructor.io is a remote-first company. Note: "This position is fully remote — Constructor.io is a remote-first company." is similar to earlier; we can keep. We must not include boilerplate like Diversity, EEO, data handling. Now craft HTML. We'll start with

        About the role

        containing two

        paragraphs: About Us and Job Summary. Then

        Responsibilities

        with
        • ... each. Then

          What Success Looks Like

          with

          paragraph(s) maybe bullet? It's a list of outcomes; we could make

          • . Let's do list. Content: Within your first year, you will have: - Shipped a dashboard and tooling experience that gives business teams real transparency into and control over Constructor's agentic experiences, adopted by internal teams and customers. - Driven measurable lift in the usage and business impact (conversion, revenue) of agentic experiences across multiple customers. - Stood up a repeatable process for launching and experimenting with new agentic interfaces, measurably shortening time-to-launch. - Defined the core metrics for agentic discovery and made them visible in one place. - Begun uniting the on-site, offsite, and integrations teams behind one coherent direction for the chapter. Make list. Then

            Requirements

            with