Sr. Principal Design Engineer
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 can include a short paragraph with relocation assistance, clearance, travel maybe. We need sections: About the role (description paragraph). Responsibilities (list of essential functions). Requirements (maybe basic qualifications?). Qualifications (maybe preferred qualifications?). Skills (maybe tools proficiency). Benefits (benefits paragraph). Pay (salary range). Schedule (maybe not given; there is travel 10% of time but not schedule; we should not create Schedule unless posting actually states them. It does not state schedule like full-time, shift, etc. So we omit Schedule section. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: salary range. Benefits is stated: variety of benefits including health insurance etc. So include Benefits and Pay sections. We must not include filler like "commensurate with experience". Not present. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from description, essential functions, basic qualifications, preferred qualifications, tools, etc. We need to decide how to split into sections.
Potential sections:
- About the role: description paragraph about Northrop Grumman, culture, position location, etc.
- Responsibilities: essential functions list (the bullet points after "Essential Functions").
- Requirements: maybe basic qualifications? Or we could have Requirements = basic qualifications, Qualifications = preferred qualifications. But we need to avoid duplication. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections. We'll put basic qualifications under Requirements, and preferred qualifications under Qualifications.
- Skills: maybe list of tools proficiency (CAD, Nastran, etc.) and other skills like MBSE, etc. Could also include some from preferred qualifications.
- Benefits: paragraph about benefits.
- Pay: paragraph about salary range.
We also need to include minor metadata like relocation assistance, clearance required, travel. Could fold into a short
maybe after About the role or at top. Since they said fold minor metadata into a short
or drop it. We'll include a short paragraph after About the role maybe: "
Relocation assistance may be available. Secret clearance required for start. Travel up to 10% of time.
"
We must not include EEO boilerplate etc. Remove that.
Now ensure we preserve all substantive info: Let's extract.
Description paragraph: "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 Aeronautic Systems has an opening for a Sr. Principal Design Engineer to join our team of qualified diverse individuals. This position will be located in Palmdale or El Segundo, CA. The candidate should be a self-starter with familiarity working in an Integrated Product Team (IPT) construct. Looking for an Engineer who analyzes, researches and develops structural engineering specifications involving metals, non-metallic or composite structural materials for product design. Analyzes damage tolerance, durability of metal and composite airframe structures. Knowledge of random vibration analysis. Tools utilized may include Catia, FEMAP, Patran, Nastran and a variety of software applications."
That's the description.
Essential Functions list (each starts with a verb). We'll list them as - .
Basic Qualifications: "BS degree in Engineering (Aerospace, Mechanical, or Civil) and a minimum of 8 years of experience in Aerospace structural analysis or MS degree in Engineering (Aerospace, Mechanical, or Civil) with 6 years of experience OR a PhD in a STEM discipline and 4 years of related engineering experience..Proficiency with CAD and drafting tools (e.g., CATIA, NX, SolidWorks) and creation of engineering drawings and BOMs. Strong knowledge of requirements development and management practices and toolsExperience with subsystem test planning, execution, troubleshooting, and hardware-in-the-loop or bench testing.Familiarity with manufacturing/ producibility considerations, design for maintainability, and configuration management processes.Active USG Secret clearance (with a background investigation within the past 5 years or enrolled into Continuous Evaluation).Ability to obtain and maintain initial Special Access Program (SAP) access via a Program Access Request (PAR). This SAP/PAR must be obtained prior to commencement of employment and must be obtained within a reasonable amount of time as determined by the company to meet its business needs.Ability to obtain and maintain subsequent SAP PARs following commencement of employment to be able to completely support statement of work."
Note there is some missing punctuation but we keep as is.
Preferred Qualifications: "Current applicable Special Access Program (SAP) clearance.Active USG Top Secret clearance or higher (with a background investigation within the past 5 years or enrolled into Continuous Evaluation).Experience integrating avionics, flight control electronics, sensors, or actuators.Proficiency with MBSE and simulationFamiliarity with certification processesExperience performing engineering analyses and simulations (structural, thermal, vibration, aeroelastic) using tools such as Nastran, Ansys, MATLAB/Simulink.Have some proficiency in 3-dimensional, constraint based, design systems, CATIA or NX.Have some familiarity with configuration management tools such as Teamcenter or CPLMExperience with EVMS, CAM certificationPrevious Team Leadership - IPT, Project Management, etc"
We need to keep that.
Skills: Could combine tools proficiency etc. But we already have some in qualifications. Perhaps we can make a Skills section listing specific tools: Catia, FEMAP, Patran, Nastran, CAD tools (CATIA, NX, SolidWorks), MBSE, simulation, Ansys, MATLAB/Simulink, configuration management tools (Teamcenter, CPLM), etc. However we must not invent; we can list those that appear.
But we already have many in qualifications; maybe we can skip Skills section to avoid duplication. However instruction says prefer a few substantive sections over many thin ones. We could combine Skills into Qualifications or Requirements. But we have separate headings for Skills; we could include it if we have specific skill list not covered elsewhere. The qualifications already mention proficiency with CAD and drafting tools, experience with subsystem test planning, familiarity with manufacturing, etc. Preferred qualifications mention MBSE, simulation, certification processes, engineering analyses using Nastran, Ansys, MATLAB/Simulink, proficiency in 3D constraint based design systems CATIA or NX, familiarity with configuration management tools Teamcenter or CPLM, experience with EVMS, CAM certification, previous team leadership.
Thus we could put Skills section listing: Catia, FEMAP, Patran, Nastran, CAD tools (CATIA, NX, SolidWorks), MBSE, simulation, Ansys, MATLAB/Simulink, configuration management tools (Teamcenter, CPLM), EVMS, CAM certification, team leadership (IPT, Project Management). But some of these are already in qualifications; but it's okay to repeat? The instruction says preserve ALL substantive information; not to invent or summarize away detail. Repeating is okay as long as we don't lose info. However we might be duplicating; but it's not prohibited. However we should aim to avoid thin sections. Maybe better to not have a separate Skills section and instead include those details under Qualifications (preferred) and Requirements (basic). Since we already have Requirements and Qualifications sections covering those, we can omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We also need to include minor metadata paragraph maybe after About the role.
Now ensure we don't include any boilerplate like EEO, relocation assistance? We included relocation assistance in a short paragraph.
Check for any other substantive info: "Primary Level Salary Range: $142,200.00 - $213,400.00" plus description about salary determination, overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director, benefits list. We need to preserve all that.
Thus Pay section should include the salary range and the accompanying text about factors, overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director.
Benefits section should include: "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."
Also maybe mention application period? That's not a benefit; it's metadata about application period. Could be folded into minor metadata paragraph? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Application period is minor metadata; we can include in a short paragraph.
Thus we will have a short metadata paragraph after About the role: includes relocation assistance, clearance, travel, application period.
Now let's craft HTML.
We'll start with
About the role
then with the description paragraph (the long description). Then
for metadata: "Relocation assistance may be available. Secret clearance required for start. Travel up to 10% of time. Application period estimated at 20 days from posting date, subject to change."
Then
Responsibilities
then - each essential function.
Essential functions list (as per text):
- Design and develop subsystem components (avionics, control surfaces, propulsion interfaces, environmental systems) meeting performance, weight, and reliability requirements.
- Translate system-level requirements into detailed subsystem specifications, interfaces, and engineering drawings.
- Perform trade studies, engineering analyses, and simulations (stress, aeroelasticity, thermal, vibration) to validate subsystem concepts and support design decisions.
- Create and maintain technical documentation, including schematics, bills of materials, test plans, and verification matrices.
- Support integration and interface activities with other engineering disciplines to ensure subsystem compatibility and compliance.
- Plan, execute, and analyze subsystem-level tests (bench, hardware-in-the-loop, environmental) and resolve design deficiencies through corrective actions.
- Contribute to configuration management, design reviews, risk assessments, and continuous improvement activities to ensure producible, maintainable subsystem designs.
We need to keep the exact phrasing.
Now
Requirements
then for basic qualifications? Or we could use
- for each requirement. The basic qualifications contain multiple sentences; we could break into list items for clarity. But we must preserve all info; using list is fine as long as we don't lose info. The instruction: Use
- for any list of duties/requirements/benefits. So we can treat basic qualifications as a list of requirements.
Thus we will create
- items:
- BS degree in Engineering (Aerospace, Mechanical, or
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from description, essential functions, basic qualifications, preferred qualifications, tools, etc. We need to decide how to split into sections. Potential sections: - About the role: description paragraph about Northrop Grumman, culture, position location, etc. - Responsibilities: essential functions list (the bullet points after "Essential Functions"). - Requirements: maybe basic qualifications? Or we could have Requirements = basic qualifications, Qualifications = preferred qualifications. But we need to avoid duplication. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections. We'll put basic qualifications under Requirements, and preferred qualifications under Qualifications. - Skills: maybe list of tools proficiency (CAD, Nastran, etc.) and other skills like MBSE, etc. Could also include some from preferred qualifications. - Benefits: paragraph about benefits. - Pay: paragraph about salary range. We also need to include minor metadata like relocation assistance, clearance required, travel. Could fold into a short
maybe after About the role or at top. Since they said fold minor metadata into a short
or drop it. We'll include a short paragraph after About the role maybe: "
Relocation assistance may be available. Secret clearance required for start. Travel up to 10% of time.
" We must not include EEO boilerplate etc. Remove that. Now ensure we preserve all substantive info: Let's extract. Description paragraph: "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 Aeronautic Systems has an opening for a Sr. Principal Design Engineer to join our team of qualified diverse individuals. This position will be located in Palmdale or El Segundo, CA. The candidate should be a self-starter with familiarity working in an Integrated Product Team (IPT) construct. Looking for an Engineer who analyzes, researches and develops structural engineering specifications involving metals, non-metallic or composite structural materials for product design. Analyzes damage tolerance, durability of metal and composite airframe structures. Knowledge of random vibration analysis. Tools utilized may include Catia, FEMAP, Patran, Nastran and a variety of software applications." That's the description. Essential Functions list (each starts with a verb). We'll list them as- .
Basic Qualifications: "BS degree in Engineering (Aerospace, Mechanical, or Civil) and a minimum of 8 years of experience in Aerospace structural analysis or MS degree in Engineering (Aerospace, Mechanical, or Civil) with 6 years of experience OR a PhD in a STEM discipline and 4 years of related engineering experience..Proficiency with CAD and drafting tools (e.g., CATIA, NX, SolidWorks) and creation of engineering drawings and BOMs. Strong knowledge of requirements development and management practices and toolsExperience with subsystem test planning, execution, troubleshooting, and hardware-in-the-loop or bench testing.Familiarity with manufacturing/ producibility considerations, design for maintainability, and configuration management processes.Active USG Secret clearance (with a background investigation within the past 5 years or enrolled into Continuous Evaluation).Ability to obtain and maintain initial Special Access Program (SAP) access via a Program Access Request (PAR). This SAP/PAR must be obtained prior to commencement of employment and must be obtained within a reasonable amount of time as determined by the company to meet its business needs.Ability to obtain and maintain subsequent SAP PARs following commencement of employment to be able to completely support statement of work."
Note there is some missing punctuation but we keep as is.
Preferred Qualifications: "Current applicable Special Access Program (SAP) clearance.Active USG Top Secret clearance or higher (with a background investigation within the past 5 years or enrolled into Continuous Evaluation).Experience integrating avionics, flight control electronics, sensors, or actuators.Proficiency with MBSE and simulationFamiliarity with certification processesExperience performing engineering analyses and simulations (structural, thermal, vibration, aeroelastic) using tools such as Nastran, Ansys, MATLAB/Simulink.Have some proficiency in 3-dimensional, constraint based, design systems, CATIA or NX.Have some familiarity with configuration management tools such as Teamcenter or CPLMExperience with EVMS, CAM certificationPrevious Team Leadership - IPT, Project Management, etc"
We need to keep that.
Skills: Could combine tools proficiency etc. But we already have some in qualifications. Perhaps we can make a Skills section listing specific tools: Catia, FEMAP, Patran, Nastran, CAD tools (CATIA, NX, SolidWorks), MBSE, simulation, Ansys, MATLAB/Simulink, configuration management tools (Teamcenter, CPLM), etc. However we must not invent; we can list those that appear.
But we already have many in qualifications; maybe we can skip Skills section to avoid duplication. However instruction says prefer a few substantive sections over many thin ones. We could combine Skills into Qualifications or Requirements. But we have separate headings for Skills; we could include it if we have specific skill list not covered elsewhere. The qualifications already mention proficiency with CAD and drafting tools, experience with subsystem test planning, familiarity with manufacturing, etc. Preferred qualifications mention MBSE, simulation, certification processes, engineering analyses using Nastran, Ansys, MATLAB/Simulink, proficiency in 3D constraint based design systems CATIA or NX, familiarity with configuration management tools Teamcenter or CPLM, experience with EVMS, CAM certification, previous team leadership.
Thus we could put Skills section listing: Catia, FEMAP, Patran, Nastran, CAD tools (CATIA, NX, SolidWorks), MBSE, simulation, Ansys, MATLAB/Simulink, configuration management tools (Teamcenter, CPLM), EVMS, CAM certification, team leadership (IPT, Project Management). But some of these are already in qualifications; but it's okay to repeat? The instruction says preserve ALL substantive information; not to invent or summarize away detail. Repeating is okay as long as we don't lose info. However we might be duplicating; but it's not prohibited. However we should aim to avoid thin sections. Maybe better to not have a separate Skills section and instead include those details under Qualifications (preferred) and Requirements (basic). Since we already have Requirements and Qualifications sections covering those, we can omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We also need to include minor metadata paragraph maybe after About the role.
Now ensure we don't include any boilerplate like EEO, relocation assistance? We included relocation assistance in a short paragraph.
Check for any other substantive info: "Primary Level Salary Range: $142,200.00 - $213,400.00" plus description about salary determination, overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director, benefits list. We need to preserve all that.
Thus Pay section should include the salary range and the accompanying text about factors, overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director.
Benefits section should include: "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."
Also maybe mention application period? That's not a benefit; it's metadata about application period. Could be folded into minor metadata paragraph? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Application period is minor metadata; we can include in a short paragraph. Thus we will have a short metadata paragraph after About the role: includes relocation assistance, clearance, travel, application period. Now let's craft HTML. We'll start with
About the role
thenwith the description paragraph (the long description). Then
for metadata: "Relocation assistance may be available. Secret clearance required for start. Travel up to 10% of time. Application period estimated at 20 days from posting date, subject to change." Then
Responsibilities
then- each essential function.
Essential functions list (as per text):
- Design and develop subsystem components (avionics, control surfaces, propulsion interfaces, environmental systems) meeting performance, weight, and reliability requirements.
- Translate system-level requirements into detailed subsystem specifications, interfaces, and engineering drawings.
- Perform trade studies, engineering analyses, and simulations (stress, aeroelasticity, thermal, vibration) to validate subsystem concepts and support design decisions.
- Create and maintain technical documentation, including schematics, bills of materials, test plans, and verification matrices.
- Support integration and interface activities with other engineering disciplines to ensure subsystem compatibility and compliance.
- Plan, execute, and analyze subsystem-level tests (bench, hardware-in-the-loop, environmental) and resolve design deficiencies through corrective actions.
- Contribute to configuration management, design reviews, risk assessments, and continuous improvement activities to ensure producible, maintainable subsystem designs.
We need to keep the exact phrasing.
Now
Requirements
thenfor basic qualifications? Or we could use
- for each requirement. The basic qualifications contain multiple sentences; we could break into list items for clarity. But we must preserve all info; using list is fine as long as we don't lose info. The instruction: Use
- for any list of duties/requirements/benefits. So we can treat basic qualifications as a list of requirements.
Thus we will create
- items: - BS degree in Engineering (Aerospace, Mechanical, or
- for any list of duties/requirements/benefits. So we can treat basic qualifications as a list of requirements.
Thus we will create
- for each requirement. The basic qualifications contain multiple sentences; we could break into list items for clarity. But we must preserve all info; using list is fine as long as we don't lose info. The instruction: Use
- each essential function.
Essential functions list (as per text):
- Design and develop subsystem components (avionics, control surfaces, propulsion interfaces, environmental systems) meeting performance, weight, and reliability requirements.
- Translate system-level requirements into detailed subsystem specifications, interfaces, and engineering drawings.
- Perform trade studies, engineering analyses, and simulations (stress, aeroelasticity, thermal, vibration) to validate subsystem concepts and support design decisions.
- Create and maintain technical documentation, including schematics, bills of materials, test plans, and verification matrices.
- Support integration and interface activities with other engineering disciplines to ensure subsystem compatibility and compliance.
- Plan, execute, and analyze subsystem-level tests (bench, hardware-in-the-loop, environmental) and resolve design deficiencies through corrective actions.
- Contribute to configuration management, design reviews, risk assessments, and continuous improvement activities to ensure producible, maintainable subsystem designs.
We need to keep the exact phrasing.
Now