MBSE Systems Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content. So we need sections: About the role (position summary), Responsibilities (Job Duties), Requirements (Minimum Qualifications), Preferred Qualifications (maybe as Qualifications? but they have separate Preferred Qualifications). Could also have Skills? Not needed. No Pay, Schedule, Benefits as not present.
We must not repeat job title as heading. No Job ID. Remove boilerplate: Special Instructions To Applicants, Closing Statement (EEO etc). Also remove "Due to the requirements of our research contracts..."? That's a requirement (citizenship, clearance) - that is substantive, keep. Also "Applicants must be currently authorized to work in the United States on a full-time basis. The University does not provide work visa sponsorship for this position." That's also a requirement (work authorization). Keep.
We need to preserve all substantive info. So include citizenship, clearance, work authorization.
We need to format lists with - . For prose use
.
We need to avoid filler like "commensurate with experience" etc. Not present.
Let's extract content:
Position Summary paragraph: "We are seeking a Model-Based Systems Engineer (MBSE) to drive digital and systems engineering initiatives across multiple programs primarily within a program-management-led government acquisition environment. The successful candidate will manage the full digital lifecycle for new and continuing programs while serving as the technical anchor for the team. This role requires the professional stamina and technical acumen to advance complex models through shifting customer priorities, evolving timelines, and rigid regulatory frameworks. We are looking for individuals who can hit the ground running but are fully prepared to train the right candidate on specific MBSE toolsets. You will interface directly with program managers, external vendors, and multi-disciplinary teams to guide execution and support critical acquisition milestones."
Job Duties list: bullet points after "Job Duties". Let's capture:
- Author new MBSE models from scratch or inherit and mature legacy baselines depending on the program phase.
- Manage software-intensive system architectures within Magic System of Systems Architect, Cameo Systems Modeler (or equivalent SysML tools), updating requirements, complex interfaces, software behaviors, and performance metrics.
- Advance the digital baseline through acquisition milestones including pre-RFP, source selection, and technical reviews.
- Guide, track, and verify systems execution by external vendors using the authoritative model baseline.
- Translate complex technical architecture into clear, actionable progress for non-technical program managers and multi-disciplinary stakeholders.
Minimum Qualifications: It repeats "Minimum Qualifications" heading then content. We'll extract:
Candidates must hold a BS or MS in an engineering discipline or Computer Science.
Staff Engineer (R2) requires a BS + 3 years or an MS + 2 years of direct experience in systems engineering, software systems engineering, or a related technical discipline.
Senior Engineer (R3) requires a BS + 8 years or an MS + 7 years of relevant engineering experience with a track record of technical leadership.
Demonstrated successful experience in any or all of the following:
- Model-based system engineering (MBSE), SysML
- Applying Cameo or similar MBSE-enabling toolset
- Requirements derivation, flow down, & management
Demonstrated experience supporting government or commercial PMs within complex, structured, or heavily regulated environments (DoD/USAF) is required.
Strong attention to detail, specifically regarding model consistency, strict requirement tracing, and technical documentation.
Proficiency with the Microsoft Office suite, including advanced use of Excel for data analysis, requirement matrices, or tracking.
Applicants must possess strong communication skills to collaborate effectively with multi-disciplinary teams through changing project environments.
Due to the requirements of our research contracts with the United States of America federal government, candidates for this position must be a U.S. Citizen and capable of obtaining and maintaining a DoD security clearance.
Applicants must be currently authorized to work in the United States on a full-time basis. The University does not provide work visa sponsorship for this position.
Preferred Qualifications: heading repeated. Content:
While not everyone may possess all of the preferred qualifications, the ideal candidate will bring many of the following:
- Background modeling complex architectures, information data flows, or software-driven government applications.
- R2 candidates should have direct experience supporting a USAF program office (AFMC/AFLCMC) and translating model elements into T&E verification matrices.
- R2 candidates are preferred to hold an INCOSE ASEP, OCSMP, or equivalent systems engineering certification.
- R3 candidates should have extensive experience partnering with non-technical program managers to steady engineering projects through personnel turnover and shifting client directives.
- R3 candidates should bring a background modeling multi-domain architectures and integrations across both hardware and software systems.
- R3 candidates are preferred to hold an INCOSE CSEP, advanced OCSMP certifications, or an advanced degree (MS or MBA).
We should not include "Special Instructions To Applicants" etc. Also not include closing statement.
Now produce HTML:
About the role
...position summary...
Responsibilities
- ...
...
Requirements
...minimum qualifications prose? Some are bullet lists. We'll split: maybe a paragraph for first sentences then list for bullet items. But we can just put all as
with line breaks? Better to use
for lists. Let's structure:
Candidates must hold a BS or MS in an engineering discipline or Computer Science.
Staff Engineer (R2) requires a BS + 3 years or an MS + 2 years of direct experience in systems engineering, software systems engineering, or a related technical discipline.
Senior Engineer (R3) requires a BS + 8 years or an MS + 7 years of relevant engineering experience with a track record of technical leadership.
Demonstrated successful experience in any or all of the following:
- Model-based system engineering (MBSE), SysML
- Applying Cameo or similar MBSE-enabling toolset
- Requirements derivation, flow down, & management
Demonstrated experience supporting government or commercial PMs within complex, structured, or heavily regulated environments (DoD/USAF) is required.
Strong attention to detail, specifically regarding model consistency, strict requirement tracing, and technical documentation.
Proficiency with the Microsoft Office suite, including advanced use of Excel for data analysis, requirement matrices, or tracking.
Applicants must possess strong communication skills to collaborate effectively with multi-disciplinary teams through changing project environments.
Due to the requirements of our research contracts with the United States of America federal government, candidates for this position must be a U.S. Citizen and capable of obtaining and maintaining a DoD security clearance.
Applicants must be currently authorized to work in the United States on a full-time basis. The University does not provide work visa sponsorship for this position.
But we are only allowed to use for section headings, not . So we cannot use . We need to keep within allowed headings: only . So we cannot add . We can instead incorporate that line into a
preceding the list. Eg:
Demonstrated successful experience in any or all of the following:
then list.
That's fine.
Similarly for Preferred Qualifications: we can have a section Preferred Qualifications
and then list.
We must not include sections with filler. We have content.
Thus final HTML fragment:
About the role
We are seeking a Model-Based Systems Engineer (MBSE) to drive digital and systems engineering initiatives across multiple programs primarily within a program-management-led government acquisition environment. The successful candidate will manage the full digital lifecycle for new and continuing programs while serving as the technical anchor for the team. This role requires the professional stamina and technical acumen to advance complex models through shifting customer priorities, evolving timelines, and rigid regulatory frameworks. We are looking for individuals who can hit the ground running but are fully prepared to train the right candidate on specific MBSE toolsets. You will interface directly with program managers, external vendors, and multi-disciplinary teams to guide execution and support critical acquisition milestones.
Responsibilities
- Author new MBSE models from scratch or inherit and mature legacy baselines depending on the program phase.
- Manage software-intensive system architectures within Magic System of Systems Architect, Cameo Systems Modeler (or equivalent SysML tools), updating requirements, complex interfaces, software behaviors, and performance metrics.
- Advance the digital baseline through acquisition milestones including pre-RFP, source selection, and technical reviews.
- Guide, track, and verify systems execution by external vendors using the authoritative model baseline.
- Translate complex technical architecture into clear, actionable progress for non-technical program managers and multi-disciplinary stakeholders.
Requirements
Candidates must hold a BS or MS in an engineering discipline or Computer Science.
Staff Engineer (R2) requires a BS + 3 years or an MS + 2 years of direct experience in systems engineering, software systems engineering, or a related technical discipline.
Senior Engineer (R3) requires a BS + 8 years or an MS + 7 years of relevant engineering experience with a track record of technical leadership.
Demonstrated successful experience in any or all of the following:
- Model-based system engineering (MBSE), SysML
- Applying Cameo or similar MBSE-enabling toolset
- Requirements derivation, flow down, & management
Demonstrated experience supporting government or commercial PMs within complex, structured, or heavily regulated environments (DoD/USAF) is required.
Strong attention to detail, specifically regarding model consistency, strict requirement tracing, and technical documentation.
Proficiency with the Microsoft Office suite, including advanced use of Excel for data analysis, requirement matrices, or tracking.
Applicants must possess strong communication skills to collaborate effectively with multi-disciplinary teams through changing project environments.
Due to the requirements of our research contracts with the United States of America federal government, candidates for this position must be a U.S. Citizen and capable of obtaining and maintaining a DoD security clearance.
Applicants must be currently authorized to work in the United States on a full-time basis. The University does not provide work visa sponsorship for this position.
Preferred Qualifications
While not everyone may possess all of the preferred qualifications, the ideal candidate will bring many of the following:
- Background modeling complex architectures, information data flows, or software-driven government applications.
- R2 candidates should have direct experience supporting a USAF program office (AFMC/AFLCMC) and translating model elements into T&E verification matrices.
- R2 candidates are preferred to hold an INCOSE ASEP, OCSMP, or equivalent systems engineering certification.
- R3 candidates should have extensive experience partnering with non-technical program managers to steady engineering projects through personnel turnover and shifting client directives.
- R3 candidates should bring a background modeling multi-domain architectures and integrations across both hardware and software systems.
- R3 candidates are preferred to hold an INCOSE CSEP, advanced OCSMP certifications, or an advanced degree (MS or MBA).
That's it.
. We need to avoid filler like "commensurate with experience" etc. Not present. Let's extract content: Position Summary paragraph: "We are seeking a Model-Based Systems Engineer (MBSE) to drive digital and systems engineering initiatives across multiple programs primarily within a program-management-led government acquisition environment. The successful candidate will manage the full digital lifecycle for new and continuing programs while serving as the technical anchor for the team. This role requires the professional stamina and technical acumen to advance complex models through shifting customer priorities, evolving timelines, and rigid regulatory frameworks. We are looking for individuals who can hit the ground running but are fully prepared to train the right candidate on specific MBSE toolsets. You will interface directly with program managers, external vendors, and multi-disciplinary teams to guide execution and support critical acquisition milestones." Job Duties list: bullet points after "Job Duties". Let's capture: - Author new MBSE models from scratch or inherit and mature legacy baselines depending on the program phase. - Manage software-intensive system architectures within Magic System of Systems Architect, Cameo Systems Modeler (or equivalent SysML tools), updating requirements, complex interfaces, software behaviors, and performance metrics. - Advance the digital baseline through acquisition milestones including pre-RFP, source selection, and technical reviews. - Guide, track, and verify systems execution by external vendors using the authoritative model baseline. - Translate complex technical architecture into clear, actionable progress for non-technical program managers and multi-disciplinary stakeholders. Minimum Qualifications: It repeats "Minimum Qualifications" heading then content. We'll extract: Candidates must hold a BS or MS in an engineering discipline or Computer Science. Staff Engineer (R2) requires a BS + 3 years or an MS + 2 years of direct experience in systems engineering, software systems engineering, or a related technical discipline. Senior Engineer (R3) requires a BS + 8 years or an MS + 7 years of relevant engineering experience with a track record of technical leadership. Demonstrated successful experience in any or all of the following: - Model-based system engineering (MBSE), SysML - Applying Cameo or similar MBSE-enabling toolset - Requirements derivation, flow down, & management Demonstrated experience supporting government or commercial PMs within complex, structured, or heavily regulated environments (DoD/USAF) is required. Strong attention to detail, specifically regarding model consistency, strict requirement tracing, and technical documentation. Proficiency with the Microsoft Office suite, including advanced use of Excel for data analysis, requirement matrices, or tracking. Applicants must possess strong communication skills to collaborate effectively with multi-disciplinary teams through changing project environments. Due to the requirements of our research contracts with the United States of America federal government, candidates for this position must be a U.S. Citizen and capable of obtaining and maintaining a DoD security clearance. Applicants must be currently authorized to work in the United States on a full-time basis. The University does not provide work visa sponsorship for this position. Preferred Qualifications: heading repeated. Content: While not everyone may possess all of the preferred qualifications, the ideal candidate will bring many of the following: - Background modeling complex architectures, information data flows, or software-driven government applications. - R2 candidates should have direct experience supporting a USAF program office (AFMC/AFLCMC) and translating model elements into T&E verification matrices. - R2 candidates are preferred to hold an INCOSE ASEP, OCSMP, or equivalent systems engineering certification. - R3 candidates should have extensive experience partnering with non-technical program managers to steady engineering projects through personnel turnover and shifting client directives. - R3 candidates should bring a background modeling multi-domain architectures and integrations across both hardware and software systems. - R3 candidates are preferred to hold an INCOSE CSEP, advanced OCSMP certifications, or an advanced degree (MS or MBA). We should not include "Special Instructions To Applicants" etc. Also not include closing statement. Now produce HTML:
About the role
...position summary...
Responsibilities
- ... ...
Requirements
...minimum qualifications prose? Some are bullet lists. We'll split: maybe a paragraph for first sentences then list for bullet items. But we can just put all as
with line breaks? Better to use
- for lists. Let's structure:
- Model-based system engineering (MBSE), SysML
- Applying Cameo or similar MBSE-enabling toolset
- Requirements derivation, flow down, & management
- Author new MBSE models from scratch or inherit and mature legacy baselines depending on the program phase.
- Manage software-intensive system architectures within Magic System of Systems Architect, Cameo Systems Modeler (or equivalent SysML tools), updating requirements, complex interfaces, software behaviors, and performance metrics.
- Advance the digital baseline through acquisition milestones including pre-RFP, source selection, and technical reviews.
- Guide, track, and verify systems execution by external vendors using the authoritative model baseline.
- Translate complex technical architecture into clear, actionable progress for non-technical program managers and multi-disciplinary stakeholders.
- Model-based system engineering (MBSE), SysML
- Applying Cameo or similar MBSE-enabling toolset
- Requirements derivation, flow down, & management
- Background modeling complex architectures, information data flows, or software-driven government applications.
- R2 candidates should have direct experience supporting a USAF program office (AFMC/AFLCMC) and translating model elements into T&E verification matrices.
- R2 candidates are preferred to hold an INCOSE ASEP, OCSMP, or equivalent systems engineering certification.
- R3 candidates should have extensive experience partnering with non-technical program managers to steady engineering projects through personnel turnover and shifting client directives.
- R3 candidates should bring a background modeling multi-domain architectures and integrations across both hardware and software systems.
- R3 candidates are preferred to hold an INCOSE CSEP, advanced OCSMP certifications, or an advanced degree (MS or MBA).
Candidates must hold a BS or MS in an engineering discipline or Computer Science.
Staff Engineer (R2) requires a BS + 3 years or an MS + 2 years of direct experience in systems engineering, software systems engineering, or a related technical discipline.
Senior Engineer (R3) requires a BS + 8 years or an MS + 7 years of relevant engineering experience with a track record of technical leadership.
Demonstrated successful experience in any or all of the following:
Demonstrated experience supporting government or commercial PMs within complex, structured, or heavily regulated environments (DoD/USAF) is required.
Strong attention to detail, specifically regarding model consistency, strict requirement tracing, and technical documentation.
Proficiency with the Microsoft Office suite, including advanced use of Excel for data analysis, requirement matrices, or tracking.
Applicants must possess strong communication skills to collaborate effectively with multi-disciplinary teams through changing project environments.
Due to the requirements of our research contracts with the United States of America federal government, candidates for this position must be a U.S. Citizen and capable of obtaining and maintaining a DoD security clearance.
Applicants must be currently authorized to work in the United States on a full-time basis. The University does not provide work visa sponsorship for this position.
But we are only allowed to use for section headings, not . So we cannot use . We need to keep within allowed headings: only . So we cannot add . We can instead incorporate that line into a
. We need to keep within allowed headings: only . So we cannot add . We can instead incorporate that line into a
. We can instead incorporate that line into a
preceding the list. Eg:
Demonstrated successful experience in any or all of the following:
then list. That's fine. Similarly for Preferred Qualifications: we can have a sectionPreferred Qualifications
and then list. We must not include sections with filler. We have content. Thus final HTML fragment:About the role
We are seeking a Model-Based Systems Engineer (MBSE) to drive digital and systems engineering initiatives across multiple programs primarily within a program-management-led government acquisition environment. The successful candidate will manage the full digital lifecycle for new and continuing programs while serving as the technical anchor for the team. This role requires the professional stamina and technical acumen to advance complex models through shifting customer priorities, evolving timelines, and rigid regulatory frameworks. We are looking for individuals who can hit the ground running but are fully prepared to train the right candidate on specific MBSE toolsets. You will interface directly with program managers, external vendors, and multi-disciplinary teams to guide execution and support critical acquisition milestones.
Responsibilities
Requirements
Candidates must hold a BS or MS in an engineering discipline or Computer Science.
Staff Engineer (R2) requires a BS + 3 years or an MS + 2 years of direct experience in systems engineering, software systems engineering, or a related technical discipline.
Senior Engineer (R3) requires a BS + 8 years or an MS + 7 years of relevant engineering experience with a track record of technical leadership.
Demonstrated successful experience in any or all of the following:
Demonstrated experience supporting government or commercial PMs within complex, structured, or heavily regulated environments (DoD/USAF) is required.
Strong attention to detail, specifically regarding model consistency, strict requirement tracing, and technical documentation.
Proficiency with the Microsoft Office suite, including advanced use of Excel for data analysis, requirement matrices, or tracking.
Applicants must possess strong communication skills to collaborate effectively with multi-disciplinary teams through changing project environments.
Due to the requirements of our research contracts with the United States of America federal government, candidates for this position must be a U.S. Citizen and capable of obtaining and maintaining a DoD security clearance.
Applicants must be currently authorized to work in the United States on a full-time basis. The University does not provide work visa sponsorship for this position.
Preferred Qualifications
While not everyone may possess all of the preferred qualifications, the ideal candidate will bring many of the following: