Software Engineer (Active Secret Clearance Required)
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide sections: About the role (description paragraph), Responsibilities (list of duties), Requirements (basic qualifications?), Qualifications (maybe preferred qualifications?), Skills (maybe list of specific technical skills?), Benefits (benefits + relocation assistance), Pay (salary range), Schedule (maybe travel %? but schedule is not given; we have travel 10% of time; schedule not specified. So we should not create Schedule section unless there is real content. Travel is not schedule; it's travel percentage. Could we put travel under About the role? Probably.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated: health insurance, life and disability, savings plan, company paid holidays, PTO, relocation assistance maybe. So Benefits section is valid.
Pay: salary range given, so Pay section valid.
Schedule: not given; we have travel but not schedule. So we should not create Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
Now we need to fill content.
About the role: prose describing Northrop Grumman, the role, location, etc. Use the description paragraph: "At Northrop Grumman, our employees have incredible opportunities..." plus maybe the sentence about position supporting Aeronautics Systems sector in Rancho Bernardo, CA. Also mention travel 10%? Could embed.
Responsibilities: list after "The selected candidate will join our team of software engineers to:" includes bullet points: Support the development of Strategic Operating Units, executing both sustainment and modernization programs; Contribute to software engineering initiatives for several programs with software design & development, software test and integration, and DevOps expertise; Use a variety of software languages, technologies, and industry best practices; Support all phases of the development life cycle for flight, mission, lab and tools software.
We need to preserve all substantive information; also maybe include travel? Not needed.
Requirements: Basic Qualifications list. Should we separate as Requirements? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements for basic qualifications, Qualifications for preferred qualifications, Skills for technical skills list? But we already have many technical skills in both basic and preferred. Might combine.
Better: Requirements = Basic Qualifications (bullet list). Qualifications = Preferred Qualifications (bullet list). Skills = maybe list of specific technologies/languages etc. But we already have those in both lists; we could extract a distinct Skills section from the text: "Experience with developing software and scripts on various programming languages: C, C++, Python, PowerShell, VBScript, Bash, AND/OR KornShell for Safety-Critical applications/Systems", etc. However that duplicates. To avoid duplication, we could keep Requirements and Qualifications as the two qualification blocks, and not have a separate Skills section unless there is distinct skill list not covered. The posting includes many skill mentions within both basic and preferred; we could still have a Skills section summarizing them, but that would duplicate info. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot omit details; but we can include them in either Requirements or Qualifications sections. Having a separate Skills section would be okay if we also include the details there, but we must not omit them elsewhere. Duplication is allowed? It says do NOT repeat the job title as a heading and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid duplication of content. However "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. Better to combine skills into Requirements and Qualifications.
Thus we will have sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay.
We need to include clearance requirement and travel and relocation assistance somewhere. Clearance requirement is part of basic qualifications? It says "Active U.S. government Secret level or higher clearance (in-scope), with the ability to obtain (and maintain) special program access (PAR)". That's a requirement; we can include in Requirements list.
Travel: "TRAVEL: Yes, 10% of the Time". Could be included in About the role or Responsibilities as a note.
Relocation assistance: "RELOCATION ASSISTANCE: Relocation assistance may be available". Could be in Benefits.
Now craft HTML.
We'll produce:
About the role
At Northrop Grumman, our employees have incredible opportunities to work on revolutionary systems that impact people's lives around the world today, and for generations to come. Our pioneering and inventive spirit has enabled us to be at the forefront of many technological advancements in our nation's history - from the first flight across the Atlantic Ocean, to stealth bombers, to landing on the moon. We look for people who have bold new ideas, courage and a pioneering spirit to join forces to invent the future, and have fun along the way. Our culture thrives on intellectual curiosity, cognitive diversity and bringing your whole self to work — and we have an insatiable drive to do what others think is impossible. Our employees are not only part of history, they're making history. Northrop Grumman is seeking an experienced Software Engineer to join our dynamic team. This position will support our Aeronautics Systems sector in Rancho Bernardo, CA. Travel is expected approximately 10% of the time.
Responsibilities
- Support the development of Strategic Operating Units, executing both sustainment and modernization programs
- Contribute to software engineering initiatives for several programs with software design & development, software test and integration, and DevOps expertise
- Use a variety of software languages, technologies, and industry best practices
- Support all phases of the development life cycle for flight, mission, lab and tools software
Requirements
- Bachelor’s degree in a Science, Technology, Engineering, or Mathematics (STEM) discipline from an accredited university and 2 years of experience in software engineering OR a Master’s degree in a (STEM) discipline from an accredited university and 0 years of experience in software engineering OR a PhD degree in a (STEM) discipline from an accredited university and 0 years of experience
- Familiar with Safety-Critical Embedded Real Time Software
- Familiar with all phases of the software development life cycle and Agile framework as a Product Owner, SCRUM Master, and/or team member
- Experience with developing software and scripts on various programming languages: C, C++, Python, PowerShell, VBScript, Bash, AND/OR KornShell for Safety-Critical applications/Systems
- Familiar with Architecting, Designing, Implementing, Integrating, Verifying and Qualifying Safety-Critical Embedded Real Time Software running on various RTOS (VxWorks, Integrity, Real Time Embedded Linux)
- Familiar with Static & Dynamic Code Analysis Tools and Fuzzing Tools such as: Coverity, Fortify, AND/OR SonarQube
- Familiar with Software Change Control, Change Management, and CI/CD tools
- Active U.S. government Secret level or higher clearance (in-scope), with the ability to obtain (and maintain) special program access (PAR)
- U.S. Citizenship is required for all positions with a government clearance and certain other restricted positions.
Qualifications
- Demonstrated leadership, teamwork capabilities, excellent oral and written communications skills, and strong interpersonal communication skills at all levels of employees and management
- Experience with Agile Software Development, object-oriented architectures, designs, programming, debugging, and hardware-software integration and testing
- Experience with Software Change Control, Change Management, Code Quality, Static Analysis, and CI/CD tools such as: Atlassian tool suite, Jira, GitHub, GitLab, SonarQube, Coverity, AND/OR Jenkins
- Experience architecting, Designing, Modeling (Rhapsody or Cameo), Implementing, Maintaining, integrating, and Debugging OO C++ software running on Real-Time Operating systems such as: VxWorks, Integrity, AND/OR Real Time Embedded Linux
- Experience with DOORs AND Software Requirement Specification Testing using Simulators, automated scripting languages such as Python, MATLAB, JavaScript, AND/OR Bash
- Experience with Static & Dynamic Code Analysis Tools and Fuzzing Tools such as: Coverity, Fortify, AND/OR SonarQube
- Experience with software network interfaces -and troubleshooting networks (TCP/IP, UDP, LAN, VLAN, SNMP or others)
Benefits
- Health insurance coverage
- Life and disability insurance
- Savings plan
- Company paid holidays
- Paid time off (PTO) for vacation and/or personal business
- Relocation assistance may be available
Pay
Primary Level Salary Range: $91,800.00 - $137,600.00
Secondary Level Salary Range: $0.00 - $0.00
The above salary range represents a general guideline; however, Northrop Grumman considers a number of factors when determining base salary offers such as the scope and responsibilities of the position and the candidate's experience, education, skills and current market conditions. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay. Annual bonuses are designed to reward individual contributions as well as allow employees to share in company results. Employees in Vice President or Director positions may be eligible for Long Term Incentives.
We must not include any markdown fences. Just raw
for prose. We need to decide sections: About the role (description paragraph), Responsibilities (list of duties), Requirements (basic qualifications?), Qualifications (maybe preferred qualifications?), Skills (maybe list of specific technical skills?), Benefits (benefits + relocation assistance), Pay (salary range), Schedule (maybe travel %? but schedule is not given; we have travel 10% of time; schedule not specified. So we should not create Schedule section unless there is real content. Travel is not schedule; it's travel percentage. Could we put travel under About the role? Probably. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated: health insurance, life and disability, savings plan, company paid holidays, PTO, relocation assistance maybe. So Benefits section is valid. Pay: salary range given, so Pay section valid. Schedule: not given; we have travel but not schedule. So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Now we need to fill content. About the role: prose describing Northrop Grumman, the role, location, etc. Use the description paragraph: "At Northrop Grumman, our employees have incredible opportunities..." plus maybe the sentence about position supporting Aeronautics Systems sector in Rancho Bernardo, CA. Also mention travel 10%? Could embed. Responsibilities: list after "The selected candidate will join our team of software engineers to:" includes bullet points: Support the development of Strategic Operating Units, executing both sustainment and modernization programs; Contribute to software engineering initiatives for several programs with software design & development, software test and integration, and DevOps expertise; Use a variety of software languages, technologies, and industry best practices; Support all phases of the development life cycle for flight, mission, lab and tools software. We need to preserve all substantive information; also maybe include travel? Not needed. Requirements: Basic Qualifications list. Should we separate as Requirements? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements for basic qualifications, Qualifications for preferred qualifications, Skills for technical skills list? But we already have many technical skills in both basic and preferred. Might combine. Better: Requirements = Basic Qualifications (bullet list). Qualifications = Preferred Qualifications (bullet list). Skills = maybe list of specific technologies/languages etc. But we already have those in both lists; we could extract a distinct Skills section from the text: "Experience with developing software and scripts on various programming languages: C, C++, Python, PowerShell, VBScript, Bash, AND/OR KornShell for Safety-Critical applications/Systems", etc. However that duplicates. To avoid duplication, we could keep Requirements and Qualifications as the two qualification blocks, and not have a separate Skills section unless there is distinct skill list not covered. The posting includes many skill mentions within both basic and preferred; we could still have a Skills section summarizing them, but that would duplicate info. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot omit details; but we can include them in either Requirements or Qualifications sections. Having a separate Skills section would be okay if we also include the details there, but we must not omit them elsewhere. Duplication is allowed? It says do NOT repeat the job title as a heading and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid duplication of content. However "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. Better to combine skills into Requirements and Qualifications. Thus we will have sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. We need to include clearance requirement and travel and relocation assistance somewhere. Clearance requirement is part of basic qualifications? It says "Active U.S. government Secret level or higher clearance (in-scope), with the ability to obtain (and maintain) special program access (PAR)". That's a requirement; we can include in Requirements list. Travel: "TRAVEL: Yes, 10% of the Time". Could be included in About the role or Responsibilities as a note. Relocation assistance: "RELOCATION ASSISTANCE: Relocation assistance may be available". Could be in Benefits. Now craft HTML. We'll produce:
About the role
At Northrop Grumman, our employees have incredible opportunities to work on revolutionary systems that impact people's lives around the world today, and for generations to come. Our pioneering and inventive spirit has enabled us to be at the forefront of many technological advancements in our nation's history - from the first flight across the Atlantic Ocean, to stealth bombers, to landing on the moon. We look for people who have bold new ideas, courage and a pioneering spirit to join forces to invent the future, and have fun along the way. Our culture thrives on intellectual curiosity, cognitive diversity and bringing your whole self to work — and we have an insatiable drive to do what others think is impossible. Our employees are not only part of history, they're making history. Northrop Grumman is seeking an experienced Software Engineer to join our dynamic team. This position will support our Aeronautics Systems sector in Rancho Bernardo, CA. Travel is expected approximately 10% of the time.
Responsibilities
- Support the development of Strategic Operating Units, executing both sustainment and modernization programs
- Contribute to software engineering initiatives for several programs with software design & development, software test and integration, and DevOps expertise
- Use a variety of software languages, technologies, and industry best practices
- Support all phases of the development life cycle for flight, mission, lab and tools software
Requirements
- Bachelor’s degree in a Science, Technology, Engineering, or Mathematics (STEM) discipline from an accredited university and 2 years of experience in software engineering OR a Master’s degree in a (STEM) discipline from an accredited university and 0 years of experience in software engineering OR a PhD degree in a (STEM) discipline from an accredited university and 0 years of experience
- Familiar with Safety-Critical Embedded Real Time Software
- Familiar with all phases of the software development life cycle and Agile framework as a Product Owner, SCRUM Master, and/or team member
- Experience with developing software and scripts on various programming languages: C, C++, Python, PowerShell, VBScript, Bash, AND/OR KornShell for Safety-Critical applications/Systems
- Familiar with Architecting, Designing, Implementing, Integrating, Verifying and Qualifying Safety-Critical Embedded Real Time Software running on various RTOS (VxWorks, Integrity, Real Time Embedded Linux)
- Familiar with Static & Dynamic Code Analysis Tools and Fuzzing Tools such as: Coverity, Fortify, AND/OR SonarQube
- Familiar with Software Change Control, Change Management, and CI/CD tools
- Active U.S. government Secret level or higher clearance (in-scope), with the ability to obtain (and maintain) special program access (PAR)
- U.S. Citizenship is required for all positions with a government clearance and certain other restricted positions.
Qualifications
- Demonstrated leadership, teamwork capabilities, excellent oral and written communications skills, and strong interpersonal communication skills at all levels of employees and management
- Experience with Agile Software Development, object-oriented architectures, designs, programming, debugging, and hardware-software integration and testing
- Experience with Software Change Control, Change Management, Code Quality, Static Analysis, and CI/CD tools such as: Atlassian tool suite, Jira, GitHub, GitLab, SonarQube, Coverity, AND/OR Jenkins
- Experience architecting, Designing, Modeling (Rhapsody or Cameo), Implementing, Maintaining, integrating, and Debugging OO C++ software running on Real-Time Operating systems such as: VxWorks, Integrity, AND/OR Real Time Embedded Linux
- Experience with DOORs AND Software Requirement Specification Testing using Simulators, automated scripting languages such as Python, MATLAB, JavaScript, AND/OR Bash
- Experience with Static & Dynamic Code Analysis Tools and Fuzzing Tools such as: Coverity, Fortify, AND/OR SonarQube
- Experience with software network interfaces -and troubleshooting networks (TCP/IP, UDP, LAN, VLAN, SNMP or others)
Benefits
- Health insurance coverage
- Life and disability insurance
- Savings plan
- Company paid holidays
- Paid time off (PTO) for vacation and/or personal business
- Relocation assistance may be available
Pay
Primary Level Salary Range: $91,800.00 - $137,600.00
Secondary Level Salary Range: $0.00 - $0.00
The above salary range represents a general guideline; however, Northrop Grumman considers a number of factors when determining base salary offers such as the scope and responsibilities of the position and the candidate's experience, education, skills and current market conditions. Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay. Annual bonuses are designed to reward individual contributions as well as allow employees to share in company results. Employees in Vice President or Director positions may be eligible for Long Term Incentives.
We must not include any markdown fences. Just raw