Embedded Software Engineer - All Levels

We need to output HTML fragment with sections: h3 for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role? There's a description: "Lead the future of flight..." etc. That could be "About the role". Responsibilities: bullet list. Requirements: maybe "Required Education, Experience, & Skills". Qualifications: maybe "Preferred Education, Experience, & Skills". Skills: could be combined? But we can separate Required and Preferred as Requirements and Qualifications. Skills maybe not separate. Benefits: there is "What We Offer" includes flexible hybrid work environment and 9/80 work schedule, opportunities for career growth, collaborative team environment, competitive salary and benefits package. Also later "Employee Benefits:" details. So Benefits section should include those details. Pay: there is Pay Information with salary range. Schedule: there is "flexible hybrid work environment and 9/80 work schedule" which is schedule info. So we can have Schedule section. We must not repeat job title as heading. No Job ID. Remove boilerplate like "Thank you for your interest...", "If your background...", "If selected...", "Lead the future of flight..."? Actually that is substantive about role. Keep. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We need to output only HTML fragment, no /, no markdown fences. Let's craft sections:

About the role

Lead the future of flight with BAE Systems! Are you a highly experienced and visionary embedded software engineer seeking a leadership role in a dynamic and innovative environment? At BAE Systems’ Electronic Systems business, within our Controls & Avionics Solutions (CAS) sector, we are dedicated to creating cutting-edge avionics systems that ensure the safety and efficiency of air travel. We’re seeking a talented and motivated Embedded Software Engineers to join our teams in Endicott, NY & Austin, TX developing the next-generation of flight control and related systems. As an Embedded Software Engineer, you will design and develop software for a variety of applications, including Fly-By-Wire Flight Controls, Aircraft Engine Controls, Ground Vehicle Power Management Systems, Aircraft Electrification Systems, Advanced Air Mobility Systems, Autonomous Flight Systems, Flight Deck Systems, Cabin Management Systems, Weapon Control Systems, Electronic Warfare Systems, and Threat Detection Systems. You will work in a collaborative, hybrid environment with mid-size teams, collaborating with Systems, Hardware, Test, and Operations during all phases of the Product Development Lifecycle.

Responsibilities

• Participate in each phases of the software life cycle, including project planning, requirements development, software design/implementation, and integration and test
• Develop software designs and implementations that meet stringent requirements for complex embedded control systems
• Develop software using Green Hills, ARM Development Studio, or other software development environments for embedded targets ranging from PowerPC to multi-core ARM processors
• Use and evolve existing processes to utilize the most effective techniques to minimize design/product cost
• Demonstrate leadership as you mentor your team and interface with customers
• Opportunities are available as a technical collaborator or as a technical leader on the program where you will mentor your team and present the technical design at technical interchange meetings with the customer

Requirements

Bachelor's Degree in Computer Science, Computer Engineering, or related field

4+ years of work experience in embedded software development using C/C++/Assembly languages

Experience with bare metal operating systems (no OS or proprietary RTOS) development, including low-level software development (e.g., device drivers and BSP development)

Alternatively could use ul for list. The instruction: Use

