About Pyka
Pyka’s goal is to provide society with a new form of safe, clean, and cost-effective transportation enabled by autonomous electric aviation.
To get there, we’re taking a different approach than most. We're applying our technologies to every industry where autonomous electric aircraft can be useful, starting with the highest value and most dangerous jobs. In doing so, we're building game-changing products manufactured at scale, while perfecting the safety, reliability, and capabilities of our autonomy engine and electric propulsion systems.
We design, develop and manufacture an ecosystem of technologies including proprietary flight control software, avionics, high power density motors, motor controllers, batteries, and custom carbon-fiber composite airframes.
Today, we supply autonomous electric aircraft for cargo transport and crop protection to real-world customers across four separate continents and have secured industry-first regulatory approvals from the FAA. Our cargo aircraft enables remote connectivity, enhances express delivery networks, and ensures fast and reliable shipping of critical supplies to areas in need. Our crop protection aircraft offers agricultural services providers and farmers an autonomous tool to make aerial application safer, more precise, and less harmful to surrounding environments. Both vehicles are highly economical to operate, easy to deploy, and significantly reduce CO2 emissions in their respective industries.
What you work on at Pyka makes people’s lives better now and brings the future of electric aviation one step closer each day.
Role Overview
Pyka is looking for a software engineer to own the path our software takes from the development branch to the fleet. Issues from the field arrive without regard to subsystem boundaries, so you will work across the full aircraft software stack: autonomy, controls, avionics interfaces, and ground systems. You will decide what ships to the fleet and when, own several aircraft software systems directly, and build the testing and release infrastructure the engineering team relies on.
Much of the role is responding to what comes in: reproducing issues from flight logs, isolating them, and either fixing them or handing the subsystem owner a diagnosed problem with a test case attached. The rest is work you scope yourself out of that same pipeline: adding the regression test that would have caught an issue, instrumenting a subsystem so the next occurrence produces usable data, or automating a release step that a person currently does by hand.
Some of the current and future projects you will likely contribute to include:
Expanding our automated test infrastructure that gates every release, including hardware-in-the-loop tests, simulation-based regression suites, and log replay against real flight data
Developing tooling to aid in triaging, bug reproduction, and root cause analysis
Improving our six-week release cadence, including release tooling, versioning, artifact distribution, release notes generation, and staged rollout across a growing fleet
Maintaining and improving core aircraft software systems such as logging and telemetry, configuration management, health monitoring, and over-the-air software distribution
Adding observability to parts of the aircraft that are currently difficult to debug after the fact
