Forward Deployed Design Lead — Product Lifecycle Management

We need to output HTML fragment with sections: About the role? Actually we have sections: About Avathon (maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the job posting and produce sections. We have content: "Who We Are & Why Join Us" (some description). Then "About Avathon" repeated. Then "About The Role". Then "Key Responsibilities". Then "PLM Platform Proficiency". Then "Preferred Qualifications". Then "Qualifications". Then "Compensation & Benefits". Then EEO boilerplate (remove). Also there is "Learn more at: avathon.com" maybe minor metadata. We need to decide which sections to include: The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: from "About The Role" paragraph(s). That's a prose description. - Responsibilities: from "Key Responsibilities" (multiple bullet-like paragraphs). We'll need to convert each bullet into

  • . The text includes multiple paragraphs each starting with a bold heading? Actually they are headings like "PLM Implementation & Configuration", "Experience Design & Workflow Mapping", "User Adoption & Change Management", "Client Engagement & Delivery". Under each there are bullet-like sentences. We could treat each of those as separate
    maybe with subheadings? But instruction says use

    for section headings, and

    • for any list of duties/requirements/benefits. So we could have a section

      Responsibilities

      then a
      containing each duty as
      • . We need to preserve all substantive information; we can break down each duty into separate
      • items. - Requirements: maybe combine "PLM Platform Proficiency", "Preferred Qualifications", "Qualifications". But we need to decide if we should have separate sections for Requirements and Qualifications? The instruction list includes Requirements and Qualifications as possible headings. We could combine all qualification-like content under a single

        Qualifications

        (or Requirements). But we need to avoid thin sections. Perhaps we can have one Qualifications section that includes all: PLM Platform Proficiency (mandatory), Preferred Qualifications (preferred), Qualifications (basic). Could also split into Requirements (mandatory) and Preferred Qualifications (preferred). But instruction says prefer a few substantive sections over many thin ones. So maybe we have two sections: Responsibilities and Qualifications (which includes both mandatory and preferred). Or we could have About the role, Responsibilities, Qualifications, Benefits. Pay is present: "California Base Salary: $170,000 - $200,000". That's pay info, so we should include a Pay section. Benefits: there is a list: Equity, health coverage, 401k, PTO, travel expenses. So Benefits section. Schedule: not mentioned (maybe remote Fridays? Actually they said Fridays are typically remote for synthesis, documentation, and cross-team collaboration. That's schedule info? Could be considered schedule. But it's not explicit schedule like full-time, etc. Might be considered schedule but it's not a clear schedule statement. The instruction says never create Schedule section unless posting actually states them. It does mention Fridays remote, which is a schedule detail. Could include under About the role or Responsibilities? Probably better to include a Schedule section with that detail. However they said "Prefer a few substantive sections over many thin ones." Adding a Schedule section with just one sentence might be thin. Could incorporate into About the role or Responsibilities. I'd lean to not create a separate Schedule section unless there is explicit schedule like "Full-time", "Mon-Fri". The remote Friday detail is more about work arrangement; could be included in About the role. Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits. We need to remove duplicated lines and boilerplate. Also remove "Learn more at: avathon.com" maybe minor metadata; could be placed in a short

        if we want but instruction says fold minor metadata into a short

        or drop it. We can drop it. Now we need to preserve all substantive information. Let's extract. About the role: The paragraph(s) under "About The Role": "The Forward Deployed Design Lead — PLM is embedded directly at customer sites as the primary experience and implementation owner for Avathon's Product Lifecycle Management deployments. You live at the intersection of PLM domain knowledge and experience design, responsible for configuring, implementing, and continuously improving how engineering teams, manufacturing planners, and quality engineers interact with Avathon's AI layer across their PLM environment. You will spend Monday through Thursday working alongside CAD engineers, PLM administrators, and manufacturing process owners — mapping BOM workflows, configuring integrations with PLM and ERP systems, designing the screens and workflows users will rely on daily, and driving adoption from go-live through steady-state operations. Fridays are typically remote for synthesis, documentation, and cross-team collaboration." We need to preserve that. Could be a

        . Responsibilities: We need to extract each duty from the sections under Key Responsibilities. Let's list them: Under "PLM Implementation & Configuration": - Own end-to-end implementation of Avathon's AI platform within customer PLM environments — configuring product structure hierarchies, BOM variants, change workflow rules, and AI-enriched analytics views to match each customer's engineering and manufacturing context - Lead functional configuration of PLM-adjacent modules: engineering change order (ECO) tracking, eBOM/mBOM/sBOM linkage, part master data enrichment, effectivity management, and configuration control workflows aligned to customer standards - Set up and validate integrations between Avathon's platform and customer PLM systems (Siemens Teamcenter, PTC Windchill, Dassault 3DEXPERIENCE, SAP PLM, Oracle Agile PLM) — ensuring BOM data, change notifications, and lifecycle state transitions flow accurately and traceably - Configure data pipelines from CAD/PDM sources and ERP systems — validating part metadata extraction, revision mapping, and BOM hand-off logic in live engineering environments - Conduct go-live readiness checks — verifying integration health, data completeness, user access, and workflow configuration before each deployment milestone Under "Experience Design & Workflow Mapping": - Lead onsite discovery and process mapping sessions — working directly with PLM administrators, CAD engineers, manufacturing engineers, and IT architects to document current-state workflows and define the future-state experience on Avathon's platform - Produce implementation-grade design artifacts: annotated screen flows, configured BOM view layouts, change workflow diagrams, alert routing specs, and role-based dashboard definitions — directly actionable by the engineering team without further interpretation - Design and validate end-user interfaces within Avathon's PLM-adjacent surfaces: BOM comparison views, engineering change dashboards, digital thread navigation, and AI-driven part similarity and anomaly detection screens - Facilitate working sessions with engineering and manufacturing stakeholders to validate designs against real workflow scenarios — iterating in real time based on user feedback before configuration is locked - Ensure designs reflect the operational realities of PLM users: structured review cycles, multi-discipline concurrency, cross-site data sharing, and the precision demands of engineering documentation and compliance Under "User Adoption & Change Management": - Design and execute role-specific onboarding programs — building training plans, hands-on exercises, quick-reference guides, and SOPs tailored to how each PLM user group (PLM administrator, design engineer, manufacturing planner, quality engineer, change board member) will use Avathon daily - Conduct live training sessions and hands-on working sessions at client sites — coaching engineering teams through new AI-augmented change management and BOM analytics capabilities with the domain credibility to earn their trust - Identify adoption barriers early — distrust of AI-generated insights, workflow disruption, data quality concerns — and develop targeted interventions in partnership with client PLM leads and process owners - Track adoption metrics post-go-live (active users, change workflow utilization, BOM accuracy rates, AI recommendation acceptance) and use data to drive continuous improvement sprints with the client - Serve as the primary point of contact for end-user questions, configuration requests, and workflow adjustments during hypercare — escalating to engineering only when platform-level changes are required Under "Client Engagement & Delivery": - Act as the day-to-day client contact for all design, configuration, and adoption activities — building trusted working relationships with engineering leads, PLM system owners, and IT integration teams - Facilitate weekly client working sessions, design reviews, and sprint demos that keep stakeholders aligned, engaged, and confident in the deployment's progress - Maintain implementation documentation — configuration logs, integration specs, training materials, and acceptance test records — that serve as the client's operational handbook post go-live - Capture PLM workflow patterns, integration approaches, and configuration best practices from each engagement and contribute them to Avathon's delivery playbooks, accelerating future PLM implementations - Identify opportunities to expand Avathon's footprint within accounts — additional PLM modules, new user populations such as supply chain or service engineering, or adjacent use cases in quality and manufacturing — and surface them to the engagement director Now Qualifications: We have PLM Platform Proficiency (mandatory), Preferred Qualifications, Qualifications (basic). Let's extract. PLM Platform Proficiency: - Candidates should have hands-on implementation or configuration experience with one or more enterprise PLM platforms — such as Siemens Teamcenter, PTC Windchill, Dassault Systèmes 3DEXPERIENCE/ENOVIA, SAP PLM, or Oracle Agile PLM — as well as familiarity with mid-market and cloud-native solutions including Aras Innovator, Arena PLM, Autodesk Vault, or Propel PLM. - Experience integrating PLM environments with adjacent systems — ERP platforms (SAP S/4HANA, Oracle ERP Cloud, Microsoft Dynamics 365), CAD tools (Siemens NX, PTC Creo, CATIA, SolidWorks), MES execution systems, and quality management workflows (FMEA, APQP, PPAP, CAPA) — is strongly valued. Preferred Qualifications: - 6+ years of experience in PLM implementation, industrial systems delivery, or a UX/design role embedded in client-facing delivery — with hands-on configuration and deployment ownership across one or more major PLM platforms - Deep functional knowledge of PLM processes: BOM management (eBOM/mBOM/sBOM), engineering change management (ECR/ECO/ECN), product configuration, effectivity management, and revision control - Proven ability to map as-is PLM workflows, facilitate cross-functional design sessions with engineering and manufacturing stakeholders, and produce implementation-ready specifications - Strong UX and design execution skills — able to produce annotated wireframes, workflow diagrams, and dashboard layouts that engineering teams can build directly from (Figma preferred) - Experience designing and delivering role-based training and onboarding programs for PLM users in manufacturing, aerospace, automotive, or defense environments — including hands-on working sessions -