About the role
You make the same promise hold across Windows and Linux, where the platform details decide whether the thing is reliable and trustworthy. Much of this is making complex software work for people who are not administrators and should not have to be.
The work
Build installation, service lifecycle, device integration, permissions and updates for supported Windows and Linux configurations. Work with inference and security engineers on accelerator access and protected credentials. Test differences rather than promising identical behavior everywhere.
What good looks like
In your first 90 days, deliver a supported installation and upgrade path on one target platform with diagnostics and recovery.
Evidence we look for
Bring substantial experience on Windows or Linux and a willingness to learn across boundaries. Show how you have made complex software reliable for people who are not system administrators.
What we need to see
- Substantial Windows or Linux engineering experience
- Willingness to learn across the boundary rather than staying on one side
- You have made complex software reliable for non-technical users, and can describe how
- You handle packaging, updates and permissions as product problems
Nice to have
- Both platforms
- Driver, service, or systemd-level work
- Enterprise deployment tooling
The exercise
Design a migration that preserves the user's vault and permissions when an operating-system or driver update changes behavior.
Where and how we work
In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.