Sr Advanced Project Engineer

after the role description that includes company overview. That's still substantive. We also have "Travel: up to 10% US/International". That's a detail; could be placed under Responsibilities or maybe a separate section like "Travel". Not in allowed headings; maybe fold into Responsibilities or About the role. Pay and Schedule: The posting mentions hybrid work schedule, first 90 days 100% onsite M-F. That's schedule info. So we can create a Schedule section with that detail. Pay: not mentioned explicitly (no salary). So we should NOT create Pay section because no specific content. Benefits: we have a Benefits section with details. So include Benefits. Skills: Could be derived from qualifications and responsibilities; but we might not need a separate Skills section if content overlaps. However we could create Skills section summarizing technical skills like MS Project, SAP, WBS, EVMS, IPDS, DOORS, PTS, ClearCase, MATLAB/Simulink, Python, etc. But we must not invent or summarize away detail; we can list them as they appear. That's okay. Qualifications: Must have and WE VALUE. Also U.S. Person Requirements. So include Qualifications section with those details. Requirements: Might be similar to Qualifications; but we have a separate "Key Responsibilities". The "Requirements" heading maybe for job requirements (like education, experience). Since we have Qualifications, we could treat Qualifications as requirements. But the instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have both Requirements and Qualifications if content distinct. However the posting lumps qualifications under "Qualifications YOU MUST HAVE" and "WE VALUE". That's qualifications. There's no separate "Requirements" heading besides that. So we could omit Requirements section to avoid thin content. But we need to preserve all info; we can put those details under Qualifications. That's fine. Skills: Could be extracted from responsibilities and qualifications; but we might not need a separate Skills if we already have Qualifications. However we can still create Skills section listing specific tools and methodologies mentioned. That would be substantive and not duplicate? Might duplicate some content but okay. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to have fewer sections: About the role, Responsibilities, Qualifications, Benefits, Schedule. That's 5 sections. Skills could be merged into Qualifications or Responsibilities. We'll avoid Skills. Pay: not present, omit. Thus final HTML:

About the role

As a Sr Advanced Project Engineer here at Honeywell Aerospace, you will lead complex engineering projects, driving innovation and ensuring successful delivery of advanced aerospace solutions. You will collaborate with cross-functional teams to manage project timelines, resources, and technical challenges, playing a key role in advancing Honeywell's aerospace technology. You will report directly to our Sr Systems Engineering Manager and you’ll work out of our Tempe or Tucson, AZ location on a hybrid work schedule. Note: For the first 90 days, New Hires must be prepared to work 100% onsite M-F. Travel: up to 10% US/International.

About Honeywell Aerospace: Join a company that's reintroducing itself to the aviation community we've helped advance for more than a century. 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.

About the Business Unit: Honeywell Aerospace products and services are found on aircraft across commercial aviation, defense and space — from engines and cockpit electronics to cabin systems, mechanical components and connectivity solutions. Our technology helps operators fly more safely, reduce fuel consumption, improve on-time performance and deliver a better experience for the people on board. As aviation continues to evolve, we're also developing systems to support autonomous and supersonic platforms, bringing the same focus on safety and efficiency to the next era of flight. With approximately 36,000 employees worldwide and net sales of $17.4B in 2025, Honeywell Aerospace is one of the largest dedicated aerospace companies in the world. Control Systems develops the thermal and motion control systems that help aircraft take off, land safely and protect the people on board. With more than 10 million passengers per day flying on aircraft equipped with our products and more than 75% of commercial flights beginning with our engine start systems, Control Systems reaches farther across the aviation industry than most people realize.

Responsibilities

• Engineering Project Planning & Management with experience managing schedules, budgets, resources, and deliverables using MS Project, SAP, WBS, and Earned Value Management (EVMS) tools.
• Engineering Development Leadership driving projects through the full lifecycle utilizing IPDS (Integrated Product Development System) or equivalent processes.
• Statement of Work (SOW) Development for engineering teams, vendors, subcontractors, and cross-functional stakeholders.
• Program Review Support including preparation of status reports, executive presentations, charts, and supporting documentation for customer and leadership reviews.
• Phase Gate & Compliance Management through creation and coordination of PECA artifacts and gate exit review deliverables.
• Proposal Development & Cost Estimation supporting business pursuits, resource planning, and project forecasting.
• Integrated Master Schedule (IMS) Management with experience tracking and maintaining schedule and cost performance metrics, including SPI, CPI, and Earned Value (EV).
• Executive & Customer Presentations with strong public speaking skills and the ability to effectively communicate program status, risks, and technical information to leadership and customers.
• Requirements Management Expertise with deep knowledge of modern CPCS requirements development, traceability, and validation processes.
• Customer Requirements Management utilizing formal tools such as DOORS, PTS, and ClearCase to capture, track, and manage technical requirements throughout the product lifecycle.
• Requirements Implementation translating customer and system requirements into Honeywell Aerospace controls system documentation and design specifications.
• Design Review Leadership facilitating and moderating peer design reviews, while managing requirement updates and validation in accordance with IPDS AP-1235 processes.
• Configuration Management & Test Support overseeing the build, integration, and testing of development hardware and test equipment under formal configuration control using PDM systems.
• Requirements Verification & Compliance ensuring requirement changes are properly reviewed, documented, implemented, and validated throughout development and testing activities.
• Cross-Functional Coordination collaborating with engineering, test, and program teams to maintain requirements integrity and support successful product development execution.
• Test Planning & Validation by developing test cases, procedures, and automated scripts (Python) to verify and validate system requirements.
• Test Execution & Analysis performing validation testing and documenting results through detailed analysis and test reports.
• Software Verification validating development software releases, updates, and modifications against customer and system requirements.
• System Integration integrating and troubleshooting system-level test equipment, electronic hardware, mechanical hardware, and software components.
• Technical Documentation creating and maintaining test procedures, validation records, and assessment reports to support certification and program milestones.
• Cross-Functional Test Support collaborating with engineering, software, and hardware teams to resolve issues and ensure successful system integration and verification.
• Model-Based Development Expertise with advanced proficiency in Honeywell Aerospace Modeling (HAM), Beacon, and other model-based engineering tools.
• Control System Modeling & Simulation developing advanced control algorithms and system models using MATLAB/Simulink.
• Simulation Analysis & Validation executing, evaluating, and refining complex system simulations to support design, verification, and performance optimization.
• Model-Based Design Implementation utilizing simulation-driven development methodologies to improve system performance, reduce risk, and accelerate product development.
• Control Systems Engineering applying model-based approaches to support requirements analysis, system design, integration, and verification activities.
• Technical Problem Solving leveraging modeling and simulation tools to predict system behavior, assess design alternatives, and resolve technical challenges early in the development lifecycle.
• PCS Systems Expertise serving as a subject matter expert in modern electronic Cabin Pressure Control System (CPCS) design, development, and integration.
• Technical Leadership & Mentorship leading small engineering teams, providing technical guidance, and mentoring junior engineers to support project success.
• Aerospace Standards Knowledge with familiarity in industry regulations and development standards including DO-160, DO-178, DO-254, ARP4754, ARP4761, and Military Specifications.
• Aircraft Certification Support understanding FAA certification requirements and processes, including FAR Part 23 and Part