Senior Technical Program Manager - Pricing and Manufacturability

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 preserve all substantive info. Remove boilerplate like EEO, E-Verify, etc. Also remove application instructions (none). Must not create sections with filler like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting mentions hybrid schedule (3 days a week) at North Bethesda, MD or Waltham, MA office location. So schedule content exists. Pay: not mentioned. So we should not include Pay section. Benefits: they mention "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." That's specific enough to include Benefits section. Now need sections: About the role (role overview). Responsibilities (How You'll Contribute). Requirements/Qualifications/Skills: The posting has "What You'll Bring To Xometry" and "You Would Be A Great Fit With". Those contain qualifications, experience, skills. We need to split into sections: Requirements, Qualifications, Skills. The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. Likely: About the role = Role Overview paragraph. Responsibilities = How You'll Contribute bullet list. Requirements = maybe baseline requirements (10+ years experience etc). Qualifications = maybe "You Would Be A Great Fit With" details. Skills = maybe specific skills like stakeholder-management, program tooling, etc. But we must not invent or summarize away detail; we must preserve all substantive info. We can distribute content accordingly but must not lose info. Could also combine Requirements and Qualifications into one if not enough distinct content, but instruction says prefer few substantive sections over many thin ones. However we must include sections only when posting has real specific content for it. We have content for About the role, Responsibilities, What You'll Bring (which includes experience, qualifications, skills), Benefits, Schedule. We could map: About the role (role overview). Responsibilities (How You'll Contribute). Qualifications (What You'll Bring To Xometry + You Would Be A Great Fit With). Benefits (benefits package). Schedule (hybrid schedule). We could omit Requirements and Skills if not distinct. But we need to follow instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't say we must include all; we include only those with real content. So we can include About the role, Responsibilities, Qualifications, Benefits, Schedule. Omit Requirements, Skills, Pay. That seems acceptable. Now we need to format:

About the role

then

with the role overview text. Then

Responsibilities

then

