| Interview rounds | Technical screens, applied ML or systems loop, take-home or project deep dive. | Technical screens, research or systems depth, coding and team or founder-adjacent conversations. |
| ML depth | LLM serving, evals, agents, safety constraints and product integration. | Open models, training efficiency, inference optimisation and research implementation. |
| Coding style | Practical systems or applied ML coding rather than puzzle-only. | Strong algorithms and systems coding, often with research-code expectations. |
| System design depth | Inference, tool use, eval pipelines, reliability and model release gates. | Training, serving, kernels, distributed systems and model deployment tradeoffs. |
| Behavioural framework | Mission, ownership and execution under uncertainty. | Research judgement, open-source orientation and high technical independence. |
| Take-home | Possible, often close to applied work. | Possible practical exercise or deep project review. |
| Offer typical TC | Very high frontier-lab packages with fast-changing equity context. | High European lab packages, with location and equity context important. |
| Decision speed | Can move fast for priority teams but is highly selective. | Smaller-loop speed can be quick, but senior calibration is demanding. |