Fractile - Embedded & Low-Level Software Engineer - Early Career

• The people who do well in these areas tend to think below the abstraction layers. If something’s slow or broken you want to know why, down to the register and the instruction, and you don’t stop until it works and you’ve measured it. • You’ll likely have these foundations: • Strong programming fundamentals in a systems language: Rust, C, or C++ • Serious hands-on experience in Linux, bare-metal, or an RTOS • Enough knowledge of at least one architecture to reason about what the hardware is doing • If you’ve written GPU or ML kernels (CUDA, Triton, or similar), that maps directly onto our performance work and we’d like to see it. • We get especially curious when you’ve already touched the kind of work these areas involve: a Linux kernel driver wrangling PCIe, DMA, and interrupts; firmware or embedded Linux on a board you helped bring up; a QEMU model or emulator you’ve extended; a hot loop rewritten in assembly for RISC-V and profiled until it flew; an attention kernel you pushed toward the hardware’s peak; or a secure-boot chain you built. None of it’s required, and it doesn’t need to be large or polished. What it tells us is that you’re genuinely engaged with how things work underneath. • A degree in Electronic Engineering, Computer Engineering, or Computer Science is common here. However, depth counts wherever it came from: an adjacent field, industry, open source, or your own time, at any stage of your career. • We want our people to reflect the world we build for, and we welcome applicants from every background, including those whose path here hasn’t been a straight line. If you’re close but not sure you tick every box, we’d still like to hear from you. We care more that you’re excited by this kind of work, that you learn fast, and that you make the people around you better. • What you’re signing up for • This is a young company doing hard things. We started in 2022 and we’re now 110+ people, balanced across hardware and software. We’re building the software layer for a chip as the chip takes shape, so you’ll often be writing software ahead of the hardware: 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. • We work in an environment where boundaries between areas are soft. There’s always opportunity, and sometimes a need, to lend a hand in a neighbouring area. That’s a good part of the job, not the whole of it. If simulators aren’t your thing but kernels are, come and do kernels. • You’ll be there for first bring-up, the first LEDs, the first end-to-end run, and the first time a number jumps because of something you shipped. When it works, a piece of what you wrote will live in silicon. • Come build it with us.