Engineer Software Quality
Northrop Grumman · San Diego, CA · 4 wk ago
On-siteEngineering$81k–$122k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
Key info:
- Description: At Northrop Grumman... (some generic). This could be "About the role" or "Description". We'll treat as About the role.
- Responsibilities: list of bullet points after "Responsibilities Include But Are Not Limited To". Those are bullet points.
- Basic Qualifications: list of requirements.
- Preferred Qualifications: list.
- Primary Level Salary Range: $81,300.00 - $121,900.00. Also mention overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director, benefits: health insurance, life and disability, savings plan, company paid holidays, PTO.
- Travel: Yes, 10% of the Time.
- Relocation assistance: No.
- Clearance required: Secret.
- Travel: Yes, 10% of the Time.
- Possibly schedule? Not given.
- Pay: we have salary range.
- Benefits: we have list.
- Schedule: not given.
- Also mention "U.S. Citizenship is required for all positions with a government clearance and certain other restricted positions." That's a requirement.
- Also "Must have the ability to obtain and maintain DoD Clearance at the Secret level".
- Also "Active Secret Clearance" as preferred.
- Also "Experience with IBM DOORS", etc.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove the EEO statement, the application period, the note about position description not representing a current opening, etc.
We need to preserve all substantive information.
We need to decide sections:
- About the role: description paragraph(s). Could combine the introductory paragraph about Northrop Grumman and the specific role description: "Northrop Grumman Aeronautics Systems Sector is seeking an Engineer Software Quality to join our team of qualified, diverse individuals located in Rancho Bernardo, CA. The successful candidate will define and monitor mission assurance program specifications and processes to ensure mission success. Performs quality, risk management, safety, reliability and maintainability of program achievements, subcontractors, and suppliers in accordance with contractual requirements. Assesses program performance and risks and determines resources to ensure mission assurance."
That's substantive.
- Responsibilities: list bullet points.
- Requirements: maybe combine Basic Qualifications and citizenship/clearance requirement? Could have a "Qualifications" section for basic qualifications, and "Preferred Qualifications" for preferred. Or we could have "Requirements" for basic qualifications and "Preferred Qualifications" separate. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have flexibility: we can use Requirements for basic qualifications, Qualifications for preferred? Or Skills for skills? Let's map:
- Requirements: basic qualifications (Bachelor's degree, 2 years experience or Masters, ability to obtain Secret clearance, knowledge of Agile, C#/C++, Python, process monitoring, data collection, analysis, metric reporting, process and product evaluation, software code review).
- Qualifications: maybe preferred qualifications? Or we could treat "Preferred Qualifications" as Qualifications.
- Skills: maybe list specific skills like IBM DOORS, requirement traceability, Atlassian tools, etc. But we could also put those under Qualifications.
Better to follow typical structure: Requirements (mandatory), Preferred Qualifications (preferred), Skills (maybe technical skills). But we have limited headings; we can choose to include Requirements, Qualifications, Skills, Benefits, Pay.
We need to avoid empty sections.
Let's extract:
Basic Qualifications (mandatory):
- Bachelor’s degree in engineering or other STEM-related field and 2 years of relevant software development integration work experience
- OR a Masters in STEM with 0 years of relevant software development integration work experience
- Must have the ability to obtain and maintain DoD Clearance at the Secret level
- Demonstrated knowledge of Agile software development processes
- Demonstrated knowledge of C# (or C++) and Python
- Demonstrated experience in process monitoring, data collection, analysis, and metric reporting
- Demonstrated experience in process and product evaluation
- Experience with software code review
Also U.S. Citizenship required for positions with government clearance.
Preferred Qualifications:
- Active Secret Clearance
- Experience with IBM DOORS
- Experience with requirement traceability
- Experience in a Software Engineering environment in an engineering capacity, work plan review, and root cause/corrective action analysis.
- Experience using Atlassian tool suite and tools like Bitbucket, Jira, and Confluence.
- Ability to work independently with all levels of management and customer representatives to identify solutions to complex problems.
- Understanding of Python libraries related to data analysis and machine learning
- Hardware Engineering or hardware quality experience.
- Aircraft industry experience.
- Experience implementing formal software certification efforts, such as DO-178, DO-254 or DO-330
- Experience leading diverse teams via a formalized Root Cause/Corrective Action process
Skills: maybe we can list technical skills: Agile, C#/C++, Python, IBM DOORS, requirement traceability, Atlassian tools (Jira, Bitbucket, Confluence), DO-178/DO-254/DO-330, root cause/corrective action, data analysis libraries, etc.
But we could also incorporate skills into Qualifications.
Given instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one "Requirements" section that includes both basic and preferred? But they said headings like Requirements, Qualifications, Skills. Could use Requirements for basic, Qualifications for preferred, Skills for technical skills.
Let's decide:
- About the role: description paragraph.
- Responsibilities: bullet list.
- Requirements: basic qualifications (degree/experience, clearance, Agile, C#/C++/Python, process monitoring, data analysis, process/product evaluation, code review, US citizenship).
- Qualifications: preferred qualifications (active secret clearance, IBM DOORS, requirement traceability, Atlassian tools, ability to work independently, Python libraries for ML, hardware/aircraft experience, DO-178/254/330, leading diverse teams via RCCA).
- Skills: maybe we can list specific technical skills: Agile, C#/C++, Python, IBM DOORS, requirement traceability, Atlassian (Jira, Bitbucket, Confluence), DO-178/DO-254/DO-330, root cause/corrective action, data analysis libraries, etc. But this may be redundant with Qualifications. Could omit Skills section to avoid thin sections. However we have Pay and Benefits sections.
- Pay: salary range $81,300 - $121,900, plus mention overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director.
- Benefits: health insurance, life and disability insurance, savings plan, company paid holidays, paid time off (PTO) for vacation/personal business.
- Schedule: not given, so omit.
- Travel: Yes, 10% of the Time. Could be included under About the role or a separate section? There's no heading for Travel; we could include in About the role paragraph or maybe under Responsibilities? Better to add a short paragraph under About the role mentioning travel requirement.
- Relocation assistance: No relocation assistance available. Could be mentioned in About the role or a note. Not a heading.
- Clearance required: Secret. Already covered in Requirements.
We must not include boilerplate like EEO, application period, etc.
Now produce HTML fragment.
Structure:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
Key info:
- Description: At Northrop Grumman... (some generic). This could be "About the role" or "Description". We'll treat as About the role.
- Responsibilities: list of bullet points after "Responsibilities Include But Are Not Limited To". Those are bullet points.
- Basic Qualifications: list of requirements.
- Preferred Qualifications: list.
- Primary Level Salary Range: $81,300.00 - $121,900.00. Also mention overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director, benefits: health insurance, life and disability, savings plan, company paid holidays, PTO.
- Travel: Yes, 10% of the Time.
- Relocation assistance: No.
- Clearance required: Secret.
- Travel: Yes, 10% of the Time.
- Possibly schedule? Not given.
- Pay: we have salary range.
- Benefits: we have list.
- Schedule: not given.
- Also mention "U.S. Citizenship is required for all positions with a government clearance and certain other restricted positions." That's a requirement.
- Also "Must have the ability to obtain and maintain DoD Clearance at the Secret level".
- Also "Active Secret Clearance" as preferred.
- Also "Experience with IBM DOORS", etc.
We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove the EEO statement, the application period, the note about position description not representing a current opening, etc.
We need to preserve all substantive information.
We need to decide sections:
- About the role: description paragraph(s). Could combine the introductory paragraph about Northrop Grumman and the specific role description: "Northrop Grumman Aeronautics Systems Sector is seeking an Engineer Software Quality to join our team of qualified, diverse individuals located in Rancho Bernardo, CA. The successful candidate will define and monitor mission assurance program specifications and processes to ensure mission success. Performs quality, risk management, safety, reliability and maintainability of program achievements, subcontractors, and suppliers in accordance with contractual requirements. Assesses program performance and risks and determines resources to ensure mission assurance."
That's substantive.
- Responsibilities: list bullet points.
- Requirements: maybe combine Basic Qualifications and citizenship/clearance requirement? Could have a "Qualifications" section for basic qualifications, and "Preferred Qualifications" for preferred. Or we could have "Requirements" for basic qualifications and "Preferred Qualifications" separate. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have flexibility: we can use Requirements for basic qualifications, Qualifications for preferred? Or Skills for skills? Let's map:
- Requirements: basic qualifications (Bachelor's degree, 2 years experience or Masters, ability to obtain Secret clearance, knowledge of Agile, C#/C++, Python, process monitoring, data collection, analysis, metric reporting, process and product evaluation, software code review).
- Qualifications: maybe preferred qualifications? Or we could treat "Preferred Qualifications" as Qualifications.
- Skills: maybe list specific skills like IBM DOORS, requirement traceability, Atlassian tools, etc. But we could also put those under Qualifications.
Better to follow typical structure: Requirements (mandatory), Preferred Qualifications (preferred), Skills (maybe technical skills). But we have limited headings; we can choose to include Requirements, Qualifications, Skills, Benefits, Pay.
We need to avoid empty sections.
Let's extract:
Basic Qualifications (mandatory):
- Bachelor’s degree in engineering or other STEM-related field and 2 years of relevant software development integration work experience
- OR a Masters in STEM with 0 years of relevant software development integration work experience
- Must have the ability to obtain and maintain DoD Clearance at the Secret level
- Demonstrated knowledge of Agile software development processes
- Demonstrated knowledge of C# (or C++) and Python
- Demonstrated experience in process monitoring, data collection, analysis, and metric reporting
- Demonstrated experience in process and product evaluation
- Experience with software code review
Also U.S. Citizenship required for positions with government clearance.
Preferred Qualifications:
- Active Secret Clearance
- Experience with IBM DOORS
- Experience with requirement traceability
- Experience in a Software Engineering environment in an engineering capacity, work plan review, and root cause/corrective action analysis.
- Experience using Atlassian tool suite and tools like Bitbucket, Jira, and Confluence.
- Ability to work independently with all levels of management and customer representatives to identify solutions to complex problems.
- Understanding of Python libraries related to data analysis and machine learning
- Hardware Engineering or hardware quality experience.
- Aircraft industry experience.
- Experience implementing formal software certification efforts, such as DO-178, DO-254 or DO-330
- Experience leading diverse teams via a formalized Root Cause/Corrective Action process
Skills: maybe we can list technical skills: Agile, C#/C++, Python, IBM DOORS, requirement traceability, Atlassian tools (Jira, Bitbucket, Confluence), DO-178/DO-254/DO-330, root cause/corrective action, data analysis libraries, etc.
But we could also incorporate skills into Qualifications.
Given instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one "Requirements" section that includes both basic and preferred? But they said headings like Requirements, Qualifications, Skills. Could use Requirements for basic, Qualifications for preferred, Skills for technical skills.
Let's decide:
- About the role: description paragraph.
- Responsibilities: bullet list.
- Requirements: basic qualifications (degree/experience, clearance, Agile, C#/C++/Python, process monitoring, data analysis, process/product evaluation, code review, US citizenship).
- Qualifications: preferred qualifications (active secret clearance, IBM DOORS, requirement traceability, Atlassian tools, ability to work independently, Python libraries for ML, hardware/aircraft experience, DO-178/254/330, leading diverse teams via RCCA).
- Skills: maybe we can list specific technical skills: Agile, C#/C++, Python, IBM DOORS, requirement traceability, Atlassian (Jira, Bitbucket, Confluence), DO-178/DO-254/DO-330, root cause/corrective action, data analysis libraries, etc. But this may be redundant with Qualifications. Could omit Skills section to avoid thin sections. However we have Pay and Benefits sections.
- Pay: salary range $81,300 - $121,900, plus mention overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director.
- Benefits: health insurance, life and disability insurance, savings plan, company paid holidays, paid time off (PTO) for vacation/personal business.
- Schedule: not given, so omit.
- Travel: Yes, 10% of the Time. Could be included under About the role or a separate section? There's no heading for Travel; we could include in About the role paragraph or maybe under Responsibilities? Better to add a short paragraph under About the role mentioning travel requirement.
- Relocation assistance: No relocation assistance available. Could be mentioned in About the role or a note. Not a heading.
- Clearance required: Secret. Already covered in Requirements.
We must not include boilerplate like EEO, application period, etc.
Now produce HTML fragment.
Structure:
About the role
... description including travel 10% and location Rancho Bernardo, CA.
Responsibilities
- ... ...
Requirements
- Bachelor’s degree in engineering or other STEM-related field and 2 years of relevant software development integration work experience, or a Master’s in STEM with 0 years of relevant experience.
- Ability to obtain and maintain a DoD Secret clearance.
- U.S. Citizenship required for positions with a government clearance.
- Demonstrated knowledge of Agile software development processes.
- Demonstrated knowledge of C# (or C++) and Python.
- Demonstrated experience in process monitoring, data collection, analysis, and metric reporting.
- Demonstrated experience in process and product evaluation.
- Experience with software code review.
Qualifications
- Active Secret Clearance (preferred).
- Experience with IBM DOORS.
- Experience with requirement traceability.
- Experience in a Software Engineering environment, including work plan review and root cause/corrective action analysis.
- Experience using Atlassian tool suite (Bitbucket, Jira, Confluence).
- Ability to work independently with all levels of management and customer representatives to identify solutions to complex problems.
- Understanding of Python libraries related to data analysis and machine learning.
- Hardware Engineering or hardware quality experience.
- Aircraft industry experience.
- Experience implementing formal software certification efforts (DO‑178, DO‑254, DO‑330).
- Experience leading diverse teams via a formalized Root Cause/Corrective Action process.
Pay
Salary range: $81,300.00 – $121,900.00 per year. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay. Annual bonuses reward individual contributions and allow employees to share in company results. Employees in Vice President or Director positions may be eligible for Long Term Incentives.
Benefits
- Health insurance coverage
- Life and disability insurance
- Savings plan
- Company‑paid holidays
- Paid time off (PTO) for vacation and/or personal business