Went through Mistral's EM loop in spring 2026 for a role managing one of their applied research engineering teams. Posting this because EM interview write-ups for AI companies tend to be sparse and I spent a lot of time guessing what to prep.
First thing to know: Mistral's EM bar is genuinely technical. They're not hiring pure people-managers. The expectation is you can do meaningful code review, unblock engineers on system design decisions, and have a point of view on ML infrastructure choices. If you're a people-first EM who's been out of the technical weeds for 3+ years, this loop will be uncomfortable.
Phone screen with the hiring manager About 50 minutes. First half was background: how big were the teams you've managed, how do you run 1:1s, how do you handle underperformers. Second half was a technical architecture discussion. They described a rough problem (low-latency serving of fine-tuned models across regions) and wanted my instincts on the design. I wasn't expected to design it fully, more to show I could have an intelligent conversation with the engineers doing it.
Technical screen They gave me a real engineering problem and asked me to work through it with them, like I would if I were pairing with one of my engineers. Not a whiteboard algorithm question but a system-level thing. For me it was: how would you instrument a distributed model serving cluster to detect when a model replica is returning lower-quality outputs than the fleet average? I had to talk through what metrics I'd collect, how I'd set up alerting, and what the on-call runbook would look like.
Onsite (Paris, I went in person) 4 sessions. Leadership philosophy round, people scenario cases (a specific example: two engineers on your team fundamentally disagree on a technical direction, you have 2 weeks to ship, walk me through how you resolve it), a deeper technical discussion, and a session with their head of engineering on vision and org design.
The people scenario stuff was more situational than behavioral. They'd describe a specific situation and ask what you'd do now, not what you did before. I found that harder because I tend to reach for past examples.
The org design conversation was the most interesting. They asked how I think about team topologies at Mistral's stage: should infra and applied research be separate tracks or hybrid pods? No right answer but they want to see that you've thought about it, not just managed whatever structure you inherited.
Feedback loop was quick. I heard back 8 days after the onsite. Overall the interview respected my time more than most big-tech loops I've done.