About Kry10

Kry10 is a global technology company providing foundational security across critical embedded and agentic systems. We work with those responsible for critical systems. From the operators to architects to strategic leaders working across critical national infrastructure, healthcare, defense, telecommunications, transportation.

All the people who can’t afford to get it wrong. Our focused and growing team across the USA, UK, Australia and Recent Zealand builds resilience into the critical systems society depends on every day. Our foundations are mathematically proven.

KOS, our operating system based on a formally verified foundation, is built on seL4®, the world’s most highly assured microkernel. We bring mathematical assurance to critical infrastructure, building resilience deep into the technology, right from the foundation. Because critical should mean certain.

Position Purpose The role builds KOS, the tooling and context to make it useful, and prototypes that prove it, so customers can deliver secure, correct systems. The role starts from customer problems, considers experiential, business, and technical trade-offs, and delivers value early and incrementally, preserving the business’s options for what comes next. The role works within the Platform Team to serve its customers: in-market engineering teams, design and business stakeholders, and end-customers.

Key Accountabilities The role builds KOS, the tooling and context to make it useful, and prototypes that prove it, through the following work cycle accountabilities:

Shape

- Prioritize work with an understanding of experiential, business, and technical needs; priorities reflect stakeholder reasoning and customer feedback
- Realize value earlier and incrementally; big projects and features are broken into independently valuable tasks
- Scope and sequence work with engineers, designers,



and leadership; tasks and order are communicated and agreed before build starts and revised collaboratively

Design

- Make decisions which weigh experiential, business, and technical trade-offs; consequential decisions are recorded and communicated, with options and rationale explained
- Articulate designs so others can follow, challenge, and improve them; designs are written, reviewed, and revised in response to challenges
- Mature platform through each feature; contributions add new platform capabilities instead of one-off solutions

Build

- Deliver OS features people can depend upon; changes are integrated and used without repeated rework
- Deliver library and tooling features that enable engineers and agents; changes adoptable from documentation alone and reported frictions get fixed
- Make prototypes which demonstrate novel capabilities; stakeholders can use them to make decisions

Release

- Take work through review and into a release; review feedback gets prompt response, and blockers get chased instead of waited upon
- Validate work against functional requirements agreed at shaping; correctness demonstrated by tests • Validate work against non-functional requirements; performance is benchmarked or behavior is documented

Support

- Communicate changes and guidance; changes are announced and instructions are provided via documentation and presentations




- Work directly with in-market teams and customers on escalated problems; escalations get diagnosed, tracked, resolved, and the requester stays informed
- Turn support lessons into platform improvements; problems get fixed at the source instead of escalated repeatedly

Improve

- Contribute to better software development lifecycle practices; process bottlenecks are identified and changes are proposed
- Help peers develop; productive change reviews are given, pairing is offered, and a high standard is set

Experience and Capabilities

Essential

- Deep experience building an SDK, toolchain, or library that other engineers shipped on
- Right to work in Australia or New Zealand

Preferred

- Deep experience developing with Rust and proficient in C
- Experience building applications with user interfaces like console, native, or web
- Experience building low-level components like device drivers, board support packages, bootloaders, hypervisors, or language runtimes
- Experience with microkernels or separation kernels (e.g. seL4, QNX, Zephyr, or similar) • Professional experience with complex build systems (e.g. in Nix, Yocto, Bazel)
- Located in Sydney, Melbourne, or Wellington

How to Apply

Step 1: Send us a short note telling us about something you’ve made and why this is the work that demonstrates your skill best along with your resume, so we know what you’ve been up to.

Step 2: Chat with us. If successful in advancing to this stage, we will arrange an interview so that we can learn more about your past work and to learn more about the thing you’ve made

Step 3: Work with us. If successful, we’ll get you to try out a real problem with us so we can see what it’s like to work with each other.

Please submit your Resume and Short Note to [email protected] with the subject line: Platform Senior Software Engineer: [Your Name]

📌 Senior Software Engineer- Platform Team (Sydney)
🏢 Kry10
📍 Sydney