System Engineer
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real, specific content. Must preserve all substantive information; do not invent or summarize away detail. Remove filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Do not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Pay And Benefits section with pay range and benefits list. Also Work Environment includes schedule info: flexible work schedules, options such as 9/80, 4/10, or 5/8. So we can have a Schedule section. Benefits section: list benefits. Pay section: pay range. Also we have About the role? The job description includes a paragraph about role. Could be "About the role". Responsibilities section: list responsibilities. Requirements/Skills: we have Essential Skills and Additional Skills & Qualifications. Could combine into Requirements or Skills. The instruction: use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate ones. Probably include About the role (description paragraph), Responsibilities (list), Requirements (maybe combine essential and additional skills), Benefits (list), Pay (pay range), Schedule (flexible schedules). Ensure we don't create sections with filler. All content must be preserved.
We need to extract substantive content:
Job Description paragraph: "This Systems Engineer role provides system-level engineering support as part of a cross-functional team working on complex electromechanical systems, including sonar, weapons systems, and underwater technology. You will focus on requirements development, system documentation, design reviews, and supporting programs across the full system lifecycle—from concept and design through integration, test, and transition to production. Both Level II (2+ years of experience) and III (5+ years of experience) engineers are being hired for this position."
That's the About the role.
Responsibilities list: bullet points after "Responsibilities". Let's extract each line:
- Support system-level engineering activities across the full lifecycle, including concept development, design, integration, test, and transition to production.
- Write, maintain, and manage technical documentation such as requirements, specifications, interface control documents, compliance matrices, and test plans.
- Develop and document engineering processes and standards that align with customer requirements and program objectives.
- Prepare documentation for and actively support formal system design and review events, including System Requirements Review (SRR), System Functional Review (SFR), Preliminary Design Review (PDR), Critical Design Review (CDR), and Test Readiness Review (TRR).
- Work directly with customers to define, refine, and manage system requirements and ensure alignment throughout the program lifecycle.
- Identify, analyze, and help solve moderate-complexity engineering problems in a timely and structured manner.
- Apply and support digital engineering and model-based systems engineering (MBSE) practices where appropriate to improve traceability and design quality.
- Support systems engineering activities such as architecture development, system integration planning, and risk management.
- Establish and maintain requirements traceability and verification and validation (V&V) across system and subsystem levels using appropriate tools.
- Contribute to configuration and documentation control practices to ensure consistency and accuracy of system baselines.
- Collaborate closely with cross-functional engineering, test, and production teams to ensure successful implementation of system designs.
- Participate in customer and internal technical meetings, providing clear status updates, technical input, and documentation support.
That's responsibilities.
Essential Skills list (maybe as Requirements). Let's extract each bullet:
- 2+ years of related systems engineering experience for Level II roles, or 5+ years of related systems engineering experience for Sr roles. (Note: "Sr roles" maybe Level III)
- Bachelor’s degree in engineering with relevant experience, or a Master’s degree in engineering; comparable experience may be accepted in lieu of a degree.
- Hands-on experience in systems engineering across the system lifecycle, including requirements development, integration, and test.
- Strong proficiency in requirements development, requirements traceability, and verification and validation (V&V).
- Experience using DOORS or DOORS Next Generation (DNG) for requirements management.
- Ability to write clear, structured technical documentation such as specifications, interface documents, and test plans.
- Understanding of model-based systems engineering (MBSE) concepts and practices.
- Familiarity with systems engineering documentation, configuration practices, and compliance tracking.
- Ability to obtain and maintain a Secret security clearance.
- Effective communication skills for working directly with customers and cross-functional engineering teams.
- Ability to identify and resolve moderate-complexity engineering issues within program timelines.
Additional Skills & Qualifications list:
- Experience with Microsoft Power BI for data visualization and reporting.
- Experience with Microsoft SharePoint for document and collaboration management.
- Exposure to data analysis or data science tools and workflows.
- Electro-mechanical hardware design experience or familiarity with electromechanical systems.
- Familiarity with naval systems or naval operations, including maritime or NUWC-related programs.
- Experience with MBSE tools such as Cameo Enterprise Architect.
- Experience using MATLAB for modeling, analysis, or simulation.
- Proficiency with Microsoft Office tools for documentation, presentations, and analysis.
- Experience in systems engineering related to sonar, weapons systems, or underwater technology is beneficial.
We could combine Essential Skills and Additional Skills into a Requirements section (or Skills). The instruction says we can use Requirements, Qualifications, Skills headings. Probably better to have Requirements (essential) and Skills (additional). But we must not create thin sections. Could combine into one Requirements section that includes both essential and additional? Might be okay. But we need to preserve all info; we can list them all under a single Requirements section with subheadings? Not allowed to add extra headings beyond those specified? We can use
- for list; we could separate essential and additional with
headings? Not specified. Safer to have two sections: Requirements (essential) and Skills (additional). Both are substantive.
Benefits list: from Pay And Benefits section: list of benefits:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
Pay: pay range: $90000.00 - $130000.00/hr. Wait that seems odd: per hour? Probably per year but it's written as /hr. We'll keep as given.
Schedule: Work Environment mentions flexible work schedules, including options such as 9/80, 4/10, or 5/8. Also mentions primarily onsite office environment with hybrid flexibility. So schedule section can capture flexible schedule options.
We also have Work Environment paragraph about onsite, hybrid, occasional work on base at NUWC. Could be part of About the role or maybe a separate section? Not required headings. Could incorporate into About the role paragraph.
We must not include boilerplate like "Job Type & Location", "Application Deadline", "About Actalent", equal opportunity, etc. Also remove "Workplace Type" duplicate. Also remove "Job Type & Location". Also remove "Application Deadline". Also remove "About Actalent" and all legal/EEO statements. Also remove "San Francisco Fair Chance Ordinance", etc.
We must preserve all substantive information: that includes location (Middletown, RI), contract to hire, job type, location? The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location and job type maybe minor metadata; we could include in a short
under About the role or separate? The instruction says preserve ALL substantive information; location and job type are substantive. So we need to keep them. We can include them in a
after the About the role paragraph, maybe as part of About the role. Or we could create a separate section like "Job Details" but not in allowed headings. Better to fold into About the role paragraph.
Thus About the role paragraph will include: description, plus note that it's Contract to Hire based out of Middletown, RI, Level II and III.
We must not repeat job title as heading. Already not.
Now construct HTML:
About the role
This Systems Engineer role provides system-level engineering support as part of a cross-functional team working on complex electromechanical systems, including sonar, weapons systems, and underwater technology. You will focus on requirements development, system documentation, design reviews, and supporting programs across the full system lifecycle—from concept and design through integration, test, and transition to production. Both Level II (2+ years of experience) and III (5+ years of experience) engineers are being hired for this position. This is a Contract to Hire position based out of Middletown, RI.
Responsibilities
- Support system-level engineering activities across the full lifecycle, including concept development, design, integration, test, and transition to production.
- Write, maintain, and manage technical documentation such as requirements, specifications, interface control documents, compliance matrices, and test plans.
- Develop and document engineering processes and standards that align with customer requirements and program objectives.
- Prepare documentation for and actively support formal system design and review events, including System Requirements Review (SRR), System Functional Review (SFR), Preliminary Design Review (PDR), Critical Design Review (CDR), and Test Readiness Review (TRR).
- Work directly with customers to define, refine, and manage system requirements and ensure alignment throughout the program lifecycle.
- Identify, analyze, and help solve moderate-complexity engineering problems in a timely and structured manner.
- Apply and support digital engineering and model-based systems engineering (MBSE) practices where appropriate to improve traceability and design quality.
- Support systems engineering activities such as architecture development, system integration planning, and risk management.
- Establish and maintain requirements traceability and verification and validation (V&V) across system and subsystem levels using appropriate tools.
- Contribute to configuration and documentation control practices to ensure consistency and accuracy of system baselines.
- Collaborate closely with cross-functional engineering, test, and production teams to ensure successful implementation of system designs.
- Participate in customer and internal technical meetings, providing clear status updates, technical input, and documentation support.
Requirements
- 2+ years of related systems engineering experience for Level II roles, or 5+ years of related systems engineering experience for Sr roles.
- Bachelor’s degree in engineering with relevant experience, or a Master’s degree in engineering; comparable experience may be accepted in lieu of a degree.
- Hands-on experience in systems engineering across the system lifecycle, including requirements development, integration, and test.
- Strong proficiency in requirements development, requirements traceability, and verification and validation (V&V).
- Experience using DOORS or DOORS Next Generation (DNG) for requirements management.
- Ability to write clear, structured technical documentation such as specifications, interface documents, and test plans.
- Understanding of model-based systems engineering (MBSE) concepts and practices.
- Familiarity with systems engineering documentation, configuration practices, and compliance tracking.
- Ability to obtain and maintain a Secret security clearance.
- Effective
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real, specific content. Must preserve all substantive information; do not invent or summarize away detail. Remove filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Do not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Pay And Benefits section with pay range and benefits list. Also Work Environment includes schedule info: flexible work schedules, options such as 9/80, 4/10, or 5/8. So we can have a Schedule section. Benefits section: list benefits. Pay section: pay range. Also we have About the role? The job description includes a paragraph about role. Could be "About the role". Responsibilities section: list responsibilities. Requirements/Skills: we have Essential Skills and Additional Skills & Qualifications. Could combine into Requirements or Skills. The instruction: use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate ones. Probably include About the role (description paragraph), Responsibilities (list), Requirements (maybe combine essential and additional skills), Benefits (list), Pay (pay range), Schedule (flexible schedules). Ensure we don't create sections with filler. All content must be preserved. We need to extract substantive content: Job Description paragraph: "This Systems Engineer role provides system-level engineering support as part of a cross-functional team working on complex electromechanical systems, including sonar, weapons systems, and underwater technology. You will focus on requirements development, system documentation, design reviews, and supporting programs across the full system lifecycle—from concept and design through integration, test, and transition to production. Both Level II (2+ years of experience) and III (5+ years of experience) engineers are being hired for this position." That's the About the role. Responsibilities list: bullet points after "Responsibilities". Let's extract each line: - Support system-level engineering activities across the full lifecycle, including concept development, design, integration, test, and transition to production. - Write, maintain, and manage technical documentation such as requirements, specifications, interface control documents, compliance matrices, and test plans. - Develop and document engineering processes and standards that align with customer requirements and program objectives. - Prepare documentation for and actively support formal system design and review events, including System Requirements Review (SRR), System Functional Review (SFR), Preliminary Design Review (PDR), Critical Design Review (CDR), and Test Readiness Review (TRR). - Work directly with customers to define, refine, and manage system requirements and ensure alignment throughout the program lifecycle. - Identify, analyze, and help solve moderate-complexity engineering problems in a timely and structured manner. - Apply and support digital engineering and model-based systems engineering (MBSE) practices where appropriate to improve traceability and design quality. - Support systems engineering activities such as architecture development, system integration planning, and risk management. - Establish and maintain requirements traceability and verification and validation (V&V) across system and subsystem levels using appropriate tools. - Contribute to configuration and documentation control practices to ensure consistency and accuracy of system baselines. - Collaborate closely with cross-functional engineering, test, and production teams to ensure successful implementation of system designs. - Participate in customer and internal technical meetings, providing clear status updates, technical input, and documentation support. That's responsibilities. Essential Skills list (maybe as Requirements). Let's extract each bullet: - 2+ years of related systems engineering experience for Level II roles, or 5+ years of related systems engineering experience for Sr roles. (Note: "Sr roles" maybe Level III) - Bachelor’s degree in engineering with relevant experience, or a Master’s degree in engineering; comparable experience may be accepted in lieu of a degree. - Hands-on experience in systems engineering across the system lifecycle, including requirements development, integration, and test. - Strong proficiency in requirements development, requirements traceability, and verification and validation (V&V). - Experience using DOORS or DOORS Next Generation (DNG) for requirements management. - Ability to write clear, structured technical documentation such as specifications, interface documents, and test plans. - Understanding of model-based systems engineering (MBSE) concepts and practices. - Familiarity with systems engineering documentation, configuration practices, and compliance tracking. - Ability to obtain and maintain a Secret security clearance. - Effective communication skills for working directly with customers and cross-functional engineering teams. - Ability to identify and resolve moderate-complexity engineering issues within program timelines. Additional Skills & Qualifications list: - Experience with Microsoft Power BI for data visualization and reporting. - Experience with Microsoft SharePoint for document and collaboration management. - Exposure to data analysis or data science tools and workflows. - Electro-mechanical hardware design experience or familiarity with electromechanical systems. - Familiarity with naval systems or naval operations, including maritime or NUWC-related programs. - Experience with MBSE tools such as Cameo Enterprise Architect. - Experience using MATLAB for modeling, analysis, or simulation. - Proficiency with Microsoft Office tools for documentation, presentations, and analysis. - Experience in systems engineering related to sonar, weapons systems, or underwater technology is beneficial. We could combine Essential Skills and Additional Skills into a Requirements section (or Skills). The instruction says we can use Requirements, Qualifications, Skills headings. Probably better to have Requirements (essential) and Skills (additional). But we must not create thin sections. Could combine into one Requirements section that includes both essential and additional? Might be okay. But we need to preserve all info; we can list them all under a single Requirements section with subheadings? Not allowed to add extra headings beyond those specified? We can use
- for list; we could separate essential and additional with
headings? Not specified. Safer to have two sections: Requirements (essential) and Skills (additional). Both are substantive. Benefits list: from Pay And Benefits section: list of benefits: - Medical, dental & vision - Critical Illness, Accident, and Hospital - 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available - Life Insurance (Voluntary Life & AD&D for the employee and dependents) - Short and long-term disability - Health Spending Account (HSA) - Transportation benefits - Employee Assistance Program - Time Off/Leave (PTO, Vacation or Sick Leave) Pay: pay range: $90000.00 - $130000.00/hr. Wait that seems odd: per hour? Probably per year but it's written as /hr. We'll keep as given. Schedule: Work Environment mentions flexible work schedules, including options such as 9/80, 4/10, or 5/8. Also mentions primarily onsite office environment with hybrid flexibility. So schedule section can capture flexible schedule options. We also have Work Environment paragraph about onsite, hybrid, occasional work on base at NUWC. Could be part of About the role or maybe a separate section? Not required headings. Could incorporate into About the role paragraph. We must not include boilerplate like "Job Type & Location", "Application Deadline", "About Actalent", equal opportunity, etc. Also remove "Workplace Type" duplicate. Also remove "Job Type & Location". Also remove "Application Deadline". Also remove "About Actalent" and all legal/EEO statements. Also remove "San Francisco Fair Chance Ordinance", etc. We must preserve all substantive information: that includes location (Middletown, RI), contract to hire, job type, location? The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location and job type maybe minor metadata; we could include in a short
under About the role or separate? The instruction says preserve ALL substantive information; location and job type are substantive. So we need to keep them. We can include them in a
after the About the role paragraph, maybe as part of About the role. Or we could create a separate section like "Job Details" but not in allowed headings. Better to fold into About the role paragraph. Thus About the role paragraph will include: description, plus note that it's Contract to Hire based out of Middletown, RI, Level II and III. We must not repeat job title as heading. Already not. Now construct HTML:
About the role
This Systems Engineer role provides system-level engineering support as part of a cross-functional team working on complex electromechanical systems, including sonar, weapons systems, and underwater technology. You will focus on requirements development, system documentation, design reviews, and supporting programs across the full system lifecycle—from concept and design through integration, test, and transition to production. Both Level II (2+ years of experience) and III (5+ years of experience) engineers are being hired for this position. This is a Contract to Hire position based out of Middletown, RI.
Responsibilities
- Support system-level engineering activities across the full lifecycle, including concept development, design, integration, test, and transition to production.
- Write, maintain, and manage technical documentation such as requirements, specifications, interface control documents, compliance matrices, and test plans.
- Develop and document engineering processes and standards that align with customer requirements and program objectives.
- Prepare documentation for and actively support formal system design and review events, including System Requirements Review (SRR), System Functional Review (SFR), Preliminary Design Review (PDR), Critical Design Review (CDR), and Test Readiness Review (TRR).
- Work directly with customers to define, refine, and manage system requirements and ensure alignment throughout the program lifecycle.
- Identify, analyze, and help solve moderate-complexity engineering problems in a timely and structured manner.
- Apply and support digital engineering and model-based systems engineering (MBSE) practices where appropriate to improve traceability and design quality.
- Support systems engineering activities such as architecture development, system integration planning, and risk management.
- Establish and maintain requirements traceability and verification and validation (V&V) across system and subsystem levels using appropriate tools.
- Contribute to configuration and documentation control practices to ensure consistency and accuracy of system baselines.
- Collaborate closely with cross-functional engineering, test, and production teams to ensure successful implementation of system designs.
- Participate in customer and internal technical meetings, providing clear status updates, technical input, and documentation support.
Requirements
- 2+ years of related systems engineering experience for Level II roles, or 5+ years of related systems engineering experience for Sr roles.
- Bachelor’s degree in engineering with relevant experience, or a Master’s degree in engineering; comparable experience may be accepted in lieu of a degree.
- Hands-on experience in systems engineering across the system lifecycle, including requirements development, integration, and test.
- Strong proficiency in requirements development, requirements traceability, and verification and validation (V&V).
- Experience using DOORS or DOORS Next Generation (DNG) for requirements management.
- Ability to write clear, structured technical documentation such as specifications, interface documents, and test plans.
- Understanding of model-based systems engineering (MBSE) concepts and practices.
- Familiarity with systems engineering documentation, configuration practices, and compliance tracking.
- Ability to obtain and maintain a Secret security clearance.
- Effective