Principal Embedded Software Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. Remove boilerplate etc. We need to parse the posting. First, job title is already shown, we don't repeat. We need sections: - About the role: description paragraph(s) about role. The posting includes a description: "At Northrop Grumman...". We can put that under About the role. - Responsibilities: list of duties under "What You Will Get To Do". That includes bullet points. We'll put under Responsibilities. - Requirements: maybe Basic Qualifications. Could be under Requirements or Qualifications. The instruction says we can use headings like Requirements, Qualifications, Skills. We need to decide. Probably Basic Qualifications under Requirements, Preferred Qualifications under Qualifications or Skills. But we need to avoid thin sections. We can combine Basic and Preferred under Requirements? But they said prefer few substantive sections over many thin ones. Could have Requirements (basic) and Qualifications (preferred) maybe both. But we need to see if they have content. We also have Benefits: they list benefits under "What We Can Offer You". So Benefits section. Pay: they have salary range. So Pay section. Schedule: they mention 9/80 Work Schedule (where available) under benefits; also maybe schedule info? Not explicit schedule like full-time etc. Could include schedule under Benefits? But they said only create Schedule section if posting actually states them. They mention "9/80 Work Schedule (where available)" which is a schedule type. So we could include Schedule section with that detail. However they also said prefer few substantive sections over many thin ones. Could incorporate schedule into Benefits. But schedule is a specific benefit; maybe we keep Benefits includes that. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can create Benefits section (they state benefits). Pay section (they state salary range). Schedule section (they state 9/80 Work Schedule). So we can have all three. We need to avoid duplication. Also need to include clearance info? That's metadata; we can fold into a short p or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Clearance required etc is minor metadata; we could include a short p at top maybe under About the role? But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Clearance info is not boilerplate but maybe minor metadata; we could include a short p under About the role or separate? Probably better to include a short p after the heading About the role? But they said use
for section headings; we can have a
for prose. So we could have a short p containing "Clearance required: Secret. US Citizenship required." etc. But we need to preserve ALL substantive information; clearance is substantive? It's a requirement. Could be part of Requirements. Actually clearance is a requirement: Ability to obtain and maintain a Secret clearance. US Citizenship required. So we should include that in Requirements or Qualifications. So we don't need separate metadata. Thus we will have sections: - About the role (description paragraph) - Responsibilities (ul li) - Requirements (basic qualifications) (ul li) - Qualifications (preferred qualifications) (ul li) maybe combine with Skills? But we can have Qualifications for preferred. - Benefits (ul li) - Pay (p with salary range) - Schedule (p with 9/80 Work Schedule) We must not repeat job title. We need to ensure we preserve all substantive information: description, responsibilities list, basic qualifications, preferred qualifications, benefits list, salary range, schedule. We need to remove boilerplate: EEO, application period, etc. Let's extract content. Description paragraphs: "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 Principal 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 validation and release. A successful person in this role will be very effective at leading collaboration with the product Design Engineer, the Test Hardware Engineer, the Quality Assurance Engineer and the Manufacturing Technician. This position would include providing needed efforts to set up and support the acceptance testing of the Shop Replaceable Units, as well as acceptance testing and environmental screening at the payload (Line Replaceable Unit) level. This position will support aerial, military-grade, or space-grade Electronic Warfare Systems and Subsystems." That's a lot; we can keep as paragraph(s). Could split into two paragraphs for readability but not required. Responsibilities: Under "What You Will Get To Do" bullet list: - 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. - Test station/fixture development: Design and maintain/revise Manufacturing Acceptance testing fixture and stations for functional and environmental testing. This includes test station concepts (Schematics, block diagram, simulations, test requirement creation) - 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 preserve all that. Could break into separate li items each starting with bold heading? The original had headings before each bullet. We can keep as li with the heading text included. Basic Qualifications: - Bachelor of Science degree in Electrical and/or Computer Engineering or a related STEM field with a minimum of 5 years relevant experience; OR a Master of Science (MS) degree in equivalent fields with 3 or more years of experience. - Experience with programming languages such as C#, C, Java or Lab Windows CVI - Experience with troubleshooting of hardware, software, or firmware issues - Experience completing software projects involving software design / development activities and/or integration and validation activities on schedule and on budget. - Ability to obtain and maintain a Secret clearance. - US Citizenship required. Preferred Qualifications: - Python and MATLAB experience. - Experience with schematic generation such as Cadence. - Prior software troubleshooting experience of test equipment or prime hardware. - Experience in troubleshooting unit under test. - Experience with RF Electronic systems in manufacturing or design (software, firmware, etc.) environment. - Experience working with use of any test instruments such as (but not limited to) Oscilloscope, Signal Generator, Spectrum Analyzer, Network Analyzer, etc. - Familiarity with reading schematics and interpreting electrical one-lines. - Experience using GitHub. - Active DoD Security Clearance. Benefits: - Health Plan - Savings Plan - Paid Time Off - Additional Benefits including Education Assistance, Training and Development, 9/80 Work Schedule (where available), and much more! Also later: "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." That's more detail; we should include. We need to preserve all substantive info; we can combine. Pay: - Primary Level Salary Range: $108,800.00 - $163,200.00 Also note about overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director. That's also substantive; we should include in Pay section. Schedule: - 9/80 Work Schedule (where available) mentioned under benefits; but we can still have Schedule section with that detail. We need to avoid duplication: if we put 9/80 in Benefits and also Schedule, that's duplication. Better to put schedule info only in Schedule section, and benefits exclude that line. But benefits also mention "Additional Benefits including Education Assistance, Training and Development, 9/80 Work Schedule (where available), and much more!" If we remove 9/80 from benefits, we lose that mention; but we can keep benefits without that specific line, but still mention Education Assistance, Training and Development, etc. The instruction: preserve ALL substantive information; we cannot omit the 9/80 mention. So we need to keep it somewhere. Could keep it in Benefits and not have a separate Schedule section. But then we would not have Schedule section despite having schedule info; but they said never create Schedule section unless posting actually states them. It does state 9/80 Work Schedule, so we could create Schedule section. However we would then duplicate the 9/80 mention if we also keep it in Benefits. To avoid duplication, we could move the 9/80 mention to Schedule section and remove from Benefits. But then we lose the phrase "Additional Benefits including Education Assistance, Training and Development, 9/80 Work Schedule (where available), and much more!" from Benefits. However we could keep Benefits as "Additional Benefits including Education Assistance, Training and Development, and much more!" and then Schedule section includes "9/80 Work Schedule (where available)". That preserves the info: benefits still mention Education Assistance, Training and Development; schedule mentions 9/80. The original phrase "and much more!" remains. That seems acceptable and not duplicative. Thus Benefits section will list: - Health Plan - Savings Plan - Paid Time Off - Additional Benefits including Education Assistance, Training and Development, and much more! Plus later details: health insurance coverage, life and disability insurance, savings plan, Company paid holidays and paid time off (PTO) for vacation and/or personal business. Some of these overlap with Health Plan, Savings Plan, Paid Time Off. We can keep them but avoid duplication.