Principal Model-Based Systems Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. The posting includes: - Intro: "Responsibilities This position is for Strategic Technology Consulting - STC, An Arcfield Company Are you ready to take your career to the next level? Join us in St. Louis, Missouri, and play a pivotal role in enabling teams to collaborate on state-of-the-art Model-Based Systems Engineering (MBSE) solutions. As an on-site Principal Model-Based Systems Engineer, you will act as the subject matter expert in model management, administering and maintaining a federated set of SysML models in Teamwork Cloud (TWC) across multiple classification levels. If you’re enthusiastic about MBSE, managing complex systems environments, and delivering impactful technical solutions, this opportunity is made for you." That's like an overview / About the role. Then "Responsibilities:" bullet list. Then "Why Join Us?" which is like Benefits? Actually it's more about why join, could be considered Benefits or maybe not. The instructions: we have Benefits section if posting actually states them. The "Why Join Us?" includes bullet points: Join a team of world-class MBSE and DE Experts. Be part of a dynamic team working on groundbreaking projects. Contribute to the development of state-of-the-art systems and make a lasting impact in the industry. Exercise considerable latitude in determining objectives and approaches to assignments, giving you the freedom to innovate and excel. Those are more like benefits or selling points. Could be considered Benefits. But we also have explicit Benefits later: "Arcfield ’s benefits offerings include, dependent upon position, Health Insurance, Life Insurance, Paid Time Off, Holiday Pay, Short Term and Long-Term Disability, Retirement and Savings, Learning and Development opportunities, wellness programs as well as other optional benefit elections." So we have Benefits content. Pay: "Min: $110,736.50 Max: $192,549.29". So we have Pay. Schedule: Not mentioned. So we should not include Schedule. Qualifications: There's a "Qualifications" heading in the posting: "Qualifications BS 8-10, MS 6-8, PhD 3-5 (Bachelor’s degree in Systems Engineering, Aerospace Engineering, Electrical Engineering, or a related technical discipline (Master’s degree preferred).Experience with one or more of the followingNoMagicMagicDrawCameoCATIA Magic System of Systems ArchitectSysMLUPDMIBM RhapsodyAbility to obtain and maintain a Top Secret/SCI, must possesse and maintain a Top Secret to start." We need to parse that into qualifications and maybe skills. The posting also includes "Experience with one or more of the following" list: NoMagic, MagicDraw, Cameo, CATIA Magic System of Systems Architect, SysML, UPDM, IBM Rhapsody. That's skills. Also "Ability to obtain and maintain a Top Secret/SCI, must possesse and maintain a Top Secret to start." That's a requirement (clearance). So we can put under Requirements or Qualifications. We need to decide sections: About the role (overview), Responsibilities, Qualifications (education/experience), Skills (tools), Benefits, Pay. Possibly also Requirements (clearance). But we can combine clearance into Qualifications or Requirements. The instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications (including education, experience, clearance), Skills, Benefits, Pay. We must not repeat job title as heading. No Job ID. We must use

