Vice President of Marketing

We need to output HTML fragment with sections: About the role? Actually the job description includes sections: Job Description, What You'll Actually Do, Qualifications, Why This Role, Additional Information (but we need to drop boilerplate like EEO, legal, application instructions). Also we need to include sections only if there is real content. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can adapt headings to match content: maybe "About the role", "Responsibilities", "Qualifications", "Why This Role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if appropriate. But we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. We need to map content to those sections. We have: - About the role: could be the introductory paragraph about Mirantis repositioning, need for VP of Marketing, etc. - Responsibilities: "What You'll Actually Do" section. - Requirements: maybe "Qualifications" and "Practical Requirements". Could combine. - Skills: maybe not explicit; we could skip if no specific skills list. - Benefits, Pay, Schedule: not present; we should not include those sections if no real content. - Also "Why This Role" could be a section but not in list; maybe we could treat as "About the role" or "Why This Role" but instruction says prefer few substantive sections over many thin ones. Could incorporate why this role into About the role or Responsibilities. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "#remote" maybe? It's a tag but could be considered metadata; we could fold into a short p. We need to output only HTML fragment, no /, no markdown fences. Let's extract substantive content: Intro: "Mirantis is the Kubernetes-native AI infrastructure company, enabling organizations to build and operate scalable, secure, and sovereign infrastructure for modern AI, machine learning, and data-intensive applications. By combining open source innovation with deep expertise in Kubernetes orchestration, Mirantis empowers platform engineering teams to deliver composable, production-ready developer platforms across any environment—on-premises, in the cloud, at the edge, or in sovereign data centers. As enterprises navigate the growing complexity of AI-driven workloads, Mirantis delivers the automation, GPU orchestration, and policy-driven control needed to manage infrastructure with confidence and agility. Committed to open standards and freedom from lock-in, Mirantis ensures that customers retain full control of their infrastructure strategy" Then "Job Description Mirantis is repositioning from a recognized private cloud infrastructure leader into a full-stack AI Infrastructure company — the vendor-agnostic, open-standard platform for building and operating AI clouds for Neoclouds and AI outcomes for enterprises. We need a VP of Marketing who can force that shift in market perception quickly, and who has personally lived through the transitions that matter: the rise of cloud native, and now the rise of AI infrastructure — from GPUs and orchestration up through models and inferencing. This is not a role for someone who runs a marketing function well. It's a role for someone who has helped build a company's gravity — the person who gets a brand into the center of the conversation, who is known in the ecosystem, and who can point to what they built and what happened because of it. You will own marketing across both our Enterprise and CSP/Neocloud businesses, reporting to the SVP & GM, with a path to the executive table based on impact. A few reasons this moment matters: Mirantis was recently acquired as a wholly owned subsidiary of IREN, giving us a unique position in the marketTo Neoclouds, we offer a faster path to more valuable revenue — we solve the SLA/ops/services layer so they can attract customers they couldn't otherwise landWe have an installed base of 1,500 enterprise customersTo offtakers, we remove friction from consuming GPUs so they can focus on their business outcomesMirantis is an inaugural NVIDIA AI Cloud Ready ISV — one of only threeAt the industry level, we're actively promoting a standard consumption API, partnering with NVIDIA to help create the standard, not just comply with it" Then "What You'll Actually Do Reposition the company, fast. Take Mirantis from "private cloud infrastructure" to "full-stack AI infrastructure" in market perception — not just in messaging decks. Build gravity, not just pipeline. Get Mirantis into analyst conversations, buyer shortlists, and ecosystem conversations alongside NVIDIA and the leading Neocloud/AI infrastructure players — through earned attention, not just paid programs. Own the narrative personally. Craft the positioning and messaging yourself — the story of why an open, vendor-agnostic AI infrastructure standard matters to Neoclouds and enterprises. You won't write every blog post, but the strategic narrative is yours. Run marketing for two distinct motions. Enterprise (long-cycle, ABM, expansion into AI workloads within the installed base) and CSP/Neocloud (fast-moving, technically sophisticated, reputation-driven buyers) — with a coherent brand across both. Prove it. Every claim of impact should be backed by a documented artifact — a case study, a metric, a launch that moved a market. You'll be expected to bring these from your own track record and build the same discipline here. Lead and reshape an existing team. Assess, develop, and where needed replace — building a team capable of executing at the speed and technical fluency this market demands." Then "Qualifications Who You Are You were part of the cloud native rise — you understand how Kubernetes, containers, and infrastructure orchestration became categories, and you have real scar tissue from that era. You've immersed yourself in the AI infrastructure buildout — not as an observer, but as an operator with a point of view across the stack: GPU orchestration, AI clouds, model serving, and inferencing. You've worked at, marketed to, or competed against companies like CoreWeave, Nebius, Crusoe, Together.ai, Fireworks.ai, BaseTen, Modal, Northflank, VAST, Netris, ClearML, or NVIDIA — and/or bring infrastructure pedigree from AWS, Red Hat, Rancher, HPE, or Dell. A mix of the two is ideal. You are more entrepreneur than corporate marketer — you've likely spent more time at high-growth startups than large enterprises, and you default to speed and judgment over process. You can show your work: specific launches, campaigns, positioning shifts, or brand moments you drove, and the measurable outcome that followed. You have enough technical depth — whether from product marketing, product management, or technical sales — to be credible in a room of infrastructure engineers and AI researchers, but your edge is building brand awareness and demand, not writing specs. What Actually Matters Most Track record of getting a company's name into the center of buying and industry conversation — measured in brand awareness, analyst/media presence, and pipeline impact — carries more weight than years of experience, org size managed, or a traditional marketing resume. Equally important: demonstrated ability to build and activate an industry ecosystem, not just market to it. This is as much a business development and partnerships mandate as a marketing one — working in close partnership with our established BD team to forge the right relationships with players like NVIDIA and the leading Neoclouds, turn those relationships into joint go-to-market motions, and be recognized as a genuine connector in the AI infrastructure industry. We're looking for someone who can both shape that strategy alongside BD and personally help drive it forward. The bar on outcomes should be commensurate with the ambition: we're looking for someone who has been part of building outcomes at the scale of billions of dollars in enterprise value, not incremental campaign wins." Then "Practical Requirements Based in the United States, with flexibility for travelComfortable operating with a moderate budget and making sharp trade-offs rather than running every playbook" Then "Why This Role A genuine ground-floor opportunity to reposition a company with real customers and real infrastructure pedigree into the next categoryExecutive-table seat earned through impact, not tenureDirect partnership with Sales, Product, the CEO, and the executive staff to shape company direction" Then "Additional Information It is understood that Mirantis, Inc. may use automated decision-making technology (ADMT) for specific employment-related decisions. Opting out of ADMT use is requested for decisions about evaluation and review connected with the specific employment decision for the position applied for. You also have the right to appeal any decisions made by ADMT by sending your request to isamoylova@mirantis.com By submitting your resume, you consent to the processing and storage of your personal data in accordance with applicable data protection laws, for the purposes of considering your application for current and future job opportunities. #remote We are a Leader for Container Management in G2 (#2 after AWS)!" We need to remove boilerplate: the Additional Information section includes legal/admt etc. That's boilerplate; we should remove it. Also the "#remote" and G2 leader line maybe not boilerplate but could be considered metadata; but it's substantive? It's a accolade; could be kept as part of About the role maybe. However it's after the legal boilerplate; we could keep it as a short p. We need to avoid repeating job title as heading. So no heading "VP of Marketing". Good. We need to use

