FAST Labs Hardware Engineering Lead

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Remove boilerplate like EEO, legal, etc. Also remove application instructions. Must preserve all substantive info. We need to parse the job description and extract sections. Let's identify content: - Intro about FAST Labs: description of organization, vision, principles, mission campaigning, etc. This could be "About the role" or maybe "About the role" is generic; but we can treat as "About the role" or "About the team". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Role description: hardware engineering lead responsibilities: own engineering technical, cost, schedule aspects; lead teams; support business capture; contribute to bid and proposal; hardware engineering technical architecture; drive project-level hardware engineering execution; ensure designs follow best practice; provide hardware engineering input for new business capture; serve as hardware SME on proposal teams; partner with PEM and FMs; ensure hardware R&D activities adhere to appropriate level of R&D processes; drive agile process refinements; capture lessons learned; champion One-Team culture. That's responsibilities. - Requirements: Required Education, Experience, & Skills: Bachelor's degree in engineering discipline and 10+ years progressive experience; Active DoD Secret clearance; 8+ years hands-on hardware design experience; 2+ years experience leading hardware engineering teams; experience supporting business development activities; proven ability to build, lead, motivate high-performing teams; excellent communication skills; proficient in cross-functional collaboration and customer engagement; commitment to continuous learning, innovation, thought leadership. - Preferred Education, Experience, & Skills: Experience with cutting-edge engineering techniques (Model-Based Engineering, Agile, Digital Engineering); expertise in one or more critical areas: RF Systems, Signal Processing, Algorithm Implementation, Advanced Computing, EO/IR Imaging, Optical Engineering, Laser Systems. - Pay Information: Full-Time Salary Range: $149603 - $254317. Also note about market pay structures. - Benefits: Employee Benefits: health, dental, vision insurance; HSAs; 401(k); disability coverage; life and accident insurance; employee assistance program; legal plan; perks discounts; leave programs: PTO, paid holidays, paid parental, military, bereavement, sick leave; recognition program; other incentives. - Schedule: Because of need for consistent in-person collaboration, will be performed full-time on site. This means work will be conducted on location at a BAE Systems facility 100% of the time. So schedule: full-time on-site. - About the role: maybe the introductory paragraph about FAST Labs vision, mission campaigning, etc. Could be "About the role" or "About the team". We'll include "About the role" with that content. We must not include headings with filler text. Ensure we have substantive content for each. We must not repeat job title as heading. No Job ID. We must output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Preferred Qualifications

maybe "Qualifications" heading? The instruction list includes Qualifications as a possible heading. We have Required and Preferred. Could combine under Requirements and Qualifications? But we have separate sections: Required Education, Experience, & Skills; Preferred Education, Experience, & Skills. We could map Required to "Requirements" and Preferred to "Qualifications". Or we could have both under Requirements and Qualifications. Let's follow: Requirements for required; Qualifications for preferred. Thus:

Requirements

... required items

Qualifications

... preferred items

Skills

