Systems Engineer
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc.
We need to parse the job description.
Sections present:
- About the role: The description includes a paragraph about 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 Sr (5+ years of experience) engineers are being hired for this position."
That's about the role.
- Responsibilities: list of bullet points under "Responsibilities". We need to output - for each.
- Requirements: The posting includes "Essential Skills" which are essentially requirements. Could map to Requirements section. Also "Additional Skills & Qualifications" maybe Qualifications? The instruction: Use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide mapping.
We have "Essential Skills" list: includes experience years, degree, hands-on experience, proficiency, DOORS, documentation, MBSE concepts, familiarity, clearance, communication, ability to resolve issues. That's more like Requirements/Qualifications.
We have "Additional Skills & Qualifications": list of extra skills like Power BI, SharePoint, data analysis, electro-mechanical hardware design, familiarity with naval systems, MBSE tools, MATLAB, MS Office, experience in sonar etc.
We also have "Work Environment": includes onsite office, hybrid flexibility, occasional work on base, flexible work schedules (9/80, 4/10, 5/8). That could map to Schedule? Actually schedule is about work hours. The posting mentions flexible work schedules, including options such as 9/80, 4/10, or 5/8. That's schedule info. Also Work Environment could be a separate section but not in allowed headings; we could incorporate into Schedule or maybe omit if not specific heading. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have schedule content: flexible work schedules. So we can create a
Schedule
with that info.
Pay And Benefits: we have pay range and benefits list. So we need Pay and Benefits sections. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need separate Pay and Benefits headings. The posting includes "Pay And Benefits" with pay range and benefits list. We should split: Pay section with pay range; Benefits section with list of benefits.
We also have "Work Environment" maybe could be part of Skills? Not really. Could be omitted if no heading matches. But we could incorporate into Schedule? Not exactly. The schedule heading is for work schedule; work environment could be omitted. However we might include a "Skills" section for technical skills? The posting includes Essential Skills and Additional Skills & Qualifications. Could combine into Skills section. But we already have Requirements and Qualifications headings. Might be better to map Essential Skills to Requirements, Additional Skills & Qualifications to Qualifications, and maybe Skills not needed. But we have both Requirements and Qualifications headings allowed; we can use both.
Thus:
- About the role
...
- Responsibilities
- ... each bullet
- Requirements
- ... essential skills items
- Qualifications
- ... additional skills & qualifications items
- Benefits
- ... benefits list
- Pay
Pay range: $90000.00 - $130000.00/hr. (note: likely per year but as given) Individual compensation offered ... depends on many factors...
- Schedule
Flexible work schedules including options such as 9/80, 4/10, or 5/8. Primarily onsite office with hybrid flexibility; occasional work on base at NUWC.
We must not include boilerplate like EEO, legal, etc. Also must not include Application Deadline, About Actalent, etc. Also must not include Job Type & Location? Actually location is Middletown, RI. Could be included maybe in About the role? But we should preserve all substantive information. Location is substantive. Should we include it? 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. Location is not minor metadata; it's substantive. We could include location in About the role paragraph or as a separate short p. Since we don't have a heading for Location, we can fold it into About the role paragraph.
Also Job Type: Contract to Hire. That's substantive. Could fold into About the role.
Thus About the role paragraph will include: This Systems Engineer role provides system-level engineering support... Both Level II (2+ years) and Sr (5+ years) engineers are being hired. This is a Contract to Hire position based out of Middletown, RI.
We need to preserve all substantive info: also mention that the role is primarily based in an onsite office environment with hybrid flexibility depending on business needs and program requirements. That's schedule/work environment; we already have schedule section covering flexible schedules and onsite. Could also mention that the position is hands-on and involves regular interaction with customers and cross-functional teams, so candidates should expect to be onsite most of the time. That's also schedule/work environment. We'll include in Schedule section.
Now we need to ensure we don't include filler like "commensurate with experience", etc. Not present.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's craft.
First, 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 Sr (5+ years of experience) engineers are being hired for this position. This is a Contract to Hire position based out of Middletown, RI.
Now Responsibilities: list each bullet from the responsibilities section.
Let's extract bullets:
- 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.
We'll output each as - .
Now Requirements (Essential Skills):
List:
- 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 communication skills for working directly with customers and cross-functional engineering teams.
- Ability to identify and resolve moderate-complexity engineering issues within program timelines.
Now Qualifications (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.
Now Benefits: list from posting:
- 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)
We'll output each as
- .
Now Pay: we need to include the pay range and note about individual compensation.
The pay range for this position is $90000.00 - $130000.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
Note: The posting says "/hr." but likely per year; we keep as given.
Now Schedule: include flexible work schedules and onsite details.
Flexible work schedules are available, including options such as 9/80, 4/10, or 5/8. The role is primarily based in an onsite office environment with hybrid flexibility depending on business needs and program requirements, and candidates should expect to be onsite most of the time due to hands-on work and regular interaction with customers and cross‑functional teams. Occasional work may be required on base at NUWC in support of maritime and underwater technology programs.
We must ensure we didn't repeat any info unnecessarily. The About the role paragraph already mentions onsite office environment? Not yet; we
Schedule
with that info. Pay And Benefits: we have pay range and benefits list. So we need Pay and Benefits sections. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need separate Pay and Benefits headings. The posting includes "Pay And Benefits" with pay range and benefits list. We should split: Pay section with pay range; Benefits section with list of benefits.
We also have "Work Environment" maybe could be part of Skills? Not really. Could be omitted if no heading matches. But we could incorporate into Schedule? Not exactly. The schedule heading is for work schedule; work environment could be omitted. However we might include a "Skills" section for technical skills? The posting includes Essential Skills and Additional Skills & Qualifications. Could combine into Skills section. But we already have Requirements and Qualifications headings. Might be better to map Essential Skills to Requirements, Additional Skills & Qualifications to Qualifications, and maybe Skills not needed. But we have both Requirements and Qualifications headings allowed; we can use both.
Thus:
- About the role
...
-Responsibilities
- ... each bullet
Requirements
- ... essential skills items
Qualifications
- ... additional skills & qualifications items
Benefits
- ... benefits list
Pay
Pay range: $90000.00 - $130000.00/hr. (note: likely per year but as given) Individual compensation offered ... depends on many factors...
-Schedule
Flexible work schedules including options such as 9/80, 4/10, or 5/8. Primarily onsite office with hybrid flexibility; occasional work on base at NUWC.
We must not include boilerplate like EEO, legal, etc. Also must not include Application Deadline, About Actalent, etc. Also must not include Job Type & Location? Actually location is Middletown, RI. Could be included maybe in About the role? But we should preserve all substantive information. Location is substantive. Should we include it? 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 shortor drop it. Location is not minor metadata; it's substantive. We could include location in About the role paragraph or as a separate short p. Since we don't have a heading for Location, we can fold it into About the role paragraph. Also Job Type: Contract to Hire. That's substantive. Could fold into About the role. Thus About the role paragraph will include: This Systems Engineer role provides system-level engineering support... Both Level II (2+ years) and Sr (5+ years) engineers are being hired. This is a Contract to Hire position based out of Middletown, RI. We need to preserve all substantive info: also mention that the role is primarily based in an onsite office environment with hybrid flexibility depending on business needs and program requirements. That's schedule/work environment; we already have schedule section covering flexible schedules and onsite. Could also mention that the position is hands-on and involves regular interaction with customers and cross-functional teams, so candidates should expect to be onsite most of the time. That's also schedule/work environment. We'll include in Schedule section. Now we need to ensure we don't include filler like "commensurate with experience", etc. Not present. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. First, 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 Sr (5+ years of experience) engineers are being hired for this position. This is a Contract to Hire position based out of Middletown, RI.
Now Responsibilities: list each bullet from the responsibilities section. Let's extract bullets: - 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. We'll output each asThe pay range for this position is $90000.00 - $130000.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
Note: The posting says "/hr." but likely per year; we keep as given. Now Schedule: include flexible work schedules and onsite details.Flexible work schedules are available, including options such as 9/80, 4/10, or 5/8. The role is primarily based in an onsite office environment with hybrid flexibility depending on business needs and program requirements, and candidates should expect to be onsite most of the time due to hands-on work and regular interaction with customers and cross‑functional teams. Occasional work may be required on base at NUWC in support of maritime and underwater technology programs.
We must ensure we didn't repeat any info unnecessarily. The About the role paragraph already mentions onsite office environment? Not yet; we