Senior Technical Program Manager - Pricing and Manufacturability
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. The posting includes: Role Overview (we can treat as About the role). How You'll Contribute (Responsibilities). What You'll Bring To Xometry (Qualifications/Requirements/Skills). Compensation & Benefits (Pay and Benefits). Also schedule: hybrid schedule (3 days a week) at North Bethesda, MD or Waltham, MA office location. So we have Schedule section.
We must not repeat job title as heading. No Job ID. Remove boilerplate: equal opportunity, E-Verify, etc. Also remove "#Promoted". Also remove navigation etc.
We need to preserve all substantive information. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Possibly combine some. The instruction: Prefer a few substantive sections over many thin ones. But we must use those headings only if we have content. We can include About the role (role overview). Responsibilities (How You'll Contribute). Requirements/Qualifications/Skills (What You'll Bring). Benefits (Compensation & Benefits includes benefits). Pay (Compensation & Benefits includes salary). Schedule (hybrid schedule). We could combine Requirements, Qualifications, Skills into one section? But they said use headings for each if content exists. Could combine them into one heading like "Requirements" and include qualifications and skills inside. But they said use headings for each: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It might be okay to have multiple headings; but they said prefer a few substantive sections over many thin ones. However we need to follow instruction: use those headings for section headings. It doesn't say we must use all; we can use only those that have content. We have content for each: About the role, Responsibilities, Requirements (maybe combine qualifications and skills), Benefits, Pay, Schedule. Could also separate Qualifications and Skills if we want. But we can put qualifications and skills under Requirements heading, or we could have separate Qualifications and Skills headings with content. Let's see content: "What You'll Bring To Xometry" includes design and institutionalize..., drive end-to-end execution..., serve as senior thought partner..., act as trusted communications hub..., champion continuous improvement..., You Would Be A Great Fit With ... (experience requirements). That includes qualifications and skills. Could split: Requirements (experience, years) and Qualifications (specific abilities) and Skills (soft skills). But we can keep it simple: one section "Requirements" containing all.
But the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not mandatory to use all. So we can choose.
We'll output:
About the role
... role overview ...
Responsibilities
- ... each duty ...
Requirements
- ... each requirement/qualification/skill ...
Benefits
- ... benefits list ...
Pay
... salary range ...
Schedule
Hybrid schedule (3 days a week) at our North Bethesda, MD or Waltham, MA office location.
We must preserve all substantive information. Let's extract.
About the role: The 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."
Also there is "Initial Project Xometry’s Instant Quoting platform..." That's more detail about the project. Should be included in About the role or maybe Responsibilities? It describes the initial project focus. Could be part of About the role. We'll include that as part of About the role.
Responsibilities: from "How You'll Contribute" bullet list (though not bullet but sentences). We need to convert to list items.
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.
Also there is a second set under "What You'll Bring To Xometry" that includes responsibilities? Actually that's more about what you'll bring (qualifications). But there is also a list: "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."
These could be considered responsibilities as well. But they are under "What You'll Bring To Xometry" which is more about qualifications. However they are responsibilities/expectations. To avoid duplication, we could treat them as part of Requirements/Skills. But they are more like duties. However we already have a responsibilities list from "How You'll Contribute". We could add these as additional responsibilities. To preserve all substantive info, we should include them. Perhaps we can merge them into Responsibilities as additional items.
Thus Responsibilities list will combine both sets.
Now Requirements/Qualifications/Skills: from "What You'll Bring To Xometry" includes:
- 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.
- 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 put these into a list under Requirements heading.
Benefits: from "Compensation & 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 should list each benefit as - .
Pay: "The estimated base salary range for new hires into this role is $135,000-$155,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 North Bethesda, MD or Waltham, MA office location."
Now we need to output only HTML fragment, no markdown fences.
Let's craft.
We'll need to escape any HTML special characters? Not needed.
We'll produce:
About the role
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. Initial Project 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 for Manufacturability (DFM) / geometry analysis, Drawing AI (CAD and 2D drawing interpretation), and the ML models that predict cost, lead time, and drawing intelligence. The Sr. Technical Program Manager will work with senior leadership, engineering, product, data science, and business teams to deliver these capabilities end to end from model and service work through product integration, operations, and post-launch improvement. That includes coordinating how CAD models and drawings move through geometry, DFM, and Drawing AI services, how ML
for prose. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Possibly combine some. The instruction: Prefer a few substantive sections over many thin ones. But we must use those headings only if we have content. We can include About the role (role overview). Responsibilities (How You'll Contribute). Requirements/Qualifications/Skills (What You'll Bring). Benefits (Compensation & Benefits includes benefits). Pay (Compensation & Benefits includes salary). Schedule (hybrid schedule). We could combine Requirements, Qualifications, Skills into one section? But they said use headings for each if content exists. Could combine them into one heading like "Requirements" and include qualifications and skills inside. But they said use headings for each: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It might be okay to have multiple headings; but they said prefer a few substantive sections over many thin ones. However we need to follow instruction: use those headings for section headings. It doesn't say we must use all; we can use only those that have content. We have content for each: About the role, Responsibilities, Requirements (maybe combine qualifications and skills), Benefits, Pay, Schedule. Could also separate Qualifications and Skills if we want. But we can put qualifications and skills under Requirements heading, or we could have separate Qualifications and Skills headings with content. Let's see content: "What You'll Bring To Xometry" includes design and institutionalize..., drive end-to-end execution..., serve as senior thought partner..., act as trusted communications hub..., champion continuous improvement..., You Would Be A Great Fit With ... (experience requirements). That includes qualifications and skills. Could split: Requirements (experience, years) and Qualifications (specific abilities) and Skills (soft skills). But we can keep it simple: one section "Requirements" containing all. But the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not mandatory to use all. So we can choose.
We'll output:
About the role
... role overview ...
Responsibilities
- ... each duty ...
Requirements
- ... each requirement/qualification/skill ...
Benefits
- ... benefits list ...
Pay
... salary range ...
Schedule
Hybrid schedule (3 days a week) at our North Bethesda, MD or Waltham, MA office location.
We must preserve all substantive information. Let's extract. About the role: The 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." Also there is "Initial Project Xometry’s Instant Quoting platform..." That's more detail about the project. Should be included in About the role or maybe Responsibilities? It describes the initial project focus. Could be part of About the role. We'll include that as part of About the role. Responsibilities: from "How You'll Contribute" bullet list (though not bullet but sentences). We need to convert to list items. 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. Also there is a second set under "What You'll Bring To Xometry" that includes responsibilities? Actually that's more about what you'll bring (qualifications). But there is also a list: "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." These could be considered responsibilities as well. But they are under "What You'll Bring To Xometry" which is more about qualifications. However they are responsibilities/expectations. To avoid duplication, we could treat them as part of Requirements/Skills. But they are more like duties. However we already have a responsibilities list from "How You'll Contribute". We could add these as additional responsibilities. To preserve all substantive info, we should include them. Perhaps we can merge them into Responsibilities as additional items. Thus Responsibilities list will combine both sets. Now Requirements/Qualifications/Skills: from "What You'll Bring To Xometry" includes: - 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. - 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 put these into a list under Requirements heading. Benefits: from "Compensation & 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 should list each benefit asAbout the role
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. Initial Project 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 for Manufacturability (DFM) / geometry analysis, Drawing AI (CAD and 2D drawing interpretation), and the ML models that predict cost, lead time, and drawing intelligence. The Sr. Technical Program Manager will work with senior leadership, engineering, product, data science, and business teams to deliver these capabilities end to end from model and service work through product integration, operations, and post-launch improvement. That includes coordinating how CAD models and drawings move through geometry, DFM, and Drawing AI services, how ML