maybe not needed if we covered skills in requirements/qualifications. But we could include a Skills section summarizing technical skills: hardware design, leadership, etc. However we already have those. To avoid thin sections, maybe we omit Skills if content already covered. But we could still include Skills if we have specific skill list: e.g., hardware engineering, cross-functional collaboration, communication, etc. However those are already in requirements. To keep substantive sections, we could include Skills with the list of technical expertise areas (RF Systems, Signal Processing, etc.) but those are in preferred. Might be redundant. Better to have: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if we have content for each. - About the role: intro about FAST Labs, vision, mission campaigning, etc. - Responsibilities: list of duties. - Requirements: required education/experience/clearance etc. - Qualifications: preferred experience/skills. - Benefits: employee benefits. - Pay: salary range. - Schedule: full-time on-site. Now we need to ensure we don't include boilerplate like "Please note: This range is based on our market pay structures..." That's part of Pay info, we can keep it as prose. We must not include EEO/legal etc. The text includes "This position will be posted for at least 5 calendar days..." That's boilerplate; we should remove. Also "About BAE Systems Electronic Systems" is a description of the company; could be considered part of About the role? Might be considered boilerplate but it's substantive about the company. Might keep as part of About the role? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About BAE Systems Electronic Systems" is not exactly boilerplate but could be considered company overview; it's okay to keep. However it's fairly generic; but we can include as part of About the role. We need to preserve ALL substantive information; do not invent or summarize away detail. So we should keep the company overview. Thus About the role could contain two paragraphs: FAST Labs description and BAE Systems overview. Now we need to format lists. Let's extract exact sentences. About FAST Labs: "FAST Labs™ is a world-class research and microelectronics production organization. Our vision, we secure the future through fearless innovation, fuels our curiosity, and propels our teams to take on ‘never been done before’ challenges. We believe how we work is just as important as what we work on, and we are guided by three key principles: We are one team who embraces the power of learning and collaboration; We innovate for impact; and Our innovation is multidimensional. Sitting at the heart of BAE Systems Electronic Systems (ES), FAST Labs provides the next generation of technology across ES’s defense and commercial portfolios. We seek to turn groundbreaking research and partnerships into real-life impact for our customers, as we develop advanced capabilities in advanced electronics, EW, sensors and processing, AI, autonomy, RF, EO/IR, cyber, and more. We value internal and external partnerships and collaborate across a broad innovation ecosystem that includes DOW and research teams, universities, small businesses, and venture firms/accelerators – all in service of developing advanced technologies to enable our nation’s warfighting mission needs. To help drive even greater impact for our business and our customers, FAST Labs has embarked on a strategy of Mission Campaigning. Mission Campaigning is a holistic mindset and approach to technology/product conceptualization and prioritization. It involves a continuous focus on a definitive path to drive from early science to end‑user capability to solve a war fighter problem and deliver a product/capability as quickly as possible to fielding and scaling. Campaigns include the creation of new markets and business models, if necessary to deliver the product/capability. It is similar to what entrepreneurs call a “go to market strategy”. As part of this pivot to Mission Campaigning, FAST Labs Sensing Technologies (ST) is seeking project hardware engineering leads who understand how lead a team of project engineers through the dynamics of research and development (R&D) programs, and transition technology to the business." That's a lot; we can keep as prose. Then maybe a second paragraph about BAE Systems: "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." We can include that as part of About the role. Now Responsibilities: list of duties from the role description after the intro. Let's extract bullet points: - As a hardware engineering lead, you’ll have opportunity to own the engineering technical, cost, and schedule aspects of our projects with the freedom to lead and shape teams consisting of talented electrical, mechanical, optical, as well as firmware engineers and designers. - You will lead teams on research, development, and consulting projects requiring deep expertise in hardware engineering principles and practices to achieve project goals. - The FAST Labs Sensing Technologies (ST) product line develops next-generation lasers, precision optical pointers, advanced multi-model (RF & EO/IR) seekers, expendables and underwater sensors. ST has established itself as a market leader in the development of EO/IR, RF and Acoustic technologies applicable to Army, Navy, Air Force and Space Force missions. (This is more about product line; maybe part of About the role.) But responsibilities continue: - In this role you will be the senior technical leader on research and development projects within our FAST Labs organization. - You will support business capture by contributing to bid and proposal activities, as well as providing hardware‑engineering technical‑architecture expertise, and driving project‑level hardware engineering execution. - Ensure designs follow best‑practice engineering methods - Provide hardware‑engineering input for new‑business capture – influence technical baselines, develop cost estimates, identify technical risks, and suggest mitigation strategies - Serve as the hardware subject‑matter expert on proposal teams, helping shape technical scopes and pricing models - Partner with Product Engineering Management (PEM), and Functional Managers (FMs), to identify, prioritize, and fill staffing requirements on your hardware development projects - Ensure all hardware R&D activities adhere to an appropriate level or research and development processes and are well matched to the scope of the efforts - Drive agile process refinements, capture lessons learned, and champion “One‑Team” culture across your project We can turn each into

. Now Requirements (required): - Bachelor’s degree in engineering discipline and 10+ years of progressive experience in a related field. - Active DoW Secret clearance (should be DoD Secret clearance). We'll keep as "Active DoD Secret clearance". - 8+ years of hands-on experience in hardware design, including laboratory troubleshooting, technical problem-solving, and field testing. - 2+ years of experience leading hardware engineering teams on development programs, including responsibility as a Lead Hardware Engineer and Control Account Manager (CAM). - Experience supporting business development activities, including proposal development and generation of hardware engineering cost and schedule estimates. - Proven ability to build, lead, and motivate high-performing project technical teams. - Excellent communication skills, with the ability to clearly present complex technical information both verbally and in writing. - Proficient in cross-functional collaboration and customer engagement. - Commitment to continuous learning, innovation, and thought leadership. Now