Sr Advanced Project Engineer - Actuation Systems

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes: Job Description (intro), Key Responsibilities, Qualifications (MUST HAVE, WE VALUE), What Makes You Successful (maybe Skills?), U.S. Person Requirements (maybe not needed), Benefits Of Working For Honeywell Aerospace, About Honeywell Aerospace, Posting Timeline (maybe not needed). We need to avoid repeating job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none. Also remove application instructions (none). We need to preserve all substantive info. We need to decide sections: About the role (intro paragraph), Responsibilities (Key Responsibilities), Requirements (maybe combine MUST HAVE and WE VALUE? Could separate Qualifications and Skills? The instruction says use headings like Qualifications, Skills. We have Qualifications (MUST HAVE) and WE VALUE could be Skills. Also "What Makes You Successful" could be Skills or maybe part of Qualifications. We'll treat "What Makes You Successful" as Skills. Benefits section present. Pay? Not mentioned. Schedule? Mention hybrid work schedule, first 90 days onsite. That's schedule info. So we can include Schedule section. We should not include sections with placeholder like Pay if not present. We need to output only HTML fragment, no /. Use

headings,

• for lists,

  for prose. We need to preserve all substantive info: include details like location Tempe site, hybrid schedule, first 90 days onsite, reporting to Sr. Engineering Program Manager, etc. Let's extract. Intro: "Join Honeywell Aerospace and Shape the Future of Flight Honeywell Aerospace is seeking a Senior Advanced Project Engineer to join our Actuation Systems team, where you'll play a critical role in developing next-generation electro-mechanical actuation technologies for defense and more-electric aircraft platforms. In this highly visible role, you will lead technical project execution across the entire product lifecycle—from early requirements definition and system architecture through design, analysis, testing, qualification, and production transition. You'll collaborate with multidisciplinary engineering teams, customers, suppliers, and program stakeholders to deliver innovative solutions that advance aerospace technology. You will report to the Sr. Engineering Program Manager, and work out of our Tempe site on a hybrid work schedule. Please note that the new hires are expected to work fully onsite for the first 90 days." We can put that in About the role

  . Responsibilities: list under Key Responsibilities with subheadings? The text includes bullet-like sentences but not bullet list. We can convert each sentence to

• . There are sections: Project & Program Leadership, Technical Execution, Collaboration & Customer Engagement. Could keep as headings inside? But we only allowed

  for section headings; we could have subheadings but not required. Simpler: make a

  with each responsibility as
  • . Keep all sentences. Let's list them: - Lead engineering project execution to achieve technical, cost, schedule, and quality objectives. - Develop and manage project plans, schedules, milestones, and resource estimates. - Support Earned Value Management System (EVMS) activities, including performance tracking and reporting. - Identify, assess, and manage project risks and opportunities throughout the development lifecycle. - Contribute to proposal development, including technical planning, cost estimation, and schedule creation. - Support the design, development, integration, and validation of electro-mechanical actuation systems. - Analyze customer requirements and translate them into technical solutions and verification strategies. - Evaluate compliance with applicable government, regulatory, and aerospace industry requirements. - Lead technical problem-solving efforts, root cause investigations, and corrective action implementation. - Develop and review technical documentation, including test plans, procedures, reports, and design artifacts. - Analyze test data and communicate findings to technical and program stakeholders. - Support design verification, qualification testing, and validation activities through hardware builds and test execution. - Serve as a technical interface with customers, fostering strong relationships and effective communication. - Coordinate with suppliers and manufacturing partners to ensure successful hardware development and delivery. - Develop program metrics and status reporting to support leadership decision-making. - Work effectively within cross-functional teams spanning systems, mechanical, electrical, manufacturing, quality, and program management functions. Qualifications: MUST HAVE and WE VALUE. We'll put under Qualifications heading maybe with two sublists? Could separate:

    Qualifications

    then

    MUST HAVE:

    then
    etc. But we need to use

    for section headings only; we can still have

    inside. That's fine. MUST HAVE list: - Bachelor’s degree from an accredited institution in a technical discipline such as the sciences, technology, engineering or mathematics. - Minimum of 3 years of engineering experience in aerospace, defense, electromechanical systems, manufacturing, testing, product development, or a related technical field. - Experience managing technical deliverables, schedules, and priorities within a project environment. WE VALUE list (could be Skills). We'll put under Skills heading. Skills list: - Experience with electro-mechanical actuation systems, motion control systems, or aerospace subsystems. - Knowledge of aerospace development processes, system validation, verification, qualification, and certification activities. - Familiarity with Earned Value Management (EVM/EVMS), project planning, and risk management. - Experience interpreting engineering drawings and applying GD&T principles. - Manufacturing, production support, or hardware integration experience. - Strong analytical and troubleshooting skills with a structured approach to root cause analysis. - Experience working with customers, suppliers, and cross-functional engineering teams. - Strong written, verbal, and presentation communication skills. - Demonstrated ability to take initiative, drive results, and thrive in a fast-paced environment. What Makes You Successful: could be part of Skills or separate. We'll incorporate into Skills maybe as additional bullet points? But we already have skills list; we could add those as separate bullet points under Skills. However the instruction: Prefer few substantive sections over many thin ones. Could combine What Makes You Successful into Skills as additional bullets. Let's add those bullets: - You are a proactive problem solver who enjoys tackling complex technical challenges. - You balance technical depth with strong project execution skills. - You build trust and maintain productive relationships across teams and organizations. - You can communicate complex concepts clearly to both technical and non-technical audiences. - You are motivated to influence product success from concept through production. We'll include them in Skills. Benefits: list. - Employer-subsidized medical, dental, vision and life insurance - Short-term and long-term disability coverage - 401(k) match, flexible spending accounts and health savings accounts - Employee assistance program and educational assistance - Parental leave and 12 paid holidays - Paid time off for vacation, personal and sick time - Explore your benefits: https://honeywellaerospacebenefits.com/ We can keep the link as part of

    maybe. Schedule: hybrid work schedule, first 90 days fully onsite. We'll put in Schedule section

    . About Honeywell Aerospace: we can include as About the company maybe not required but we have About Honeywell Aerospace paragraph. Could be included as About the role? Already used About the role for intro. We could add another section About Honeywell Aerospace but heading not in list; allowed headings are only those listed. So we should not create a heading not in list. We could incorporate that info into About the role or maybe omit? 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 stick to those headings. It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely we should only use those headings. So we should not add About Honeywell Aerospace heading. We could incorporate that paragraph into About the role or maybe drop? But we must preserve ALL substantive information. So we need to include that info somewhere. Could add as a

    under About the role after intro. That's fine. Posting Timeline: not needed? It's metadata but not required; could be omitted as minor metadata? It's not job ID but could be considered minor metadata; we could drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Posting Timeline maybe minor metadata; we can drop it. U.S. Person Requirements: also maybe minor metadata but it's substantive (citizenship requirement). Should we include? It's a requirement; could be part of Qualifications. We'll add as a bullet under Qualifications maybe. Let's incorporate U.S. Person Requirements as a bullet under Qualifications (maybe under MUST HAVE). It says: Due to compliance with U.S. export control laws and regulations, candidate must be a U.S. Person, which is defined as, a U.S. citizen, a U.S. permanent resident, or have protected status in the U.S. under asylum or refugee status or have the ability to obtain an export authorization. We'll add that as a bullet. Now construct HTML. Structure:

    About the role

    Join Honeywell Aerospace and Shape the Future of Flight Honeywell Aerospace is seeking a Senior Advanced Project Engineer to join our Actuation Systems team, where you'll play a critical role in developing next-generation electro-mechanical actuation technologies for defense and more-electric aircraft platforms. In this highly visible role, you will lead technical project execution across the entire product lifecycle—from early requirements definition and system architecture through design, analysis, testing, qualification, and production transition. You'll collaborate with multidisciplinary engineering teams, customers, suppliers, and program stakeholders to deliver innovative solutions that advance aerospace technology. You will report to the Sr. Engineering Program Manager, and work out of our Tempe site on a hybrid work schedule. Please note that the new hires are expected to work fully onsite for the first 90 days. At Honeywell Aerospace (NASDAQ: HONA), we're launching as an independent, publicly traded aerospace and defense company built on a legacy of operational excellence and mission-focused execution. Our new brand identity pairs that heritage with real momentum, as we build technology that helps pilots navigate with confidence, aircraft operate more efficiently, and operators stay ahead of change. With our systems on board 90% of the world's aircraft, your work here has reach that's rare to find anywhere else. Focusing on our customers, investing in innovation, and building a culture of accountability and performance is how we're shaping what comes next. Every horizon. Every mission. Every day.

    But we duplicated some sentences from About Honeywell Aerospace; we need to ensure we included all. We'll combine. Better: After intro paragraph, add another paragraph with About Honeywell Aerospace content. Now Responsibilities:

    Responsibilities

    • ...
    ...
    Qualifications:

    Qualifications

    MUST HAVE:

    • Bachelor’s degree from an accredited institution in a technical discipline such as the sciences, technology, engineering or mathematics.
    • Minimum of 3 years of engineering experience in aerospace, defense, electromechanical systems, manufacturing, testing, product development, or a related technical field.
    • Experience managing technical deliverables, schedules, and priorities within a project environment.
    • Due to compliance with U.S. export control laws and regulations, candidate must be a U.S. Person, which is defined as, a U.S. citizen, a U.S. permanent resident, or have protected status in the U.S. under asylum or refugee status or have the ability to obtain an export authorization.
    Skills:

    Skills

    • Experience with electro-mechanical