Staff Electrical Engineer, Hardware Test

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, navigation, etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes compensation: "$185,000 - $275,000 a year" and details about compensation based on location, bonus, benefits, equity, temporary employee package. So we have Pay and Benefits info. Also schedule? Not explicitly mentioned; it's full-time regular employee offer package. It mentions "Full-time regular employee offer package". That implies schedule: full-time. So we can include Schedule section with "Full-time". Benefits: mention "Bonus + Benefits + Equity" and "temporary benefits package (applicable after 60 days of employment)". Also mention "Military fellows and part-time employees are not eligible for benefits." So we can include Benefits section summarizing: bonus, benefits, equity, temporary benefits after 60 days, etc. We need to include About the role: maybe a brief description from first paragraph? The job description includes mission etc. We can put About the role: description of Shield AI mission and role overview. Must not repeat job title. Use prose

. Responsibilities: list from "What you'll do:" bullet points. Use

• . Requirements: maybe "Required qualifications:" list. Use
  • . Qualifications: maybe "Preferred qualifications:" list. Use
    • . Skills: maybe we can extract skill statements from responsibilities? But we could combine required and preferred as qualifications; skills maybe not needed if no explicit skills list. The instruction says prefer few substantive sections over many thin ones. We could combine Required and Preferred into Qualifications? But they ask to use headings for Requirements, Qualifications, Skills. We need to decide which sections have content. We have Required qualifications (list) and Preferred qualifications (list). Could treat Required as Requirements, Preferred as Qualifications. Skills maybe not explicitly listed; we could omit Skills section if no specific skill list beyond those already covered. However we could extract skills like "power electronics, analog and digital design, RF and communications, instrumentation, data acquisition, control systems, signal integrity, grounding, or system safety" etc. Those are part of required qualifications. Might be better to put them under Requirements. Skills section could be omitted. Benefits: we have info. Pay: we have salary range. Schedule: we have full-time. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include headings with filler. Ensure each heading has substantive content. Now craft HTML. We need to preserve all substantive information; do not invent or summarize away detail. Must not omit details like specific bullet points. Must include all bullet points from responsibilities, required qualifications, preferred qualifications, benefits, pay, schedule. We must not include boilerplate like EEO, legal, navigation, social media links, etc. Also remove "Follow Shield AI on LinkedIn , X , Instagram , and YouTube ." and "For more information, visit www.shield.ai". Also remove "Job Description:" line maybe but we can keep content. We must not include "Direct people management is not required." That's substantive; include in responsibilities maybe. We must not include "What Success Looks Like" bullet points; those are also substantive; could be part of responsibilities or separate? Could be included under Responsibilities as they describe success metrics. But we already have responsibilities list; we could incorporate those as part of responsibilities or maybe as a separate section "What Success Looks Like". However headings limited to given list; we could put them under Responsibilities as additional bullet points. But we must not lose detail. So we can merge them into responsibilities list. Similarly "What you'll do:" list is responsibilities. We need to include all bullet points from both "What Success Looks Like" and "What you'll do:" as responsibilities. Let's extract responsibilities bullets: From "What Success Looks Like": - Create a coherent test-equipment architecture and roadmap that closes the program's highest-risk verification gaps and supports development, qualification, and recurring test needs. - Standardize reusable electrical, software, data, safety, calibration, and documentation patterns that shorten delivery time without weakening rigor. - Increase equipment reliability, diagnosability, maintainability, and utilization while reducing recurring failures, manual interventions, and one-off designs. - Raise the quality of aircraft requirements and interfaces by making testability, observability, fault isolation, and verification strategy explicit early in design. - Develop senior technical talent and create durable practices that allow the organization to deliver more capability through the team rather than through individual heroics. From "What you'll do:" (each line ends with period): - Own the technical strategy, architecture, and roadmap for electrical test equipment supporting X-BAT avionics, power, communications, actuation, and other aircraft subsystems. - Identify program verification risks and capability gaps; convert them into prioritized investments, platform decisions, development plans, and clear technical ownership. - Define common architectures for racks, stands, interface units, power and fault insertion, instrumentation, data acquisition, timing, automation, diagnostics, and operator interfaces. - Lead the most complex or novel test-equipment programs through requirements, trade studies, architecture, detailed design, build, integration, acceptance, deployment, and sustainment. - Set and uphold engineering standards for schematics, PCB and harness design, calibration, documentation, and release readiness. - Establish system-safety expectations for energized test equipment, including hazard analysis, safe-state design, interlocks, isolation, emergency stops, access control, and verification of protective functions. - Chair high-consequence architecture, design, and readiness reviews; make or drive closure on cross-domain technical decisions and unresolved risks. - Partner with systems and design engineering to define testable requirements, electrical interfaces, built-in observability, fault isolation, and verification approaches before aircraft designs are released. - Develop strategies for equipment reliability, availability, maintainability, calibration, obsolescence, spares, vendor support, and recovery from failures during critical test campaigns. - Lead cross-functional root-cause investigations that span test equipment, units under test, software, facilities, manufacturing, and supplier processes; ensure corrective actions improve both products and test capability. - Make informed build-versus-buy decisions and provide technical direction to vendors, integrators, technicians, and partner teams delivering portions of the test ecosystem. - Define and use meaningful operating metrics such as first-pass acceptance, schedule predictability, equipment uptime, test repeatability, recurring anomalies, action closure, and reuse of proven designs. - Mentor senior and developing engineers, delegate architecture and project ownership effectively, and improve the quality of technical reasoning and review across the organization. Also earlier: "You will be the technical authority for a portfolio of electrical test capabilities rather than a single stand or project. You will establish common architectures, engineering standards, safety practices, and lifecycle expectations; align capability roadmaps with program risk and verification needs; and lead the most ambiguous or consequential test-equipment efforts from concept through deployment. Your influence will extend into aircraft design through design-for-testability, interface definition, reliability learning, and closed-loop corrective action. This is a hands-on staff individual-contributor role with broad organizational reach. You will remain close to schematics, code, hardware, and lab operations while multiplying the effectiveness of other engineers through architecture, reviews, mentorship, reusable platforms, and clear technical decisions. Direct people management is not required." These are also responsibilities; we can incorporate them as prose or bullet points. Probably better to include them as part of responsibilities prose or bullet list. Since we already have a bullet list, we could add these as additional bullets. Now Required qualifications list: - B.S. in Electrical Engineering or a related STEM discipline, or equivalent practical experience. - 8+ years of relevant industry experience developing complex electrical hardware, automated test equipment, or multidisciplinary verification systems. - A record of leading multiple hardware development cycles and delivering equipment or products from ambiguous requirements through release, deployment, and sustained use. - Deep expertise in several relevant domains, such as power electronics, analog and digital design, RF and communications, instrumentation, data acquisition, control systems, signal integrity, grounding, or system safety. - Demonstrated ability to architect systems that span custom electronics, commercial instruments, harnessing, embedded control, automation software, mechanical equipment, and facility interfaces. - Strong command of requirements decomposition, interface control, verification planning, design reviews, configuration management, acceptance testing, and technical documentation. - Experience establishing technical standards or reusable platforms and influencing teams beyond direct project authority. - Demonstrated success resolving complex cross-domain failures using data, first-principles reasoning, structured root-cause analysis, and disciplined corrective action. - Ability to communicate technical decisions, risks, and tradeoffs clearly to engineers, operators, program leaders, and executives. - A record of mentoring engineers, raising technical quality, and delivering exceptional outcomes in a fast-moving environment. Preferred qualifications list: - Experience architecting aerospace or defense ground-test, qualification-test, hardware-in-the-loop, or production-test systems for flight-critical hardware. - Experience across several aircraft electrical domains, including high-voltage or high-power systems, batteries, motors and drives, RF, avionics networks, sensors, flight controls, or mission systems. - Experience scaling a test capability from early prototype equipment to configuration-controlled platforms used across multiple teams, sites, or product phases. - Experience applying safety and reliability methods such as hazard analysis, FMEA, fault-tree analysis, proof testing, fault insertion, redundancy, and safe-state verification. - Knowledge of environmental and qualification testing such as thermal, vibration, shock, HALT, HASS, ESS, EMI or EMC, and the controls and instrumentation required to execute it well. - Working knowledge of standards such as DO-160, MIL-STD-810, MIL-STD-461, IPC, IEEE, NFPA 70E, or equivalent standards relevant to prior work. - Experience with calibration systems, measurement uncertainty, metrology, data traceability, equipment cybersecurity, or regulated lab and production environments. - Experience developing capital-equipment plans, managing technical suppliers or integrators, and balancing capability, schedule, cost, and lifecycle risk. - Eligibility to obtain a U.S. security clearance if required by the program. Now Benefits: from text: - Full-time regular employee offer package: Pay within range listed + Bonus + Benefits + Equity - Temporary employee offer package: Pay within range listed above + temporary benefits package (applicable after 60 days of employment) - Military fellows and part-time employees are not eligible for benefits. Also maybe mention "Bonus + Benefits + Equity". So we can summarize Benefits: bonus, benefits (health etc unspecified), equity, temporary benefits after 60 days, etc. We must not invent details beyond what's given. So we can list: Bonus, Benefits (unspecified), Equity; temporary benefits package after 60 days; note that military fellows and part-time employees not eligible for benefits. Pay: "$185,000 - $275,000 a year". Also note compensation based on location, may vary, actual compensation considers experience, skills, qualifications, internal equity. Also mention "Compensation for this role is based on the position’s work location. The salary range shown reflects the listed location and may vary if the position is based in a different geographic market. Actual compensation will also consider factors such as experience, skills, qualifications, and internal equity." Also "Salary compensation is influenced by a wide array of factors including but not limited to skill set, level of experience, licenses and certifications, and specific work location." Also "All offers are contingent on a cleared background and possible reference check." That's more about offer contingencies; could be included in Pay or maybe separate but we can include in Pay section as notes. Schedule: "Full-time regular employee offer package". Also maybe mention "Full-time". So schedule: Full-time. Now About the role: we can include the introductory paragraph about Shield AI mission and role overview: "Sh