Senior Flight Software Platform Engineer
Leads the platform layer of flight software for HyPrix's low-cost missile systems, giving flight applications a deterministic runtime for tasks, timing, messaging and health on an RTOS and real-time embedded Linux. Core tech: C/C++, RTOS integration (FreeRTOS/VxWorks/Zephyr etc.), PREEMPT_RT Linux, Yocto, and DO-178C-style traceability.
- Compensation
- Not disclosed
- Location
- Bengaluru, India
- Work setup
- Not specified
- Seniority
- Senior
- Employment
- Not specified
- Experience
- 2+ years
- Category
- Devops
- Posted
Skills
Must have
- Strong C and C++ in a safety subset such as MISRA C or MISRA C++
- Unit tests, static analysis, code review, Git and CI pipelines
- Production work with FreeRTOS, VxWorks, INTEGRITY, ThreadX, Zephyr or RTEMS, with kernel configuration and a port onto a new board
- Embedded Linux: kernel configuration, device trees, U-Boot, Yocto or Buildroot, systemd and cgroups on ARM SoCs (NVIDIA Jetson, NXP i.MX 8, Zynq UltraScale+)
- Real-time Linux: PREEMPT_RT, SCHED_FIFO and SCHED_DEADLINE, CPU isolation, IRQ affinity, memory lock; latency measurement with cyclictest, ftrace and perf
- Deep knowledge of priority inversion, priority inheritance, lock-free queues and interrupt-safe design
- WCET measurement and schedulability analysis for rate-monotonic or cyclic-executive designs; latency/jitter measurement with GPIO toggles and a scope
- Software layers above a BSP on Cortex-M, Cortex-R or Cortex-A processors; static memory design, stack analysis and MPU configuration
- Test of embedded software in SIL and HIL setups
- Debug with JTAG or SWD probes, gdb, RTOS-aware and trace tools; Linux debug with ftrace, trace-cmd, LTTng, perf and kernel logs
- Technical leadership: clear design documents, design reviews and guidance of other engineers
- Bachelor's degree in electronics, electrical, computer engineering or computer science
Nice to have
- 4-6 years of real-time embedded software development, with 2 years on RTOS integration or flight software infrastructure (preferred, not mandatory — demonstrated capability matters more)
- Experience with NASA core Flight System (cFS), JPL F Prime (F´) or PX4 internals (uORB, parameters, ULog)
- Experience with ARINC 653 partitions on VxWorks 653, INTEGRITY-178 tuMP, PikeOS or Deos
- Knowledge of DO-178C, DO-331 or IEC 61508 at a high software level
- Experience with multicore WCET analysis and AMP designs
- Experience with Linux and an RTOS on one SoC, with OpenAMP and RPMsg, or with Xenomai
- Experience with Linux kernel drivers, real-time kernel patches, or DDS and ROS 2 on real-time Linux
- Knowledge of MIL-STD-1553 or MIL-STD-1760 bus schedules, and of FACE or MOSA standards
- Experience with Rust, and with Python for code generators and analysis tools
- Experience on a UAV, missile, launch vehicle or aircraft programme through first flight
Full description
Who Are We?
At HyPrix, we're building attritable payload delivery systems for autonomy. Things that fly fast, we're enabling them with conscious software. Replicating the capabilities of expensive conventional frontline systems, we're building the cheapest micro and cruise missile systems on the planet. Built for a war of attrition, built for the era of software-defined warfare, built to cater to the front lines of battlefields where no man should stand in the future.
Learn more about us:
What You’ll Do
The Senior Flight Software Platform Engineer leads the platform layer of the flight software. This layer gives each flight application a deterministic runtime for tasks, time, messages, health and records, on the aircraft and in SIL. The platform runs on the RTOS of the flight computer and on real-time embedded Linux.
The position holder sets the platform architecture with the Head of Avionics Software. Drivers, the BSP, control laws, flight modes, fault reactions and the air-to-ground link are not in the scope of this role.
- RTOS ownership. Select the RTOS with the Low-Level team against determinism, certification evidence, memory protection and licence terms. Configure the kernel, port it onto the BSP. Control the RTOS version, vendor patches and known errata.
- OS abstraction layer. Design and maintain the OSAL for tasks, mutexes, queues, timers and memory pools, with ports for the RTOS, Linux and a host PC. Block direct RTOS calls outside the OSAL in CI.
- Real-time Linux. Set the real-time design for each Linux target: PREEMPT_RT kernel options, CPU isolation, IRQ affinity, thread priorities, and SCHED_FIFO and SCHED_DEADLINE policies. Measure the worst-case latency with cyclic test under full load.
- Embedded Linux platform. Set rules for the process model, IPC, supervision and sandbox. Agree the boot chain, kernel configuration, device trees, Yocto images and A/B updates with the Low-Level team.
- Component framework. Build framework for flight applications, cFS-class or F´-class. Define the component model, templates and code rules. Define wrapper that runs model-generated code (Simulink Embedded Coder or SCADE) as a scheduled component.
- Task architecture and time budgets. Define the task set, rates, priorities and core allocation, and the interrupt priority map. Measure the latency and jitter from sensor input to command output, and agree the limits with the GNC team.
- Deadline monitors and instrumentation. Add a deadline monitor to periodic tasks, and report each miss to the health framework. Add built-in measurement of execution time, CPU load, stack high-water marks and queue depth, and trace capture for test builds.