Advanced Software Engineer - Flight Management System I UI

📍 Job Overview

Job Title: Advanced Software Engineer - Flight Management System I UI

Company: Honeywell Aerospace

Location: Phoenix, AZ, United States

Job Type: Full time

Category: Software Engineering (Aerospace/Avionics)

Date Posted: 2026-09-21

Experience Level: 5-10 Years

Remote Status: Hybrid

🚀 Role Summary

• Design, develop, and implement innovative software solutions for Flight Management Systems (FMS) with a focus on User Interface (UI) development.

• Participate in the complete software development lifecycle, adhering to stringent aerospace standards like DO-178B.

• Collaborate with cross-functional engineering teams to define requirements and deliver high-quality, reliable software applications.

• Contribute to the porting and implementation of services on the Linux platform, ensuring seamless integration and performance.

• Solve complex real-time challenges related to concurrent process execution in multicore environments.

📝 Enhancement Note: This role is positioned as an "Advanced Software Engineer," suggesting a need for seasoned professionals capable of independent contribution, complex problem-solving, and potentially mentoring junior engineers. The focus on UI within FMS implies a need for skills bridging user experience design principles with embedded software development realities.

📈 Primary Responsibilities

• Engage in the full software development lifecycle (SDLC), encompassing requirements gathering, detailed design, robust coding, comprehensive testing, and successful deployment.

• Ensure all software development activities strictly comply with DO-178B guidelines, a critical standard for avionics software safety.

• Collaborate effectively with cross-functional teams, including systems engineers, hardware engineers, and quality assurance, to accurately define project requirements and ensure alignment.

• Develop and maintain high-quality software documentation, including design specifications, user manuals, and test reports.

• Implement and optimize services on the Linux platform to facilitate the successful porting of applications, ensuring compatibility and performance.

• Design, develop, and maintain the User Interface (UI) components of the Flight Management System, ensuring intuitive and efficient user interaction.

• Troubleshoot and resolve complex software defects, particularly those arising from concurrent execution and multicore processing environments.

• Contribute to the continuous improvement of software development processes, tools, and methodologies within the team.

📝 Enhancement Note: The emphasis on DO-178B compliance is paramount and suggests a highly regulated development environment. Responsibilities clearly outline a need for end-to-end involvement in the software lifecycle, with a specific focus on UI within a complex avionics system.

🎓 Skills & Qualifications

Education:

• Bachelor's degree from an accredited institution in a technical discipline such as Computer Science, Software Engineering, Electrical Engineering, or a related field. Experience:

• Minimum of 5 years of progressive experience in Flight Management System (FMS) product software development.

• Proven experience in User Interface (UI) software development and maintenance, specifically within embedded or avionics systems. Required Skills:

• Embedded C++: Strong proficiency in Embedded C++ for developing real-time, safety-critical software.

• Flight Management System (FMS) Domain: Deep understanding of FMS architecture, functionality, and development principles.

• User Interface (UI) Development: Expertise in designing and implementing user-friendly and efficient interfaces for complex systems.

• Linux Platform: Experience in implementing and porting services on the Linux operating system.

• DO-178B Compliance: Familiarity with or experience in developing software under DO-178B guidelines.

• Software Development Lifecycle (SDLC): Comprehensive understanding and practical application of SDLC methodologies.

• Version Control Systems: Proficiency with industry-standard version control systems (e.g., Git, SVN).

• Multicore Environment: Experience or strong understanding of challenges related to concurrent execution and multicore processing.

• Debugging & Toolchains: Familiarity with build and debug toolchains for embedded systems.

• Requirements Gathering: Ability to elicit, analyze, and document software requirements effectively.

• Analytical & Problem-Solving Skills: Demonstrated ability to analyze complex problems and devise effective solutions.

Preferred Skills:

• A661 Protocol: Familiarity with the ARINC 661 standard for cockpit display systems.

• UI Software Design: Advanced knowledge of UI software design principles and best practices for avionics.

• FMS Functional Area Interfaces: Understanding of interfaces between FMS and other avionics systems.

• Lab Testing & Verification: Experience in testing and verifying system and software requirements in a lab environment.

• Self-Motivation & Initiative: Ability to work independently, take initiative, and drive tasks to completion with minimal supervision.

• Multitasking & Task Management: Proven ability to manage multiple complex tasks simultaneously.