for section headings. Let's decide sections: - About the role (intro + Mirantis description + reasons this moment matters + maybe the accolade) - Responsibilities (What You'll Actually Do) - Qualifications (Who You Are + What Actually Matters Most + Practical Requirements) maybe combine. - Why This Role (maybe as its own section? Could be part of About the role but it's separate motivational. Could be its own heading "Why This Role" but not in the list; but instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those headings. We could map "Why This Role" into About the role or Responsibilities. Probably better to include as its own section but heading not from list might be okay? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but they give examples. To be safe, we could use "About the role" for intro, "Responsibilities" for what you'll do, "Qualifications" for qualifications + practical requirements, and maybe "Why This Role" as a separate

though not in examples; but maybe they'd accept. However they said "Prefer a few substantive sections over many thin ones." So maybe combine why this role into About the role. Thus sections: About the role, Responsibilities, Qualifications. We need to use

• for any list of duties/requirements/benefits. We have lists within paragraphs (like list of companies, list of reasons). We should convert those to
  • . Also the "A few reasons this moment matters:" is a list; we should make a list. Also "You've worked at, marketed to, or competed against companies like ..." is a list; we can make a list. Also "You are more entrepreneur than corporate marketer — ..." maybe not a list. Also "What Actually Matters Most" includes bullet-like statements; we could make list. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the exact phrasing? We can keep sentences but restructure into list items. We must not repeat job title as heading. Not include