Software Engineer / Principal Software Engineer

We need to output HTML fragment with sections: About the role (maybe description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Key info: - Relocation assistance may be available. - Clearance required: Yes, Secret. - Travel: No. - Description: paragraph about Northrop Grumman, culture, etc. - Location: Northrop Grumman Defense Systems (NGDS), Bellevue, NE. - Position: Software Engineer or Principal Software Engineer. - Successful candidates will demonstrate broad skill set balanced between interpersonal and technical capabilities achieving sustainable quality products. They will have a track record as an effective communicator and problem solver who is able to develop and maintain good working relationships with internal and external stakeholders. The selected candidates will participate in the entire software development lifecycle with a concentration in software engineering. The candidates will work closely with other software developers accomplishing the following: - Complete work independently and as a part of an Agile team - Support team in completing necessary software on schedule - Solve complex problems through innovative and creative solutions - Collaborate with software designers and/or software engineers in the planning, design, development, and utilization of software systems - Regularly demonstrate progress to customers - Basic Qualifications: list for Software Engineer and Principal Software Engineer. - Preferred Qualifications: list. - Primary Level Salary Range: $79,300.00 - $118,900.00 - Secondary Level Salary Range: $98,400.00 - $147,600.00 - Note about salary range. - Benefits: health insurance coverage, life and disability insurance, savings plan, Company paid holidays and paid time off (PTO) for vacation and/or personal business. Also mention overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director. - Schedule: Not explicitly mentioned. There's no schedule info. So we should not create Schedule section. - Pay: we have salary ranges, so include Pay section. - Benefits: we have benefits info, include Benefits section. - About the role: we have description paragraph; could be About the role. - Responsibilities: we have list of duties (the bullet list). So Responsibilities section. - Requirements: Basic Qualifications (maybe Requirements). Could be Requirements section. - Qualifications: Preferred Qualifications could be Qualifications section. - Skills: maybe combine technical skills from qualifications? But we have separate sections; we could put Skills as a subsection? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Skills section if there is specific skill content. The posting includes many skills: Java, Linux OS, relational DB, SQL, Agile, testing, interpersonal skills, etc. Also preferred qualifications include DevOps, CI/CD, Jenkins, SonarQube, IDEs, configuration management. So we can create Skills section. We need to avoid repeating job title as heading. Also avoid Job ID/requisition numbers. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, application instructions, cookie/navigation/legal. The posting includes EEO statement and link; we should remove that. Also "U.S. Citizenship is required for all positions with a government clearance and certain other restricted positions." That's maybe relevant to clearance but could be considered boilerplate? It's about citizenship requirement; it's substantive? Might be considered part of clearance requirement. But we already have clearance required: Secret. Could keep mention of US citizenship as part of clearance? Might be considered boilerplate but it's a requirement. However the instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The citizenship line is not exactly EEO but could be considered legal. I'd lean to remove it as it's generic legal. But we already have clearance required; maybe we can keep clearance info. The line about US citizenship is tied to clearance; but we can keep clearance required statement. I'd keep "CLEARANCE REQUIRED FOR START: Yes CLEARANCE TYPE: Secret". Also relocation assistance line. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to include: - Relocation assistance may be available. - Clearance required: Yes, Secret. - Travel: No. These could be placed in a short

maybe under About the role or as metadata. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short paragraph with that metadata. Now structure:

About the role

... description paragraph ...

Relocation assistance: may be available. Clearance: Secret required. Travel: None.

Then Responsibilities:

Responsibilities

• Complete work independently and as a part of an Agile team
• Support team in completing necessary software on schedule
• Solve complex problems through innovative and creative solutions
• Collaborate with software designers and/or software engineers in the planning, design, development, and utilization of software systems
• Regularly demonstrate progress to customers

Requirements (Basic Qualifications): We need to list both Software Engineer and Principal Software Engineer qualifications. Could be two sublists? But we can just list them as items. Better to have

Requirements

• Software Engineer:
  • High school diploma with minimum 6 years of software development experience
  • Bachelor's of science degree in a STEM field with minimum 2 years of software development experience
  • Master's of science degree in a STEM field with 0 years of software development experience
• Principal Software Engineer:
  • High school diploma with minimum 9 years of software development experience
  • Bachelor's of science degree in a STEM field with minimum 5 years of software development experience
  • Master's of science degree in a STEM field with 3 years of software development experience
  • Active U.S. Department of Defense (DoD) Secret Security Clearance
  • Experience as a Full Stack Software Developer
  • Demonstrated experience in Java
  • Proven experience with Linux OS
  • Familiarity with relational database management systems (Oracle/PDBs) and SQL
  • Working knowledge of the Agile development processes
  • Familiarity with Software Testing (Integration testing, Unit testing)
  • Strong interpersonal skills to communicate effectively with small technical teams
  • Ability to prioritize and adjust tasks to accomplish project results
  • Ability to obtain/maintain access to work full time on-site in Bellevue, NE

But note that some of those are also skills; but we can keep them in Requirements. Qualifications (Preferred Qualifications):

Qualifications

• Experience working in Agile software development environment
• Experience with Enterprise Database
• DevOps / DevSecOps experience
• Continuous Integration (CI) / Continuous Deployment (CD)
• Setting up Jenkins Builds
• Software Security Tools (SonarQube)
• Demonstrated use of Integrated Development Environments (IDEs) and configuration management (BitBucket)

Skills: Could extract technical skills: Java, Linux OS, relational DB (Oracle/PDBs), SQL, Agile, testing, interpersonal skills, etc. But we already have many in Requirements and Qualifications. To avoid duplication, maybe we can combine Skills as a separate section highlighting technical skills: Java, Linux, Oracle/P DBs, SQL, Agile, CI/CD, Jenkins, SonarQube, IDEs, BitBucket, etc. However we risk duplicating content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but we should avoid unnecessary duplication? It didn't forbid duplication but said remove duplicated lines. So we should avoid repeating same exact lines. We can keep Skills section with a concise list of skills not already captured elsewhere? But many are already in Requirements/Qualifications. Might be okay to have Skills section summarizing technical skills: Java, Linux OS, Oracle/P DBs, SQL, Agile development, CI/CD, Jenkins, SonarQube, IDEs, BitBucket, etc. However that would be summarizing, which might be considered summarizing away detail? The instruction says do NOT invent or summarize away detail. Summarizing could be considered summarizing away detail if we omit some details. But we could list them as items, not summarizing. It's okay to list them; it's not summarizing away detail if we list each skill. However we already listed many of those in Requirements/Qualifications. Duplicating them might be considered duplicated lines? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines likely means exact duplicate sentences. If we list same skill in two places, it's duplicated lines. So better not to duplicate. So we could omit Skills section if its content is already covered. But the instruction says we can include Skills section if posting has real specific content for it. The posting does have specific skill mentions (Java, Linux, etc.) but they are already in Requirements/Qualifications. However we could still have Skills section that lists those skills without duplicating exact sentences? Might be considered duplication if we list same phrases. Safer to omit Skills section and rely on Requirements and Qualifications to capture skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we need to include Schedule: none. Now Benefits section: include health insurance, life and disability insurance, savings plan, Company paid holidays, paid time off (PTO) for vacation and/or personal business, overtime eligibility, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director. We should preserve all detail: "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. In addition, Northrop Grumman provides a variety of benefits including health insurance coverage, life and disability insurance, savings plan, Company paid holidays and paid time off (PTO) for vacation and/or personal business." We'll put that in

items. Pay section: include Primary Level Salary Range and Secondary Level Salary Range, plus note about factors determining base salary, overtime, shift differential, discretionary bonus, annual bonuses, long term incentives. We'll put that in

maybe. Now ensure we don't include boilerplate: EEO statement, link, citizenship requirement, application period timeline (maybe we could keep? It's not boilerplate but it's about application period. The instruction: remove application instructions. The timeline is not exactly instruction but could be considered metadata. Might be okay to keep? It's not a heading; we could fold into a short p. But it's not essential. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The application period is minor metadata; we could include in a short p under About the role or separate. But we might drop it to keep concise. However we need to preserve ALL substantive information; is application period substantive? It's about timeline; maybe considered substantive but minor. The instruction says we can fold minor metadata into a short p or