• Global Collaboration: Experience working effectively in diverse, global engineering teams.

• Continuous Learning: A passion for technology and a commitment to ongoing professional development.

📝 Enhancement Note: The combination of "Advanced" in the title and the 5-10 year experience range suggests that candidates with a solid track record in safety-critical software development, particularly within aerospace, will be highly competitive. The specific mention of DO-178B and A661 Protocol indicates a need for specialized knowledge.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• DO-178B Compliant Code Samples: Showcase examples of code developed under or demonstrating an understanding of safety-critical software standards, emphasizing clarity, modularity, and robustness.

• UI Design Mockups/Prototypes: Present visual examples of UI designs or interactive prototypes for complex systems, highlighting user-centric design principles and efficient workflow implementation.

• System Integration Case Studies: Include examples of how your software components were integrated into larger systems, detailing the challenges faced and the solutions implemented for seamless interoperability.

• Problem-Solving Demonstrations: Provide case studies illustrating your approach to solving complex technical challenges, particularly those involving real-time constraints, multicore environments, or performance optimization, with a clear articulation of the resolution and its impact.

Process Documentation:

• SDLC Documentation: Demonstrate experience with documenting various stages of the SDLC, including requirements specifications, design documents, test plans, and verification reports, with an emphasis on aerospace standards.

• Workflow Optimization Examples: Present instances where you identified inefficiencies in software development workflows and implemented improvements to enhance productivity, reduce cycle times, or improve code quality.

• Collaboration & Communication Protocols: Document your approach to collaborating with cross-functional teams, including how you facilitate communication, manage feedback, and ensure alignment on project goals and technical solutions.

• Toolchain & Environment Setup: Illustrate your understanding of setting up and managing development, build, and debug toolchains for embedded Linux environments.

📝 Enhancement Note: For an "Advanced" role in aerospace, a portfolio that not only demonstrates technical proficiency but also adherence to rigorous development processes and safety standards is crucial. The ability to articulate the "why" behind design choices and process implementations will be key.

💵 Compensation & Benefits

Salary Range:

• Estimated Range: $120,000 - $170,000 annually.

• Methodology: This estimate is based on industry benchmarks for Advanced Software Engineers with 5-10 years of experience in specialized fields like aerospace and avionics in the Phoenix, AZ metropolitan area. Factors considered include the demand for expertise in Embedded C++, DO-178B, FMS, and UI development, as well as Honeywell's standing as a major aerospace employer. Actual compensation will be determined by candidate experience, specific skill alignment, and internal equity.

Benefits:

• Comprehensive Health Coverage: Employer-subsidized medical, dental, and vision insurance plans.

• Life & Disability Insurance: Robust life insurance and both short-term and long-term disability coverage.

• Retirement Savings: Competitive 401(k) plan with employer match.

• Financial Wellness: Flexible Spending Accounts (FSAs) and Health Savings Accounts (HSAs) for tax-advantaged savings.

• Employee Support: Access to an Employee Assistance Program (EAP) for personal and professional support.

• Professional Development: Educational assistance programs to support continued learning and skill enhancement.

• Work-Life Balance: Generous parental leave, 12 paid holidays, and paid time off (PTO) for vacation, personal, and sick time.

• Additional Perks: Access to Honeywell's extensive benefits portal and resources.

Working Hours:

• Standard full-time work schedule, typically 40 hours per week.

• Hybrid work arrangement requires flexibility to be in the Phoenix, AZ office as needed, with specific days determined by team and project requirements.

📝 Enhancement Note: The estimated salary range reflects the advanced nature of the role and the specialized technical skills required. Honeywell's comprehensive benefits package is a significant component of total compensation, particularly attractive for experienced professionals.

🎯 Team & Company Context

🏢 Company Culture

Industry: Aerospace & Defense Technology. Honeywell Aerospace is a global leader in providing innovative solutions for commercial aviation, defense, and space applications, including avionics, engines, and connectivity.

Company Size: Large Enterprise (Honeywell Aerospace is part of Honeywell International, a Fortune 100 company with tens of thousands of employees globally).

Founded: Honeywell was founded in 1906, with its Aerospace division boasting over a century of innovation in aviation technology.

Team Structure:

• Operations Team: This role is within the Electronic Solutions business unit, focusing on avionics and navigation systems. The software engineering team is likely structured around specific product lines or functional areas (like FMS UI).

