System Test Engineer - Level 3 or 4
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID/requisition numbers. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to preserve all substantive information. Let's parse the posting. Key content: - Relocation assistance: No relocation assistance available. - Clearance required for start: Yes. - Clearance type: Secret. - Travel: No. - Description: At Northrop Grumman ... repeated paragraphs about culture etc. We need to keep substantive info: description of company culture, mission, etc. Should we include as "About the role" or "About the company"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Position Overview: selected Engineer will support GMD Weapon System program as individual contributor on Architecture and Delivery (A&D) Automated Test and Verification (ATV) Team and is responsible for developing manual, automation, and systems engineering related test products in support of the GWS contract execution on behalf of MDA. - Essential Functions: bullet list (but not formatted as list in text). It says: "You will be expected to build systems engineering and test products assigned by your leadership related to requirement verification efforts at the system level Candidate develops software and hardware test artifacts in an Agile environment Candidate should thrive in a fast-paced work environment with high expectations, diverse assignments, and collaborative team settings across all levels." We can turn into list items. - Basic Qualifications: includes details for Level 3 and Level 4. - Preferred Qualifications: list. - Salary ranges: Primary Level Salary Range: $98,900.00 - $148,300.00; Secondary Level Salary Range: $123,400.00 - $185,000.00. Also note about salary determination etc. - Benefits: list: Health Plan, Savings Plan, Paid Time Off, Education Assistance, Training and Development, Flexible Work Arrangements. Also mention 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 flexible and customizable benefits. - Also mention: The application period etc (but that's application instructions? Might be considered boilerplate? It's not exactly application instructions but timeline. Might be considered metadata; but instruction says remove application instructions. The timeline may be considered application instruction? Probably remove. - Also mention: Northrop Grumman is an Equal Opportunity Employer etc. Remove EEO boilerplate. - Also mention: U.S. Citizenship required for all positions with a government clearance and certain other restricted positions. That's relevant to clearance; maybe keep as part of Requirements? Could be a note. - Also mention: Relocation assistance: No relocation assistance available. That's a detail; we could include in a short paragraph maybe under Benefits? Or as a note. Since it's a specific statement, we should preserve. Could be under Benefits heading? Not exactly benefit. Could be under "About the role" maybe. But we need to avoid filler. It's substantive: No relocation assistance. So we can include a
stating that. - Clearance required: Yes, Secret. That's a requirement. - Travel: No. We need to decide sections. Potential sections: - About the role: could include position overview, description of work, location (Huntsville, AL), maybe relocation assistance note, clearance, travel. - Responsibilities: essential functions. - Requirements: basic qualifications (maybe also clearance, citizenship, etc.) - Qualifications: could be preferred qualifications? Or we could combine basic and preferred under Requirements and Qualifications? The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. We could treat: - About the role: position overview, location, relocation, clearance, travel. - Responsibilities: essential functions (list). - Requirements: basic qualifications (including education/experience, clearance, citizenship, ability to work office/on site). - Qualifications: preferred qualifications (list). - Skills: maybe we could extract skills from preferred qualifications? But we could also put skills under Qualifications. However we need to follow instruction: Use headings for those sections only if posting has real specific content. We have content for Skills? The posting mentions "good communication skills", "capable of working both independently and within team environments", "Experience with components of SDLC", "Experience with requirements management tools such as DOORS", "Familiarity with Agile software development using tools like Jira, Confluence, Fisheye/Crucible, and Bitbucket", "Experience in developing test artifacts/cases and executing manual test", "Working knowledge of systems engineering principles and processes", "Verification experience or knowledge". Those are skills/experience. Could be placed under Skills. But we also have "Preferred Qualifications" list includes many items like CAMEO/MBSE, instrumentation, hardware trouble-shooting, requirements decomposition, degree in Systems Engineering, Requirement Verification methods such as TestGMD Knowledge, independent planning, understanding of Systems Engineering V-Model, degree in Software Engineering or Computer Science, experience developing technical solutions, experience in software development related to Test Automation, experience using Jenkins and Elasticsearch, Agile/Scrum leadership roles, Security+ certification, professional experience development using Python or similar languages. We could split: Requirements = basic qualifications (mandatory). Qualifications = preferred qualifications (nice-to-have). Skills = maybe the specific skill items like communication, teamwork, etc. But we might be overlapping. Given instruction to prefer few substantive sections over many thin ones, we could combine some. Maybe we do: - About the role (position overview, location, relocation, clearance, travel) - Responsibilities (essential functions) - Requirements (basic qualifications + clearance/citizenship + ability to work office/on site) - Qualifications (preferred qualifications) - Benefits (benefits list) - Pay (salary ranges) We could omit Skills section if we incorporate skills into Requirements/Qualifications. Schedule: not mentioned; no schedule info (like full-time, shift). So we omit Schedule. We must not include headings with filler. So we will not include Schedule. Now we need to output HTML fragment only, no /, no markdown. We'll produce something like:
About the role
Position: Systems Test Engineer – Level 3 or 4 at Northrop Grumman Space Systems, Multi-Domain Operations, and Missile Defense Integration Business Unit in Huntsville, AL. The role supports the Ground-based Midcourse Defense (GMD) Weapon System program as an individual contributor on the Architecture and Delivery (A&D) Automated Test and Verification (ATV) Team, developing manual, automation, and systems engineering related test products for the GWS contract execution on behalf of the Missile Defense Agency (MDA). Relocation assistance is not available. A DoD Secret clearance is required for start; U.S. citizenship is required for cleared positions. Travel is not required.
Responsibilities
- Build systems engineering and test products assigned by leadership related to requirement verification efforts at the system level.
- Develop software and hardware test artifacts in an Agile environment.
- Thrive in a fast-paced work environment with high expectations, diverse assignments, and collaborative team settings across all levels.
Requirements
- Systems Test Engineer Level 3: Bachelor’s degree in a STEM discipline from an accredited university and 5 years of related work experience, or a Master's degree in STEM and 3 years of related work experience, or a PhD and 1 year of related work experience.
- Systems Test Engineer Level 4: Bachelor’s degree in a STEM discipline and 8 years of related work experience, or a Master's degree in STEM and 6 years of related work experience, or a PhD and 4 years of related work experience.
- Experience with components of the Software Development Life Cycle (SDLC) – software design, requirements, application development, integration, testing, or deployment.
- Experience with requirements management tools such as DOORS.
- Familiarity with Agile software development using tools like Jira, Confluence, Fisheye/Crucible, and Bitbucket.
- Experience developing test artifacts/cases and executing manual tests in support of requirements verification efforts.
- Working knowledge of systems engineering principles and processes.
- Verification experience or knowledge.
- Good communication skills; capable of working independently and within team environments.
- Must possess an active DoD Secret or higher clearance.
- Must be able to work in office, on site.
- U.S. citizenship required for positions with government clearance.
Qualifications
- Knowledge and experience using CAMEO and/or Model Based Systems Engineering (MBSE) principles.
- Experience with instrumentation, data acquisition, and data review.
- Hands‑on experience troubleshooting, building, and testing hardware.
- Experience with requirements decomposition and requirements management.
- Degree in Systems Engineering.
- Experience with requirement verification methods such as TestGMD.
- Demonstrated independent planning, organization, and working in cross‑functional teams with a customer focus.
- Understanding of the Systems Engineering V‑Model.
- Degree in Software Engineering or Computer Science discipline(s).
- Experience developing technical solutions in collaboration with product teams.
- Experience in software development related to test automation.
- Experience using Jenkins and Elasticsearch.
- Experience in Agile/Scrum leadership roles such as Scrum Master or Product Owner.
- Current Security+ certification.
- Professional experience developing with Python or similar languages.
Benefits
- Health plan (medical, dental, vision).
- Savings plan (401(k) with company match).
- Paid time off (PTO) for vacation and personal business.
- Education assistance.
- Training and development.
- Flexible work arrangements.
- Life and disability insurance.
- Company‑paid holidays.
Pay
Primary level salary range: $98,900.00 – $148,300.00.
Secondary level salary range: $123,400.00 – $185,000.00.
Salary is determined based on scope, responsibilities, experience, education, skills, and market conditions; eligible for overtime, shift differential, discretionary bonus, and annual bonuses that reward individual contributions and share in company results; employees in VP or Director roles may be eligible for long‑term incentives.
We need to ensure we didn't include any boilerplate like EEO, application period, etc. We removed those. Check for duplicated lines: we didn't repeat the culture paragraphs; we omitted them because they were duplicated and not essential to role? The instruction says preserve ALL substantive information. The culture paragraphs might be considered substantive? They are generic but maybe considered boilerplate? They are repeated twice. They are about company culture, mission, history. Might be considered substantive but could be considered fluff. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The culture description is substantive about the company. Should we include it? Possibly under About the