Hardware Reliability Engineer

Join Zipline, a pioneering company in drone delivery systems. As a Mechanical Hardware Reliability Engineer, you will be responsible for defining and delivering the safety and reliability attributes of our latest drone-delivery systems. Your work will involve early architecture decisions, accelerated tests, reliability models, and verification methods. You will directly shape the long-term reliability and safety of Zipline's autonomous aircraft and ground infrastructure.

• Définir et livrer l'attribut de sécurité et de fiabilité des systèmes de livraison de drones.
• Combiner des connaissances approfondies des phénomènes de défaillance dans les dispositifs électromécaniques, l'expérimentation pratique et la modélisation statistique.
• Posséder la stratégie de fiabilité pour les sous-systèmes mécaniques critiques pour la mission ou les systèmes entiers, en appliquant les principes de conception pour la fiabilité (DfR) et de physique de la défaillance (PoF).
• B.S. or M.S. in Mechanical Engineering, Materials Engineering, or a related technical discipline
• Strong technical communication skills, including the ability to:
• Drive cross-functional alignment on reliability trade-offs and technical decisions around design, supply-chain, quality, manufacturing, finance, and operations
• Write concise, decision-oriented technical documentation; and
• Synthesize ambiguous information into a coherent problem statement
• Experience applying reliability methods such as DFMEA, accelerated-life testing, environmental testing, failure analysis, or life modeling
• Explain complex technical issues clearly
• Demonstrated ownership and practical problem-solving ability, including driving technically complex issues through resolution
• Hands-on experience developing and validating safety-critical electromechanical systems through delivery to customers
• Strong mechanical engineering fundamentals and the ability to reason from first principles about hardware behavior and failure
• Ability to learn quickly, independently develop new technical depth, and adapt as program needs evolve