Senior Systems Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content.
We have:
- About the role: The "Position Summary" paragraph(s). Also maybe the introductory paragraph about company? That could be part of About the role. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can include About the role with the summary and maybe company description.
- Responsibilities: There's a "Responsibilities" heading with bullet list. Also "Secondary Responsibilities". We can combine them under Responsibilities.
- Requirements: There's "Qualifications" heading with bullet list (Bachelor's degree etc). Also "Physical Requirements". Could be part of Requirements or Qualifications. The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where.
We have qualifications: Bachelor's degree, 5 years experience, fluency, ability to lead, proficiency with embedded systems, electrical/mechanical knowledge preferred. That's qualifications.
We have skills? Not explicit separate list; maybe we can treat some as Skills: e.g., "Ability to lead a technical group", "Proficiency with embedded systems", "Electrical/mechanical knowledge". But we already have qualifications. Could create Skills section for those.
We have Benefits: list under "Top Benefits". Include those.
We have Pay: "The annualized pay range for this role is $82,000.00 – 150,000.00 USD." Also mention discretionary target incentive compensation plan. That's pay.
We have Schedule: "9/80 Work Schedule (every other Friday off) work schedule, every other Friday off". Also mention Onsite Full Time Position. So schedule: 9/80 (every other Friday off). Also full-time onsite.
We need to avoid boilerplate: remove cookie/navigation/legal/EEO etc. So we strip the paragraphs about website, EEO, VERIFY, accommodation, privacy notice, contact hr, etc. Also remove "For additional information about Advanced Acoustic Concepts ("AAC"), please visit our website at: https://www.aaccorp.com". Also remove "Top Benefits (Subject To Terms Of Applicable Policies/plans)" maybe keep benefits list but drop the parenthetical note.
We must preserve all substantive information. So keep company description: "Advanced Acoustic Concepts, LLC, a wholly owned subsidiary Thales Defense & Security Inc., is a technical leader in the fields of sonar systems, sonar signal processing, acoustic training systems, and open architecture system and software integration. The venture focuses on emerging areas in the undersea warfare domain where the customer has identified mission-critical needs."
Also keep "Position Summary" paragraph(s). Keep responsibilities list (including secondary). Keep qualifications list (including physical requirements). Keep benefits list. Keep pay range. Keep schedule.
We must not invent or summarize away detail. So we need to keep each bullet point.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must not create sections with filler like "commensurate with experience". We have actual content for each.
We need to decide which headings to use.
Potential sections:
- About the role: includes company description and position summary paragraph(s). Could be two paragraphs.
- Responsibilities: includes primary responsibilities list and secondary responsibilities list (maybe combine).
- Qualifications: includes education/experience requirements, fluency, ability to lead, proficiency with embedded systems, electrical/mechanical knowledge preferred, plus physical requirements? Physical requirements could be separate but we could put under Qualifications or Requirements. Since we have a Requirements heading, maybe put physical requirements under Requirements. But we also have "Qualifications" heading for education/experience etc. Let's follow typical: Requirements = education/experience etc. Qualifications = maybe skills? But we have both headings available. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections.
We need to allocate content:
- Requirements: maybe the bullet list under "Qualifications" heading in the posting (Bachelor’s degree ...). That's more like requirements. Also physical requirements could be under Requirements.
- Qualifications: maybe the "Fluency in technologies and application domain", "Ability to lead a technical group independently", "Demonstrated proficiency and experience with embedded systems highly preferred.", "Electrical and/or mechanical engineering knowledge preferred." That's more like qualifications/skills.
- Skills: maybe we could put some of those as Skills, but we already have Qualifications. Could also have Skills for things like "computer-aided engineering or other design/analysis software", "budget, cost and schedule input", "specify and evaluate supplier components", etc. Those are more skills/duties. But we already have Responsibilities covering many of those. So maybe we don't need Skills section if content is thin. Better to avoid thin sections.
Thus we can have:
- About the role (company description + position summary)
- Responsibilities (primary + secondary)
- Requirements (education/experience + physical requirements)
- Qualifications (fluency, lead ability, embedded systems, electrical/mechanical knowledge)
- Benefits (list)
- Pay (pay range + incentive note)
- Schedule (9/80 work schedule, onsite full-time)
We must ensure we don't create sections with filler. All have real content.
Now format.
We need to output only HTML fragment, no /. Use
for each section heading.
Inside each section, we put appropriate
or
- .
Let's draft.
About the role:
Advanced Acoustic Concepts, LLC, a wholly owned subsidiary of Thales Defense & Security Inc., is a technical leader in the fields of sonar systems, sonar signal processing, acoustic training systems, and open architecture system and software integration. The venture focuses on emerging areas in the undersea warfare domain where the customer has identified mission‑critical needs.
Using a holistic approach, the senior systems engineer designs, develops, evaluates and modifies end‑to‑end systems and systems‑oriented products through the entire life cycle. This includes generating quantifiable requirements, system planning/design, acquisition logistics, and ensuring requirements comply with government and customer standards through formal verification methods. Translate high level product development strategies into system requirement specifications and work with other engineering disciplines to develop lower‑level detailed implementation requirements. Establish and coordinate development of standards, practices, and procedures as related to the overall product development. Designs interfaces and brings system elements together so they work as a whole. Assesses performance using evaluation criteria and technical performance measures. Generates system level requirements verification procedures and customer acceptance test procedures. Reviews test plans/procedures and ensures they meet the objectives of the contractual requirements and participates in the testing process to validate requirements.
That's the position summary.
Responsibilities:
We have primary responsibilities list (bulleted) and secondary responsibilities list.
Let's extract bullet points from the text:
Primary responsibilities (under "Responsibilities" heading):
- Responsible for leading engineering technical activities to completion on time and within budget. May lead a team of engineers to complete engineering projects successfully
- Design, develop, analyze, document and support testing of products, systems or subsystems
- May use computer-aided engineering or other design/analysis software in the performance of assignments.
- Review customer specifications and requirements, and under direction, develop designs to best support them, including cost as a key design variable
- Provide budget, cost and schedule input for design assignments
- Specify and evaluate supplier components, subsystems and services
- Drive the program design to cost and design for manufacture requirements
- Develop prototypes to retire key development risks
- Communicate clearly (written and oral) with other company personnel and the customer as required
- Participate in preparation of proposals
- Provide technical knowledge and assistance to other engineers and support personnel
- Lead and direct the work of others as assigned
- Support, communicate, reinforce and defend the mission, values and culture of the organization
Secondary responsibilities (under "Secondary Responsibilities"):
- Attend appropriate engineering, customer or business meetings
- Lead less-experienced engineers
We'll combine into one list.
Responsibilities section:
- Responsible for leading engineering technical activities to completion on time and within budget; may lead a team of engineers to complete engineering projects successfully.
- Design, develop, analyze, document and support testing of products, systems or subsystems.
- May use computer‑aided engineering or other design/analysis software in the performance of assignments.
- Review customer specifications and requirements, and under direction, develop designs to best support them, including cost as a key design variable.
- Provide budget, cost and schedule input for design assignments.
- Specify and evaluate supplier components, subsystems and services.
- Drive the program design to cost and design for manufacture requirements.
- Develop prototypes to retire key development risks.
- Communicate clearly (written and oral) with other company personnel and the customer as required.
- Participate in preparation of proposals.
- Provide technical knowledge and assistance to other engineers and support personnel.
- Lead and direct the work of others as assigned.
- Support, communicate, reinforce and defend the mission, values and culture of the organization.
- Attend appropriate engineering, customer or business meetings.
- Lead less‑experienced engineers.
Requirements:
We have Bachelor’s degree in engineering or related technical field with a minimum of 5 years of experience. Also physical requirements.
Let's list:
- Bachelor’s degree in engineering or related technical field
- Minimum of 5 years of experience
- Physical requirements: Lifting (up to 20 lbs.): up to 25% of time; Walking: up to 25% of time; Climbing, Bending, Standing, Stooping: up to 10% of time; Sitting: up to 75% of time; Travel: up to 10% of time
We could also include "Fluency in technologies and application domain" maybe under Qualifications.
Thus Requirements section:
- Bachelor’s degree in engineering or related technical field.
- Minimum of 5 years of experience.
- Physical requirements:
- Lifting (up to 20 lbs.): up to 25% of time.
- Walking: up to 25% of time.
- Climbing, Bending, Standing, Stooping: up to 10% of time.
- Sitting: up to 75% of time.
- Travel: up to 10% of time.
But nested lists maybe okay. Could also just put as separate - with semicolons. Simpler: just list each as separate
- . We'll do:
- Bachelor’s degree in engineering or related technical field.
- Minimum of 5 years of experience.
- Lifting (up to 20 lbs.): up to 25% of time.
- Walking: up to 25% of time.
- Climbing, Bending, Standing, Stooping: up to 10% of time.
- Sitting: up to 75% of time.
- Travel: up to 10% of time.
Qualifications:
From posting: Fluency in technologies and application domain; Ability to lead a technical group independently; Demonstrated proficiency and experience with embedded systems highly preferred.; Electrical and/or mechanical engineering knowledge preferred.
We'll list as - .
Qualifications section:
- F
for prose. We must not create sections with filler like "commensurate with experience". We have actual content for each. We need to decide which headings to use. Potential sections: - About the role: includes company description and position summary paragraph(s). Could be two paragraphs. - Responsibilities: includes primary responsibilities list and secondary responsibilities list (maybe combine). - Qualifications: includes education/experience requirements, fluency, ability to lead, proficiency with embedded systems, electrical/mechanical knowledge preferred, plus physical requirements? Physical requirements could be separate but we could put under Qualifications or Requirements. Since we have a Requirements heading, maybe put physical requirements under Requirements. But we also have "Qualifications" heading for education/experience etc. Let's follow typical: Requirements = education/experience etc. Qualifications = maybe skills? But we have both headings available. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections. We need to allocate content: - Requirements: maybe the bullet list under "Qualifications" heading in the posting (Bachelor’s degree ...). That's more like requirements. Also physical requirements could be under Requirements. - Qualifications: maybe the "Fluency in technologies and application domain", "Ability to lead a technical group independently", "Demonstrated proficiency and experience with embedded systems highly preferred.", "Electrical and/or mechanical engineering knowledge preferred." That's more like qualifications/skills. - Skills: maybe we could put some of those as Skills, but we already have Qualifications. Could also have Skills for things like "computer-aided engineering or other design/analysis software", "budget, cost and schedule input", "specify and evaluate supplier components", etc. Those are more skills/duties. But we already have Responsibilities covering many of those. So maybe we don't need Skills section if content is thin. Better to avoid thin sections. Thus we can have: - About the role (company description + position summary) - Responsibilities (primary + secondary) - Requirements (education/experience + physical requirements) - Qualifications (fluency, lead ability, embedded systems, electrical/mechanical knowledge) - Benefits (list) - Pay (pay range + incentive note) - Schedule (9/80 work schedule, onsite full-time) We must ensure we don't create sections with filler. All have real content. Now format. We need to output only HTML fragment, no /. Use
for each section heading. Inside each section, we put appropriate
or
- .
Let's draft.
About the role:
Advanced Acoustic Concepts, LLC, a wholly owned subsidiary of Thales Defense & Security Inc., is a technical leader in the fields of sonar systems, sonar signal processing, acoustic training systems, and open architecture system and software integration. The venture focuses on emerging areas in the undersea warfare domain where the customer has identified mission‑critical needs.
Using a holistic approach, the senior systems engineer designs, develops, evaluates and modifies end‑to‑end systems and systems‑oriented products through the entire life cycle. This includes generating quantifiable requirements, system planning/design, acquisition logistics, and ensuring requirements comply with government and customer standards through formal verification methods. Translate high level product development strategies into system requirement specifications and work with other engineering disciplines to develop lower‑level detailed implementation requirements. Establish and coordinate development of standards, practices, and procedures as related to the overall product development. Designs interfaces and brings system elements together so they work as a whole. Assesses performance using evaluation criteria and technical performance measures. Generates system level requirements verification procedures and customer acceptance test procedures. Reviews test plans/procedures and ensures they meet the objectives of the contractual requirements and participates in the testing process to validate requirements.
That's the position summary. Responsibilities: We have primary responsibilities list (bulleted) and secondary responsibilities list. Let's extract bullet points from the text: Primary responsibilities (under "Responsibilities" heading): - Responsible for leading engineering technical activities to completion on time and within budget. May lead a team of engineers to complete engineering projects successfully - Design, develop, analyze, document and support testing of products, systems or subsystems - May use computer-aided engineering or other design/analysis software in the performance of assignments. - Review customer specifications and requirements, and under direction, develop designs to best support them, including cost as a key design variable - Provide budget, cost and schedule input for design assignments - Specify and evaluate supplier components, subsystems and services - Drive the program design to cost and design for manufacture requirements - Develop prototypes to retire key development risks - Communicate clearly (written and oral) with other company personnel and the customer as required - Participate in preparation of proposals - Provide technical knowledge and assistance to other engineers and support personnel - Lead and direct the work of others as assigned - Support, communicate, reinforce and defend the mission, values and culture of the organization Secondary responsibilities (under "Secondary Responsibilities"): - Attend appropriate engineering, customer or business meetings - Lead less-experienced engineers We'll combine into one list. Responsibilities section:- Responsible for leading engineering technical activities to completion on time and within budget; may lead a team of engineers to complete engineering projects successfully.
- Design, develop, analyze, document and support testing of products, systems or subsystems.
- May use computer‑aided engineering or other design/analysis software in the performance of assignments.
- Review customer specifications and requirements, and under direction, develop designs to best support them, including cost as a key design variable.
- Provide budget, cost and schedule input for design assignments.
- Specify and evaluate supplier components, subsystems and services.
- Drive the program design to cost and design for manufacture requirements.
- Develop prototypes to retire key development risks.
- Communicate clearly (written and oral) with other company personnel and the customer as required.
- Participate in preparation of proposals.
- Provide technical knowledge and assistance to other engineers and support personnel.
- Lead and direct the work of others as assigned.
- Support, communicate, reinforce and defend the mission, values and culture of the organization.
- Attend appropriate engineering, customer or business meetings.
- Lead less‑experienced engineers.
- Bachelor’s degree in engineering or related technical field.
- Minimum of 5 years of experience.
- Physical requirements:
- Lifting (up to 20 lbs.): up to 25% of time.
- Walking: up to 25% of time.
- Climbing, Bending, Standing, Stooping: up to 10% of time.
- Sitting: up to 75% of time.
- Travel: up to 10% of time.
- with semicolons. Simpler: just list each as separate
- . We'll do:
- Bachelor’s degree in engineering or related technical field.
- Minimum of 5 years of experience.
- Lifting (up to 20 lbs.): up to 25% of time.
- Walking: up to 25% of time.
- Climbing, Bending, Standing, Stooping: up to 10% of time.
- Sitting: up to 75% of time.
- Travel: up to 10% of time.
- .
Qualifications section:
- F