Lead Engineer Program Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions.
We need to parse the job posting content.
Let's extract sections:
- "Who YOU Are And What YOU Can Become": description of role: leading engineering team, managing Nacelle and Engine Build Up programs, providing leadership, coordination, support internal investigations, interfacing with customers and internal senior staff. This is about the role. Could be "About the role" section.
- "Who WE Are And Where WE Are Going": description of company. Might be "About the company" but not in allowed headings. Could be omitted or maybe part of "About the role"? The allowed headings list does not include "About the company". We could either omit or put under "About the role"? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should prefer those headings. Probably we should map content to those headings. The company description may not fit any; maybe we can omit it as not required. But we must preserve ALL substantive information; we cannot drop substantive info. However we could incorporate company description into "About the role" or maybe a separate section like "About the company" but not allowed. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not exclusive? It says "e.g." meaning examples. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create other headings if needed, but they gave examples. Safer to stick to those headings; we can put company info under "About the role" maybe as part of role context. But that might dilute.
Better: Use "About the role" for the description of what you would be doing (the first block). Use "Responsibilities" for the "What YOU Will Do" block. Use "Requirements" for the "What YOU Must Bring To Succeed" block (education, experience, US person). Use "Qualifications" maybe for desired characteristics? Or we could split: Requirements = mandatory; Qualifications = desired. Skills = maybe desired characteristics like leadership, communication, etc. Benefits = benefits block. Pay = salary range. Schedule = not mentioned; we should not create Schedule section if no info.
We must not create sections with filler like "not specified". So we omit Schedule.
Now extract content:
About the role: "Who YOU Are And What YOU Can Become You would be leading the engineering team and managing new and existing Nacelle and Engine Build Up programs. It includes providing leadership and coordination of the engineering team assigned to the programs to support new designs and improving existing designs. You would be providing support for internal investigations of field issues and determining if design changes can provide relief for certain supply chain challenges are also part of the job. In addition, you would be interfacing with customers and internal senior staff."
We need to preserve all substantive information. Could split into sentences.
Responsibilities: "What YOU Will Do Responsible for developing and managing cross-functional product focused programs. Manages the project and interfaces with partners, contractors, suppliers, customers and internal functions. Manages program resource and budget allocation/integration. Engineering lead and focal for the program. Responsible for the planning and execution of all Engineering deliverables to support qualification, certification, and production of Nacelle hardware to agree technical specifications, schedule, and budget. Develops, maintains, and communicates; priorities and executable plans for a diverse domestic and global team to support internal business and Customer requirements. Supports monthly Engineering Operations reviews with variance assessments, corrective action, updated Forecast (budget and resource), key risks/abatements, and help needed. Manage an integrated master schedule (IMS) with inputs from the team and provide assessment of multiple critical path(s). Develop action plans with guidance to respond to issues/problems."
Requirements (mandatory): "What YOU Must Bring To Succeed Bachelor’s degree in engineering or equivalent technical degree from an accredited university or college. Minimum of 5 years of engineering work experience. This position involves access to export-controlled technology which requires U.S. Person status or government authorization. A ‘U.S. Person,’ as defined by 22 C.F.R.120.62, includes U.S. citizens, U.S. nationals, individuals lawfully admitted for permanent residence (green card holders), and individuals granted asylum or refugee status in the United States. To be considered for this position, you must either be a U.S. Person or fall within a legally recognized export control exception or authorization. If hired, you will be required to provide valid proof of such status."
Qualifications (desired): "Desired Characteristics Experience in leading technical programs in the Aerospace industry. Strong oral and written communication skills. Strong interpersonal and leadership skills. Ability to influence others and lead small teams. Ability to coordinate several projects simultaneously. Effective problem solver and clear thinker. Proven analytical and organizational ability. Project Management Professional (PMP) Certification."
Skills: maybe overlapping with desired characteristics; but we could treat desired characteristics as Skills. However we already used Qualifications for desired characteristics. Could separate: Qualifications = education/experience? But we already used Requirements for education/experience. Let's think: Usually Requirements = mandatory qualifications; Qualifications = preferred qualifications; Skills = specific abilities. But we have both mandatory and desired. We could assign:
- Requirements: Bachelor’s degree, 5 years experience, US Person status.
- Qualifications: Experience in leading technical programs in Aerospace industry, PMP Certification.
- Skills: Strong oral/written communication, interpersonal/leadership, ability to influence, coordinate several projects, problem solver, analytical/organizational ability.
But the instruction says prefer a few substantive sections over many thin ones. So maybe combine desired characteristics and skills into one "Skills" section. But we need to keep all info.
We could have:
- Requirements (mandatory)
- Qualifications (desired)
- Skills (maybe not needed if we combine). But we could omit Skills and put desired characteristics under Qualifications. However Qualifications heading is allowed; we can put both experience and PMP and soft skills there. That would be okay.
Thus:
- About the role
- Responsibilities
- Requirements
- Qualifications
- Benefits
- Pay
We must not include Schedule.
Now Benefits block: "At ST Engineering, we offer great rewards, competitive pay, career advancement and growth opportunities. Estimate salary range for this role: $92,000 to $138,100 per year. ST Engineering considers several factors with extending job offers, including but not limited to candidates’ key skills, relevant work experience, education/training/certification, job level, and work location. Base salary is only one component of our competitive Total Rewards package. ST Engineering - MRAS Benefits As a full-time employee of ST Engineering- MRAS, you are eligible for our benefits package including: Medical, Dental, and Vision coverage starting from start date Health Flexible Spending Accounts Free Onsite Gym with weekly fitness classes Immediate 401k vesting!!! Educational Assistance Life Insurance Paid Time off (Permissive for exempt staff)"
We need to separate Pay and Benefits. Pay: salary range. Benefits: list.
Thus:
Pay: "Estimate salary range for this role: $92,000 to $138,100 per year." Also maybe mention that base salary is one component of total rewards, but that's more about benefits. We'll keep Pay as salary range.
Benefits: list items.
Now we need to remove boilerplate: The sections about Employment Notice: Background and Drug Screening Requirements, EEO statement, accommodation request, etc. Those are boilerplate; remove them.
Also remove duplicated lines: maybe "At ST Engineering, we offer great rewards..." appears also later? We'll keep only once.
Now craft HTML.
We'll output:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical but not exclusive? It says "e.g." meaning examples. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create other headings if needed, but they gave examples. Safer to stick to those headings; we can put company info under "About the role" maybe as part of role context. But that might dilute.
Better: Use "About the role" for the description of what you would be doing (the first block). Use "Responsibilities" for the "What YOU Will Do" block. Use "Requirements" for the "What YOU Must Bring To Succeed" block (education, experience, US person). Use "Qualifications" maybe for desired characteristics? Or we could split: Requirements = mandatory; Qualifications = desired. Skills = maybe desired characteristics like leadership, communication, etc. Benefits = benefits block. Pay = salary range. Schedule = not mentioned; we should not create Schedule section if no info.
We must not create sections with filler like "not specified". So we omit Schedule.
Now extract content:
About the role: "Who YOU Are And What YOU Can Become You would be leading the engineering team and managing new and existing Nacelle and Engine Build Up programs. It includes providing leadership and coordination of the engineering team assigned to the programs to support new designs and improving existing designs. You would be providing support for internal investigations of field issues and determining if design changes can provide relief for certain supply chain challenges are also part of the job. In addition, you would be interfacing with customers and internal senior staff."
We need to preserve all substantive information. Could split into sentences.
Responsibilities: "What YOU Will Do Responsible for developing and managing cross-functional product focused programs. Manages the project and interfaces with partners, contractors, suppliers, customers and internal functions. Manages program resource and budget allocation/integration. Engineering lead and focal for the program. Responsible for the planning and execution of all Engineering deliverables to support qualification, certification, and production of Nacelle hardware to agree technical specifications, schedule, and budget. Develops, maintains, and communicates; priorities and executable plans for a diverse domestic and global team to support internal business and Customer requirements. Supports monthly Engineering Operations reviews with variance assessments, corrective action, updated Forecast (budget and resource), key risks/abatements, and help needed. Manage an integrated master schedule (IMS) with inputs from the team and provide assessment of multiple critical path(s). Develop action plans with guidance to respond to issues/problems."
Requirements (mandatory): "What YOU Must Bring To Succeed Bachelor’s degree in engineering or equivalent technical degree from an accredited university or college. Minimum of 5 years of engineering work experience. This position involves access to export-controlled technology which requires U.S. Person status or government authorization. A ‘U.S. Person,’ as defined by 22 C.F.R.120.62, includes U.S. citizens, U.S. nationals, individuals lawfully admitted for permanent residence (green card holders), and individuals granted asylum or refugee status in the United States. To be considered for this position, you must either be a U.S. Person or fall within a legally recognized export control exception or authorization. If hired, you will be required to provide valid proof of such status."
Qualifications (desired): "Desired Characteristics Experience in leading technical programs in the Aerospace industry. Strong oral and written communication skills. Strong interpersonal and leadership skills. Ability to influence others and lead small teams. Ability to coordinate several projects simultaneously. Effective problem solver and clear thinker. Proven analytical and organizational ability. Project Management Professional (PMP) Certification."
Skills: maybe overlapping with desired characteristics; but we could treat desired characteristics as Skills. However we already used Qualifications for desired characteristics. Could separate: Qualifications = education/experience? But we already used Requirements for education/experience. Let's think: Usually Requirements = mandatory qualifications; Qualifications = preferred qualifications; Skills = specific abilities. But we have both mandatory and desired. We could assign:
- Requirements: Bachelor’s degree, 5 years experience, US Person status.
- Qualifications: Experience in leading technical programs in Aerospace industry, PMP Certification.
- Skills: Strong oral/written communication, interpersonal/leadership, ability to influence, coordinate several projects, problem solver, analytical/organizational ability.
But the instruction says prefer a few substantive sections over many thin ones. So maybe combine desired characteristics and skills into one "Skills" section. But we need to keep all info.
We could have:
- Requirements (mandatory)
- Qualifications (desired)
- Skills (maybe not needed if we combine). But we could omit Skills and put desired characteristics under Qualifications. However Qualifications heading is allowed; we can put both experience and PMP and soft skills there. That would be okay.
Thus:
- About the role
- Responsibilities
- Requirements
- Qualifications
- Benefits
- Pay
We must not include Schedule.
Now Benefits block: "At ST Engineering, we offer great rewards, competitive pay, career advancement and growth opportunities. Estimate salary range for this role: $92,000 to $138,100 per year. ST Engineering considers several factors with extending job offers, including but not limited to candidates’ key skills, relevant work experience, education/training/certification, job level, and work location. Base salary is only one component of our competitive Total Rewards package. ST Engineering - MRAS Benefits As a full-time employee of ST Engineering- MRAS, you are eligible for our benefits package including: Medical, Dental, and Vision coverage starting from start date Health Flexible Spending Accounts Free Onsite Gym with weekly fitness classes Immediate 401k vesting!!! Educational Assistance Life Insurance Paid Time off (Permissive for exempt staff)"
We need to separate Pay and Benefits. Pay: salary range. Benefits: list.
Thus:
Pay: "Estimate salary range for this role: $92,000 to $138,100 per year." Also maybe mention that base salary is one component of total rewards, but that's more about benefits. We'll keep Pay as salary range.
Benefits: list items.
Now we need to remove boilerplate: The sections about Employment Notice: Background and Drug Screening Requirements, EEO statement, accommodation request, etc. Those are boilerplate; remove them.
Also remove duplicated lines: maybe "At ST Engineering, we offer great rewards..." appears also later? We'll keep only once.
Now craft HTML.
We'll output:
About the role
...
Responsibilities
- ... each responsibility as li
with salary range. Make sure not to include extra whitespace? It's fine. Now extract each bullet. Responsibilities bullet list: - Responsible for developing and managing cross-functional product focused programs. - Manages the project and interfaces with partners, contractors, suppliers, customers and internal functions. - Manages program resource and budget allocation/integration. - Engineering lead and focal for the program. - Responsible for the planning and execution of all Engineering deliverables to support qualification, certification, and production of Nacelle hardware to agree technical specifications, schedule, and budget. - Develops, maintains, and communicates priorities and executable plans for a diverse domestic and global team to support internal business and Customer requirements. - Supports monthly Engineering Operations reviews with variance assessments, corrective action, updated Forecast (budget and resource), key risks/abatements, and help needed. - Manage an integrated master schedule (IMS) with inputs from the team and provide assessment of multiple critical path(s). - Develop action plans with guidance to respond to issues/problems. We need to keep the semicolon after "Develops, maintains, and communicates;" maybe keep as is. Requirements bullet list: - Bachelor’s degree in engineering or equivalent technical degree from an accredited university or college. - Minimum of 5 years of engineering work experience. - Must be a U.S. Person (as defined by 22 C.F.R.120.62: U.S. citizens, U.S. nationals, lawful permanent residents (green card holders), individuals granted asylum or refugee status) or have a legally recognized export control exception/authorization. - If hired, must provide valid proof of such status. We could combine the US Person description. Qualifications bullet list (desired): - Experience in leading technical programs in the Aerospace industry. - Strong oral and written communication skills. - Strong interpersonal and leadership skills. - Ability to influence others and lead small teams. - Ability to coordinate several projects simultaneously. - Effective problem solver and clear thinker. - Proven analytical and organizational ability. - Project Management Professional (PMP) Certification. We could also include "Experience in leading technical programs in the Aerospace industry" as qualification. Now Benefits bullet list: - Medical, Dental, and Vision coverage starting from start date - Health Flexible Spending Accounts - Free Onsite Gym with weekly fitness classes - Immediate 401k vesting - Educational Assistance - Life Insurance - Paid Time off (Permissive for exempt staff) We might keep the exclamation marks? Remove excessive punctuation? Keep as is but maybe remove multiple exclamation marks. We'll keep "Immediate 401k vesting". Pay:
Estimated salary range: $92,000 to $138,100 per year.
Now About the role paragraph: combine sentences. Let's craft:You would be leading the engineering team and managing new and existing Nacelle and Engine Build Up programs, providing leadership and coordination of the engineering team assigned to the programs to support new designs and improving existing designs. You would also provide support for internal investigations of field issues and determine if design changes can relieve certain supply chain challenges, and interface with customers and internal senior staff.
Now ensure we didn't miss any substantive info: The company description "Who WE Are And Where WE Are Going" we omitted. That is substantive info about the company. We need to preserve ALL substantive information. So we must include it somewhere. Since we don't have a heading for company, we could incorporate it into "About the role" as a brief intro about the company