Lead Engineer, PLM Architecture & Digital Tools

We need to produce HTML fragment with sections: About the role? The posting includes description. We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Let's parse. Content: - Intro: "Rise above..." etc. That's about company, maybe "About the role"? Actually it's about company and mission. Could be "About the role" but maybe better as "About the role" includes description of role? The posting includes "What we do:" then description of role responsibilities. Then "What you can do:" list of responsibilities. Then "What you can contribute:" list of qualifications/requirements/skills. Also mention: "This position is required to work on-site 5 days a week." That's schedule. Pay: "Base pay offered may vary depending on skills, experience, job-related knowledge and location. This position is also eligible for a bonus as part of total compensation. The pay range for this position is: $168,566—$206,025 USD". So we have pay range. Benefits: "Click HERE or visit: https://jobs.supernal.aero/benefits to view our benefits!" That's a link to benefits but not specific benefits listed. The instruction: do NOT create Benefits section unless posting actually states them. It only says view benefits via link, not enumerated. So we should not create Benefits section because no specific benefits listed. However we could include a short paragraph referencing benefits link? The rule: "Prefer a few substantive sections over many thin ones." Might still include a Benefits section with link? But they said never create Benefits sections unless posting actually states them. It does state that benefits exist and provide a link, but not list them. Is that considered stating them? Probably not; they want actual benefit details. So omit Benefits. Schedule: we have on-site 5 days a week. That's specific. So include Schedule section. Pay: we have pay range. Include Pay section. Responsibilities: we have "What you can do:" list of responsibilities. Also "What we do:" maybe also responsibilities. We'll combine into Responsibilities. Requirements/Qualifications/Skills: "What you can contribute:" includes degree, experience, etc. Also list of skills. We'll separate maybe into Requirements (education, experience) and Skills (technical and soft). But we can combine into Qualifications. The instruction: prefer few substantive sections over many thin ones. Could have sections: Responsibilities, Qualifications, Pay, Schedule. Maybe also About the role? The intro about company could be About the role? But they said do NOT repeat job title as heading; page already shows it. Could still have About the role as a short paragraph describing role purpose. The intro includes mission etc. Might be suitable for About the role. Let's include About the role section with the introductory paragraphs up to "Join our dynamic team...". That's substantive. Thus sections: About the role, Responsibilities, Qualifications, Pay, Schedule. Now we need to format: headings

. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Must not omit details. We need to capture all details from posting. Let's extract About the role prose: "Rise above. Are you ready to take human possibility to a new dimension with us? Supernal is an Advanced Air Mobility (AAM) company that’s developing an electric vertical take-off and landing (eVTOL) vehicle and the ground-to-air ecosystem to support the emerging industry. By creating a sustainable, integrated, and human-centered ecosystem, we are committed to taking a thoughtful and responsible approach to entering the AAM market with a product that meets the high level of safety and reliability in today’s air transportation system. The future of mobility starts with people. We believe in creative thinking and collaboration to help build a better mobility experience for everyone, improving people’s ability to move – whether for work or play. Join our dynamic team as we strive to be a part of something greater where potential powers tomorrow! Supernal provides an inviting open-space workplace designed to foster collaboration, which aligns with one of our core values. This position is required to work on-site 5 days a week." Note: The last sentence about on-site 5 days a week is schedule; maybe we should move that to Schedule section. But it's also part of About the role prose. We could keep it there but then also have Schedule section duplicate. Better to separate: keep About the role without schedule line, and schedule separate. However we must preserve all info; we can keep schedule line in About the role and also have Schedule section? That would duplicate. Better to extract schedule line to Schedule section and keep About the role without it. But we must not lose info; we can keep schedule line only in Schedule section. So About the role prose ends before "This position is required to work on-site 5 days a week." Let's check if any other schedule info elsewhere: none. Thus About the role prose: up to "Supernal provides an inviting open-space workplace designed to foster collaboration, which aligns with one of our core values." Now Responsibilities: from "What we do:" and "What you can do:" Let's capture all bullet-like sentences. What we do: "Supernal is looking for an experienced engineer to manage the engineering/development team by overseeing all digital tools. As a part of Systems Engineering, Integration & Test team, the Lead, PLM Architecture & Digital Tools Engineer will ensure all the engineering digital systems are integrated, connected, modern, and positioned to enable a full digital thread throughout the value stream of the product. This role will incubate many of the technologies to be leveraged in the future production system and will interface often with the operations and IT teams to ensure the future production systems are able to leverage the engineering digital data to enable that fully connected vision of the future." What you can do: list: - Responsible for standing up and managing the Product Lifecycle Management (PLM) system and all associated digital toolsets required for product development. This includes, but is not limited to, CAD, CAE, Simulation, Program Management, and Requirements Management - Evaluating the integration of these tools with the downstream digital tools used by operations and ensuring a digital backbone is in place that can enable the full digital thread - Evaluate connected factory/industry 4.0 digital tools and inform operations team of potential benefits and technologies to use - Integrate seamlessly with IT to ensure a stable, secure, and reliable platform is stood up - Administer engineering software license infrastructure, including installation, configuration, and support of license managers such as FlexNet, RLM, and Dassault Systèmes DSLS. - Administer databases such as Microsoft SQL Server (MSSQL), PostgreSQL, MySQL/MariaDB - Install and administer engineering applications on Windows and Linux (Ubuntu) servers - Develop elastic server architecture that can scale up along with the demand - Deep understanding of the 3DEXPERIENCE data model, core capabilities and guide the team in meeting the business goals using the out-of-the-box features and functionalities - Architect and manage the 3DEXPERIENCE security model to enable a collaborative product development environment while protecting intellectual property, enforcing appropriate access controls, and supporting export compliance requirements. - Translate PLM business requirements into scalable solution architectures, collaborate with external developers to define and implement customizations, and ensure delivered solutions support business objectives and user needs - Administer enterprise engineering applications, including Dassault Systèmes 3DEXPERIENCE and IBM DOORS Next, to ensure reliable performance, effective configuration, and alignment with product development needs. - Plan budget to manage and maintain digital tool landscape based on license utilization, emerging business needs and phase of the program - Negotiate with key software vendors, optimize the license mix to maximize value - Actively mentor colleagues, train in troubleshooting techniques and guiding them through the complexities of aerospace-specific data hierarchies and security protocols - This position may eventually broaden to a leadership position in or outside of the engineering organization We need to put each as

