Fractile - Member of Technical Staff - Security Engineering

• We expect you to know the fundamentals, and to have real, practical experience across several of these: • An adversarial mindset and sharp threat-modeling instincts: trust boundaries, assets, attacks, and honesty about residual risk • Hands-on experience with the core security primitives in software and in silicon: secure boot, root of trust, cryptography, and key management, including how they’re implemented and where they can fail • Secure protocol and channel design between components • Strong C and Rust, and the instinct for memory safety and defensive coding that low-level security work needs • Experience building, not just using, security mechanisms: a secure-boot chain, key hierarchy, or attestation flow you shaped • That’s the core. We get especially curious about your application when you also bring some of the following. Very few candidates tick every box here, and we don’t expect you to: • Attestation at boot and at runtime, and management-plane protocols (DICE, IETF RATS, SPDM, MCTP, PLDM; confidential-computing directions like TDISP) • Hardware building blocks and firmware/Linux hardening (HSM, TPM, secure element, Caliptra, secure debug; open firmware/boot projects, image minimisation) • Assurance and resistance (supply-chain security with SBOM and SLSA, fuzzing and testing, standards like NIST 800-series, Common Criteria, OCP incl. S.A.F.E., TCG/DMTF; physical and side-channel awareness) • AI/LLM-assisted security tooling, and RISC-V / GPU / ML-accelerator experience • What you’re signing up for: • This is a young company doing hard things, balanced across hardware and software. We’re building the software layer for a whole inference system as it takes shape, so you’ll often be securing systems ahead of the hardware: reasoning about a threat model against a specification first, then a simulator, then early boards. You’ll work with incomplete information and watch it get sharper with every iteration. That takes comfort with ambiguity and a bias for action. If that sounds daunting, this may not be the role. If it sounds like the fun part, we should talk. • Boundaries between areas are soft here. Security touches every layer, so you’ll work across bare metal, RTOS, and Linux, and alongside the architecture and hardware teams as much as the rest of the software team. That breadth is a good part of the job. • You’ll be there for first bring-up, the first secure boot that verifies, the first device that attests itself, the first clean end-to-end run. A piece of what you built will live in silicon and in every rack we ship. • We want a team that reflects the world it’s built for, and we welcome applicants from every background, including those whose path here hasn’t been a straight line. We care that you’re excited by this kind of work, that you bring security rigour, and that you make a team better. • Come build it with us.