Genesis
More roles at GenesisQuadrants: Compiler Lead
Part remote, part office, you need to live within commuting distance of a named location.
Hybrid · London
Employer listed it 2 months ago · Added 8 weeks ago
Been open since 2 months ago. Long-running listings are sometimes left up after the role is filled.
Salary
Not stated
Location
Hybrid · London
Timezone
Not stated
Contract
Full-time
Experience
Lead
Category
Software
The employer did not publish a salary, and we have too few comparable roles to estimate one.
What the advert says
Quoted word for word from the employer's advert. Where it says nothing, we say so.
- Working hours
- Not mentioned in the advert
- Where you can work from
- Location eligibility not confirmed
- Contract
- Not mentioned in the advert
- Experience asked for
- Not mentioned in the advert
- Pay
- Not mentioned in the advert
Remote flexibility
Hybrid
This role is only partly remote, the employer expects time in the office around London, Hybrid, so you need to live within commuting distance.
What the employer says
- Source listing states candidate location: "London, Hybrid"
- Listing mentions "Hybrid"
What Nomaders makes of it
- Not suitable if you plan to move between countries
The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.
Before you apply
Questions worth asking: Nomaders interpretation
- This role involves office time, but the advert does not say how often. Ask how many days a week are expected on site.
- No pay is stated. Ask for the salary range before investing time in interviews.
- The advert does not say whether this is employment or a contractor arrangement. Ask, as it affects tax and benefits.
Produced automatically from this advert's text; not reviewed by a person. The employer's own page is the final word.
About the role
What Quadrants is
Quadrants is an open-source translation layer that turns ordinary Python into optimized machine code at runtime, across CPU (Arm64, x86) and GPU (AMDGPU, CUDA, Metal, Vulkan) backends. CUDA is the primary target, with x86 the strong runner-up, especially for real-time simulation. The others drive adoption and support fast prototyping for research.
The ambition is explicit: build the best “Python compiler” in the world for physics and performance-critical numerical computing. We are fully committed to it, and we intend to beat leading alternatives like Nvidia Warp, Numba, or Triton.
It’s a standalone project with its own roadmap, built in the open. Genesis, our physics simulator, is its first and top-priority user, the source of its hardest workloads and its benchmarks. But Quadrants is general-purpose infrastructure for anyone writing performance-critical numerical Python, not an internal tool that happens to be public.
The bet: high-performance code should feel natural to write. Engineers write plain Python in a NumPy or PyTorch style, and Quadrants makes it fast.
The role
You own Quadrants end to end: the API, the IR and lowering, the optimization passes, the numerical primitives, and the roadmap.
Our ultimate objective: engineers write for readability and maintainability, never for performance. They write the version of an algorithm they are most comfortable with, and Quadrants rebuilds it into kernels that run as if an expert had hand-tuned them. Performance is the compiler’s job, not theirs. Getting there is a frontier problem, part research and part engineering, and we intend to define the state of the art on it, relentlessly pushing the limit further.
It calls for two things at once: the low-level GPU and compiler skill to make a single kernel optimal, and the ability to keep the whole system coherent as it grows.
The core tradeoff is settled: usability comes first. When usability and performance collide, usability wins, unless the cost is severe. We will limit what the system supports to go fast (static shapes and fixed-size allocation baked into kernels, say), but never the convenience of the API itself. Experts who want maximum performance and full control over the generated code get lower-level escape hatches, down to inline assembly, C, or PTX.
Your mandate is to build the best open-source Python compiler for physics simulation out there. No limit on what that takes. If it means replacing the entire engine, your call. Either way, you keep Quadrants healthy and unblocking the company in the meantime.
What you’ll own
API & authoring experience. The surface that physics and numerical-computing engineers write against, and, as an open-source library, the product’s face to the world. Idiomatic, natural to Python users, never a separate language bolted onto Python. Clean decorators, legible constraints, sharp errors, real escape hatches.
IR, lowering & backends. A stable IR that lowers to multiple backends, with room to grow and the door kept open for differentiable simulation. Today the computation graph is expressed through Quadrants’ own constructs. Recovering it automatically from ordinary Python is hard, and a long-term goal rather than today’s reality.
Optimization. Turn naive code into strong execution plans: vectorization, register and shared-memory usage, barriers and atomics, cooperative threading, dead-buffer and redundant-traffic elimination, dropping needless synchronization. Move low-level optimization off users and into the platform.
Primitives. Cholesky, eigendecomposition, matmul, reductions, solver kernels. Each owned with its correctness, benchmarks, and regression tracking.
Watching Genesis and the compiler together. Hunt for performance wins on both sides, in Genesis and in Quadrants itself. Propose API changes that cut duplication, improve readability, and reduce platform-specific special-casing. Less to maintain, more that simply works.
The project as a product. Benchmark real workloads, track performance over time, catch regressions early. Stay close to users (Genesis first), find friction and missing abstractions, drive adoption, set direction.
Who you are
You reason about whole systems and have taste for where complexity should live. You measure before you optimize, and you reach for memory traffic and launch overhead before FLOPs. You have opinions about API design. You write tests and benchmarks as you go, not afterward.
The ground that judgment stands on:
GPU. What optimal looks like and why: access patterns, registers, shared memory, barriers, atomics, threading. CPU intuition a plus.
Python & API taste. Idiomatic Python. A feel for what’s natural to Python users. APIs that free users rather than constrain them.
Compilers. The path from authoring to kernels (IR, lowering, optimization), weighed against maintainability.
Requirements
The employer hasn't listed requirements separately, they're described in the role summary above and on the original listing.
Benefits
No benefits package published with this listing. Ask about it at first interview.
How to apply
- 1Check the flexibility label above, hybrid, matches where you plan to live and work.
- 2Tailor your CV to the role at Genesis, mentioning your remote working experience.
- 3Apply directly on the employer's careers page using the button below. Nomaders never handles your application.
Found 2mo ago. Last checked today. Always confirm the details on the original posting, salary and location can change after publication.
Listing sourced from Company boards.
Similar roles
Other open software roles with comparable remote rules.
Browse all open rolesPay not stated · You'll be taken to the employer's careers page.