Get more replies from employers
Send a job-specific resume in minutes.
Clausal is building terrain-referenced navigation that operates when GNSS is unavailable, using vision as the primary sensor and embedded hardware for deployment. You will design and train neural networks central to the navigation stack, aiming for robust absolute geolocation from a cold start and maintaining lock through challenging terrain.
The role is hands-on with a high bar for performance in real-world, constrained hardware.
Why this role exists
GNSS jamming and spoofing are now standard electronic warfare. From active theatres in Ukraine to Baltic shipping lanes to civilian airspace over Northern Europe, satellite navigation can no longer be treated as reliable infrastructure. Operators launch knowing the fix and the control link will degrade within minutes.
Most autonomous systems assume GPS is available. We assume it is gone.
Clausal builds terrain-referenced navigation that delivers bounded absolute position without GNSS. Multimodal sensor inputs are fused with inertial sensing to bound drift over long distances and difficult terrain. It runs on microcontroller hardware, at SWaP levels that fit platforms from small drones upward, and is designed from inception for mass production.
This is defence and dual-use work. The same stack goes onto multiple platform classes, from small uncrewed aircraft upward, all of it in contested environments.
We’re a twenty-five head strong team in Helsinki. Clausal was founded by Tatu Ylönen, inventor of the SSH protocol, who built and took public SSH Communications Security and holds patents across AI, cybersecurity and aerospace. Engineering is led by Eero Jyske, who led the engineering scale-up at ICEYE as VP Software, was VP of Engineering at AlphaSense before that, and spent a decade in embedded engineering at Nokia. You'd work with both of them directly.
The team spans mathematics, machine learning, embedded software, hardware, systems engineering and supply chain: the disciplines it takes to ship serious autonomy on serious hardware. We've built at scale before, and we know the difference between a prototype and a deployable product.
You’ll be part of the team designing and training the neural networks at the centre of the navigation stack, the models that tell an aircraft where it is on the earth, with vision as the primary sensor and no prior fix to bootstrap from.
This is not SLAM. Relative pose is the easy half. The hard problem is absolute: acquiring geolocation from a cold start with no external aiding, then holding position against terrain for the duration of the mission, fused across vision and other onboard sensing. Then fitting all of it inside the memory and cycle budget of a microcontroller.
Positioning is where the work starts. It is not where it stops.
The role is deeply hands‑on and the bar is high. You’ll own models that ship onto flight hardware and get trusted in the field.
Absolute positioning is the foundation, and a hard enough problem to hold anyone’s attention for a while. It isn’t the whole of what runs onboard, and the roadmap beyond it is substantial.
We’d rather walk through that in person than publish it. What matters here is that how far you move beyond positioning is wide open, and depends on where your interests and judgement take the stack. We’re hiring someone we expect to help decide what comes next, not just execute what’s already planned.
Training runs on our own compute in Finland, under EU jurisdiction. Training, synthetic data generation, evaluation and stress testing happen in‑house, alongside a simulator and digital twin. No training data leaves European jurisdiction. That’s the architecture, not a compliance workaround.
64× NVIDIA B200 / 16× A100 / 5,000+ CPU cores / 15+ PB storage / 400G internal fabric.
You won’t be waiting on cloud credits or sharing compute with anyone else.
Finland. Snow‑covered terrain, low sun angles, dense canopy, extended low light, Arctic winter. Conditions most programmes treat as edge cases are our default test environment. The feedback loop runs from architecture to embedded target to field performance in a Finnish winter. If it works here, it works where it needs to.
Vision is the sensor of last resort. When the satellites are jammed and the link is gone, the model you built is what tells the aircraft where it is. Very few people get to work on absolute geolocation under this kind of constraint, and fewer still get to watch it fly.
The problem is real. The team is still small enough that early engineers shape what it becomes.