CSMC Advanced Engine Design (Onsite)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. So we need to keep details like responsibilities list, qualifications, etc.
Let's extract sections:
- About the role: maybe combine intro paragraph about RTX and Pratt & Whitney and mission. Could be "About the role" or "About the company". We'll use "About the role". Content: paragraphs describing RTX, Pratt & Whitney, mission, join us.
- Responsibilities: "What You Will Do" bullet list? It's a paragraph with sentences. Could break into list? The instruction: use
- for any list of duties/requirements/benefits. If it's not a list but prose, we can keep as
. But we can also convert sentences into list items if they are distinct duties. The text: "Sound mechanical engineering across all phases of the design cycle, with focus on Concept Initiation and Optimization and rig/demo hardware designs. Mechanical engineering across a variety of part types (static and rotating) and compressor modules. Tasks will include integration of detail components into functioning modules and engine systems. Resolution of mechanical engineering problems of difficult and complex scope, seeking a balanced system solution, ensuring engineering excellence, while providing oversight of execution. Clear communication with all levels of the organization. Coordination of product definition data - layouts, sketches, and notes necessary to present design proposals and mfg. Involvement in generation of Intellectual Property (IP) patents. Establish new concepts and the defining of rigs and applications to validate and utilize them. Viable candidates must have relevant design background or experience in these areas and possess the skills and motivation to bring new ideas into practice."
We could treat each sentence as a duty item. Use
- . That seems appropriate.
- What You Will Learn: maybe could be part of About the role or separate section? Could be "What You Will Learn" but not a standard heading; we could incorporate into About the role or maybe "Learning Opportunities". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those. "What You Will Learn" could go under About the role or maybe under Qualifications? Probably About the role.
- Qualifications You Must Have: that's Requirements. So Requirements section.
- Qualifications We Prefer: that's Qualifications section (preferred). Could also include Skills? There's also "Proficiency in Teamcenter, Unigraphics, Ansys, and classical “hand” methods of analysis." etc. That's skills. Could put under Skills section. But we have both Qualifications and Skills headings allowed. We'll put required qualifications under Requirements, preferred qualifications under Qualifications, and specific technical proficiencies under Skills.
- Benefits: What We Offer includes relocation eligibility? Actually "Relocation Eligibility Learn More & Apply Now!" then description of CSE. Then benefits list. We'll extract benefits list.
- Pay: salary range.
- Schedule: not present, omit.
We must not include filler like "commensurate with experience". Not present.
We must not repeat job title.
We must not include metadata like Date Posted, Country, Location, Position Role Type, etc. Could fold minor metadata into short p or drop. Probably drop.
We must remove boilerplate: EEO, privacy, etc.
Now craft HTML.
Structure:
About the role
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.
Maybe also include "What You Will Learn" content as part of About the role? Could add another paragraph: "The Compression Systems Engineering (CSE) Advanced Engine Programs (AEP) Mechanical Design team is seeking mechanical engineering professionals to join our team. AEP is a dynamic and exciting environment. Unlike most other groups in the organization, AEP covers all Fan & Compressor hardware from nosecone/spinner to entrance to diffuser. Our work encompasses both commercial and military/government projects, leveraging insights from both sectors to drive innovation and improvements at Pratt & Whitney. An AEP role will help you better understand the considerations, trades and complexities that go into technology development and new product type definition. Role will provide the opportunity to shape the engine architecture of the future. This is a Technology group, whereby definition, new design standards are explored and defined. Assignments are challenging and open for innovation and creativity."
We'll add as another .
Then Responsibilities:
Responsibilities
- Sound mechanical engineering across all phases of the design cycle, with focus on Concept Initiation and Optimization and rig/demo hardware designs.
- Mechanical engineering across a variety of part types (static and rotating) and compressor modules.
- Tasks will include integration of detail components into functioning modules and engine systems.
- Resolution of mechanical engineering problems of difficult and complex scope, seeking a balanced system solution, ensuring engineering excellence, while providing oversight of execution.
- Clear communication with all levels of the organization.
- Coordination of product definition data - layouts, sketches, and notes necessary to present design proposals and mfg.
- Involvement in generation of Intellectual Property (IP) patents.
- Establish new concepts and the defining of rigs and applications to validate and utilize them.
Note: The last sentence about viable candidates is more a requirement; we could move to Requirements. But it's part of responsibilities paragraph. We'll keep it as responsibility? It says "Viable candidates must have relevant design background or experience in these areas and possess the skills and motivation to bring new ideas into practice." That's a requirement. Might be better to put under Requirements. But we already have Requirements section. We'll move that sentence to Requirements.
Thus responsibilities list ends before that sentence.
Now Requirements:
Requirements
- B.S. in Mechanical or Aerospace engineering with 5+ years of Mechanical Design engineering experience
- OR an Advanced Degree with 3+ years of in a related field with engineering experience.
- U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.
- Viable candidates must have relevant design background or experience in these areas and possess the skills and motivation to bring new ideas into practice.
But note: The "Viable candidates must have relevant design background..." we already used. Might be duplicate. Could keep.
Now Qualifications (preferred):
Qualifications
- M.S. or greater in Mechanical or Aerospace engineering.
- Proficiency in Teamcenter, Unigraphics, Ansys, and classical “hand” methods of analysis.
- Active US government security clearance or the ability to obtain one.
- Excellent communication and interpersonal skills.
- Understanding of hardware, blueprints, dimensions & tolerances, and manufacturing methods.
- Turbomachinery experience.
- Rotating hardware experience.
Skills
for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to keep details like responsibilities list, qualifications, etc. Let's extract sections: - About the role: maybe combine intro paragraph about RTX and Pratt & Whitney and mission. Could be "About the role" or "About the company". We'll use "About the role". Content: paragraphs describing RTX, Pratt & Whitney, mission, join us. - Responsibilities: "What You Will Do" bullet list? It's a paragraph with sentences. Could break into list? The instruction: use
- for any list of duties/requirements/benefits. If it's not a list but prose, we can keep as
. But we can also convert sentences into list items if they are distinct duties. The text: "Sound mechanical engineering across all phases of the design cycle, with focus on Concept Initiation and Optimization and rig/demo hardware designs. Mechanical engineering across a variety of part types (static and rotating) and compressor modules. Tasks will include integration of detail components into functioning modules and engine systems. Resolution of mechanical engineering problems of difficult and complex scope, seeking a balanced system solution, ensuring engineering excellence, while providing oversight of execution. Clear communication with all levels of the organization. Coordination of product definition data - layouts, sketches, and notes necessary to present design proposals and mfg. Involvement in generation of Intellectual Property (IP) patents. Establish new concepts and the defining of rigs and applications to validate and utilize them. Viable candidates must have relevant design background or experience in these areas and possess the skills and motivation to bring new ideas into practice." We could treat each sentence as a duty item. Use
- . That seems appropriate.
- What You Will Learn: maybe could be part of About the role or separate section? Could be "What You Will Learn" but not a standard heading; we could incorporate into About the role or maybe "Learning Opportunities". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those. "What You Will Learn" could go under About the role or maybe under Qualifications? Probably About the role.
- Qualifications You Must Have: that's Requirements. So Requirements section.
- Qualifications We Prefer: that's Qualifications section (preferred). Could also include Skills? There's also "Proficiency in Teamcenter, Unigraphics, Ansys, and classical “hand” methods of analysis." etc. That's skills. Could put under Skills section. But we have both Qualifications and Skills headings allowed. We'll put required qualifications under Requirements, preferred qualifications under Qualifications, and specific technical proficiencies under Skills.
- Benefits: What We Offer includes relocation eligibility? Actually "Relocation Eligibility Learn More & Apply Now!" then description of CSE. Then benefits list. We'll extract benefits list.
- Pay: salary range.
- Schedule: not present, omit.
We must not include filler like "commensurate with experience". Not present.
We must not repeat job title.
We must not include metadata like Date Posted, Country, Location, Position Role Type, etc. Could fold minor metadata into short p or drop. Probably drop.
We must remove boilerplate: EEO, privacy, etc.
Now craft HTML.
Structure:
About the role
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.
Maybe also include "What You Will Learn" content as part of About the role? Could add another paragraph: "The Compression Systems Engineering (CSE) Advanced Engine Programs (AEP) Mechanical Design team is seeking mechanical engineering professionals to join our team. AEP is a dynamic and exciting environment. Unlike most other groups in the organization, AEP covers all Fan & Compressor hardware from nosecone/spinner to entrance to diffuser. Our work encompasses both commercial and military/government projects, leveraging insights from both sectors to drive innovation and improvements at Pratt & Whitney. An AEP role will help you better understand the considerations, trades and complexities that go into technology development and new product type definition. Role will provide the opportunity to shape the engine architecture of the future. This is a Technology group, whereby definition, new design standards are explored and defined. Assignments are challenging and open for innovation and creativity." We'll add as another. Then Responsibilities:
Responsibilities
- Sound mechanical engineering across all phases of the design cycle, with focus on Concept Initiation and Optimization and rig/demo hardware designs.
- Mechanical engineering across a variety of part types (static and rotating) and compressor modules.
- Tasks will include integration of detail components into functioning modules and engine systems.
- Resolution of mechanical engineering problems of difficult and complex scope, seeking a balanced system solution, ensuring engineering excellence, while providing oversight of execution.
- Clear communication with all levels of the organization.
- Coordination of product definition data - layouts, sketches, and notes necessary to present design proposals and mfg.
- Involvement in generation of Intellectual Property (IP) patents.
- Establish new concepts and the defining of rigs and applications to validate and utilize them.
Requirements
- B.S. in Mechanical or Aerospace engineering with 5+ years of Mechanical Design engineering experience
- OR an Advanced Degree with 3+ years of in a related field with engineering experience.
- U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract.
- Viable candidates must have relevant design background or experience in these areas and possess the skills and motivation to bring new ideas into practice.
Qualifications
- M.S. or greater in Mechanical or Aerospace engineering.
- Proficiency in Teamcenter, Unigraphics, Ansys, and classical “hand” methods of analysis.
- Active US government security clearance or the ability to obtain one.
- Excellent communication and interpersonal skills.
- Understanding of hardware, blueprints, dimensions & tolerances, and manufacturing methods.
- Turbomachinery experience.
- Rotating hardware experience. Skills
- . That seems appropriate.
- What You Will Learn: maybe could be part of About the role or separate section? Could be "What You Will Learn" but not a standard heading; we could incorporate into About the role or maybe "Learning Opportunities". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those. "What You Will Learn" could go under About the role or maybe under Qualifications? Probably About the role.
- Qualifications You Must Have: that's Requirements. So Requirements section.
- Qualifications We Prefer: that's Qualifications section (preferred). Could also include Skills? There's also "Proficiency in Teamcenter, Unigraphics, Ansys, and classical “hand” methods of analysis." etc. That's skills. Could put under Skills section. But we have both Qualifications and Skills headings allowed. We'll put required qualifications under Requirements, preferred qualifications under Qualifications, and specific technical proficiencies under Skills.
- Benefits: What We Offer includes relocation eligibility? Actually "Relocation Eligibility Learn More & Apply Now!" then description of CSE. Then benefits list. We'll extract benefits list.
- Pay: salary range.
- Schedule: not present, omit.
We must not include filler like "commensurate with experience". Not present.
We must not repeat job title.
We must not include metadata like Date Posted, Country, Location, Position Role Type, etc. Could fold minor metadata into short p or drop. Probably drop.
We must remove boilerplate: EEO, privacy, etc.
Now craft HTML.
Structure:
- Proficiency in Teamcenter, Unigraphics, Ansys, and classical “hand” methods of analysis.
- Understanding of hardware, blueprints, dimensions & tolerances, and manufacturing methods.
- Turbomachinery experience.
- Rotating hardware experience.
- Excellent communication and interpersonal skills.
Qualifications
- M.S. or greater in Mechanical or Aerospace engineering.
- Active US government security clearance or the ability to obtain one.
- 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
- Annual short-term and/or long-term incentive compensation programs (depending on position level and collective-bargaining coverage)
Pay
The salary range for this role is 86,800 USD - 165,200 USD.
We should not include "The salary range provided is a good faith estimate..." etc. That's extra detail but maybe considered substantive? It's about the salary range description. Could include as part of Pay paragraph. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that sentence as well. It's substantive about the range being a good faith estimate. So include