• items from How You'll Contribute. Then

  Qualifications

  then maybe combine the two paragraphs into

  or

  . The content includes paragraphs and bullet-like sentences. We could use

  for prose and

  • for list. The "What You'll Bring To Xometry" is a paragraph with bullet-like sentences separated by line breaks. Could treat as
    • . Similarly "You Would Be A Great Fit With" also list-like. We'll combine them into one list under Qualifications. We must preserve all substantive information; not invent or summarize away detail. So we need to copy the text exactly (or close) but we can reformat into list items. Must not lose any detail. Let's extract. Role Overview paragraph: "As the first individual-contributor hire in our nascent TPM organization, you will set the bar for program excellence across Product & Technology. You will architect, run, and continuously improve the operational frameworks that keep our highest-value initiatives on track from roadmap definition and cross-team execution to release management and post-launch optimization. Partnering closely with Engineering, Product, Design, Data Science / ML, and Business Operations, you will both deliver complex programs and shape what it means to be a TPM at the company." Then there is a paragraph about Initial Project Xometry’s Instant Quoting platform... That seems part of role overview as well. Should we include that in About the role? Probably yes, as it's part of role overview. The instruction: About the role section heading. So we can include all descriptive paragraphs before How You'll Contribute. Thus About the role includes: - Role Overview paragraph. - Initial Project Xometry’s Instant Quoting platform paragraph (starting with "Xometry’s Instant Quoting platform is the core..."). We need to preserve that. Now Responsibilities: How You'll Contribute bullet points: List: - Own end-to-end program management for the Pricing & Manufacturability portfolio, with initial focus on Auto-Quote pricing/cost, DFM, Drawing AI, and related ML model work. - Drive program planning from concept through execution and post-launch analysis, including model evaluation, staged rollouts, and production monitoring. - Partner with Engineering, Product, Data Science / ML, Operations, Sales, and Finance to set realistic goals, timelines, and milestones across engine, model, and product workstreams. - Translate CAD/geometry, DFM, and Drawing AI work into a single sequenced plan clarifying what the models own, what product/UX owns, and where Buyer Experience, Pricing Experience, and P&M must handshake. - Implement lightweight, rigorous project management processes that increase execution speed, transparency, and accountability across multi-squad, model-plus-product delivery. - Lead risk management and mitigation model quality, data/labeling capacity, service latency, integration dependencies, and go-live readiness so blockers are visible before they slip dates. - Collaborate with senior leadership to prioritize initiatives, sequence model vs. product work, and manage stakeholder expectations. - Provide clear, concise, actionable communication on progress, risks, model/product trade-offs, and outcomes to executive teams. - Drive continuous improvement in execution and process, using quoting, DFM, and model-quality data to inform decisions. - Foster a high-performance culture across teams, keeping delivery aligned to company goals in a fast-paced, high-stakes environment. Now Qualifications: combine "What You'll Bring To Xometry" and "You Would Be A Great Fit With". What You'll Bring To Xometry paragraph: "Design and institutionalize lightweight but rigorous operating rhythms (intake, planning, risk management, status reporting, post-mortems) that scale with the business. Drive end-to-end execution of strategic, multi-team programs clarifying scope, aligning stakeholders, forecasting resources, and unblocking delivery. Serve as a senior thought partner to the Director of Technology Operations, codifying TPM best practices, mentoring future hires, and evolving the career ladder for the function. Act as a trusted communications hub, producing crisp executive readouts and facilitating decision-making forums that keep leadership focused on the right trade-offs. Champion continuous improvement by synthesizing lessons learned into updated playbooks, tooling, and training." That's a list of bullet-like sentences. You Would Be A Great Fit With: "10+ years of progressive experience in technical program management, engineering management, or product management, with at least three years leading cross-functional software initiatives of material business impact. Proven ability to create and scale operational processes in high-growth or transformation environments; start-up or “first-TPM-in” experience strongly preferred. Experience delivering programs that combine software platforms with ML/AI models in production (training, evaluation, deployment, monitoring, and product integration) or a demonstrated ability to partner closely with data science and ML engineering on that lifecycle. Deep understanding of modern SDLC practices (Agile, CI/CD, DevOps) and how to tailor them for speed, quality, and compliance; familiarity with ML delivery practices (experimentation, evaluation sets, staged rollout) is a plus. Exceptional stakeholder-management and influence skills from engineers, ML scientists, and product managers to C-level executives. Demonstrated mastery of program tooling (e.g., Jira, Google Sheets) and data-driven decision-making. Adept at balancing strategic thinking with hands-on execution; comfortable rolling up sleeves to remove blockers. Clear, concise communicator with a track record of producing executive-ready artifacts and leading high-stakes discussions. Experience with pricing engines, DFM / manufacturability, CAD/drawing intelligence, quoting platforms, or marketplace/adjacencies is a plus." We need to preserve all. We'll put each as
    • . Now 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." We'll put that in

      . Schedule: "This role requires a hybrid schedule (3 days a week) at our North Bethesda, MD or Waltham, MA office location." We'll put that in

      . Now ensure we removed boilerplate: EEO, equal opportunity, E-Verify, etc. Also removed "Xometry (NASDAQ: XMTR) powers the industries..." that's introductory fluff but maybe considered boilerplate? It's not a section heading; it's just introductory description of company. Should we keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The introductory sentence about Xometry powers industries is not boilerplate per se but could be considered company description; it's substantive? It's not about the role. Might be considered fluff but not explicitly prohibited. However we might keep it as part of About the role? It appears before Role Overview. Could be considered company overview, not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That sentence is substantive about company but not about role. Might be okay to keep. However the role overview already describes role; the introductory line may be considered filler. I'd lean to keep it as part of About the role? But it's not about the role. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." It doesn't say to drop company description. I'd keep it as a short paragraph under About the role maybe. But to be safe, we could include it as part of About the role paragraph before the role overview. It's not harmful. Now produce HTML fragment. We'll need to escape any special characters? Not needed. Let's craft:

      About the role

      Xometry (NASDAQ: XMTR) powers the industries of today and tomorrow by connecting the people with big ideas to the manufacturers who can bring them to life. Xometry’s digital marketplace gives manufacturers the critical resources they need to grow their business while also making it easy for buyers at Fortune 1000 companies to tap into global manufacturing capacity.

      As the first individual-contributor hire in our nascent TPM organization, you will set the bar for program excellence across Product & Technology. You will architect, run, and continuously improve the operational frameworks that keep our highest-value initiatives on track from roadmap definition and cross-team execution to release management and post-launch optimization. Partnering closely with Engineering, Product, Design, Data Science / ML, and Business Operations, you will both deliver complex programs and shape what it means to be a TPM at the company.

      Xometry’s Instant Quoting platform is the core of how buyers get a price, lead time, and manufacturability signal on a part. Pricing & Manufacturability (P&M) owns the engines and models behind that experience: Auto-Quote pricing and cost, Design