Principal or Sr. Principal Mechanical Systems Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, remove boilerplate: relocation assistance line, clearance required, clearance type, travel line? Travel: Yes, 10% of the Time. That's schedule info? It's travel requirement. Could be part of Schedule? Not exactly schedule but travel. Might be part of "Schedule" if we treat travel as schedule? The instruction: include Schedule section only if posting actually states them. Travel is not schedule of work hours, but maybe we can include under "Schedule"? Probably not. Better to omit Schedule unless explicit work hours. No explicit schedule given. So omit Schedule. Pay: we have salary ranges: Primary Level Salary Range: $108,800.00 - $163,200.00; Secondary Level Salary Range: $135,800.00 - $203,600.00. Also mention overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director. So we have pay info. Include Pay section. Benefits: mention health insurance, life and disability insurance, savings plan, company paid holidays, paid time off (PTO). Also mention relocation assistance may be available. So include Benefits. Qualifications: we have Basic Qualifications for Principal and Senior Principal. Also Preferred Qualifications. So we can have Requirements (maybe basic qualifications) and Qualifications (preferred) or combine. The instruction: Use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have "Essential Functions" which are duties/responsibilities. So Responsibilities section. We have description paragraph about company culture etc. That could be About the role. We have "Basic Qualifications" etc. Those are Requirements. We have "Preferred Qualifications". Could be Qualifications or Skills. Probably Qualifications. Skills: maybe list specific skills like proficiency in FEA tools, bolted joint analysis, structural hand calculations, ability to work on site, US citizen, TS/SCI, etc. Those are more like qualifications. But we can put them under Skills if we want. However we need to avoid duplication. Let's think: The posting includes both basic and preferred qualifications. We could put basic under Requirements, preferred under Qualifications. Skills maybe not needed separately if covered. But we need to include a section only if there is real specific content. We could omit Skills if we feel it's covered. But we have to decide. Better to include Skills for things like "Proficiency in using common engineering design, production, analysis, and office tools.", "Experience with Finite Element Analysis tools, bolted joint analysis, and structural hand calculations", "Ability to work in a fast-paced environment", "Proficiency in using Finite Element Analysis tools (ANSYS, FEMAP/Nastran)", etc. Those are skills. Thus we can have: - About the role: description paragraph(s) about company culture and mission. - Responsibilities: Essential Functions bullet list. - Requirements: Basic Qualifications (both Principal and Senior Principal) maybe as list. - Qualifications: Preferred Qualifications list. - Skills: maybe we can merge with Requirements/Qualifications; but to follow instruction, we could still include Skills if we have content. However we might duplicate. Let's see if we can assign distinct content: Requirements = citizenship, clearance, education, experience. Skills = technical proficiencies (FEA tools, bolted joint analysis, structural hand calculations, office tools, ability to work on site, fast-paced environment). Qualifications = preferred qualifications (active TS/SCI clearance, ability to work in fast-paced environment, proficiency in FEA tools etc). There's overlap. Maybe better: Requirements = Basic Qualifications (education, experience, citizenship, clearance). Skills = technical skills (FEA tools, bolted joint analysis, structural hand calculations, office tools, ability to work on site, fast-paced environment). Qualifications = Preferred Qualifications (active TS/SCI clearance, ability to work in fast-paced environment, proficiency in FEA tools etc). There's still overlap but okay. We need to ensure we don't invent content. We'll list items exactly as in posting. Let's extract text. About the role: The paragraph starting "At Northrop Grumman, our employees have incredible opportunities..." up to "...providing real-life solutions to our world’s biggest challenges." Also maybe the sentence "We take pride in creating purposeful work and allowing our employees to grow and achieve their goals every day by Defining Possible." That's part of same paragraph. Also "With our competitive pay and comprehensive benefits, we have the right opportunities to fit your life and launch your career today." That's also part of description. Also "The Naval & Oceanic Systems business unit headquartered in Annapolis, MD is seeking dependable individuals willing to work in a collaborative environment and that are interested in expanding their horizons. The Mechanical Engineering Department is seeking a Principal Mechanical Systems Engineer or Senior Principal Mechanical Systems Engineer to join our team of qualified, diverse individuals." That's also about the role. So we can combine all descriptive paragraphs before Essential Functions. Responsibilities: Essential Functions bullet list: concept development, problem solving, structural analysis, technical planning, design development and integration & testing of undersea hardware. The applicant will translate customer requirements into systems solutions that acknowledge technical, schedule, and cost constraints. The candidate must be able to collaborate in a team environment, prioritize and adjust tasks to accomplish the project result, prioritize multiple responsibilities and/or accomplishing them simultaneously, and comprehend and analyze complex problems and develop solutions. Excellent verbal and written communication skills are required. This position can be filled at a Principal or Senior Principal level. We can break into list items. Requirements (Basic Qualifications): For Principal: BS degree in Engineering (Mechanical Engineering, Ocean Engineering or equivalent STEM) and a minimum of 5 years of experience or MS degree with 3 years of experience. Proficiency in using common engineering design, production, analysis, and office tools. Experience with Finite Element Analysis tools, bolted joint analysis, and structural hand calculations. Ability to work on site at Annapolis, MD campus. US citizen with the ability to obtain a TS/SCI and pass a polygraph. For Senior Principal: BS degree in Engineering (Mechanical Engineering, Ocean Engineering or equivalent STEM) and a minimum of 8 years of experience or MS degree with 6 years of experience. Proficiency in using common engineering design, production, analysis, and office tools. Experience with Finite Element Analysis tools, bolted joint analysis, and structural hand calculations. Ability to work on site at Annapolis, MD campus. US citizen with the ability to obtain a TS/SCI and pass a polygraph. We could combine as list items, maybe note both levels. Qualifications (Preferred Qualifications): Able to work in a fast-paced environment where multiple projects are being developed and deployed simultaneously. Proficiency in using Finite Element Analysis tools (ANSYS, FEMAP/Nastran), bolted joint analysis, and structural hand calculations. Active TS/SCI clearance. Skills: Could list technical skills: Proficiency in using common engineering design, production, analysis, and office tools. Experience with Finite Element Analysis tools, bolted joint analysis, and structural hand calculations. Ability to work on site at Annapolis, MD campus. Ability to work in a fast-paced environment where multiple projects are being developed and deployed simultaneously. Proficiency in using Finite Element Analysis tools (ANSYS, FEMAP/Nastran). etc. But this duplicates. Maybe better to omit Skills section and just have Requirements and Qualifications. The instruction says we can have sections like Skills, but not required. Prefer few substantive sections over many thin ones. So we can omit Skills if its content overlaps. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we have Schedule: travel 10% of time. That's not schedule of work hours, but could be considered schedule? The instruction: include Schedule section only if posting actually states them. Travel is not schedule of work hours, but it's a schedule of travel. Might be considered schedule? Probably not. Safer to omit Schedule. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: relocation assistance line, clearance required for start, clearance type, travel line? Travel line we might keep as part of Responsibilities? Actually travel is not a duty but a condition. Could be included in Requirements? Not exactly. Might be omitted as it's minor metadata. The instruction: fold minor metadata into a short

  or drop it. Travel 10% of time is minor metadata; we could drop it or include in a short p under maybe Responsibilities? But better to drop. Relocation assistance line: also minor metadata; could drop. Clearance required for start: No; clearance type: SCI; these are metadata; drop. Now we need to preserve all substantive information. So we must keep the description, essential functions, qualifications, benefits, pay. Let's craft. About the role: combine paragraphs into one or multiple

  . Use

  for prose. We'll produce:

  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. Join Northrop Grumman on our continued mission to push the boundaries of possible across land, sea, air, space, and cyberspace. Enjoy a culture where your voice is valued and start contributing to our team of passionate professionals providing real-life solutions to our world’s biggest challenges. We take pride in creating purposeful work and allowing our employees to grow and achieve their goals every day by Defining Possible. With our competitive pay and comprehensive benefits, we have the right opportunities to fit your life and launch your career today. The Naval & Oceanic Systems business unit headquartered in Annapolis, MD is seeking dependable individuals willing to work in a collaborative environment and that are interested in expanding their horizons. The Mechanical Engineering Department is seeking a Principal Mechanical Systems Engineer or Senior Principal Mechanical Systems Engineer to join our team of qualified, diverse individuals.

  Responsibilities:

  Responsibilities

  then
  • each bullet. We need to split the essential functions into list items. Essential Functions text: "This position tasking includes concept development, problem solving, structural analysis, technical planning, design development and integration & testing of undersea hardware. The applicant will translate customer requirements into systems solutions that acknowledge technical, schedule, and cost constraints. The candidate must be able to collaborate in a team environment, prioritize and adjust tasks to accomplish the project result, prioritize multiple responsibilities and/or accomplishing them simultaneously, and comprehend and analyze complex problems and develop solutions. Excellent verbal and written communication skills are required. This position can be filled at a Principal or Senior Principal level." We can break into list items: - Concept development, problem solving, structural analysis, technical planning, design development and integration & testing of undersea hardware. - Translate customer requirements into systems solutions that acknowledge technical, schedule, and cost constraints. - Collaborate in a team environment, prioritize and adjust tasks to accomplish project results. - Prioritize multiple responsibilities and/or accomplish them simultaneously. - Comprehend and analyze complex problems and develop solutions. - Demonstrate excellent verbal and written communication skills. - Position may be filled at a Principal or Senior Principal level