• Reporting Structure: Typically, software engineers report to a Software Engineering Manager or Lead, who in turn reports up through engineering management within the business unit.

• Cross-functional Collaboration: Engineers will work closely with systems engineers, hardware designers, test engineers, project managers, and potentially customer representatives.

Methodology:

• Data-Driven Development: Emphasis on rigorous testing, verification, and data analysis to ensure software safety and reliability, especially under DO-178B.

• Agile & Waterfall Hybrid: While DO-178B often mandates more structured, waterfall-like phases, teams may incorporate agile principles for iterative development within those constraints.

• Continuous Improvement: A culture that encourages learning from past projects, refining processes, and adopting new technologies where appropriate.

Company Website: https://www.honeywellaerospace.com/

📝 Enhancement Note: Honeywell's long history and market leadership imply a culture of high standards, reliability, and continuous innovation. The "Advanced" title suggests a meritocratic environment where technical expertise is highly valued.

📈 Career & Growth Analysis

Operations Career Level: Advanced Software Engineer. This level signifies a mid-to-senior career stage, requiring deep technical expertise, independent problem-solving capabilities, and the ability to contribute significantly to project success. It often involves tackling the most challenging technical problems and potentially guiding less experienced engineers.

Reporting Structure: You will likely report to a Software Engineering Manager or a Technical Lead within the Electronic Solutions division, working within a project team environment. Collaboration with other engineers, systems architects, and project managers will be key.

Operations Impact: As an Advanced Software Engineer on the Flight Management System UI, your work will directly impact the safety, efficiency, and user experience of aircraft. This includes ensuring pilots have clear, accurate, and timely information for navigation and flight control, contributing to Honeywell's reputation for reliability and innovation in avionics.

Growth Opportunities:

• Technical Specialization: Deepen expertise in avionics software, DO-178B, UI/UX for complex systems, or multicore embedded development.

• Leadership Development: Potential to move into roles like Technical Lead, Software Architect, or Engineering Manager.

• Cross-Business Unit Mobility: Opportunities to explore roles in other Honeywell divisions (e.g., Performance Materials and Technologies, Building Technologies) after gaining experience.

• Advanced Education & Certifications: Support for pursuing further certifications or advanced degrees relevant to aerospace engineering and software development.

• Project Management: Transitioning into program or project management roles within engineering.

📝 Enhancement Note: The "Advanced" designation suggests a clear path for further technical leadership or management roles within Honeywell Aerospace, supported by the company's commitment to employee development and its vast internal opportunities.

🌐 Work Environment

Office Type: Hybrid work environment. This means a blend of remote work and on-site presence at the Phoenix, AZ office. Specific days in the office will likely be determined by team needs, project milestones, and collaborative requirements.

Office Location(s): Phoenix, Arizona, United States. This location is a significant hub for Honeywell Aerospace, offering a well-equipped engineering environment.

Workspace Context:

• Collaborative Spaces: The Phoenix office will likely feature collaborative work areas, meeting rooms, and potentially dedicated project spaces to facilitate team interaction and problem-solving.

• Engineering Tools & Technology: Access to state-of-the-art development workstations, specialized avionics simulation tools, testing labs, and robust IT infrastructure necessary for safety-critical software development.

• Team Interaction: Opportunities for direct interaction with a team of highly skilled aerospace engineers, fostering knowledge sharing and a culture of innovation.

Work Schedule: Standard business hours (approximately 40 hours per week) with a hybrid arrangement. Flexibility may be required during critical project phases or for specific testing activities.

📝 Enhancement Note: The hybrid model is common for advanced engineering roles, balancing flexibility with the need for in-person collaboration, especially for complex design reviews and hands-on testing in an aerospace context.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: HR or recruiter call to assess basic qualifications, interest, and cultural fit.

• Technical Interview(s): In-depth interviews focusing on Embedded C++, FMS, UI development, DO-178B principles, and problem-solving scenarios. Expect coding challenges or architecture discussions.

• System Design/Architecture Discussion: May involve discussing how to design or improve specific FMS UI features, considering constraints like safety, performance, and real-time operation.

• Behavioral Interview: Assessing soft skills, teamwork, leadership potential, and alignment with Honeywell's values.

• On-site/Virtual Panel Interview: Potentially a final round with multiple team members or managers to finalize assessment.

