Staff Product Manager, Buyer Experience

We need to output HTML fragment with sections: About the role, Responsibilities (maybe "How You'll Contribute"), Requirements/Qualifications/Skills (maybe "What You'll Bring To Xometry"), Benefits, Pay, Schedule. Must not include boilerplate like EEO, E-Verify, etc. Must not repeat job title. Must not include Job ID. Must preserve all substantive info. Must not include placeholder sections. Must only include sections where there is real content. We need to parse the posting. Key sections: - About This Role: description paragraph. - How You'll Contribute: bullet list of contributions (Enterprise Ecosystem Growth, User Research and Insights, Problem Discovery, Product Strategy and Roadmap, Data-Driven Decisions and Accountability, Cross-Functional Collaboration and Enablement, Build and Ship with AI Agents). Each bullet has description. - What You'll Bring To Xometry: list of qualifications (10+ years experience, etc.) plus "Signals we look for" bullet list. - Pace: description about startup pace. - The estimated base salary range: Pay. - Benefits: description of benefits package. - Schedule: hybrid schedule (3 days a week) at Waltham, MA or North Bethesda, MD office location. We need to output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can combine some if content overlaps. The instruction: "Prefer a few substantive sections over many thin ones." So we can maybe have sections: About the role, Responsibilities, Qualifications (including experience, skills, signals), Benefits, Pay, Schedule. Avoid thin sections like Requirements if not distinct. We must use

