VP, Global Developer Relations

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Mistral", "The Role", "What You Will Do", "What We're Looking For", "Bonus Points If You Have", "What we offer". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content accordingly. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings if content exists. We must not repeat job title as heading. We must not include Job ID etc. We must include a section ONLY when posting has real, specific content for it. So we need to decide which sections have content. We have: - About Mistral: description of company. Could map to "About the role"? Actually "About the role" is typical heading for role description. But we have "About Mistral" which is company overview. Could we treat that as "About the role"? Probably not; but we can still include a section with heading "About the role" and put the Mistral description there? The instruction says use those headings as examples, not strictly limited to those exact strings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we should map content to appropriate headings. We have sections: - The Role: description of role. That fits "About the role" heading. - What You Will Do: responsibilities. That fits "Responsibilities". - What We're Looking For: qualifications/requirements. That fits "Requirements" or "Qualifications". Could split: "Requirements" for must-have, "Bonus Points If You Have" for preferred qualifications. - What we offer: benefits. That fits "Benefits". - Pay and Schedule: not provided, so we should NOT include those sections. Thus we will output:

About the role

with content from "The Role" paragraph(s). Should we include the "About Mistral" description? It is about company, not role. Could we include it under About the role? Might be okay but maybe better to include as a separate section? The instruction only lists examples; we could also add other headings if needed? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "use

for section headings (e.g. ...)". Likely they expect only those headings. So we should map all content into those headings. The "About Mistral" could be considered part of "About the role" (company context). We'll include it. Thus:

About the role

Mistral provides full-stack AI solutions: from frontier models to developer tools, applications, and compute. We partner with enterprises tackling the hardest problems across high-stakes industries like finance, manufacturing, defense, healthcare, and the public sector, co-creating customized AI systems that they can run on their terms. We are a dynamic, collaborative team passionate about AI and its potential to transform society. Our diverse workforce thrives in competitive environments and is committed to driving innovation. Our teams are distributed between Europe, North America, Asia and the Middle East. We are creative, low-ego and team-spirited.

As our VP of Global Developer Relations, you’ll be the voice and facilitator of Mistral to the developer, scientific, and technical communities. You’ll build and scale a global DevRel strategy that fosters deep engagement, advocacy, and love for Mistral’s models and technology. Your team will build communities and educate, excite, and empower developers to adopt, innovate, and evangelize Mistral’s technology—whether they’re startups, enterprises, researchers, or open-source contributors. You’ll work closely with Product, Research, Engineering, Marketing, Communications, and more to ensure developers have the tools, resources, and inspiration they need to succeed with Mistral.

Then Responsibilities: from "What You Will Do". We'll list as

