Manager, Applied AI Strategy and Operations

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate like EEO etc. Also remove navigation/legal etc. Also remove duplicated lines. Must preserve all substantive information. We need to parse the job posting. Key parts: - Business Area: Corp. Strategy Seniority Level: Mid-Senior level (metadata, can be folded into short

maybe) - Job Description: paragraph about Cloudera. - Job title: Manager, Applied AI Strategy and Operations (we don't repeat as heading) - Job Purpose: paragraph. - Key responsibilities: list of bullet points (multiple paragraphs). We need to put under

Responsibilities

with

• each bullet. - Preferred Qualifications: list of bullet points (multiple). Could be under

  Qualifications

  or

  Preferred Qualifications

  . The instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. So we can use

  Qualifications

  for Preferred Qualifications. - Preferred Experience: list of bullet points. Could be under

  Experience

  but not in allowed list? Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Experience could go under Qualifications or Requirements. Probably Requirements. We'll put under

  Requirements

  (or maybe Qualifications). Since they have Preferred Qualifications and Preferred Experience, we could combine into Qualifications and Requirements sections. Let's decide: Use

  Requirements

  for Preferred Experience (since it's experience). Use

  Qualifications

  for Preferred Qualifications. - Note about candidates without direct commercial ownership experience etc. That's a note; we can include as paragraph under Requirements or Qualifications? Probably under Requirements as a note. - The right person ... If this position ... we invite you apply! That's a call to action; we should remove application instructions. So remove that sentence. - This role is not eligible for immigration sponsorship. That's metadata; could be folded into short

  maybe under a short paragraph after job purpose? But we can include as a short

  maybe under a generic "About the role"? Actually we have "About the role" heading allowed. Could put a short paragraph summarizing role and metadata. - The anticipated annual base salary range for this position is: Washington: $144,000 - $162,000 New York: $144,000 - $162,000 California: $144,000 - $162,000 Individual compensation within the published range is determined by the candidate's skills, experience, qualifications, and primary work location. In addition to base pay, sales roles are eligible for Cloudera's commission plan, while non-sales roles are eligible for the corporate incentive plan. All employees receive a comprehensive benefits package Thus we have Pay info (salary range) and Benefits info (comprehensive benefits package). Also "What you can expect from us:" list of benefits: Generous PTO Policy Support work life balance with Unplugged Days Flexible WFH Policy Mental & Physical Wellness programs Phone and Internet Reimbursement program Access to Continued Career Development Comprehensive Benefits and Competitive Packages Paid Volunteer Time Employee Resource Groups Thus we have Benefits section content. Schedule? Not mentioned. So we should not create Schedule section. We also have "EEO/VEVRAA LI-SF1" which is boilerplate; remove. We need to preserve all substantive information; not invent or summarize away detail. Must not include placeholder text like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Thus structure:

  Business Area: Corp. Strategy. Seniority Level: Mid-Senior level.

  maybe combine. Then

  About the role

  with paragraphs: Job Description paragraph, Job Purpose paragraph. Then

  Responsibilities

  with
  • each bullet from Key responsibilities. Then

    Requirements

    with
    • each bullet from Preferred Experience plus note about candidates without direct commercial ownership experience. Then

      Qualifications

      with
      • each bullet from Preferred Qualifications. Then

        Skills

        ? Not explicitly listed; but we could include skills from qualifications? However we already have Qualifications covering skills. The instruction says we can use Skills heading if there is real specific content. We could extract skills like problem-solving, analytical, communication, familiarity with platforms, quantitative, financial modeling, data manipulation, proficiency in GTM systems, BI tools, SQL, ability to operate with high autonomy. Those are in Preferred Qualifications. But we already used Qualifications heading for those. Could also create Skills heading for those specific skill bullets, but that would duplicate. Better to keep Qualifications heading for qualifications and experience, and maybe Skills heading for technical skills? However we risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we should not create many thin sections. So we can combine qualifications and skills into Qualifications section. Or we could have Qualifications for Preferred Qualifications, and Requirements for Preferred Experience, and maybe Skills for technical skills? But that would be thin. Better to have Qualifications include both qualifications and skills. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Pay section: we need to include salary range details. Use

        Pay

        with paragraph(s) containing the salary ranges and note about commission/incentive. Benefits section:

        Benefits

        with
        • each benefit from "What you can expect from us:" plus note about comprehensive benefits package. We must not include boilerplate like EEO etc. Check for duplicated lines: The job description paragraph appears twice? Actually there is "Job Description: At Cloudera, we empower..." and later "Job Purpose: As a Manager...". Those are distinct. Now let's extract bullets. Key responsibilities bullets (as per text): - Drive Global Governance & Operating Rhythms: Establish, evolve, and manage the programmatic operating rhythm for the global Applied AI organization across AMER, EMEA, and APAC. Lead the monthly business review (MBR) process—from metric gathering and CRM ingestion through deep quantitative analysis and executive synthesis for senior leadership. - Manage the AI Adoption Funnel: Partner with regional FDE and Applied AI Specialist leadership to track, analyze, and optimize customer progression through our four core execution stages: Discovery & Strategy, Solution & Value, Pilot & Prove, and Production & Scale. - Account Prioritization & Use Case Frameworks: Structure analytical frameworks grounded in real customer signal—joining technical discovery sessions, reviewing triage outcomes, and working directly with field engineering teams to filter and isolate high-ROI Private AI workloads. Conduct rigorous analyses to down-select and prioritize target accounts across our Top 100 strategic enterprise lists. - Define & Standardize Strategic Metrics: Collaborate with central Revenue Operations and AI GTM Sales Strategy to define, refine, and standardize key performance indicators around subscription and consumption-based Private AI adoption. Track organizational progress against critical milestones, including customer pitch meetings, on-site Use Case Workshops, Applied AI Hands-on Labs, and deployed production solutions. - Ecosystem & Commercial Strategy: Analyze and support go-to-market operational alignment with major AI infrastructure and ecosystem partners (including NVIDIA Blueprints and VAST). Evaluate revenue share models, joint sales plays, and co-deployment strategies to maximize platform pull-through and annual recurring revenue (ARR) expansion. - Cross-Functional Leadership & Solution Productization: Act as an embedded, highly trusted thought partner to technical and commercial leaders. Design and implement scalable processes for tracking team allocations and solution productization, ensuring repeatable delivery patterns are codified and communicated across Account Executives, Solution Engineers, and Professional Services globally. - Business Planning & Executive Storytelling: Build comprehensive segment analyses, growth models, and strategic business cases to support critical investment decisions, headcount planning, and resource allocation across regional pods. That's 7 bullets. Preferred Qualifications bullets: - Strong problem-solving and structuring skills, with a proven ability to scope complex, ambiguous strategic challenges and identify root causes within technical go-to-market organizations. - Highly analytical and excellent at leveraging facts, CRM data, and customer insights to generate and validate strategic hypotheses regarding enterprise AI adoption and workload consumption. - Proven ability to communicate and build trust with stakeholders at all levels—including C-suite executives, technical engineering leaders, and regional sales VPs—by turning granular data and research into actionable insight and a well-structured executive storyline. - Deep familiarity with enterprise data management platforms, hybrid cloud architectures, data lakehouses (e.g., Apache Iceberg), and the broader AI/ML ecosystem capabilities. - Strong quantitative, financial modeling, and data manipulation skills; proficiency in GTM systems (e.g., Salesforce, Clari), business intelligence tools (e.g., Tableau, Power BI), and SQL is a strong plus. - Demonstrated capacity to operate with high autonomy in dynamic, fast-moving environments, building structure and operational rigor from the ground up rather than inheriting legacy processes. That's 6 bullets. Preferred Experience bullets: - 6+ years of progressive work experience in sales strategy, revenue operations, business operations, or management consulting, with a demonstrated track record of driving cross-functional alignment and measurable business impact. - Direct experience supporting specialized technical sales, pre-sales, or post-sales delivery teams—particularly within Forward Deployed Engineering (FDE), Solution Architecture, or Applied AI Specialist organizations. - Deep domain experience in enterprise software, big data analytics, machine learning/AI, or hybrid cloud infrastructure companies. - Proven expertise working with cloud subscription, consumption-based (usage-driven), or product-led growth (PLG) business models, specifically tracking workload transition from pilot to production scale. - Experience supporting enterprise commercial or technical organizations through rapid 2–3x+ revenue growth periods and global expansion across AMER, EMEA, and APAC regions. - Note: Candidates without direct commercial ownership experience will still be strongly considered if they demonstrate long, deep tenure supporting commercial or technical sales leaders in a closely comparable enterprise GTM model. That's 6 bullets (including note as bullet? It's a note but we can keep as bullet or paragraph). We'll keep as bullet. Now Benefits bullets from "What you can expect from us:": - Generous PTO Policy - Support work life balance with Unplugged Days - Flexible WFH Policy - Mental & Physical Wellness programs - Phone and Internet Reimbursement program - Access to Continued Career Development - Comprehensive Benefits and Competitive Packages - Paid Volunteer Time - Employee Resource Groups Also earlier: "All employees receive a comprehensive benefits package" (already covered). We'll include as bullet maybe. Now Pay paragraph: - The anticipated annual base salary range for this position is: Washington: $144,000 - $162,000; New York: $144,000 - $162,000; California: $144,000 - $162,000. Individual compensation within the published range is determined by the candidate's skills, experience, qualifications, and primary work location. In addition to base pay, sales roles are eligible for Cloudera's commission plan, while non-sales roles are eligible for the corporate incentive plan. All employees receive a comprehensive benefits package. We could split into two paragraphs but okay. Now About the role paragraph(s): We have Business Area and Seniority Level metadata; we can include as short paragraph. Job Description paragraph: "At Cloudera, we empower people to transform complex data into clear and actionable insights. With as much data under