Serious Work for Serious Engineers
We are small and deliberate. We hire engineers who want working systems, clear ownership, and technical problems with consequences. The work spans mission systems, modeling and simulation, aircraft software, open systems, telemetry, sensor-adjacent systems, and secure infrastructure.
What the work looks like
You may work on aircraft display software, simulation tools, telemetry paths, RF and sensor-adjacent systems, secure software delivery, open-system interfaces, or infrastructure that supports controlled engineering environments.
The work is rarely isolated. Software touches requirements, hardware, data flows, test seams, authorization paths, customer reviews, and fielded constraints.
This is supported by current Polyrhythm work and personnel history across flight-test telemetry, aircraft display architecture, engine controller firmware, mission-level simulation, RF sensor hardware, secure development environments, and simulation and visualization systems.
Building careers, not just jobs
Small teams. Real programs. Working code.
You work close to the system: program offices, primes, secure environments, test constraints, hardware, models, and users who need the software to hold up beyond the demo.
We protect focus time, direct communication, and sustainable pace. Heroics are not a process. Strong engineering over the life of a program matters more than one dramatic push.
Where you fit
Builds under guidance, learns the domain, and ships real program work.
Owns components end to end, communicates tradeoffs, and carries delivery through integration.
Sets technical direction across a program area and makes complex systems easier to build, test, and change.
Shapes architecture, resolves hard tradeoffs, and leads the technical path when the problem has no clean precedent.
Years are rough guides. Scope, judgment, domain depth, and customer constraints matter more than title mechanics.
This may not be for you
You may not enjoy Polyrhythm if you want only clean greenfield work, prefer demos over durable systems, avoid ambiguous problems, or do not want to work within customer, security, or program constraints.
The work rewards people who can reason from evidence, communicate tradeoffs, and stay with a problem until the system is usable.
Simple and streamlined
- 01Intro Call
A short conversation about your background, what you want to work on, and whether the role fits.
- 02Technical Discussion
A working conversation with engineers about how you build, reason, and communicate tradeoffs.
- 03Problem Interview
A deeper session on problems similar to the work you would own. No trick questions.
- 04Offer
A clear offer with no games. We move quickly once we know there is a fit.
Before you apply
Is the work remote or on site?
Mostly remote, with role-dependent on-site work for customer meetings, integration events, secure environments, or lab work. Dayton and Wright-Patterson proximity matter for some roles.
What is the employment type?
We hire both W-2 employees and 1099 contractors depending on the program and the role.
Do you require a security clearance?
Some roles do. Where a clearance is required it is stated in the posting, and we sponsor when the program supports it.
How do you use open source?
We use and contribute to open source when it serves the work and the customer environment allows it. Some code can be public. Some cannot. The standard is the same either way: clear ownership, governed dependencies, repeatable builds, and reviewable artifacts.
What tools and languages do you use?
It depends on the role. We work across mission systems software, modeling and simulation, aircraft software, secure infrastructure, open systems, telemetry, and sensor-adjacent systems. Specific tools and languages belong in the role description, not the company identity.
Open roles
All current openings live on our job board. If nothing fits today, send us a note and tell us what you would rather be building.