for section headings. Use

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

  for prose. We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: equal opportunity, E-Verify, etc. We must preserve all substantive info. Let's craft. First, About the role: paragraph(s) from "About This Role" and maybe first paragraph after that. Content: "Xometry is looking for a driven, curious and customer obsessed Staff Product Manager to join its Buyer Experience group. In this role, you will manage the enterprise market segment - large enterprises that use Xometry to get their custom parts manufactured. Enterprise buyers bring a unique set of problems to solve: very large orders, procurement systems, complex purchase orders, contract terms, security and compliance reviews, and multiple stakeholders on a single account. Your job is to design self-service and human-assisted experiences inside that complexity, so an enterprise buyer gets the same frictionless quoting and ordering experience as anyone else, without giving up the controls and process their organization requires. You will define a 6-12 month forward-looking strategy for the enterprise segment, secure cross-functional buy-in across engineering, design, data science, category management, marketing, sales, legal/compliance and customer success, and hold accountability for outcomes that make quoting and ordering with Xometry frictionless for large accounts. You will be given a metric and a problem space, not a fully scoped backlog. Comfort defining your own roadmap from ambiguous signals is a requirement, not a bonus. This role requires a hybrid schedule (3 days a week) at our Waltham, MA or North Bethesda, MD office location." We might split schedule into its own section later. Now Responsibilities: from "How You'll Contribute" bullet points. List each bullet with description. We need to preserve each bullet's content. Let's extract: - Enterprise Ecosystem Growth: Own the enterprise quote-to-order funnel end to end, from procurement intake and account onboarding through repeat ordering. Run structured experiments on RFQ intake flows and multi-stakeholder approval steps, using the results to drive measurable lifts in enterprise activation, conversion, and account expansion, all while keeping the experience self-service or human assisted depending on the need. - User Research and Insights: Get very close to our enterprise customers and deeply understand the needs of all user personas - the engineer who needs the part, the procurement lead who has to source the part and the compliance reviewer who has to sign off, and their needs do not always line up. Gather feedback directly through interviews, surveys, and usage data, and then build creative solutions to solve their problems. - Problem Discovery: Proactively identify and define new problem spaces across the enterprise buyer lifecycle that will solve complex pain points for customers and drive the growth of our enterprise business. - Product Strategy and Roadmap: Define and own the product strategy and the roadmap, with clear outcomes and milestones you present to technical and non-technical audiences. - Data-Driven Decisions and Accountability: Set desired outcomes and define KPIs for each initiative you run. Monitor results closely and adjust priorities in real time, synthesizing findings into clear narratives for technical and non-technical audiences alike. - Cross-Functional Collaboration and Enablement: Secure alignment across engineering, design, data science, category management and marketing, and drive adoption of new capabilities through rollout strategy, in-app education, and customer communication. - Build and Ship with AI Agents: Operate spec-first. Translate your experimentation roadmap into structured, machine-executable specs that AI agents (Claude, Cursor) can build against, and work hand-in-hand with marketing, design, engineering and product analytics to prototype, validate, and ship statistically sound changes fast. Now Qualifications/Requirements/Skills: from "What You'll Bring To Xometry" and "Signals we look for" and "Pace". What You'll Bring To Xometry bullet list: - 10+ years of experience in product management, including direct ownership of an enterprise B2B or two-sided marketplace product. - Experience working with large enterprise customers and a track record of not just building features, but crafting solutions that fit into complex organizational structures and workflows. - AI-native, with hands-on fluency in tools like Claude and Cursor, and a track record of using them to compress the path from idea to validated, shipped product change. - Strong strategic and analytical skills, with a systems-thinking approach to managing complexity and trade-offs across multiple product areas. - Comfort making decisions under ambiguity, based on limited information, translating a loosely defined problem into a testable hypothesis and a plan. - Strong communication and influence skills, with the ability to align senior leadership and cross-functional partners without direct authority. - Proven ability to drive change within a fast-paced, scaling organization. - Bachelor's degree in Business, Computer Science, Engineering, or a related field. Signals we look for bullet list: - You can walk through a specific enterprise feature or workflow you redesigned: the friction you removed, and the before and after numbers, not just the shipped feature. - You have designed a product experience on a marketplace or B2B platform that supported large enterprise buyers with multiple personas whose needs did not always line up. - You have shipped an ML or AI powered feature into a complex flow with multiple organizational hierarchies. - You have worked on manufacturing, supply chain, or logistics products, or you can show how you learn unfamiliar operational domains fast. Pace paragraph: - Pace: This is a startup pace inside a public company. You will be given a metric and an open problem, not a scoped project plan, and you will be expected to quickly move from hypothesis to shipped test. If you do your best work with a clear brief and a stable backlog, this is not the right role. We could combine Qualifications and Signals into one section "What You'll Bring" maybe with subheadings? But we only allowed

  for section headings; we could have multiple

  sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Signals could be part of Qualifications. We need to avoid thin sections; we can combine Qualifications and Signals into one section with two lists: "Required Experience" and "Desired Signals". But we must use

  • for any list. Could have two
    under same section. Now Benefits: paragraph about competitive benefits package. Pay: paragraph about estimated base salary range $180,000 - 207,000 annually + bonus depending on factors such as job-related skills, relevant experience, and location. Schedule: hybrid schedule (3 days a week) at Waltham, MA or North Bethesda, MD office location. We must not include boilerplate like EEO, E-Verify, etc. Now produce HTML. Structure:

    About the role

    ... paragraphs ...

    Responsibilities

    • ...
    ...

    Qualifications

    Required experience:

    • ...
    ...

    Desired signals:

    • ...
    ...

    Pace: This is a startup pace inside a public company. You will be given a metric and an open problem, not a scoped project plan, and you will be expected to quickly move from hypothesis to shipped test. If you do your best work with a clear brief and a stable backlog, this is not the right role.

    Benefits

    We also offer a competitive benefits package, including 401(k) match, medical, dental and vision insurance; life and disability insurance; generous paid time off including vacation, sick leave, floating and fixed holidays, maternity and bonding leave; EAP, other wellbeing resources; and much more.

    Pay

    The estimated base salary range for new hires into this role is $180,000 - 207,000 annually + bonus depending on factors such as job-related skills, relevant experience, and location.

    Schedule

    This role requires a hybrid schedule (3 days a week) at our Waltham, MA or North Bethesda, MD office location.

    Check for any leftover boilerplate: removed equal opportunity, E-Verify, etc. Check for any placeholder text: none. Check for duplication: we didn't repeat job title. Check for preserving all substantive info: we included about role, responsibilities, qualifications (including degree), signals, pace, benefits, pay, schedule. Did we include the part about "You will define a 6-12 month forward-looking strategy..."? Yes in responsibilities bullet? Actually that was in About the role paragraph. We included that in About the role paragraph. Good. Check if we missed any piece: "You will be given a metric and a problem space, not a fully scoped backlog. Comfort defining your own roadmap from ambiguous signals is a requirement, not a bonus." That's in About the role paragraph? Actually we included that sentence in About the role? We included: "You will define a 6-12 month forward-looking strategy for the enterprise segment, secure cross-functional buy-in..., and hold accountability for outcomes that make quoting and ordering with Xometry frictionless for large accounts. You will be given a metric and a problem space, not a fully scoped backlog. Comfort defining your own roadmap from ambiguous signals is a requirement, not a bonus." Did we include that? In our About the role paragraph we wrote: "You will define a 6-12 month forward-looking strategy for the enterprise segment, secure cross-functional buy-in across engineering, design, data science, category management, marketing, sales, legal/compliance and customer success, and hold accountability for outcomes that make quoting and ordering with Xometry frictionless for large accounts. You will be given a metric and a problem space, not a fully scoped backlog. Comfort defining your own roadmap from ambiguous signals is a requirement, not a bonus." Yes we included that. Check if we missed "This role requires a hybrid schedule (3 days a week) at our Waltham, MA or North Bethesda, MD office location." That's in Schedule section. Check if we missed "Pace: This is a startup pace inside a public company..." we included in Qualifications section as a paragraph. Check if we missed "Signals we look for" bullet list: we included as Desired signals. Check if we missed "What You'll Bring To X