Engineer Embedded Software
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting.
We have description paragraphs about company, role description, responsibilities, qualifications, etc.
We need to extract:
- About the role: maybe a short paragraph summarizing role? The posting includes description: "At Northrop Grumman..." then description of role. Could be "About the role" section.
- Responsibilities: bullet list of duties: "Support to Production: ..." etc. We need to list each bullet.
- Requirements: maybe basic qualifications? Or "Qualifications" could be basic and preferred? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include.
We have Basic Qualifications and Preferred Qualifications. Could combine into Requirements (basic) and Qualifications (preferred) or Skills. But we need to follow typical pattern: Requirements = basic qualifications; Qualifications = preferred qualifications; Skills = maybe specific skills like programming languages, tools.
But we must not create sections with filler. If we don't have content for a heading, omit it.
We have Pay: salary range given: $87,600.00 - $131,400.00. So we can include Pay section.
Schedule: Not mentioned explicitly; there is "9/80 Work Schedule (where available)" under benefits. That's a schedule detail but it's in benefits. Could we create Schedule section? The posting mentions "9/80 Work Schedule (where available)" as part of benefits. It's not a explicit schedule requirement. Might be better to include under Benefits. Since we only create Schedule if posting actually states them. It does mention a work schedule option but it's under benefits. Could still create Schedule section with that detail? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state "9/80 Work Schedule (where available)" as part of benefits. So we could include Schedule section with that detail. However, it's also in Benefits list. Might be duplication. Safer to include Benefits section with health plan, savings plan, PTO, education assistance, training, 9/80 work schedule, etc. And not create separate Schedule.
Pay section: we have salary range.
Benefits: we have list: Health Plan, Savings Plan, Paid Time Off and Additional Benefits including Education Assistance, Training and Development, 9/80 Work Schedule (where available), and much more! Also later: health insurance coverage, life and disability insurance, savings plan, Company paid holidays and paid time off (PTO) for vacation and/or personal business. So we can combine.
Now we need to output HTML fragment only, no /, no markdown.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
$87,600.00 - $131,400.00
We must ensure we preserve all substantive information, not invent or summarize away detail. Need to include all details from posting. Let's extract details. First, About the role: The description includes company overview and role description. We need to preserve all substantive information but not repeat job title. We can summarize but must not invent or summarize away detail. However we can condense but must keep all info? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should not omit details; we need to keep them. But we can rephrase? Probably we should keep the sentences as is, maybe split into paragraphs. Thus About the role could contain the paragraphs describing the company and role: Starting from "At Northrop Grumman, our employees have incredible opportunities..." through "This position will support aerial, military-grade, or space-grade Electronic Warfare Systems and Subsystems." That's a lot. We'll keep that as prose intags. Responsibilities: The bullet list under "What You Will Get To Do". Let's extract each bullet: - Support to Production: Review and make needed updates to software governing how test equipment operates. - Troubleshoot discrepancies in software packages. - Coordinate with Electrical Design Engineering, Software & Firmware Engineering, Production technician, Project Management, Manufacturing Engineering, Industrial Engineering, and Quality organizations to meet contractual acceptance testing and environmental screening commitments. - Software design – coding & integration/validation: Investigate, design, and provide solutions to meet new or modified testing requirements. - Test procedure development/Maintenance: Generate and maintain/revise Manufacturing Acceptance testing procedures, Environmental Screening procedures, hardware drawings of test equipment and fixtures. - Continuous improvement: Review of quality metrics to identify and implement continuous improvement initiatives to reduce cost, cycle time, defects. - Testability reviews: Collaborate with design engineering to achieve testability in new and updated product design. - Ability to interface/communicate with multiple levels of leadership, clients, and vendors. - Building a strong professional relationship with other Manufacturing disciplines (Process Engineering, Project Management, Shop Operations, Mission Assurance), strong decision-making skills and a high-level ethical standard is essential. We need to keep each as
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a short paragraph at top maybe: "Relocation assistance: None. Clearance: Secret required. Travel: 10% of time." But we need to decide if we include that as a paragraph. It's minor metadata; we could include a short
after the heading? But we have no heading for metadata. Could just drop it. The instruction says fold minor metadata into a short
or drop it. So we could include a
with that info, but not as a heading. Where to place? Possibly after About the role? Might be okay. But we need to preserve ALL substantive information; this metadata is substantive? It's about relocation assistance, clearance, travel. It's substantive. So we should include it. We'll add a
after the About the role maybe, or before Responsibilities. Let's add a
with: "Relocation assistance: None. Clearance required: Secret. Travel: 10% of time." Now we need to ensure we don't repeat job title as heading. We'll not. Now produce HTML. Let's craft.
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 Mission Systems is a trusted provider of mission-enabling solutions for global security. We have a wide portfolio of secure, affordable, integrated, and multi-domain systems and technologies. Our differentiated battle management and cyber solutions deliver timely, mission-enabling information and provide superior situational awareness and understanding to protect the U.S. and its global allies. Northrop Grumman Mission Systems (NGMS) is looking for you to join our team as a Embedded Software Engineer - Manufacturing Test Engineering (RF Systems) based out of Rolling Meadows, IL. Manufacturing Engineers thrive in an environment of daily unique challenges and close proximity to products. Partnering with production, successful test engineers lead troubleshooting and ensure excellence in hardware and software. Engineers who do well in this setting enjoy seeing their work perform in a test or a product, collaborate and communicate well across functions, and are innovative problem solvers. Best suited to this role are those who enjoy learning and bring a sense of urgency and energy to their tasks. This position will support software efforts associated with testing Radio Frequency (RF) production hardware in a dynamic, fast-paced and technically challenging production environment. This individual will be responsible for all aspects of test software development from requirements capture through final