Engineering Team Lead, Mistral Cloud

What You Will Do

• Design and ship the systems. You write Go alongside your team and own the architecture and the hardest implementation decisions, not just the roadmap that tracks them.
• Run Kubernetes in production and understand the layers beneath it. You make the calls when the platform breaks at 3am and your engineers learn from how you do it.
• Own delivery of your team's roadmap. Projects ship with the reliability and performance that finance, healthcare, and public-sector workloads demand.
• Build engineers, not just software. You set the standard for ownership, remove the obstacles in their way, and push them past their comfort zone until the work they ship surprises them.
• Partner with Product Managers to set priorities, scope initiatives, and make the technical and business tradeoffs. You translate between what customers need and what the platform has to become.
• Define the team's processes and execution rituals. Keep the path clear as the team and the platform scale toward a gigawatt of capacity.
• Raise the engineering bar across the org through code review, mentoring, and knowledge sharing. The team you build here sets the technical standard for the whole Cloud Platform org.
• What We're Looking For
• You have shipped production systems in Go. Not dabbled. Shipped.
• You have run Kubernetes in anger and understand what happens underneath it. You have worked on Linux directly, not just on managed services that sit on top of it.
• You are T-shaped: deep in one area (storage, networking, or observability preferred), conversant across the rest of the stack. We are building new teams in each of these areas and want leads who can help stand them up.
• You think like a developer who happens to build infrastructure, not an operator who manages it. You write code that other engineers depend on.
• 8+ years building backend or infrastructure systems, with at least 2 years leading engineers.
• You have partnered with product, design, and business teams to ship software that reached real users.
• A low-ego, team-first mindset. We care less about your exact domain and more about whether you are the kind of technical force other engineers want to work alongside.