• . Some are long sentences; keep as is. Now Qualifications: from "What you can contribute:" includes: - Bachelor’s degree in a relevant engineering or IT field is required; advanced degree preferred - A minimum of eight (8) years of aerospace experience leading digital tools engineering activities - Must have extensive understanding of modern PLM/CAD systems - Experience with Dassault 3DEXPERIENCE systems - Experience with purchasing these types of systems and their licensing models - Experience leading teams - Experience with project management and tools/methodologies - Experience with aircraft development programs - Familiarity with running business cases and justifying investments - Excellent verbal and written communication skills - Excellent listening and comprehension skills - Excellent organizational skills and attention to detail - Excellent customer service skills - Must have the ability to independently prioritize and accomplish work within time constraints - Strong analytical and problem-solving skills - Ability to act with integrity, professionalism, and confidentiality We could split into Requirements (education, experience) and Skills (technical/soft). But to keep few sections, we can have Qualifications encompassing all. However we might also separate Skills as separate section if we have enough content. The instruction: prefer a few substantive sections over many thin ones. So maybe combine into one Qualifications section. Now Pay: we have sentence: "Base pay offered may vary depending on skills, experience, job-related knowledge and location. This position is also eligible for a bonus as part of total compensation. The pay range for this position is: $168,566—$206,025 USD". We'll put as

  . Schedule: "This position is required to work on-site 5 days a week." We'll put as

  . Now ensure we don't include boilerplate like EEO, legal, etc. Remove those. Now produce HTML fragment:

  About the role

  ... (prose)

  Responsibilities

  • ...
  ...

  Qualifications

  • ...
  ...

  Pay

  ...

  Schedule

  ...

  Make sure no extra whitespace issues. Now craft the About the role prose exactly as earlier: "Rise above. Are you ready to take human possibility to a new dimension with us? Supernal is an Advanced Air Mobility (AAM) company that’s developing an electric vertical take-off and landing (eVTOL) vehicle and the ground-to-air ecosystem to support the emerging industry. By creating a sustainable, integrated, and human-centered ecosystem, we are committed to taking a thoughtful and responsible approach to entering the AAM market with a product that meets the high level of safety and reliability in today’s air transportation system. The future of mobility starts with people. We believe in creative thinking and collaboration to help build a better mobility experience for everyone, improving people’s ability to move – whether for work or play. Join our dynamic team as we strive to be a part of something greater where potential powers tomorrow! Supernal provides an inviting open-space workplace designed to foster collaboration, which aligns with one of our core values." Check for any missing punctuation: keep as is. Now Responsibilities list items: need to ensure we capture all sentences exactly. Let's list them precisely: 1. Responsible for standing up and managing the Product Lifecycle Management (PLM) system and all associated digital toolsets required for product development. This includes, but is not limited to, CAD, CAE, Simulation, Program Management, and Requirements Management 2. Evaluating the integration of these tools with the downstream digital tools used by operations and ensuring a digital backbone is in place that can enable the full digital thread 3. Evaluate connected factory/industry 4.0 digital tools and inform operations team of potential benefits and technologies to use 4. Integrate seamlessly with IT to ensure a stable, secure, and reliable platform is stood up 5. Administer engineering software license infrastructure, including installation, configuration