Calculate before you buy.
Design points are chosen from disclosed calculations and manufacturer data, not from preference. Assumptions are written down and labelled as assumptions.
Open Role
Software and Integration Engineer
Kanatir Kinetics designs uncrewed aircraft and the mission software that runs on them. The work is engineering that has to survive contact with real hardware, real power, real timing and real field conditions, and be documented well enough that someone can check it.
The Role
Software and Integration Engineer
Pipeline performance on constrained compute, and the integrity controls that run alongside it.
Making a containerized streaming pipeline run, and run fast enough, under real constraints on edge-class compute. You would instrument every stage from ingestion through feature extraction, fusion, detection and explanation, then measure per-stage and end-to-end latency, throughput, memory and compute under defined multimodal load.
The interesting part is the diagnosis: separating what is tunable from what is architectural, correcting the first, and documenting the second accurately rather than quietly.
The role also covers the integrity side of the same pipeline. Cryptographic signing and chain anchoring on an append-only, hash-chained audit record. Authenticated-source and trusted-time handling in an ingestion path that must fail closed on anything it cannot verify. Correct ordering and consistency when more than one writer records at once. Verification is by tamper and replay testing, where altered, reordered or lost records must be detectable.
What we need
- Strong Python, in a streaming or event-driven architecture.
- Containerization, and enough Linux to profile a system properly rather than guess at it.
- Track record getting software onto constrained compute.
- Applied cryptography in production: signing, hash chains, key handling.
- Understanding of fail-closed design, and why it is harder than it sounds.
- The instinct to profile before optimising, and to re-measure after every change.
- Judgment about dependencies. Every external library added to a sovereign-controlled system is a decision that needs defending.
What this is not
Not a greenfield build. The architecture exists, it is versioned, and its interfaces are deliberate. We want someone who will read it properly, challenge it where it is wrong, and work within it where it is right.
How We Work
What the engineering discipline looks like.
Test before you claim.
Nothing moves from estimate to specification without bench, ground or flight evidence, and the evidence is retained with the result.
Report what failed.
Negative results are recorded as they happened. A system that hides its own weak points cannot be trusted with anyone else's decisions.
Apply
Apply for a role.
Choose the role, tell us what you have built, and attach your CV. We read every application and reply either way.
Security notice
Do not submit classified, controlled, export-restricted or sensitive operational information through this form. Send only unclassified, releasable details. For sensitive discussions, request a briefing and we will arrange an appropriate channel.
Prefer email? Reach us at [email protected].