Configuration Management CAD Specialist

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We have description: "Description The Configuration Management CAD Specialist administers, supports, and optimizes Computer-Aided Design (CAD) tools and the PTC Windchill Product Lifecycle Management (PLM) system. This role ensures engineering data integrity, manages CAD data and product structures, supports configuration management processes, and partners with engineering, manufacturing, quality, and IT teams to keep product development workflows running smoothly." That's about the role. So we can have

About the role

with that paragraph. Key Responsibilities list: we need

Responsibilities

with

• each bullet. Required Qualifications: we can treat as Requirements? The spec says we can have Requirements and Qualifications sections. We have both Required Qualifications and Preferred Qualifications. Could combine into Requirements (required) and Qualifications (preferred) or Skills. Let's decide: Use Requirements for required qualifications, Qualifications for preferred qualifications. Also Skills maybe from required qualifications like analytical, troubleshooting, communication, etc. But we can also put those under Skills. However we must not create thin sections. Let's see content: Required Qualifications includes bullet-like sentences separated by periods. Could be turned into
  . Preferred Qualifications also bullet-like. Working Conditions maybe could be Schedule? Not exactly. There's "Working Conditions Office environment. Occasional travel (up to 10%). Availability to support engineering teams during product releases and system maintenance windows." That could be Schedule? Not exactly schedule but maybe we can put under Schedule if we have specific schedule info. There's no explicit schedule like full-time, shift. So we should not create Schedule section unless posting actually states them. It mentions occasional travel and availability during releases, but not a schedule. Probably we should not create Schedule. Pay: we have Pay Range $73,450.00 - $132,775.00. So we should include Pay section with that info. Benefits: there is a Pay And Benefits section later: "Pay and benefits are fundamental to any career decision... Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." That's benefits info. So we can include Benefits section with that list. Also there is "About Leidos" but that's boilerplate? It's about company, maybe not needed. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Leidos might be considered boilerplate? It's not EEO but it's generic company description. Might be considered not substantive to the role. Probably we should drop it. Also "Securing Your Data" etc is scam-warning boilerplate, remove. "Commitment to Non-Discrimination" is EEO boilerplate, remove. Success Factors: maybe could be Skills? It says "The successful candidate will bring strong technical expertise in SolidWorks and PTC Windchill, maintain exceptional attention to detail, promote data quality and process compliance, and partner effectively with engineering and business stakeholders to improve product development efficiency." That's skills/attributes. Could go under Skills. We also have "If you're looking for comfort, keep scrolling..." that's fluff, remove. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all substantive content from description, responsibilities, required qualifications, preferred qualifications, working conditions, success factors, pay, benefits. We must not repeat job title as heading. Already not. We must not put Job ID/requisition numbers as headings; none present. We need to output only HTML fragment. Let's structure:

  About the role

  The Configuration Management CAD Specialist administers, supports, and optimizes Computer-Aided Design (CAD) tools and the PTC Windchill Product Lifecycle Management (PLM) system. This role ensures engineering data integrity, manages CAD data and product structures, supports configuration management processes, and partners with engineering, manufacturing, quality, and IT teams to keep product development workflows running smoothly.

  Responsibilities

  • Administer and support PTC Windchill PLM, including document management, part structures, workflows, lifecycles, and access controls.
  • Manage CAD data for engineering teams, ensuring proper revision control, release processes, and data integrity.
  • Support integration between Windchill and CAD applications such as Creo, SolidWorks, AutoCAD, and other supported engineering tools.
  • Develop, maintain, and improve CAD and PLM standards, procedures, templates, and best practices.
  • Troubleshoot CAD and Windchill issues, providing timely technical support and user training.
  • Coordinate change requests (CRs), change notices (CNs), and release workflows.
  • Develop and maintain Bills of Material (BOMs), product structures, and related engineering documentation.
  • Perform data migration, validation, and cleanup for legacy and new product information.
  • Collaborate with Configuration Management, Engineering, Manufacturing, Supply Chain, and Quality teams to ensure compliance with company and customer requirements.
  • Support software upgrades, testing, and rollout of new Windchill and CAD capabilities.
  • Generate reports, dashboards, and metrics on engineering data and PLM performance.
  • Maintain system documentation, user guides, and training materials.
  • Ensure compliance with company quality standards, cybersecurity requirements, and applicable industry regulations.

  Requirements

  • Bachelor's degree in Engineering, Information Systems, Computer Science, or a related technical field; equivalent experience considered.
  • 4+ years of experience supporting CAD systems and PTC Windchill in an engineering environment.
  • Experience with PTC Windchill administration, engineering document control, and configuration management.
  • Working knowledge of CAD software, particularly SolidWorks but could also include Creo, AutoCAD, or similar platforms.
  • Solid understanding of product lifecycle management principles and engineering change processes.
  • Experience with BOM management and product structure maintenance.
  • Strong analytical, troubleshooting, and problem-solving skills.
  • Excellent written and verbal communication skills.
  • Ability to work independently while supporting cross-functional teams.

  Qualifications

  • Experience with PTC Windchill administration and workflow configuration.
  • Experience in aerospace, defense, manufacturing, or other regulated industries.

  Skills

  The successful candidate will bring strong technical expertise in SolidWorks and PTC Windchill, maintain exceptional attention to detail, promote data quality and process compliance, and partner effectively with engineering and business stakeholders to improve product development efficiency.

  Working Conditions

  Office environment. Occasional travel (up to 10%). Availability to support engineering teams during product releases and system maintenance windows.

  Pay

  Pay Range $73,450.00 - $132,775.00

  Benefits

  • Competitive compensation
  • Health and Wellness programs
  • Income Protection
  • Paid Leave
  • Retirement
  We need to ensure we didn't include any boilerplate. We omitted About Leidos, Pay And Benefits paragraph (we used benefits list). We omitted the "Pay And Benefits" heading text but we captured benefits. We omitted the "Securing Your Data", "Commitment to Non-Discrimination", "Original Posting September 17, 2026", "For U.S. Positions..." etc. Also we omitted the "If you're looking for comfort..." etc. Check if any content lost: The description about the role we captured. Responsibilities captured all bullet points. Required qualifications captured all. Preferred qualifications captured two bullets. Working conditions captured. Success factors captured as Skills. Pay captured. Benefits captured from the Pay And Benefits section: "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." We turned into list. We omitted the line "Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers." That's somewhat fluff but maybe considered substantive? It's generic. Might be considered boilerplate? It's not specific to the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories, but it's generic fluff. Might be considered boilerplate? Safer to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That sentence is substantive? It's generic but still part of posting. However it's not specific to the role; but it's still part of the posting. The instruction didn't say to remove generic marketing fluff. Only specified certain boilerplate types. So maybe we should keep it. However we already have Benefits section with list; we could add a paragraph before list: "Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers." That would be substantive. Let's add that as a

  before the

  in Benefits. Similarly, there is a line "More details are available at www.leidos.com/careers/pay-benefits." That's a link; could be considered application instruction? It's more info. Might be considered not essential but it's a detail. The instruction: remove application instructions. This is not an instruction to apply, just a link for more details. Might be okay to keep? Safer to keep? But it's a URL; could be considered not substantive? It's a reference. I'd keep it as a

  maybe. Also there is "Pay And Benefits Pay and benefits are fundamental..." Actually the heading "Pay And Benefits" appears then the paragraph. We already used Benefits heading. We could keep the paragraph. Also there is "For more information, visit www.Leidos.com." under About Leidos; we removed About Leidos entirely. That line is part of About Leidos; we removed that section. Might be okay. Also there is "Original Posting September 17, 2026" and "For U.S. Positions: While subject to change..." That's metadata about posting; not job specifics. Could be considered metadata; instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. This is minor metadata; we could drop it or fold into a short p. Probably drop it to keep concise. Also there is "Step 10 is ancient history..." etc fluff; remove. Thus final HTML includes sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Working Conditions, Pay, Benefits. We need to ensure we don't have empty sections. All have content. Let's craft final HTML. Be careful to escape any HTML special characters? Not needed. We'll output:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...

  Qualifications

  ...

  Skills

  ...

  Working Conditions

  ...

  Pay

  Pay Range $73,450.00 - $1