Senior Software Test Engineer
BAE Systems, Inc. · Layton, UT · 1 mo ago
On-siteInformation Technology$107k–$183k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule (if present). We must not repeat job title. Must include only sections with real content. Remove boilerplate.
We need to parse the job description.
Content:
- Intro: "Job Description BAE Systems is seeking an individual to fill the role of a Software Test Engineer. You will gain experience in one of the largest government contracts while reviewing software development in every facet of today's best practices. The ideal candidate would provide a mix of software and systems engineering expertise while also understanding software development practices. This is an exciting opportunity to support the Air Force's acquisition of the next-generation Sentinel Intercontinental Ballistic Missile (ICBM) System."
That's about the role.
- Responsibilities: list bullet points after "Responsibilities Included". Let's extract:
"Test software product that will enable depoloyment of other software products to warfighter"
"Ensure safety and potential NSCCA certification"
"Compliance with zero-fail safety standards and formal safety program reviews"
"Act as Software Subject Matter Expert to review and define software systems requirements, specification documents, processes, plans, guides, and reports"
"Coordinate with other teams, agencies, and stakeholders in the development and evaluation of software systems engineering requirements"
Also there is "Pursuant to Government contract, this position requires US Citizenship status #ISC" - that's a requirement, maybe under Requirements.
- Required Education, Experience, & Skills: list:
"Bachelors degree in Computer Science, Computer Engineering or Software Engineering"
"Minimum 7 years of related experience (or 5 years with Masters)"
"Proficient with C++ (MISRA standards a plus)"
"Experience with testing tools such as SonarQube, Cybpress, GBD, etc."
"Familiar with commercial encryption and signature standards (symmetric and asymmetric encryption)"
"Familiar with DOORS and MS Visual Studio"
"Familiar with secure coding standards for software assurance"
"Familiar with writing test procedures and verification of requirements"
"Knowledge of GitLab and pipelines"
"Can effectively communicate issues and test requirements to developers and external stakeholders"
"Secret Clearance"
"Ability to obtain Sentinel Program Access"
- Preferred Education, Experience, & Skills: list:
"Developmental Test and Evaluation (DT&E) or Operational Test and Evaluation (OT&E) experience"
"Strong verbal/written communications skills and peer-to-leader presentations"
"Ability to work in a dynamic setting that includes variable workloads and shifting priorities"
"Ability to take initiative and execute tasks with limited day-to-day direction"
"Experience with any coding or scripting language"
"Experience with Agile software metrics (e.g., burnup/burndown, velocity, code coverage)"
"Aerospace Software Standards (DO-178C, ARINC-653, ARINC-661, MISRA C, etc.)"
"Agile/SAFe/Lean development"
"Experience with software requirements development"
"DevSecOps pipelines, tools and techniques operated within a cloud-based environmen"
- Pay Information: "Full-Time Salary Range: $107359 - $182510" plus note about determination.
- Employee Benefits: paragraph describing benefits.
- About BAE Systems Intelligence & Security: description of company.
- Also there is "This position will be posted for at least 5 calendar days. The posting will remain active until the position is filled, or a qualified pool of candidates is identified." That's boilerplate/application instructions? It's about posting duration; maybe we can drop as it's not substantive? The instruction says remove application instructions. This is about posting duration, maybe considered boilerplate. We'll drop.
We need sections: About the role (intro), Responsibilities, Requirements (maybe combine Required Education, Experience, & Skills), Qualifications (maybe Preferred?), Skills (maybe separate?), Benefits, Pay. Schedule not present.
We must not create sections with filler. Use for each section heading.
We need to decide grouping: Could have sections: About the role, Responsibilities, Required Qualifications (Education/Experience), Preferred Qualifications, Skills (maybe combine required and preferred skills?), Benefits, Pay.
But we must not repeat job title. Use
for each section heading.
We need to decide grouping: Could have sections: About the role, Responsibilities, Required Qualifications (Education/Experience), Preferred Qualifications, Skills (maybe combine required and preferred skills?), Benefits, Pay.
But we must not repeat job title. Use - for any list of duties/requirements/benefits.
We need to preserve all substantive info.
Let's extract each piece.
About the role paragraph: combine the intro sentences.
Responsibilities list: as above.
Required Education, Experience, & Skills: list items.
Preferred Education, Experience, & Skills: list items.
Skills: maybe we could separate required skills vs preferred? But we already have required and preferred sections. Could combine skills under those sections. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to map content:
- About the role: intro paragraph.
- Responsibilities: bullet list.
- Requirements: maybe the required education/experience/skills (including clearance). Could be titled "Requirements".
- Qualifications: maybe the preferred qualifications (DT&E experience etc). Could be titled "Qualifications".
- Skills: maybe we could list specific technical skills (C++, testing tools, encryption, DOORS, VS Studio, secure coding, test procedures, GitLab, pipelines, communication). But those are already in requirements. Could split: Requirements for education/experience, Skills for technical skills. But we have to avoid duplication. The instruction says preserve ALL substantive information; we can duplicate? Better to not duplicate. We could put technical skills under Skills section, and education/experience under Requirements. But the required list includes both education/experience and skills. We could separate: Requirements: education/experience and clearance. Skills: technical skills and communication. Preferred: additional qualifications.
Let's parse required list:
- Bachelors degree in Computer Science, Computer Engineering or Software Engineering
- Minimum 7 years of related experience (or 5 years with Masters)
- Proficient with C++ (MISRA standards a plus)
- Experience with testing tools such as SonarQube, Cybpress, GBD, etc.
- Familiar with commercial encryption and signature standards (symmetric and asymmetric encryption)
- Familiar with DOORS and MS Visual Studio
- Familiar with secure coding standards for software assurance
- Familiar with writing test procedures and verification of requirements
- Knowledge of GitLab and pipelines
- Can effectively communicate issues and test requirements to developers and external stakeholders
- Secret Clearance
- Ability to obtain Sentinel Program Access
Thus we could split:
Requirements (education/experience/clearance):
- Bachelors degree in Computer Science, Computer Engineering or Software Engineering
- Minimum 7 years of related experience (or 5 years with Masters)
- Secret Clearance
- Ability to obtain Sentinel Program Access
Skills (technical):
- Proficient with C++ (MISRA standards a plus)
- Experience with testing tools such as SonarQube, Cybpress, GBD, etc.
- Familiar with commercial encryption and signature standards (symmetric and asymmetric encryption)
- Familiar with DOORS and MS Visual Studio
- Familiar with secure coding standards for software assurance
- Familiar with writing test procedures and verification of requirements
- Knowledge of GitLab and pipelines
- Can effectively communicate issues and test requirements to developers and external stakeholders
Preferred Qualifications:
- Developmental Test and Evaluation (DT&E) or Operational Test and Evaluation (OT&E) experience
- Strong verbal/written communications skills and peer-to-leader presentations
- Ability to work in a dynamic setting that includes variable workloads and shifting priorities
- Ability to take initiative and execute tasks with limited day-to-day direction
- Experience with any coding or scripting language
- Experience with Agile software metrics (e.g., burnup/burndown, velocity, code coverage)
- Aerospace Software Standards (DO-178C, ARINC-653, ARINC-661, MISRA C, etc.)
- Agile/SAFe/Lean development
- Experience with software requirements development
- DevSecOps pipelines, tools and techniques operated within a cloud-based environment
Benefits: paragraph.
Pay: salary range and note.
We must not include boilerplate like "Please note: This range is based on our market pay structures..." but that is substantive? It's explanatory but maybe we keep as part of Pay section. It's not boilerplate; it's info about determination. We'll keep.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Qualifications
- ...
...
Benefits
...
Pay
...
Make sure no extra sections.
Now craft the paragraphs.
About the role paragraph: combine sentences:
"BAE Systems is seeking an individual to fill the role of a Software Test Engineer. You will gain experience in one of the largest government contracts while reviewing software development in every facet of today's best practices. The ideal candidate would provide a mix of software and systems engineering expertise while also understanding software development practices. This is an exciting opportunity to support the Air Force's acquisition of the next-generation Sentinel Intercontinental Ballistic Missile (ICBM) System."
That's fine.
Responsibilities bullets:
- Test software product that will enable deployment of other software products to warfighter (note typo depoloyment -> deployment but we preserve as given? Should we preserve exactly? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the text as is, including typo "depoloyment". We'll keep exactly.
- Ensure safety and potential NSCCA certification
- Compliance with zero-fail safety standards and formal safety program reviews
- Act as Software Subject Matter Expert to review and define software systems requirements, specification documents, processes, plans, guides, and reports
- Coordinate with other teams, agencies, and stakeholders in the development and evaluation of software systems engineering requirements
Requirements bullets (education/experience/clearance):
- Bachelors degree in Computer Science, Computer Engineering or Software Engineering
- Minimum 7 years of related experience (or 5 years with Masters)
- Secret Clearance
- Ability to obtain Sentinel Program Access
Skills bullets:
- Proficient with C++ (MISRA standards a plus)
- Experience with testing tools such as SonarQube, Cybpress, GBD, etc.
- Familiar with commercial encryption and signature standards (symmetric and asymmetric encryption)
- Familiar with DOORS and MS Visual Studio
- Familiar with secure coding standards for software assurance
- Familiar with writing test procedures and verification of requirements
- Knowledge of GitLab and pipelines
- Can effectively communicate issues and test requirements to developers and external stakeholders
Qualifications bullets (preferred):
- Developmental Test and Evaluation (DT&E) or Operational Test and Evaluation (OT&E) experience
- Strong verbal/written communications skills and peer-to-leader presentations
- Ability to work in a dynamic setting that includes variable workloads and shifting priorities
- Ability to take initiative and execute tasks with limited day-to-day direction
- Experience with any coding or scripting language
- Experience with Agile software metrics (e.g., burnup/burndown, velocity, code coverage)
- Aerospace Software Standards (DO-178C, ARINC-653, ARINC-661, MISRA C, etc.)
- Agile/SAFe/Lean development
- Experience with software requirements development
- DevSecOps pipelines, tools and techniques operated within a cloud-based environment
Benefits paragraph: copy the benefits paragraph exactly:
"At BAE Systems, we support our employees in all aspects of their life, including their health and financial well-being. Regular
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to map content:
- About the role: intro paragraph.
- Responsibilities: bullet list.
- Requirements: maybe the required education/experience/skills (including clearance). Could be titled "Requirements".
- Qualifications: maybe the preferred qualifications (DT&E experience etc). Could be titled "Qualifications".
- Skills: maybe we could list specific technical skills (C++, testing tools, encryption, DOORS, VS Studio, secure coding, test procedures, GitLab, pipelines, communication). But those are already in requirements. Could split: Requirements for education/experience, Skills for technical skills. But we have to avoid duplication. The instruction says preserve ALL substantive information; we can duplicate? Better to not duplicate. We could put technical skills under Skills section, and education/experience under Requirements. But the required list includes both education/experience and skills. We could separate: Requirements: education/experience and clearance. Skills: technical skills and communication. Preferred: additional qualifications.
Let's parse required list:
- Bachelors degree in Computer Science, Computer Engineering or Software Engineering
- Minimum 7 years of related experience (or 5 years with Masters)
- Proficient with C++ (MISRA standards a plus)
- Experience with testing tools such as SonarQube, Cybpress, GBD, etc.
- Familiar with commercial encryption and signature standards (symmetric and asymmetric encryption)
- Familiar with DOORS and MS Visual Studio
- Familiar with secure coding standards for software assurance
- Familiar with writing test procedures and verification of requirements
- Knowledge of GitLab and pipelines
- Can effectively communicate issues and test requirements to developers and external stakeholders
- Secret Clearance
- Ability to obtain Sentinel Program Access
Thus we could split:
Requirements (education/experience/clearance):
- Bachelors degree in Computer Science, Computer Engineering or Software Engineering
- Minimum 7 years of related experience (or 5 years with Masters)
- Secret Clearance
- Ability to obtain Sentinel Program Access
Skills (technical):
- Proficient with C++ (MISRA standards a plus)
- Experience with testing tools such as SonarQube, Cybpress, GBD, etc.
- Familiar with commercial encryption and signature standards (symmetric and asymmetric encryption)
- Familiar with DOORS and MS Visual Studio
- Familiar with secure coding standards for software assurance
- Familiar with writing test procedures and verification of requirements
- Knowledge of GitLab and pipelines
- Can effectively communicate issues and test requirements to developers and external stakeholders
Preferred Qualifications:
- Developmental Test and Evaluation (DT&E) or Operational Test and Evaluation (OT&E) experience
- Strong verbal/written communications skills and peer-to-leader presentations
- Ability to work in a dynamic setting that includes variable workloads and shifting priorities
- Ability to take initiative and execute tasks with limited day-to-day direction
- Experience with any coding or scripting language
- Experience with Agile software metrics (e.g., burnup/burndown, velocity, code coverage)
- Aerospace Software Standards (DO-178C, ARINC-653, ARINC-661, MISRA C, etc.)
- Agile/SAFe/Lean development
- Experience with software requirements development
- DevSecOps pipelines, tools and techniques operated within a cloud-based environment
Benefits: paragraph.
Pay: salary range and note.
We must not include boilerplate like "Please note: This range is based on our market pay structures..." but that is substantive? It's explanatory but maybe we keep as part of Pay section. It's not boilerplate; it's info about determination. We'll keep.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Qualifications
- ... ...
Benefits
...
Pay
...
Make sure no extra sections. Now craft the paragraphs. About the role paragraph: combine sentences: "BAE Systems is seeking an individual to fill the role of a Software Test Engineer. You will gain experience in one of the largest government contracts while reviewing software development in every facet of today's best practices. The ideal candidate would provide a mix of software and systems engineering expertise while also understanding software development practices. This is an exciting opportunity to support the Air Force's acquisition of the next-generation Sentinel Intercontinental Ballistic Missile (ICBM) System." That's fine. Responsibilities bullets: - Test software product that will enable deployment of other software products to warfighter (note typo depoloyment -> deployment but we preserve as given? Should we preserve exactly? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the text as is, including typo "depoloyment". We'll keep exactly. - Ensure safety and potential NSCCA certification - Compliance with zero-fail safety standards and formal safety program reviews - Act as Software Subject Matter Expert to review and define software systems requirements, specification documents, processes, plans, guides, and reports - Coordinate with other teams, agencies, and stakeholders in the development and evaluation of software systems engineering requirements Requirements bullets (education/experience/clearance): - Bachelors degree in Computer Science, Computer Engineering or Software Engineering - Minimum 7 years of related experience (or 5 years with Masters) - Secret Clearance - Ability to obtain Sentinel Program Access Skills bullets: - Proficient with C++ (MISRA standards a plus) - Experience with testing tools such as SonarQube, Cybpress, GBD, etc. - Familiar with commercial encryption and signature standards (symmetric and asymmetric encryption) - Familiar with DOORS and MS Visual Studio - Familiar with secure coding standards for software assurance - Familiar with writing test procedures and verification of requirements - Knowledge of GitLab and pipelines - Can effectively communicate issues and test requirements to developers and external stakeholders Qualifications bullets (preferred): - Developmental Test and Evaluation (DT&E) or Operational Test and Evaluation (OT&E) experience - Strong verbal/written communications skills and peer-to-leader presentations - Ability to work in a dynamic setting that includes variable workloads and shifting priorities - Ability to take initiative and execute tasks with limited day-to-day direction - Experience with any coding or scripting language - Experience with Agile software metrics (e.g., burnup/burndown, velocity, code coverage) - Aerospace Software Standards (DO-178C, ARINC-653, ARINC-661, MISRA C, etc.) - Agile/SAFe/Lean development - Experience with software requirements development - DevSecOps pipelines, tools and techniques operated within a cloud-based environment Benefits paragraph: copy the benefits paragraph exactly: "At BAE Systems, we support our employees in all aspects of their life, including their health and financial well-being. Regular