• for any list of duties/requirements/benefits. So for requirements we should use ul. Thus:

  Requirements

  • Bachelor's Degree in Computer Science, Computer Engineering, or related field
  • 4+ years of work experience in embedded software development using C/C++/Assembly languages
  • Experience with bare metal operating systems (no OS or proprietary RTOS) development, including low-level software development (e.g., device drivers and BSP development)

  Qualifications

  • Master's Degree in Computer Science, Computer Engineering, or related field
  • Experience in Embedded real-time operating system development
  • Experience with PowerPC, ARM, x86 processor architectures
  • Hardware/Software integration and debug experience
  • Familiarity with source control systems and configuration management practice
  • Higher-level programming & scripting languages such as JAVA, Python, Matlab & Simulink
  • Familiarity with safety-critical development using DO-178B/C or equivalent stringent process requirements

  Benefits

  • Flexible hybrid work environment and 9/80 work schedule
  • Opportunities for career growth and professional development
  • Collaborative and supportive team environment
  • Competitive salary and benefits package
  • Health, dental, and vision insurance; health savings accounts; a 401(k) savings plan; disability coverage; and life and accident insurance
  • Employee assistance program, a legal plan, and other perks including discounts on things like home, auto, and pet insurance
  • Paid time off, paid holidays, as well as other types of leave, including paid parental, military, bereavement, and any applicable federal and state sick leave
  • Company recognition program to receive monetary or non-monetary recognition awards
  • Other incentives may be available based on position level and/or job specifics
  But note: "Flexible hybrid work environment and 9/80 work schedule" also belongs to Schedule section. However we can keep it in Benefits but also create Schedule section. The instruction: Prefer a few substantive sections over many thin ones. But we need to include Schedule only if posting actually states them. It does state "flexible hybrid work environment and 9/80 work schedule". That's schedule info. Could create Schedule section with that detail. However we already included it in Benefits; maybe better to separate: Benefits section for health etc, Schedule section for hybrid and 9/80. Let's do that. Thus Benefits section will exclude the flexible hybrid work schedule line. We'll keep other benefits. Schedule section:

  Schedule

  Flexible hybrid work environment and 9/80 work schedule

  Pay section:

  Pay

  Full-Time Salary Range: $107,359 - $182,510

  (maybe keep as given). Also include note about determination factors? The posting includes note: "Please note: This range is based on our market pay structures. However, individual salaries are determined by a variety of factors including, but not limited to: business considerations, local market conditions, and internal equity, as well as candidate qualifications, such as skills, education, and experience." That's substantive; we should include it. So Pay section can have p with range and another p with note. We must not include boilerplate like "This position will be posted for at least 5 calendar days..." etc. That's not substantive? It's about posting duration; maybe consider boilerplate? It's not about job. Likely we should remove it. Also remove "About BAE Systems Electronic Systems" paragraph? That's company description; maybe considered boilerplate? It's substantive about company but could be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About BAE Systems Electronic Systems" is not those; it's company overview. Might be considered substantive? It's not about the role directly but could be kept? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's clearly boilerplate like legal/EEO. This is a generic company description; could be considered boilerplate but not explicitly listed. Safer to keep? However many job postings include such generic company description; but the instruction didn't explicitly say to remove company overview. It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we keep it. Thus after Benefits, we could add a section "About BAE Systems Electronic Systems" but we don't have a heading for that; we could use

  About BAE Systems Electronic Systems

  but not in the list of allowed headings? The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list "About BAE Systems Electronic Systems". So we should not create a heading not in list. We could incorporate that info into About the role section? But About the role already has role description. Could add a paragraph after role description about company. That would be substantive and allowed. So we can append that paragraph to About the role. Thus About the role section will have two paragraphs: first the role description, second the company overview. Now we need to ensure we don't repeat any content. Let's compile. HTML:

  About the role

  Lead the future of flight with BAE Systems! Are you a highly experienced and visionary embedded software engineer seeking a leadership role in a dynamic and innovative environment? At BAE Systems’ Electronic Systems business, within our Controls & Avionics Solutions (CAS) sector, we are dedicated to creating cutting-edge avionics systems that ensure the safety and efficiency of air travel. We’re seeking a talented and motivated Embedded Software Engineers to join our teams in Endicott, NY & Austin, TX developing the next-generation of flight control and related systems. As an Embedded Software Engineer, you will design and develop software for a variety of applications, including Fly-By-Wire Flight Controls, Aircraft Engine Controls, Ground Vehicle Power Management Systems, Aircraft Electrification Systems, Advanced Air Mobility Systems, Autonomous Flight Systems, Flight Deck Systems, Cabin Management Systems, Weapon Control Systems, Electronic Warfare Systems, and Threat Detection Systems. You will work in a collaborative, hybrid environment with mid-size teams, collaborating with Systems, Hardware, Test, and Operations during all phases of the Product Development Lifecycle.

  BAE Systems, Inc. is a defense, aerospace, and security company headquartered in Falls Church, Virginia, with more than 40,000 employees worldwide. We serve, supply, and protect those who protect us. As one of the most geographically diverse international defense companies, we deliver a full range of products and services spanning air, land, maritime, space, and cyber, including advanced electronics, intelligence solutions, and dedicated customer support. Our culture is performance-driven and values-led, built on curiosity, creativity, and collaboration. Purpose isn't a tagline here. It's what drives us. We're developing breakthrough technologies that defend national security and make a lasting impact on our communities and our planet. When you join BAE Systems, you're not just building a career. You're contributing to a mission that truly matters.

  Responsibilities

  • Participate in each phases of the software life cycle, including project planning, requirements development, software design/implementation, and integration and test
  • Develop software designs and implementations that meet stringent requirements for complex embedded control systems
  • Develop software using Green Hills, ARM Development Studio, or other software development environments for embedded targets ranging from PowerPC to multi-core ARM processors
  • Use and evolve existing processes to utilize the most