PLM Lead
or drop it." Application deadline is minor metadata; we could fold into a short p or drop. Probably better to include as a short paragraph under maybe a heading? But we don't have a heading for "Application Deadline". Not in allowed headings list. So we could either drop it or include as a paragraph without heading. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." So we can just include a
with the deadline if we want to preserve substantive info. However, they said "Remove ... application instructions." The deadline is not exactly instruction but could be considered part of application process. Safer to drop it? But they said preserve ALL substantive information; do NOT invent or summarize away detail. The deadline is substantive. I'd include it as a
maybe under a generic heading? Not allowed headings. Could just put a
after other sections. We also have "Work Environment" description; we could include as a section maybe under a heading? Not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No Work Environment, Job Type & Location, Workplace Type. So we need to fold those into appropriate sections or drop? The instruction: "Prefer a few substantive sections over many thin ones." We could incorporate location into About the role or maybe into a short paragraph without heading. But we must not create headings not listed. So we can include location info in a
under About the role or maybe as a separate
without heading. 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." So location is minor metadata; we can fold into a short
. Similarly, job type (Permanent) could be folded. Pay and Benefits: we have both Pay and Benefits headings allowed. We'll need to create a Pay section with pay range, and a Benefits section with list. Schedule: not present; we should not create Schedule section if no specific content. Thus sections we will output: -
About the role
with paragraph(s) containing the description plus maybe location and job type? Could embed location there. -Responsibilities
with- for each bullet.
-
Requirements
maybe for Essential Skills. -Qualifications
for education/experience degree requirement? Or we could combine Essential Skills and Additional Skills into Requirements and Qualifications. But we need to avoid thin sections. Let's think: Essential Skills list is quite long; Additional Skills also long. Could split: Requirements = Essential Skills (mandatory). Qualifications = Additional Skills & Qualifications (preferred). Or we could have Skills section for both? But we have Skills heading allowed. Could use Skills for Additional Skills. However, we also need to capture education requirement (Associated degree...). That could go under Qualifications. Thus: - Requirements: Essential Skills (the list of minimum years etc.) - Qualifications: Education requirement (Associated degree...), maybe also the "Associated degree in engineering with 8–10+ years..." is both experience and education; but it's under Essential Skills list. Actually it's part of Essential Skills list. So maybe we should not duplicate. Let's re-evaluate: The Essential Skills list includes that education/experience line. So we could keep all Essential Skills under Requirements. Then Additional Skills & Qualifications could go under Skills. Then we could have Qualifications section for maybe nothing? Could drop Qualifications if no specific content besides what's already covered. But we have education line already in Requirements; we could still have Qualifications for maybe "Associated degree..." but it's duplicate. Better to not create Qualifications section if no unique content. However, we have "Associated degree in engineering with 8–10+ years of relevant experience, or at least 4+ years of experience with a BSEE, Industrial Engineering, Computer Engineering (BSCE), or similar engineering degree." That's both education and experience; it's in Essential Skills. So we can keep it there. Thus sections: - About the role - Responsibilities - Requirements (Essential Skills) - Skills (Additional Skills & Qualifications) - Pay - Benefits We also need to include location and job type maybe as a short paragraph under About the role or separate. Let's add a
after the About the role paragraph: "This is a Permanent position based out of Minneapolis, MN." Also we could add workplace type: "This is a fully onsite position in Minneapolis, MN." Might be redundant; we can combine. We also have Work Environment description; we could incorporate into About the role as additional sentence. Thus About the role paragraph: combine original description plus work environment plus location/job type. Let's craft: "The Engineering Systems Administration Manager oversees the analysis, coordination, and processing of engineering change requests and orders within a Product Lifecycle Management (PLM) system. This role works closely with cross-functional teams, including engineering, software, quality, product management, and compliance, to ensure accurate and timely implementation of changes with minimal errors, rework, and delays. The position focuses on managing change controls for complex systems and components, including software, electronics, mechanical elements, and sensors, supporting both new product introduction and sustaining engineering activities in a high-tech, long-term project environment. The role operates within an engineering-focused environment that supports high-tech, safety-critical products such as flame and gas detection and hazard-mitigation systems. The work involves extensive use of PLM systems, ERP/MRP platforms, and standard office productivity tools such as Microsoft Office. You will collaborate closely with cross-functional engineering teams, including software, electronics, mechanical, quality, product management, and compliance. The position supports both new product introduction and sustaining engineering projects, requiring careful coordination of configuration and change management activities. Work is primarily performed in a professional office and engineering setting, with a focus on digital tools and systems to manage engineering data and changes. This is a Permanent position based out of Minneapolis, MN. This is a fully onsite position in Minneapolis, MN." We could combine location sentences. Now Responsibilities: list each bullet from the Responsibilities section. Let's extract them exactly: - Analyze, coordinate, and process engineering change requests and change orders in the designated PLM system. - Collaborate with cross-functional teams, including engineering, software, quality, product management, and compliance, to gather all information required to complete change requests and orders accurately. - Evaluate systems engineering changes in new product and sustaining projects to ensure seamless introduction into operations. - Conduct impact analyses on proposed changes, assessing feasibility, risk, and operational impact. - Assess change readiness across stakeholders and identify required actions to support successful implementation. - Prepare, communicate, and follow up with internal stakeholders to ensure timely completion of change-related tasks. - Create part numbers, assembly numbers, and structured bills of materials (BOMs) in the PLM system.