Portfolio Review Tips:

• Highlight DO-178B Relevance: If you have direct DO-178B experience, make it prominent. If not, showcase how your work demonstrates principles of safety, rigor, and traceability.

• Showcase UI Expertise: Include detailed examples of UI designs, wireframes, or interactive prototypes. Explain your design process, user-centric considerations, and how you handled complex data visualization.

• Demonstrate Problem-Solving: Use case studies to illustrate how you tackled challenging technical problems, particularly those related to real-time systems, multicore processing, or performance optimization. Quantify results where possible (e.g., "reduced latency by X%").

• Process Documentation Clarity: Provide clear examples of documentation you've produced (design docs, test plans) that reflect attention to detail and adherence to standards.

• Tailor to FMS & Linux: Emphasize projects or skills directly applicable to Flight Management Systems and Linux platform development.

Challenge Preparation:

• Embedded C++ Algorithms: Be prepared to solve algorithmic problems using C++, focusing on efficiency and correctness.

• System Design Scenarios: Practice designing components of a larger system, considering trade-offs, constraints, and potential failure modes.

• DO-178B Principles: Review the core concepts of DO-178B, including objectives, levels, and common pitfalls.

• UI/UX for Embedded Systems: Think about how to design intuitive UIs for constrained environments with critical information display.

• Multicore Concurrency: Refresh knowledge on multithreading, synchronization primitives, and potential race conditions.

📝 Enhancement Note: The interview process for an advanced role in a regulated industry like aerospace will be rigorous. A well-prepared portfolio that clearly articulates technical depth, process adherence, and problem-solving capabilities is essential for success.

🛠 Tools & Technology Stack

Primary Tools:

• Programming Languages: Embedded C++, potentially C, scripting languages (Python for tooling/automation).

• Development Environments: IDEs such as Eclipse, Visual Studio Code with embedded plugins, or proprietary IDEs.

• Version Control: Git (highly probable), potentially SVN.

• Build Systems: Make, CMake, or custom build tools for embedded Linux.

• Debugging Tools: GDB, JTAG debuggers, oscilloscopes, logic analyzers.

Analytics & Reporting:

• Testing Frameworks: Unit testing frameworks (e.g., Google Test, CppUnit), integration testing tools.

• Static Analysis Tools: Tools for code quality and security analysis (e.g., Coverity, SonarQube).

• Performance Profiling Tools: Tools to measure execution time, memory usage, and identify bottlenecks.

CRM & Automation:

• Requirements Management Tools: Tools like DOORS, Jama Connect, or similar for managing DO-178B requirements.

• Issue Tracking Systems: JIRA, Bugzilla, or similar for defect tracking and task management.

• CI/CD Pipelines: Jenkins, GitLab CI, or similar for automated builds and testing, adapted for embedded environments.

• Linux Operating System: Deep familiarity with Linux kernel, system services, and user-space applications.

📝 Enhancement Note: Proficiency with a mix of embedded development tools, safety-critical compliance software, and standard software engineering practices (version control, issue tracking) is expected. Experience with Linux as a development and target platform is critical.

👥 Team Culture & Values

Operations Values:

• Safety & Reliability: Paramount importance placed on the safety and dependability of all software developed, reflecting the critical nature of aerospace applications.

• Integrity & Ethics: Upholding the highest standards of honesty, accountability, and ethical conduct in all aspects of work.

• Innovation: A drive to develop cutting-edge technologies that push the boundaries of aviation and space exploration.

• Customer Focus: Dedication to understanding and meeting customer needs, ensuring solutions deliver tangible value and performance.

• Excellence & Quality: Commitment to delivering high-quality products and services through rigorous processes and continuous improvement.

Collaboration Style:

• Team-Oriented: Emphasis on working collaboratively within project teams and across disciplines to achieve shared goals.

• Knowledge Sharing: Encouraging the exchange of ideas, best practices, and technical expertise among team members.

• Constructive Feedback: A culture where feedback is valued and used for continuous improvement, both individually and collectively.

• Cross-Functional Partnership: Strong emphasis on working effectively with systems, hardware, and test engineers to ensure integrated solutions.

📝 Enhancement Note: Honeywell's culture likely blends the structured, process-driven environment required for safety-critical systems with a forward-looking, innovative spirit characteristic of the aerospace industry.

