Senior Project Lead (Onsite)
or drop it." So we can include a short paragraph with location, role type, citizenship requirement, etc. - About the role: The paragraph after "At RTX, the world's largest aerospace..." maybe qualifies as About the role. Also the description of Pratt & Whitney and the role. - Responsibilities: The bullet list under "What You Will Do:" includes multiple items. - What You Will Learn: Could be considered as "Learning Opportunities" maybe not a standard heading; but we could treat as part of Responsibilities? Probably better to have a section "What You Will Learn" but not in allowed headings list. The allowed headings are limited to those listed; we should not create other headings. So we should incorporate that content into existing sections like Responsibilities or Qualifications? 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 only use those headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings only. So we need to map content to those sections.
Thus:
- About the role: introductory paragraph about RTX, Pratt & Whitney, role description.
- Responsibilities: the "What You Will Do:" bullet list.
- Requirements: maybe the citizenship requirement and security clearance? Also "U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required..." plus maybe "Security Clearance Type: None/Not Required". Could be under Requirements.
- Qualifications: the "Qualifications You Must Have:" and "Qualifications We Prefer:" bullet lists.
- Skills: maybe we can extract from preferred qualifications: leadership, communication, etc. But we could also put those under Qualifications. However we need to decide if we need a Skills section. The posting includes skills like "Strong customer- and supplier-facing communication skills", "Experience with continuous improvement methodologies", "PMP certification preferred". Could be placed under Qualifications or Skills. Since we have a Qualifications section already, we could put all qualification content there, and maybe not need a separate Skills section unless there is distinct skill content not covered. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine Skills into Qualifications if needed.
- Benefits: The posting includes "What We Offer: Eligible for Relocation." plus later benefits list: medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays. Also incentive compensation programs. So we have benefits content.
- Pay: The posting includes salary range: "The salary range for this role is 86,800 USD - 165,200 USD." Also mention about incentive compensation. So we have Pay.
- Schedule: Not explicitly mentioned; maybe "flexible work schedules" is a benefit, not schedule. No explicit schedule like full-time, part-time. So we should not create a Schedule section.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate like EEO, legal, privacy, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Learn More & Apply Now!" etc. Also remove "Department / Segment Overview:" maybe we can incorporate into About the role? It's substantive about the organization; we could include it in About the role.
We need to ensure we don't include filler like "commensurate with experience" etc. Not present.
Now craft HTML.
We'll start with a short paragraph for metadata: maybe include location, role type, citizenship requirement. But we could fold that into About the role or Requirements. Since citizenship requirement is a requirement, we can put it under Requirements. Location and role type could be a short paragraph before sections? The instruction says fold minor metadata into a short
or drop it. So we can add a
at top: "Location: US-CT-EAST HARTFORD-ETC ~ 400 Main St ~ BLDG ETC. Position Role Type: Onsite. U.S. citizenship required." That's minor metadata.
Then sections.
Let's extract content precisely.
About the role: Combine the paragraphs:
"At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Pratt & Whitney is a world leader in the design, manufacture and service of aircraft engines and auxiliary power systems and has been revolutionizing modern flight for over 100 years. Join us and help shape the future of aerospace and defense. Pratt & Whitney is seeking a highly motivated and experienced engineer for a Senior Project Engineer position within our Mechanical Systems, Externals and Nacelles (MSEN) organization, supporting our GTF (Geared Turbofan) Externals Component Integrated Product Teams (CIPTs). In this role, you will have part-level ownership of CIPT task planning and execution, ensuring component goals are achieved in accordance with program requirements. You will have direct interface opportunities with engineering and program management, suppliers, and customers. The successful candidate will be customer-focused, technically proficient, and able to effectively lead and communicate across functions to meet the demands of Next Generation Programs Family (NGPF) engine programs."
Also we could include the Department / Segment Overview paragraph: "Mechanical Systems, Externals, & Nacelles (MSEN): The MSEN Engineering organization is responsible for the design, development, and in-service support of power transmission systems, bearing compartment and rotor support design and analysis, oil and thermal management systems, engine externals packaging and architecture, as well as nacelles for commercial and military engine models. Technical disciplines include Project Engineering, Mechanical Design, Structural Analysis, Product Definition, System Modeling, Mechanical Design analysis for bearings, gears, and seals, and fluid-thermal modeling of associated components and systems."
That is substantive; we can include in About the role.
Now Responsibilities: bullet list from "What You Will Do:":
- Own part-level execution within the Externals CIPT, including task planning, communication, risk management, and execution to program requirements.
- Lead the identification, mitigation, and closure of key technical risks and issues to support component objectives.
- Prepare for and participate in technical and program reviews, ensuring technical content, actions, and metrics are effectively communicated.
- Monitor and support Integrated Product Teams (IPTs) budget, schedule, technical performance, and business metrics to achieve program commitments.
- Interface with customers, suppliers, System Integrated Product Teams (SIPTs), Integrated Program Management Teams (IPMTs), engineering and program management, and senior leadership through technical discussions and presentations.
- Provide technical support for validation engine builds and engine test activities.
Also maybe include Travel Requirement: Up to 10% (Domestic and International). That could be a responsibility or a note; but it's not a duty. Could be placed under Responsibilities as a bullet? It's not a duty but a requirement. Could be placed under Requirements? Probably better as a separate bullet under Responsibilities? The instruction: Use
- for any list of duties/requirements/benefits. Travel requirement is a requirement, but we could put under Requirements. However we already have Requirements section for citizenship etc. We could add travel requirement there. But we could also add as a bullet under Responsibilities? Might be okay. I'd put under Requirements as a bullet.
Now Requirements: include:
- U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.
- Security Clearance Type: None/Not Required (maybe we can note that no clearance required).
- Travel Requirement: Up to 10% (Domestic and International).
Also maybe include "Position Role Type: Onsite" but that's metadata.
We'll keep Requirements as those.
Now Qualifications: Must Have and Preferred.
We need to preserve all detail.
Must Have:
- Bachelor’s degree in Science, Technology, Engineering, or Mathematics (STEM) and 5 years of relevant experience, or an advanced degree and 3 years of relevant experience.
- Relevant experience in engineering, aerospace, aviation, manufacturing, or a related technical industry.
Preferred:
- Degree in Mechanical or Aerospace Engineering with aerospace and/or turbofan engine industry experience.
- Experience across product lifecycle activities, including design, manufacturing, development, validation, entry into service, and/or field service support.
- Demonstrated ability to lead, influence, and coordinate across cross-functional teams, including experience managing technical risks, schedules, budgets, and strategic projects.
- Strong customer- and supplier-facing communication skills, with the ability to present technical information and simplify complex topics; willingness to mentor and provide technical guidance to junior engineers.
- Experience with continuous improvement methodologies such as Lean, CORE, ACE, or Six Sigma, and/or project management tools and systems such as Microsoft Office, Solumina, SAP, Teamcenter, or Agile frameworks; PMP certification preferred.
We could also include "Learn More & Apply Now!" but that's application instruction, drop.
Now Benefits: list from "What We Offer:" and later benefits.
What We Offer: "Eligible for Relocation." That's a benefit.
Later: "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays."
Also incentive compensation: "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company’s performance."
We'll include those as benefits.
Now Pay: Salary range: "The salary range for this role is 86,800 USD - 165,200 USD. The salary range provided is a good faith estimate representative of all experience levels. RTX considers several factors when extending an offer, including but not limited to, the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills."
We'll include that.
Now we need to ensure we don't repeat content.
Let's craft HTML.
Start with a
for metadata: maybe "Location: US-CT-EAST HARTFORD-ETC ~ 400 Main St ~ BLDG ETC. Position Role Type: Onsite. U.S. citizenship required."
Then sections.
We'll output:
About the role
...
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate like EEO, legal, privacy, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Learn More & Apply Now!" etc. Also remove "Department / Segment Overview:" maybe we can incorporate into About the role? It's substantive about the organization; we could include it in About the role.
We need to ensure we don't include filler like "commensurate with experience" etc. Not present.
Now craft HTML.
We'll start with a short paragraph for metadata: maybe include location, role type, citizenship requirement. But we could fold that into About the role or Requirements. Since citizenship requirement is a requirement, we can put it under Requirements. Location and role type could be a short paragraph before sections? The instruction says fold minor metadata into a short
or drop it. So we can add a
at top: "Location: US-CT-EAST HARTFORD-ETC ~ 400 Main St ~ BLDG ETC. Position Role Type: Onsite. U.S. citizenship required." That's minor metadata.
Then sections.
Let's extract content precisely.
About the role: Combine the paragraphs:
"At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Pratt & Whitney is a world leader in the design, manufacture and service of aircraft engines and auxiliary power systems and has been revolutionizing modern flight for over 100 years. Join us and help shape the future of aerospace and defense. Pratt & Whitney is seeking a highly motivated and experienced engineer for a Senior Project Engineer position within our Mechanical Systems, Externals and Nacelles (MSEN) organization, supporting our GTF (Geared Turbofan) Externals Component Integrated Product Teams (CIPTs). In this role, you will have part-level ownership of CIPT task planning and execution, ensuring component goals are achieved in accordance with program requirements. You will have direct interface opportunities with engineering and program management, suppliers, and customers. The successful candidate will be customer-focused, technically proficient, and able to effectively lead and communicate across functions to meet the demands of Next Generation Programs Family (NGPF) engine programs."
Also we could include the Department / Segment Overview paragraph: "Mechanical Systems, Externals, & Nacelles (MSEN): The MSEN Engineering organization is responsible for the design, development, and in-service support of power transmission systems, bearing compartment and rotor support design and analysis, oil and thermal management systems, engine externals packaging and architecture, as well as nacelles for commercial and military engine models. Technical disciplines include Project Engineering, Mechanical Design, Structural Analysis, Product Definition, System Modeling, Mechanical Design analysis for bearings, gears, and seals, and fluid-thermal modeling of associated components and systems."
That is substantive; we can include in About the role.
Now Responsibilities: bullet list from "What You Will Do:":
- Own part-level execution within the Externals CIPT, including task planning, communication, risk management, and execution to program requirements.
- Lead the identification, mitigation, and closure of key technical risks and issues to support component objectives.
- Prepare for and participate in technical and program reviews, ensuring technical content, actions, and metrics are effectively communicated.
- Monitor and support Integrated Product Teams (IPTs) budget, schedule, technical performance, and business metrics to achieve program commitments.
- Interface with customers, suppliers, System Integrated Product Teams (SIPTs), Integrated Program Management Teams (IPMTs), engineering and program management, and senior leadership through technical discussions and presentations.
- Provide technical support for validation engine builds and engine test activities.
Also maybe include Travel Requirement: Up to 10% (Domestic and International). That could be a responsibility or a note; but it's not a duty. Could be placed under Responsibilities as a bullet? It's not a duty but a requirement. Could be placed under Requirements? Probably better as a separate bullet under Responsibilities? The instruction: Use
- for any list of duties/requirements/benefits. Travel requirement is a requirement, but we could put under Requirements. However we already have Requirements section for citizenship etc. We could add travel requirement there. But we could also add as a bullet under Responsibilities? Might be okay. I'd put under Requirements as a bullet.
Now Requirements: include:
- U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.
- Security Clearance Type: None/Not Required (maybe we can note that no clearance required).
- Travel Requirement: Up to 10% (Domestic and International).
Also maybe include "Position Role Type: Onsite" but that's metadata.
We'll keep Requirements as those.
Now Qualifications: Must Have and Preferred.
We need to preserve all detail.
Must Have:
- Bachelor’s degree in Science, Technology, Engineering, or Mathematics (STEM) and 5 years of relevant experience, or an advanced degree and 3 years of relevant experience.
- Relevant experience in engineering, aerospace, aviation, manufacturing, or a related technical industry.
Preferred:
- Degree in Mechanical or Aerospace Engineering with aerospace and/or turbofan engine industry experience.
- Experience across product lifecycle activities, including design, manufacturing, development, validation, entry into service, and/or field service support.
- Demonstrated ability to lead, influence, and coordinate across cross-functional teams, including experience managing technical risks, schedules, budgets, and strategic projects.
- Strong customer- and supplier-facing communication skills, with the ability to present technical information and simplify complex topics; willingness to mentor and provide technical guidance to junior engineers.
- Experience with continuous improvement methodologies such as Lean, CORE, ACE, or Six Sigma, and/or project management tools and systems such as Microsoft Office, Solumina, SAP, Teamcenter, or Agile frameworks; PMP certification preferred.
We could also include "Learn More & Apply Now!" but that's application instruction, drop.
Now Benefits: list from "What We Offer:" and later benefits.
What We Offer: "Eligible for Relocation." That's a benefit.
Later: "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays."
Also incentive compensation: "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company’s performance."
We'll include those as benefits.
Now Pay: Salary range: "The salary range for this role is 86,800 USD - 165,200 USD. The salary range provided is a good faith estimate representative of all experience levels. RTX considers several factors when extending an offer, including but not limited to, the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills."
We'll include that.
Now we need to ensure we don't repeat content.
Let's craft HTML.
Start with a
for metadata: maybe "Location: US-CT-EAST HARTFORD-ETC ~ 400 Main St ~ BLDG ETC. Position Role Type: Onsite. U.S. citizenship required."
Then sections.
We'll output:
About the role
...
for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate like EEO, legal, privacy, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Learn More & Apply Now!" etc. Also remove "Department / Segment Overview:" maybe we can incorporate into About the role? It's substantive about the organization; we could include it in About the role. We need to ensure we don't include filler like "commensurate with experience" etc. Not present. Now craft HTML. We'll start with a short paragraph for metadata: maybe include location, role type, citizenship requirement. But we could fold that into About the role or Requirements. Since citizenship requirement is a requirement, we can put it under Requirements. Location and role type could be a short paragraph before sections? The instruction says fold minor metadata into a short
or drop it. So we can add a
at top: "Location: US-CT-EAST HARTFORD-ETC ~ 400 Main St ~ BLDG ETC. Position Role Type: Onsite. U.S. citizenship required." That's minor metadata. Then sections. Let's extract content precisely. About the role: Combine the paragraphs: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Pratt & Whitney is a world leader in the design, manufacture and service of aircraft engines and auxiliary power systems and has been revolutionizing modern flight for over 100 years. Join us and help shape the future of aerospace and defense. Pratt & Whitney is seeking a highly motivated and experienced engineer for a Senior Project Engineer position within our Mechanical Systems, Externals and Nacelles (MSEN) organization, supporting our GTF (Geared Turbofan) Externals Component Integrated Product Teams (CIPTs). In this role, you will have part-level ownership of CIPT task planning and execution, ensuring component goals are achieved in accordance with program requirements. You will have direct interface opportunities with engineering and program management, suppliers, and customers. The successful candidate will be customer-focused, technically proficient, and able to effectively lead and communicate across functions to meet the demands of Next Generation Programs Family (NGPF) engine programs." Also we could include the Department / Segment Overview paragraph: "Mechanical Systems, Externals, & Nacelles (MSEN): The MSEN Engineering organization is responsible for the design, development, and in-service support of power transmission systems, bearing compartment and rotor support design and analysis, oil and thermal management systems, engine externals packaging and architecture, as well as nacelles for commercial and military engine models. Technical disciplines include Project Engineering, Mechanical Design, Structural Analysis, Product Definition, System Modeling, Mechanical Design analysis for bearings, gears, and seals, and fluid-thermal modeling of associated components and systems." That is substantive; we can include in About the role. Now Responsibilities: bullet list from "What You Will Do:": - Own part-level execution within the Externals CIPT, including task planning, communication, risk management, and execution to program requirements. - Lead the identification, mitigation, and closure of key technical risks and issues to support component objectives. - Prepare for and participate in technical and program reviews, ensuring technical content, actions, and metrics are effectively communicated. - Monitor and support Integrated Product Teams (IPTs) budget, schedule, technical performance, and business metrics to achieve program commitments. - Interface with customers, suppliers, System Integrated Product Teams (SIPTs), Integrated Program Management Teams (IPMTs), engineering and program management, and senior leadership through technical discussions and presentations. - Provide technical support for validation engine builds and engine test activities. Also maybe include Travel Requirement: Up to 10% (Domestic and International). That could be a responsibility or a note; but it's not a duty. Could be placed under Responsibilities as a bullet? It's not a duty but a requirement. Could be placed under Requirements? Probably better as a separate bullet under Responsibilities? The instruction: Use
- for any list of duties/requirements/benefits. Travel requirement is a requirement, but we could put under Requirements. However we already have Requirements section for citizenship etc. We could add travel requirement there. But we could also add as a bullet under Responsibilities? Might be okay. I'd put under Requirements as a bullet.
Now Requirements: include:
- U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.
- Security Clearance Type: None/Not Required (maybe we can note that no clearance required).
- Travel Requirement: Up to 10% (Domestic and International).
Also maybe include "Position Role Type: Onsite" but that's metadata.
We'll keep Requirements as those.
Now Qualifications: Must Have and Preferred.
We need to preserve all detail.
Must Have:
- Bachelor’s degree in Science, Technology, Engineering, or Mathematics (STEM) and 5 years of relevant experience, or an advanced degree and 3 years of relevant experience.
- Relevant experience in engineering, aerospace, aviation, manufacturing, or a related technical industry.
Preferred:
- Degree in Mechanical or Aerospace Engineering with aerospace and/or turbofan engine industry experience.
- Experience across product lifecycle activities, including design, manufacturing, development, validation, entry into service, and/or field service support.
- Demonstrated ability to lead, influence, and coordinate across cross-functional teams, including experience managing technical risks, schedules, budgets, and strategic projects.
- Strong customer- and supplier-facing communication skills, with the ability to present technical information and simplify complex topics; willingness to mentor and provide technical guidance to junior engineers.
- Experience with continuous improvement methodologies such as Lean, CORE, ACE, or Six Sigma, and/or project management tools and systems such as Microsoft Office, Solumina, SAP, Teamcenter, or Agile frameworks; PMP certification preferred.
We could also include "Learn More & Apply Now!" but that's application instruction, drop.
Now Benefits: list from "What We Offer:" and later benefits.
What We Offer: "Eligible for Relocation." That's a benefit.
Later: "Hired applicants may be eligible for benefits, including but not limited to, medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, and holidays."
Also incentive compensation: "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company’s performance."
We'll include those as benefits.
Now Pay: Salary range: "The salary range for this role is 86,800 USD - 165,200 USD. The salary range provided is a good faith estimate representative of all experience levels. RTX considers several factors when extending an offer, including but not limited to, the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills."
We'll include that.
Now we need to ensure we don't repeat content.
Let's craft HTML.
Start with a
for metadata: maybe "Location: US-CT-EAST HARTFORD-ETC ~ 400 Main St ~ BLDG ETC. Position Role Type: Onsite. U.S. citizenship required." Then sections. We'll output:
About the role
...