Senior Embedded Security Engineer, Flight Software

Required

• Strong candidates tend to arrive from one of two directions: embedded systems engineers who moved into offensive security, or hardware and firmware security researchers who can write and review production C/C++. Real depth on both sides is rare and we are not expecting it on day one. Tell us which side you come from.
• A good candidate will have:
• 5+ years of hands-on experience across embedded systems security, hardware security, or offensive security against firmware and embedded targets
• Hands-on offensive hardware experience on real boards, including side-channel analysis, voltage or clock glitching, electromagnetic fault injection, chip desoldering and rework, and decapping
• Practical experience attacking embedded debug and bus interfaces (JTAG, SWD, UART, SPI, I2C), including sniffing, injection, and firmware extraction
• A track record of independently discovering, validating, and root-causing vulnerabilities in embedded systems, firmware, or hardware
• Firmware reverse engineering across common embedded architectures, using tools such as Ghidra, IDA, or binwalk
• Solid grounding in exploitation fundamentals on constrained targets: memory corruption, exploit primitives, the mitigations you will run into, and escalation toward full system control
• Experience building your own tooling rather than only running off-the-shelf tools: coverage-guided or protocol fuzzing harnesses (AFL++, libFuzzer), emulation-based rigs (QEMU, Unicorn), test fixtures, and bench instrumentation
• Experience analyzing protocols, wired or wireless or proprietary, and reasoning about both design and implementation weaknesses
• Strong C/C++ skills with deep understanding of memory safety and secure coding practices, sufficient to review flight software at the source level
• Working understanding of hardware root of trust and secure boot, whether from implementing them or from breaking them