⚡ Challenges & Growth Opportunities

Challenges:

• DO-178B Compliance Complexity: Navigating the rigorous documentation, verification, and traceability requirements of DO-178B can be demanding, requiring meticulous attention to detail.

• Real-time Multicore Debugging: Diagnosing and resolving issues in concurrent, multicore embedded systems presents significant technical challenges due to timing dependencies and subtle race conditions.

• Balancing UI/UX with Safety Constraints: Designing intuitive and modern user interfaces within the strict safety and performance limitations of avionics systems requires creative problem-solving.

• Integrating Legacy and Modern Systems: Working with existing FMS architecture while introducing new UI features and potentially porting to newer platforms like Linux.

Learning & Development Opportunities:

• Specialized Training: Access to training programs focused on DO-178C (the successor to B), avionics systems, advanced C++ techniques, and UI/UX design for critical applications.

• Industry Conferences: Opportunities to attend aerospace and software engineering conferences to stay abreast of the latest trends and technologies.

• Mentorship Programs: Potential to be mentored by senior engineers or architects, and to mentor junior team members, fostering leadership skills.

• Cross-Disciplinary Exposure: Gaining exposure to systems engineering, hardware design, and flight testing processes within the aerospace domain.

📝 Enhancement Note: This role offers significant challenges that are highly rewarding for engineers passionate about aerospace and safety-critical systems, coupled with ample opportunities for professional growth and specialization.

💡 Interview Preparation

Strategy Questions:

• "Describe a complex UI feature you developed for an embedded system. What were the key challenges, and how did you ensure its reliability and usability within system constraints?" (Focus on process, problem-solving, and impact).

• "How would you approach designing a new feature for a Flight Management System's UI, considering DO-178B compliance and real-time performance requirements?" (Focus on methodology, safety, and technical trade-offs).

• "Walk me through your process for debugging a concurrency issue in a multicore Linux environment. What tools and techniques would you employ?" (Focus on technical depth and systematic approach). Company & Culture Questions:

• "Based on your understanding of Honeywell Aerospace, what do you believe are the most critical aspects of software development for this industry, and how do your skills align?" (Demonstrate research and alignment with values like safety, reliability).

• "Describe a time you had to collaborate with engineers from different disciplines (e.g., hardware, systems) to achieve a project goal. What was your role, and how did you ensure effective communication?" (Focus on teamwork and cross-functional skills).

• "How do you stay current with advancements in embedded software development, particularly in avionics and UI technologies?" (Showcase commitment to continuous learning). Portfolio Presentation Strategy:

• Structure Your Case Studies: For each project, clearly outline the problem, your solution, the technologies used (especially Embedded C++, Linux, UI frameworks), the challenges overcome, and the quantifiable results or impact.

• Emphasize Process: For DO-178B relevant work, highlight your understanding of documentation, traceability, and verification steps.

• Visual Aids: Use diagrams, screenshots, or mockups to illustrate your UI designs and system architectures effectively.

• Quantify Impact: Whenever possible, use metrics to demonstrate the success of your work (e.g., performance improvements, defect reduction, user satisfaction).

• Be Prepared for Deep Dives: Expect interviewers to ask detailed questions about specific technical decisions made in your portfolio projects.

📝 Enhancement Note: Interview preparation should focus on showcasing a blend of deep technical expertise in core areas (Embedded C++, UI, Linux, FMS), a strong understanding of safety-critical development processes (DO-178B), and effective collaboration and problem-solving skills.

📌 Application Steps

To apply for this Advanced Software Engineer position:

• Submit your comprehensive application through the Honeywell Aerospace careers portal.

• Tailor Your Resume: Highlight keywords and experiences directly related to Embedded C++, Flight Management Systems (FMS), User Interface (UI) development, Linux, and DO-178B compliance. Quantify achievements and responsibilities.

• Prepare Your Portfolio: Curate examples of your most relevant work, focusing on UI design, embedded C++ projects, and any experience with safety-critical systems or Linux development. Be ready to articulate your process and impact.

• Research Honeywell Aerospace: Understand their mission, values, recent innovations (especially in Electronic Solutions), and the importance of safety and reliability in their products.

• Practice Interview Questions: Prepare detailed responses for technical, behavioral, and situational questions, drawing upon your experience and portfolio examples. Practice explaining complex technical concepts clearly and concisely.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.