for section headings. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop the EEO statement, Equal Pay Act paragraph (though it contains pay range; we already extracted pay). Actually the Equal Pay Act paragraph includes the pay range and other details. We need to preserve the pay range but we can drop the rest of that paragraph (the boilerplate). The paragraph: "Equal Pay Act This is the projected compensation range for this position. There are differentiating factors that can impact a final salary/hourly rate, including, but not limited to, Contract Wage Determination, relevant work experience, skills and competencies that align to the specified role, geographic location (For Remote Opportunities), education and certifications as well as Federal Government Contract Labor categories. In addition, Arcfield invests in its employees beyond just compensation. Arcfield ’s benefits offerings include, dependent upon position, Health Insurance, Life Insurance, Paid Time Off, Holiday Pay, Short Term and Long-Term Disability, Retirement and Savings, Learning and Development opportunities, wellness programs as well as other optional benefit elections. Min: $110,736.50 Max: $192,549.29" We need to keep the benefits list and the pay range. The benefits list is already there; we can keep that as Benefits section. The pay range we keep as Pay section. We need to drop the rest of that paragraph (the boilerplate about Equal Pay Act, differentiating factors, etc.) but keep the benefits list and pay range. However the benefits list is within that paragraph; we need to extract it. The benefits list: "Health Insurance, Life Insurance, Paid Time Off, Holiday Pay, Short Term and Long-Term Disability, Retirement and Savings, Learning and Development opportunities, wellness programs as well as other optional benefit elections." We'll put that as a

  • list. Now the "Why Join Us?" section: It's more like benefits but we already have Benefits. Could treat it as "Why Join Us?" but not a standard heading; we could incorporate into Benefits or maybe into About the role? The instruction: Prefer a few substantive sections over many thin ones. So we could merge "Why Join Us?" points into Benefits section as additional bullet points. However they are not typical benefits like health insurance; they are more about culture/impact. Could be considered Benefits but we already have a Benefits section for tangible benefits. Might be better to create a section "Why Join Us?" but that's not one of the allowed headings list (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings only. So we should not create a "Why Join Us?" heading. Instead we can incorporate those points into Benefits or maybe About the role. Since they are about why join, they could be considered Benefits (non-tangible). We'll add them to Benefits section as bullet points. Now we need to parse Responsibilities bullet list: - Serve as the model management Subject Matter Expert (SME) for the Teamwork Cloud environment. - Administer and maintain a federated set of SysML models across different classification levels. - Ensure up-to-date and consistent project usages across hundreds of projects utilizing Teamwork Cloud. - Troubleshoot issues with the Cameo Systems Modeler tool and the Teamwork Cloud environment, ensuring minimal disruption to engineering processes. - Oversee and manage user accounts, access permissions, and all other aspects of environment access administration. - Implement and maintain standard workflows, processes, and templates for SysML modeling, ensuring compliance with organizational and program-specific guidelines. - Collaborate with system architects, project teams, and IT support staff to resolve configuration, deployment, and integration challenges. We'll put those as

    • . Now Qualifications: The posting says "Qualifications BS 8-10, MS 6-8, PhD 3-5 (Bachelor’s degree in Systems Engineering, Aerospace Engineering, Electrical Engineering, or a related technical discipline (Master’s degree preferred).Experience with one or more of the followingNoMagicMagicDrawCameoCATIA Magic System of Systems ArchitectSysMLUPDMIBM RhapsodyAbility to obtain and maintain a Top Secret/SCI, must possesse and maintain a Top Secret to start." We need to separate education, experience, clearance. The "BS 8-10, MS 6-8, PhD 3-5" likely means years of experience: BS 8-10 years, MS 6-8 years, PhD 3-5 years. We'll keep that as part of qualifications. We'll create a Qualifications section with prose: maybe a

      summarizing education and experience requirements. Then a separate Skills section for the tools list. But we could also put the tools list under Skills. The clearance could be under Requirements (maybe a separate Requirements section). However we prefer few sections. Could put clearance under Qualifications as a requirement. Thus Qualifications section could include: education (Bachelor’s degree in Systems Engineering, Aerospace Engineering, Electrical Engineering, or related technical discipline; Master’s degree preferred), experience (BS: 8-10 years, MS: 6-8 years, PhD: 3-5 years), and clearance (Ability to obtain and maintain a Top Secret/SCI clearance; must possess and maintain Top Secret to start). We'll put that in a

      . Skills section: list of tools: NoMagic, MagicDraw, Cameo, CATIA Magic System of Systems Architect, SysML, UPDM, IBM Rhapsody. We'll put as

      • . Now Benefits section: we have tangible benefits list from the paragraph plus the "Why Join Us?" points. We'll combine them. Benefits list items: - Health Insurance - Life Insurance - Paid Time Off - Holiday Pay - Short Term and Long-Term Disability - Retirement and Savings - Learning and Development opportunities - Wellness programs - Other optional benefit elections - Join a team of world-class MBSE and DE Experts - Be part of a dynamic team working on groundbreaking projects - Contribute to the development of state-of-the-art systems and make a lasting impact in the industry - Exercise considerable latitude in determining objectives and approaches to assignments, giving you the freedom to innovate and excel We'll put each as
      • . Pay section: we need to show Min and Max. Could be a

        with the range. Now we need to ensure we don't include any boilerplate: we removed EEO statement, Equal Pay Act boilerplate (except benefits and pay). Also we need to remove duplicated lines: there may be duplicated "Responsibilities" heading at start; we already have that. Now produce HTML fragment:

        About the role

        ...

        Responsibilities

        • ...
        ...

        Qualifications

        ...

        Skills

        • ...
        ...

        Benefits

        • ...
        ...

        Pay

        Min: $110,736.50 – Max: $192,549.29

        We need to ensure we don't add extra sections like Schedule. Now craft the About the role paragraph: Use the introductory text: "This position is for Strategic Technology Consulting - STC, An Arcfield Company Are you ready to take your career to the next level? Join us in St. Louis, Missouri, and play a pivotal role in enabling teams to collaborate on state-of-the-art Model-Based Systems Engineering (MBSE) solutions. As an on-site Principal Model-Based Systems Engineer, you will act as the subject matter expert in model management, administering and maintaining a federated set of SysML models in Teamwork Cloud (TWC) across multiple classification levels. If you’re enthusiastic about MBSE, managing complex systems environments