HMI/Desktop Applications Software Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key content: - Job description: Ready to put your C++ and C# skills to work on software that directly controls unmanned aircraft systems? Airbus is seeking an Entry-Level Software Engineer to design, refine, and maintain the desktop ground-control applications our operators rely on to fly cutting-edge UAS fleets. This is an ideal launchpad for an early-career engineer who loves building user-facing interfaces, working close to hardware, and translating complex real-time telemetry into actionable visual tools. - Meet the Team: description of Flexrotor Program. - Your Working Environment: location Bingen, WA, description. - How We Care for You: Financial Rewards: Competitive base salary, incentive compensation which may include profit sharing schemes, retirement savings plan and the ability to participate in an Employee Stock Ownership Plan (“ESOP”) Work/Life Balance: Paid time off including personal time, holidays and a generous paid parental leave program. Health & Welfare: Comprehensive insurance coverage including medical (traditional and high-deductible health plans), prescription, dental, vision, life, disability, Employee Assistance Plan (“EAP”) and other supplemental benefit coverages. - Your Challenges: list of duties. - Your Boarding Pass: (Required for consideration) Must possess a Bachelor's degree in Electrical Engineering, Computer Engineering, Computer Science, or related field. Possess a minimum of six (6) months experience programming in C++ and/or C#, through coursework or personal/academic projects. Basic understanding of object-oriented programming principles. Ability to debug and troubleshoot application-level issues. Ability to translate functional requirements into working application features. Demonstrated project experience (school, internship, or personal) building a functioning application Ability to document code and application behavior clearly for teammates. Comfortable asking questions and incorporating feedback from senior engineers and operators. - Preferred Skills: list. - Travel Required: Minimal-5% Domestic and International - Citizenship: Must be a US Person under ITAR definition (U.S. Citizen, green card holder or person covered under our existing ITAR license) - Physical Requirements: list. - Salary range based on the required profile: $116k to $178k /year. Actual minimum and maximum may vary based on geographic differential. Individual pay is based on skills, experience, and other relevant factors. - This position offers the following benefits: Medical insurance, Dental insurance, Vision insurance, Prescription insurance, Employee Assistance Program, Flexible Spending Accounts, Health Savings Accounts, Basic & Voluntary Life and Accidental Death & Dismemberment insurance, Short and Long-term Disability insurance, 401(k), Paid time off including paid holidays, Tuition Assistance, Bonus(es) subject to performance criteria. - Also earlier "How We Care for You" includes financial rewards etc. We need to map to sections: About the role (maybe summary), Responsibilities (Your Challenges), Requirements (Your Boarding Pass required), Qualifications (maybe education/experience?), Skills (Preferred Skills), Benefits (benefits list), Pay (salary range), Schedule (maybe travel required? Or work schedule? Not explicit schedule besides onsite 80% and remote 20%? Actually "Onsite or remote: 80% onsite in Bingen, WA". That's schedule/location. Also Travel Required: Minimal-5% Domestic and International. Could be schedule? But schedule section is for work schedule (e.g., full-time, part-time, shift). Not present. We could omit Schedule if no specific schedule content. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. So we need Pay (yes), Benefits (yes), Schedule (maybe not). There's no explicit schedule like "Full-time", "40 hours/week". There's "Onsite or remote: 80% onsite". That's more about work arrangement, not schedule. Could we treat as Schedule? Probably not. Safer to omit Schedule section. Now we need to decide sections: About the role (intro paragraph), Responsibilities (Your Challenges), Requirements (Your Boarding Pass required), Qualifications (maybe education/experience overlapped with Requirements; but we can combine? The instruction: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they ask to use headings for those specific names if content exists. We have content for Requirements (required qualifications) and also Preferred Skills (skills). Could treat Requirements as required qualifications, Skills as preferred skills. Qualifications maybe redundant. Could we omit Qualifications section and put education/experience under Requirements? That seems fine. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must include all; only include when posting has real specific content. So we can include About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly also include a section for "Working Environment" or "Meet the Team"? Not in list; we should not create extra headings beyond those listed. So we must fit content into those headings. We can put "Meet the Team" and "Your Working Environment" maybe under About the role? Or we could incorporate into About the role as prose. The About the role section can contain overview of role, team, environment. That seems acceptable. Responsibilities: Your Challenges list. Requirements: Your Boarding Pass (required) list. Skills: Preferred Skills list. Benefits: benefits list (including from How We Care for You and the later benefits list). Need to combine without duplication. Pay: salary range. We must not include boilerplate like EEO, legal, etc. We must preserve all substantive information. So we need to include details like location Bingen, WA, 80% onsite, minimal travel, citizenship requirement, physical requirements? Those are substantive; where to put them? They don't fit neatly into the allowed headings. Could we put them under About the role? Possibly as part of role description. The instruction: "Prefer a few substantive sections over many thin ones." So we can include extra details in About the role paragraph. That seems okay. We must not invent or summarize away detail. So we need to keep specifics: e.g., "Competitive base salary, incentive compensation which may include profit sharing schemes, retirement savings plan and the ability to participate in an Employee Stock Ownership Plan (“ESOP”)" etc. That's benefits/financial rewards. We'll include in Benefits. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must not include cookie/navigation/legal/EEO etc. We must output only HTML fragment. Let's craft:

