DirectJobHub
Jobs · Information Technology · Arizona

Chief Engineer - Electric Power Control Systems

Honeywell Aerospace · Tempe, AZ · 3 wk ago
HybridInformation TechnologyFull-time

Responsibilities

  • Leadership
  • Technical Leadership
  • Communication Skills
  • Deployment of Improvement Ideas
  • Champion Improvements
  • Sharing Best Practices
  • Engagement with Customers, Regulatory Agencies, and Suppliers
  • Guidance on Value-Added Process Changes
  • Knowledge Management and Transfer
  • Talent Development
  • Training and Mentoring
  • Approval of Processes/Tools
  • Leveraging Data from In-Service Products
  • Review and Analysis of VOC and CI Data
  • Drive Technical Strategies and Product Plans
  • Support for Development of Product Design Requirements
  • Review and Approval of Program Plan, SOW, and QE
  • Technical Oversight of Internal and External Design Reviews
  • New Product Development
  • Guide Deployment of Improvement Ideas
  • Champion Improvements
  • Remove Roadblocks
  • Deployment of Transformation for Speed
  • Ensure Impactful Speed and Cost Improvement Ideas
  • Program Execution
  • Accountability for Success
  • Risk Mitigation Planning
  • Compliance with Customer Specifications and Regulatory Authority Requirements
  • Root Cause and Corrective Action Investigations
  • Safety Assessments and Closure of PCRs
  • People Development
  • Mentorship Potential Successors
  • Provide Training and Mentoring
  • Create Succession Plan
  • Group Training & Knowledge Transfer
  • Define Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive
  • Knowledge Capture Needs
  • Process and Lessons Learned Archive

Similar jobs