• items. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep bullet points as they appear. Let's extract bullet points from "What You Will Do": - Build a Global Developer Movement - Develop and execute a global DevRel strategy that connects Mistral and our AI platform effectively with developers, scientists, and technologists. - Create authentic, developer-first engagement—focusing on education, inspiration, and community, with great content and AI tools. - Foster a culture of advocacy where developers naturally champion Mistral in their networks, projects, and conversations. - Engage and Inspire the Technical Community - Lead high-impact developer engagement initiatives, including: * Technical content (e.g., tutorials, blog posts, videos, documentation) that helps developers get started, optimize, and innovate with Mistral’s models. * Community programs (e.g., hackathons, meetups, AMAs, Discord/Slack communities) that bring together AI builders, researchers, and enthusiasts. * Evangelism & thought leadership (e.g., conference talks, podcasts, technical deep dives) that showcase Mistral’s unique value and capabilities. * Work with Product and Research teams to translate complex AI innovations into accessible, exciting, and actionable insights for developers. - Enable Developer Success, particularly for self-service adoption - Build scalable enablement programs (e.g., onboarding guides, SDKs, APIs, sample projects) that reduce friction for developers adopting Mistral’s models. - Create feedback loops between the developer community and Mistral’s Product/Engineering teams to shape the roadmap based on real-world needs. - Scale a World-Class DevRel Team - Hire, mentor, and lead a global team of Developer Advocates, Engineers and Evangelists - with particular strength in Europe and San Francisco - Define metrics and KPIs to measure the impact of DevRel (e.g., developer adoption, community growth, engagement, advocacy). - Lead from the front as a fantastic representative of Mistral at events, in social, and in project communities - Drive Open Source & Ecosystem Growth - Champion open-source contributions and collaborative innovation around Mistral’s models. - Partner with startups, enterprises, and academic institutions to accelerate adoption and co-innovation. - Identify and nurture key developer influencers, maintainers, and ambassadors who can amplify Mistral’s reach and impact. We need to preserve all detail; we can keep sub-bullets as separate
• items, maybe nested
  . The instruction says use
  • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do top-level
    with
    • items; for sub-items we can also use
      • inside. We'll produce:

        Responsibilities

        • Build a Global Developer Movement
          • Develop and execute a global DevRel strategy that connects Mistral and our AI platform effectively with developers, scientists, and technologists.
          • Create authentic, developer-first engagement—focusing on education, inspiration, and community, with great content and AI tools.
          • Foster a culture of advocacy where developers naturally champion Mistral in their networks, projects, and conversations.
        • Engage and Inspire the Technical Community
          • Lead high-impact developer engagement initiatives, including:
          • Technical content (e.g., tutorials, blog posts, videos, documentation) that helps developers get started, optimize, and innovate with Mistral’s models.
          • Community programs (e.g., hackathons, meetups, AMAs, Discord/Slack communities) that bring together AI builders, researchers, and enthusiasts.
          • Evangelism & thought leadership (e.g., conference talks, podcasts, technical deep dives) that showcase Mistral’s unique value and capabilities.
          • Work with Product and Research teams to translate complex AI innovations into accessible, exciting, and actionable insights for developers.
        • Enable Developer Success, particularly for self-service adoption
          • Build scalable enablement programs (e.g., onboarding guides, SDKs, APIs, sample projects) that reduce friction for developers adopting Mistral’s models.
          • Create feedback loops between the developer community and Mistral’s Product/Engineering teams to shape the roadmap based on real-world needs.
        • Scale a World-Class DevRel Team
          • Hire, mentor, and lead a global team of Developer Advocates, Engineers and Evangelists - with particular strength in Europe and San Francisco
          • Define metrics and KPIs to measure the impact of DevRel (e.g., developer adoption, community growth, engagement, advocacy).
          • Lead from the front as a fantastic representative of Mistral at events, in social, and in project communities
        • Drive Open Source & Ecosystem Growth
          • Champion open-source contributions and collaborative innovation around Mistral’s models.
          • Partner with startups, enterprises, and academic institutions to accelerate adoption and co-innovation.
          • Identify and nurture key developer influencers, maintainers, and ambassadors who can amplify Mistral’s reach and impact.
        Now Requirements/Qualifications: from "What We're Looking For". We'll treat as Requirements. Content: - Proven leadership in Developer Relations, Developer Marketing, or Technical Evangelism for a B2B technology company, preferably in AI, cloud, and open-source. - Deep technical credibility—ability to engage with developers, scientists, and engineers on their terms (e.g., code, research, architecture). - Passion for community building—a track record of growing and nurturing technical communities (e.g., open-source projects, developer forums, hackathons). - Strong storytelling and communication skills—ability to simplify complex concepts and inspire developers through content, talks, and interactions. - Strategic and operational excellence—ability to scale DevRel globally while maintaining a hands-on, authentic approach. - Collaborative mindset—ability to work across Product, Engineering, Marketing, and Sales to align DevRel with Mistral’s broader goals. We'll output as
        • . Then Bonus Points If You Have: we can treat as "Qualifications" maybe separate section "Qualifications" for preferred? Or we could add another section "Qualifications" for bonus points. The instruction includes Qualifications as a possible heading. We'll put bonus points under "Qualifications". Or we could have two sections: Requirements and Qualifications. Let's do:

          Requirements

          for must-have.

          Qualifications

          for bonus points. Bonus points content: - Experience in AI, machine learning, or large language models (LLMs). - Personally contributed meaningfully to open source projects and communities. - Led global DevRel teams in high-growth, competitive markets. - Personal brand or following in the developer or AI community - Experience launching and scaling developer-focused products or tools. We'll output as
          • . Now Benefits: from "What we offer". Content: We offer a comprehensive benefits package designed to support your well-being, growth, and work-life balance. Benefits vary by country and may include healthcare coverage, parental leave, retirement plans, relocation support, wellness programs, meal and transportation allowances, and other location-specific perks. For the most up-to-date details on benefits available in your location, please refer to our Benefits page. We should preserve all substantive information. So we output a <