About the role

Airbus is seeking an Entry-Level Software Engineer to design, refine, and maintain desktop ground‑control applications that operators use to fly cutting‑edge unmanned aircraft systems (UAS). You will work on the Airbus Helicopters Flexrotor Program, a sophisticated small tactical unmanned aerial system (STUAS) with vertical take‑off and landing (VTOL) used for ISTAR missions. The position is based in Bingen, WA (80% onsite, 20% remote) with minimal domestic/international travel (≈5%). You must be a US Person under ITAR (U.S. citizen, green‑card holder, or covered under existing ITAR license) and meet the physical requirements for occasional lifting/carrying up to 30 lbs, sitting, standing, walking, etc. This role offers the chance to build user‑facing interfaces, work close to hardware, and translate real‑time telemetry into actionable visual tools.

Responsibilities

• Develop and maintain desktop applications (C++/C#) that serve as the operator‑facing interface to ground control and aircraft systems.
• Implement and refine UI/UX elements to make complex system data clear and actionable for operators.
• Debug and resolve application issues reported by internal users/operators.
• Write unit and integration tests to ensure application reliability.
• Collaborate with systems/network and embedded engineers to integrate data feeds (telemetry, network/health status, sensor data) into the application layer.
• Participate in code reviews and follow established software development practices.
• Document application features, known issues, and usage guidance for operators and internal teams.

Requirements

• Bachelor's degree in Electrical Engineering, Computer Engineering, Computer Science, or a related field.
• Minimum of six (6) months experience programming in C++ and/or C# (coursework, personal, or academic projects).
• Basic understanding of object‑oriented programming principles.
• Ability to debug and troubleshoot application‑level issues.
• Ability to translate functional requirements into working application features.
• Demonstrated project experience (school, internship, or personal) building a functioning application.
• Ability to document code and application behavior clearly for teammates.
• Comfortable asking questions and incorporating feedback from senior engineers and operators.

Skills

• Coursework or projects involving UI/UX design or human‑computer interaction.
• Experience with Windows desktop application frameworks (e.g., WPF, WinForms, MFC, or similar).
• Personal, academic, or internship projects involving a graphical user interface.
• Exposure to real‑time or data‑driven applications (dashboards, monitoring tools, games, simulations).
• Familiarity with WPF, WinForms, or similar Windows UI frameworks.
• Basic UI/UX design sensibility – layout, usability, clarity of information display.
• Exposure to multithreaded or event‑driven programming.
• Interest in or aptitude for designing interfaces that simplify complex information for end users.
• Ability to work through ambiguous requirements with guidance from senior engineers.
• Ability to gather and interpret user feedback (from operators) to inform application improvements.
• Basic familiarity with UI/UX design tools or principles (e.g., Figma, wireframing basics) – nice to have, not a deal‑breaker.
• Exposure to telemetry/data visualization libraries or techniques.

Benefits

• Competitive base salary
• Incentive compensation which may include profit sharing schemes
• Retirement savings plan
• Ability to participate in an Employee Stock Ownership Plan (ESOP)
• Paid time off including personal time, holidays, and generous paid parental leave program
• Comprehensive insurance coverage: medical (traditional and high‑deductible health plans), prescription, dental, vision, life, disability
• Employee Assistance Program (EAP)
• Other supplemental benefit coverages
• Flexible Spending Accounts
• Health Savings Accounts
• Basic & Voluntary Life and Accidental Death & Dismemberment insurance
• Short‑ and Long‑term Disability insurance
• 401(k)
• Tuition Assistance
• Bonus(es) subject to performance criteria

Pay

Salary range based on the required profile: $116,000 to $178,000 per year. Actual minimum and maximum may vary based on geographic differential. Individual pay is based on skills, experience, and