Software/Principal Embedded Software Engineer
Northrop Grumman · Rolling Meadows, IL · 3 wk ago
On-siteEngineering$88k–$131k/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 must preserve all substantive info, remove boilerplate (EEO, etc). No job title heading. No Job ID etc.
We need to parse the posting.
Key info:
- Relocation assistance may be available.
- Clearance required for start: Yes, Secret.
- Travel: Yes, 10% of the time.
- Description: paragraphs about Northrop Grumman, mission, etc. This is "About the role" maybe.
- Position: Software Engineer/Principal Software Engineer.
- Responsibilities: design, develop, operate, maintain software and firmware components; interface with customers, suppliers, etc; full SDLC; etc.
- Requirements: Basic Qualifications for Software Engineer and Principal Software Engineer.
- Preferred Qualifications list.
- Salary range: Primary Level Salary Range: $87,600.00 - $131,400.00 (Pay).
- Benefits: mention health insurance, life and disability insurance, savings plan, company paid holidays, PTO, overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director.
- Schedule: full-time, on-site at Rolling Meadows, IL.
- Also mention relocation assistance, clearance, travel.
We need sections: About the role (description), Responsibilities, Requirements (maybe combine basic qualifications?), Qualifications (maybe preferred?), Skills, Benefits, Pay, Schedule.
We must not create sections with filler like "not specified". So include only those with content.
We need to decide what goes where.
About the role: The introductory description about Northrop Grumman, mission, culture, etc. Could be a paragraph.
Responsibilities: The bullet list of duties: designs, develops, operates, maintains software/firmware; applies standards; interfaces with customers/suppliers/application users/technical support; full SDLC; etc.
Requirements: Basic qualifications (both levels). Could be a list.
Preferred Qualifications: Could be under Qualifications or Skills. Since we have a Skills section, we could put preferred qualifications there.
But we have separate sections: Qualifications, Skills. 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. Requirements likely = basic qualifications. Qualifications = preferred qualifications.
Skills: maybe list specific skills like C++, OOP, Linux/VxWorks, scripting, Agile, etc. Could be derived from preferred qualifications.
But we must not duplicate content. We can split: Requirements = basic qualifications (both levels). Qualifications = preferred qualifications (maybe also include leadership etc). Skills = maybe list technical skills: C++ (OOP), Linux/VxWorks, scripting languages (Python, Bash, Batch), Agile/Waterfall, testing/debugging, parallel processing, multi-threading, etc. However that may duplicate preferred qualifications. But we can keep Qualifications as preferred qualifications and Skills as a subset? Might be redundant. Better to follow instruction: include sections only when posting has real specific content. We can decide to have Requirements (basic qualifications) and Qualifications (preferred qualifications). Skills maybe not needed if we already covered in Qualifications. But we could still include Skills if we have distinct content: e.g., "Object Oriented Programming in C++", "Experience Developing Embedded Software running Linux or VxWorks Operating Systems", "Knowledge with scripting languages (Python, Bash, Batch, etc)", "Experience with Software development methodologies and frameworks such as Waterfall Methodology and/or Agile.", "Experience testing, debugging, and integrating Embedded Software on target hardware.", "Experience with complex systems that utilize Parallel Processing, Multi-Threading, Distributed Processing, Multi-Core, System-on-Chip, and Secure Processing." Those are skills.
Thus we can have Skills section listing those.
Qualifications could be leadership etc: "Differentiating characteristics include demonstrated leadership and teamwork capability, interpersonal communication skills and activities". Also maybe "Active Secret Clearance" (but that's a requirement). Actually Active Secret Clearance is a basic qualification (must have). So it's in Requirements.
Thus Qualifications could be the "Preferred Qualifications" list (including leadership etc). But we already have some of those in Skills. Might be okay to have overlap but we should avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we can split: Requirements = basic qualifications (education, experience, citizenship, clearance, C++ OOP, embedded Linux/VxWorks). Skills = technical skills like scripting, Agile, testing, parallel processing, etc. Qualifications = preferred qualifications like leadership, interpersonal communication, etc.
Let's extract:
Basic Qualifications For Software Engineer:
- Bachelor’s degree in Computer Science, Computer Engineering, or similar engineering discipline with a minimum of 2+ years of engineering experience, or Master’s degree in Computer Science, Computer Engineering or similar engineering discipline, or in lieu of degree, an additional 4 years of experience is required.
- Object Oriented Programming in C++
- Experience Developing Embedded Software running Linux or VxWorks Operating Systems
- US Citizenship
- Must have current Active Secret Clearance prior to starting.
Basic Qualifications For Principal Software Engineer:
- Bachelor’s degree in Computer Science, Computer Engineering, or similar engineering discipline with a minimum of 5+ years of engineering experience, or Master’s degree in Computer Science, Computer Engineering or similar engineering discipline with a minimum of 3+ years of engineering experience, or in lieu of degree, an additional 4 years of experience is required.
- Object Oriented Programming in C++
- Experience Developing Embedded Software running Linux or VxWorks Operating Systems
- US Citizenship
- Must have current Active Secret Clearance prior to starting.
Thus basic qualifications are similar except experience years.
We can combine: Requirements: education/experience alternatives, OOP C++, embedded Linux/VxWorks, US Citizenship, Active Secret Clearance.
We could note the experience variations but keep generic.
Responsibilities: list:
- Designs, develops, operates, and maintains software and firmware components and computing systems software to be applied to and integrated with engineering, scientific and manufacturing requirements.
- Apply appropriate standards, processes, procedures, and tools throughout the system development life cycle to support generation of engineering applications and products within Targeting, RF and MSS Business Units.
- Interface with customers, suppliers, application users and other technical and support personnel.
- Full software development life cycle: requirements, design, coding, testing, integration.
- (maybe also) collaborative, open, transparent, team-oriented, focus on team empowerment & shared responsibility, flexibility, continuous learning, culture of automation. That's more about culture but could be responsibilities.
We'll include those.
About the role: The initial paragraphs about Northrop Grumman mission, culture, digital transformation, Model-based Engineering, DevSecOps, Agile, etc. Also mention "As a Software Engineer/ Principal Software Engineer at Northrop Grumman you will have a challenging and rewarding opportunity to be a part of our Enterprise-wide digital transformation." That's part of role.
We'll craft a paragraph.
Benefits: list: health insurance coverage, 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 positions.
Also relocation assistance may be available.
Pay: Primary Level Salary Range: $87,600.00 - $131,400.00.
Schedule: full-time, on-site at Rolling Meadows, IL. Travel: Yes, 10% of the time.
We could include travel under Schedule or separate? Since we have Schedule heading, we can include schedule details: full-time, on-site, location, travel 10%.
Now we must not include boilerplate: EEO, equal opportunity, application period, etc. Remove those.
Now produce HTML fragment:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We must preserve all substantive info, remove boilerplate (EEO, etc). No job title heading. No Job ID etc.
We need to parse the posting.
Key info:
- Relocation assistance may be available.
- Clearance required for start: Yes, Secret.
- Travel: Yes, 10% of the time.
- Description: paragraphs about Northrop Grumman, mission, etc. This is "About the role" maybe.
- Position: Software Engineer/Principal Software Engineer.
- Responsibilities: design, develop, operate, maintain software and firmware components; interface with customers, suppliers, etc; full SDLC; etc.
- Requirements: Basic Qualifications for Software Engineer and Principal Software Engineer.
- Preferred Qualifications list.
- Salary range: Primary Level Salary Range: $87,600.00 - $131,400.00 (Pay).
- Benefits: mention health insurance, life and disability insurance, savings plan, company paid holidays, PTO, overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director.
- Schedule: full-time, on-site at Rolling Meadows, IL.
- Also mention relocation assistance, clearance, travel.
We need sections: About the role (description), Responsibilities, Requirements (maybe combine basic qualifications?), Qualifications (maybe preferred?), Skills, Benefits, Pay, Schedule.
We must not create sections with filler like "not specified". So include only those with content.
We need to decide what goes where.
About the role: The introductory description about Northrop Grumman, mission, culture, etc. Could be a paragraph.
Responsibilities: The bullet list of duties: designs, develops, operates, maintains software/firmware; applies standards; interfaces with customers/suppliers/application users/technical support; full SDLC; etc.
Requirements: Basic qualifications (both levels). Could be a list.
Preferred Qualifications: Could be under Qualifications or Skills. Since we have a Skills section, we could put preferred qualifications there.
But we have separate sections: Qualifications, Skills. 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. Requirements likely = basic qualifications. Qualifications = preferred qualifications.
Skills: maybe list specific skills like C++, OOP, Linux/VxWorks, scripting, Agile, etc. Could be derived from preferred qualifications.
But we must not duplicate content. We can split: Requirements = basic qualifications (both levels). Qualifications = preferred qualifications (maybe also include leadership etc). Skills = maybe list technical skills: C++ (OOP), Linux/VxWorks, scripting languages (Python, Bash, Batch), Agile/Waterfall, testing/debugging, parallel processing, multi-threading, etc. However that may duplicate preferred qualifications. But we can keep Qualifications as preferred qualifications and Skills as a subset? Might be redundant. Better to follow instruction: include sections only when posting has real specific content. We can decide to have Requirements (basic qualifications) and Qualifications (preferred qualifications). Skills maybe not needed if we already covered in Qualifications. But we could still include Skills if we have distinct content: e.g., "Object Oriented Programming in C++", "Experience Developing Embedded Software running Linux or VxWorks Operating Systems", "Knowledge with scripting languages (Python, Bash, Batch, etc)", "Experience with Software development methodologies and frameworks such as Waterfall Methodology and/or Agile.", "Experience testing, debugging, and integrating Embedded Software on target hardware.", "Experience with complex systems that utilize Parallel Processing, Multi-Threading, Distributed Processing, Multi-Core, System-on-Chip, and Secure Processing." Those are skills.
Thus we can have Skills section listing those.
Qualifications could be leadership etc: "Differentiating characteristics include demonstrated leadership and teamwork capability, interpersonal communication skills and activities". Also maybe "Active Secret Clearance" (but that's a requirement). Actually Active Secret Clearance is a basic qualification (must have). So it's in Requirements.
Thus Qualifications could be the "Preferred Qualifications" list (including leadership etc). But we already have some of those in Skills. Might be okay to have overlap but we should avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we can split: Requirements = basic qualifications (education, experience, citizenship, clearance, C++ OOP, embedded Linux/VxWorks). Skills = technical skills like scripting, Agile, testing, parallel processing, etc. Qualifications = preferred qualifications like leadership, interpersonal communication, etc.
Let's extract:
Basic Qualifications For Software Engineer:
- Bachelor’s degree in Computer Science, Computer Engineering, or similar engineering discipline with a minimum of 2+ years of engineering experience, or Master’s degree in Computer Science, Computer Engineering or similar engineering discipline, or in lieu of degree, an additional 4 years of experience is required.
- Object Oriented Programming in C++
- Experience Developing Embedded Software running Linux or VxWorks Operating Systems
- US Citizenship
- Must have current Active Secret Clearance prior to starting.
Basic Qualifications For Principal Software Engineer:
- Bachelor’s degree in Computer Science, Computer Engineering, or similar engineering discipline with a minimum of 5+ years of engineering experience, or Master’s degree in Computer Science, Computer Engineering or similar engineering discipline with a minimum of 3+ years of engineering experience, or in lieu of degree, an additional 4 years of experience is required.
- Object Oriented Programming in C++
- Experience Developing Embedded Software running Linux or VxWorks Operating Systems
- US Citizenship
- Must have current Active Secret Clearance prior to starting.
Thus basic qualifications are similar except experience years.
We can combine: Requirements: education/experience alternatives, OOP C++, embedded Linux/VxWorks, US Citizenship, Active Secret Clearance.
We could note the experience variations but keep generic.
Responsibilities: list:
- Designs, develops, operates, and maintains software and firmware components and computing systems software to be applied to and integrated with engineering, scientific and manufacturing requirements.
- Apply appropriate standards, processes, procedures, and tools throughout the system development life cycle to support generation of engineering applications and products within Targeting, RF and MSS Business Units.
- Interface with customers, suppliers, application users and other technical and support personnel.
- Full software development life cycle: requirements, design, coding, testing, integration.
- (maybe also) collaborative, open, transparent, team-oriented, focus on team empowerment & shared responsibility, flexibility, continuous learning, culture of automation. That's more about culture but could be responsibilities.
We'll include those.
About the role: The initial paragraphs about Northrop Grumman mission, culture, digital transformation, Model-based Engineering, DevSecOps, Agile, etc. Also mention "As a Software Engineer/ Principal Software Engineer at Northrop Grumman you will have a challenging and rewarding opportunity to be a part of our Enterprise-wide digital transformation." That's part of role.
We'll craft a paragraph.
Benefits: list: health insurance coverage, 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 positions.
Also relocation assistance may be available.
Pay: Primary Level Salary Range: $87,600.00 - $131,400.00.
Schedule: full-time, on-site at Rolling Meadows, IL. Travel: Yes, 10% of the time.
We could include travel under Schedule or separate? Since we have Schedule heading, we can include schedule details: full-time, on-site, location, travel 10%.
Now we must not include boilerplate: EEO, equal opportunity, application period, etc. Remove those.
Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
Primary Level Salary Range: $87,600.00 - $131,400.00
Schedule
Full-time, on-site position at Rolling Meadows, IL. Travel required approximately 10% of the time.
We also need to include relocation assistance maybe under Benefits or a separate note. Could add to Benefits: "Relocation assistance may be available." Also clearance requirement is in Requirements. Now ensure we preserve all substantive info: we must not lose any details like "Model-based Engineering, DevSecOps and Agile practices". That is in About the role maybe. Let's craft About the role paragraph: "At Northrop Grumman, employees work on revolutionary systems that impact lives around the world today and for generations to come. The company’s pioneering spirit has driven advancements from the first transatlantic flight to stealth bombers and moon landings. As a Software Engineer or Principal Software Engineer, you will contribute to the Enterprise-wide digital transformation using Model-based Engineering, DevSecOps, and Agile practices to deliver critical national defense products. The role emphasizes collaboration, transparency, team empowerment, continuous learning, and a culture of automation within the Engineering and Sciences organization." That captures. Now Responsibilities list: - Designs, develops, operates, and maintains software and firmware components and computing systems software to be applied to and integrated with engineering, scientific, and manufacturing requirements. - Applies appropriate standards, processes, procedures, and tools throughout the system development life cycle to support generation of engineering applications and products for the Targeting, RF, and MSS Business Units. - Interfaces with customers, suppliers, application users, and other technical and support personnel. - Executes the full software development life cycle: requirements gathering, design, coding, testing, and integration. - Works collaboratively in a team‑oriented environment, emphasizing open communication, shared responsibility, flexibility, continuous learning, and automation. Now Requirements list (basic qualifications): - Bachelor’s degree in Computer Science, Computer Engineering, or similar engineering discipline with 2+ years of engineering experience (or Master’s degree, or equivalent experience); for Principal Software Engineer level, 5+ years Bachelor’s or 3+ years Master’s (or equivalent experience). - Proficiency in Object‑Oriented Programming using C++. - Experience developing embedded software on Linux or VxWorks operating systems. - U.S. citizenship. - Must possess an active Secret security clearance prior to start. We could combine experience statements. Now Skills list (technical skills from preferred qualifications): - Object‑Oriented Programming in C++11. - Scripting languages (Python, Bash, Batch, etc.). - Software development methodologies and frameworks (Waterfall and/or Agile). - Testing, debugging, and integrating embedded software on target hardware. - Experience with complex systems utilizing parallel processing, multi‑threading, distributed processing, multi‑core, System‑on‑Chip, and secure processing. - Demonstrated leadership and teamwork capability. - Strong interpersonal communication skills. But leadership and communication maybe better under Qualifications. Let's decide: Qualifications = preferred qualifications (including leadership, interpersonal communication). Skills = technical skills (C++11, scripting, methodologies, testing, parallel processing, etc.). That seems reasonable. Thus Skills list: - Object‑Oriented Programming in C++11. - Scripting languages (Python, Bash, Batch, etc.). - Software development methodologies and frameworks (Waterfall and/or Agile). - Testing, debugging, and integrating embedded software on target hardware. - Experience with