AI Partner Solutions Manager, Google Cloud Marketplace
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Key content:
- Application window open until at least October 9, 2026. This opportunity will remain online based on business needs which may be before or after the specified date. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Boulder, CO, USA; Atlanta, GA, USA; Austin, TX, USA; Chicago, IL, USA; Vancouver, BC, Canada.
- Minimum qualifications: Bachelor's degree in Business Administration, Engineering, Computer Science, or equivalent practical experience. 15 years of experience with technology. Experience in a hyperscaler cloud marketplace, with focus on software licensing, procurement, and governance. Experience with IaaS/PaaS/SaaS markets, B2B software ecosystem and lifecycle, and cloud-based technologies. Experience with AI agent and infrastructure technologies, user experiences, and economics.
- Preferred qualifications: MBA or equivalent. Experience managing complex enterprise products through scale distribution platforms. Expertise in cloud marketplace dynamics with experience in both supply and demand side domains, with measurable results fostering ecosystem development and enterprise procurement enablement. Knowledge of the evidence-driven approach that combines both qualitative and quantitative analysis grounded in cloud economics. Technical understanding of AI agents, agentic systems, trust, governance, and interoperability. Excellent cross-organizational leadership to influence executive business, product, engineering, and partner stakeholders.
- About The Job: paragraph describing AI agents, role, etc.
- Individual pay is determined by factors including job-related skills, experience, and relevant education or training. Canada: $232000 - $237000 (CAD) + 25% bonus target + equity + benefits US: $224000 - $311000 (USD) + 25% bonus target + equity + benefits
- Responsibilities: list bullet points (starting with "Partner with product teams..." etc.)
- Benefits: Not explicitly listed beyond "equity + benefits". The posting mentions benefits generically but not specifics. We should not create a Benefits section unless specific benefits are listed. The posting only says "+ equity + benefits". That's vague; maybe we can treat as part of Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay ranges and mentions bonus target, equity, benefits. So we can have a Pay section that includes the pay ranges and mention bonus, equity, benefits. Benefits section not needed if not detailed.
- Schedule: Not mentioned. So no Schedule section.
- About the role: we have "About The Job" paragraph. Could map to "About the role" heading.
- Requirements: Minimum qualifications and Preferred qualifications could be combined into Requirements or Qualifications. The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have content for About the role (About The Job). Responsibilities (list). Requirements (minimum qualifications). Qualifications (preferred qualifications). Could also have Skills (maybe cross-organizational leadership etc). But we should avoid thin sections. Perhaps combine Minimum and Preferred into a single "Requirements" section with sublists? Or separate "Minimum Qualifications" and "Preferred Qualifications" as subheadings? But only allowed headings are those listed; we cannot create custom headings like "Minimum Qualifications". We could use "Requirements" for minimum qualifications and "Qualifications" for preferred qualifications. That seems okay.
- Skills: maybe we could list cross-organizational leadership etc under Skills. But we already have those in preferred qualifications. Could put them under Skills. However we need to avoid duplication. Let's think: The posting includes "Excellent cross-organizational leadership to influence executive business, product, engineering, and partner stakeholders." That's a skill. Also "Technical understanding of AI agents, agentic systems, trust, governance, and interoperability." That's also skill/knowledge. Could be placed under Skills.
But we need to preserve all substantive information. If we put them under Skills, we still preserve. If we put them under Qualifications (preferred), also preserve. We need to decide which sections to include to avoid thin sections.
We have:
- About the role: paragraph about AI agents, role description.
- Responsibilities: list of bullet points.
- Requirements (minimum qualifications): Bachelor's degree, 15 years experience, experience in hyperscaler cloud marketplace, experience with IaaS/PaaS/SaaS markets, experience with AI agent and infrastructure technologies, user experiences, economics.
- Qualifications (preferred): MBA or equivalent, experience managing complex enterprise products through scale distribution platforms, expertise in cloud marketplace dynamics (supply/demand), knowledge of evidence-driven approach, technical understanding of AI agents etc, excellent cross-organizational leadership.
- Pay: salary ranges and bonus, equity, benefits.
We could also include a short paragraph about application window and preferred working locations. That could be placed under a heading like "About the role" or maybe a separate "Details" but not in allowed headings. Could fold into About the role paragraph? The allowed headings are limited; we could include that info in a
under About the role or maybe under a generic
before sections. The instruction: do NOT repeat the job title as a heading and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short
for application window and locations before sections.
Thus output:
The application window will be open until at least October 9, 2026. This opportunity will remain online based on business needs which may be before or after the specified date. By applying to this position you will have an opportunity to share your preferred working location from the following: Boulder, CO, USA; Atlanta, GA, USA; Austin, TX, USA; Chicago, IL, USA; Vancouver, BC, Canada.
Then sections:
About the role
[the About The Job paragraph]
Responsibilities
- Partner with product teams to translate business priorities into product truth across multiple experiences using usage telemetry and user research.
- Focus on high-value, enterprise problems with an evidence-based approach, supported by a deep understanding of competitive experiences.
- Improve business value by improving end user discoverability and ease of use.
- Unblock enterprise procurement with controls that enable governance and trust without sacrificing usability.
- Launch capabilities that allow Google to recruit and co-innovate with partners enabling customer choice and scale leveraging Marketplace’s favorable economics, and distribution at-scale.
- Turn commercial and operational constraints into differentiated value for customers, partners, and Google.
Requirements
- Bachelor's degree in Business Administration, Engineering, Computer Science, or equivalent practical experience.
- 15 years of experience with technology.
- Experience in a hyperscaler cloud marketplace, with focus on software licensing, procurement, and governance.
- Experience with IaaS/PaaS/SaaS markets, B2B software ecosystem and lifecycle, and cloud-based technologies.
- Experience with AI agent and infrastructure technologies, user experiences, and economics.
Qualifications
- MBA or equivalent.
- Experience managing complex enterprise products through scale distribution platforms.
- Expertise in cloud marketplace dynamics with experience in both supply and demand side domains, with measurable results fostering ecosystem development and enterprise procurement enablement.
- Knowledge of the evidence-driven approach that combines both qualitative and quantitative analysis grounded in cloud economics.
- Technical understanding of AI agents, agentic systems, trust, governance, and interoperability.
- Excellent cross-organizational leadership to influence executive business, product, engineering, and partner stakeholders.
Pay
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. Canada: $232,000 - $237,000 (CAD) + 25% bonus target + equity + benefits. US: $224,000 - $311,000 (USD) + 25% bonus target + equity + benefits.
We should not include Benefits section separately because we already mention benefits in Pay. No Schedule.
We must ensure we didn't include any boilerplate like EEO etc. We removed that.
Check for duplicated lines: we didn't repeat.
Check for any placeholder text: none.
Check that we preserved all substantive info: application window, locations, about the job paragraph, responsibilities list, minimum qualifications, preferred qualifications, pay details. Did we miss any? The posting also includes "Learn more about benefits at Google ." That's a link; we removed as boilerplate/application instruction. It's okay.
Also there is a sentence: "As the Google Cloud Marketplace AI Partner Solutions Leader, you will grow in a fast-paced environment, develops a strong understanding of internal Google processes, products, and teams, and revels in managing big, complex and strategically important product and operations initiatives for Google Cloud Marketplace." That's part of About The Job paragraph; we included the whole paragraph? We need to ensure we included the entire About The Job paragraph. Let's capture it exactly:
"About The Job AI agents are transforming enterprise innovation and productivity. Scaling this value requires a trusted marketplace where enterprises can discover, evaluate, deploy, and govern solutions with confidence. This role sits at the intersection of marketplace business and product strategy, setting roadmap priorities, driving customer adoption, and enabling ecosystem scale As the Google Cloud Marketplace AI Partner Solutions Leader, you will grow in a fast-paced environment, develops a strong understanding of internal Google processes, products, and teams, and revels in managing big, complex and strategically important product and operations initiatives for Google Cloud Marketplace. You will elevate Google's differentiated strengths in AI, cloud, and enterprise products to deliver a market-leading commercial marketplace capabilities built with governance and interoperability in mind, and that will be used by a global partner and customer ecosystem. You will collaborate with cross-functional peers, navigate a rapidly-changing environment, and drive operational excellence across the business will be essential to success. The Global Partnerships organization is responsible for exploring new opportunities with Google's partners. Google’s Global Partnerships team works with a wide range of partners to bring the best of Google to power their business. The Global Partnerships team supports Google’s own Product teams with essential partnerships to help Google’s user experiences in advertising, Search, Assistant, Maps, Travel, Shopping, Payments and more. Teams create product-enabling partnerships, go-to-market strategies and incubate business growth for a variety of products."
We need to include that as prose in . Ensure we keep all sentences. The text has some minor grammatical issues but we keep as is
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key content: - Application window open until at least October 9, 2026. This opportunity will remain online based on business needs which may be before or after the specified date. Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Boulder, CO, USA; Atlanta, GA, USA; Austin, TX, USA; Chicago, IL, USA; Vancouver, BC, Canada. - Minimum qualifications: Bachelor's degree in Business Administration, Engineering, Computer Science, or equivalent practical experience. 15 years of experience with technology. Experience in a hyperscaler cloud marketplace, with focus on software licensing, procurement, and governance. Experience with IaaS/PaaS/SaaS markets, B2B software ecosystem and lifecycle, and cloud-based technologies. Experience with AI agent and infrastructure technologies, user experiences, and economics. - Preferred qualifications: MBA or equivalent. Experience managing complex enterprise products through scale distribution platforms. Expertise in cloud marketplace dynamics with experience in both supply and demand side domains, with measurable results fostering ecosystem development and enterprise procurement enablement. Knowledge of the evidence-driven approach that combines both qualitative and quantitative analysis grounded in cloud economics. Technical understanding of AI agents, agentic systems, trust, governance, and interoperability. Excellent cross-organizational leadership to influence executive business, product, engineering, and partner stakeholders. - About The Job: paragraph describing AI agents, role, etc. - Individual pay is determined by factors including job-related skills, experience, and relevant education or training. Canada: $232000 - $237000 (CAD) + 25% bonus target + equity + benefits US: $224000 - $311000 (USD) + 25% bonus target + equity + benefits - Responsibilities: list bullet points (starting with "Partner with product teams..." etc.) - Benefits: Not explicitly listed beyond "equity + benefits". The posting mentions benefits generically but not specifics. We should not create a Benefits section unless specific benefits are listed. The posting only says "+ equity + benefits". That's vague; maybe we can treat as part of Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay ranges and mentions bonus target, equity, benefits. So we can have a Pay section that includes the pay ranges and mention bonus, equity, benefits. Benefits section not needed if not detailed. - Schedule: Not mentioned. So no Schedule section. - About the role: we have "About The Job" paragraph. Could map to "About the role" heading. - Requirements: Minimum qualifications and Preferred qualifications could be combined into Requirements or Qualifications. The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have content for About the role (About The Job). Responsibilities (list). Requirements (minimum qualifications). Qualifications (preferred qualifications). Could also have Skills (maybe cross-organizational leadership etc). But we should avoid thin sections. Perhaps combine Minimum and Preferred into a single "Requirements" section with sublists? Or separate "Minimum Qualifications" and "Preferred Qualifications" as subheadings? But only allowed headings are those listed; we cannot create custom headings like "Minimum Qualifications". We could use "Requirements" for minimum qualifications and "Qualifications" for preferred qualifications. That seems okay. - Skills: maybe we could list cross-organizational leadership etc under Skills. But we already have those in preferred qualifications. Could put them under Skills. However we need to avoid duplication. Let's think: The posting includes "Excellent cross-organizational leadership to influence executive business, product, engineering, and partner stakeholders." That's a skill. Also "Technical understanding of AI agents, agentic systems, trust, governance, and interoperability." That's also skill/knowledge. Could be placed under Skills. But we need to preserve all substantive information. If we put them under Skills, we still preserve. If we put them under Qualifications (preferred), also preserve. We need to decide which sections to include to avoid thin sections. We have: - About the role: paragraph about AI agents, role description. - Responsibilities: list of bullet points. - Requirements (minimum qualifications): Bachelor's degree, 15 years experience, experience in hyperscaler cloud marketplace, experience with IaaS/PaaS/SaaS markets, experience with AI agent and infrastructure technologies, user experiences, economics. - Qualifications (preferred): MBA or equivalent, experience managing complex enterprise products through scale distribution platforms, expertise in cloud marketplace dynamics (supply/demand), knowledge of evidence-driven approach, technical understanding of AI agents etc, excellent cross-organizational leadership. - Pay: salary ranges and bonus, equity, benefits. We could also include a short paragraph about application window and preferred working locations. That could be placed under a heading like "About the role" or maybe a separate "Details" but not in allowed headings. Could fold into About the role paragraph? The allowed headings are limited; we could include that info in a
under About the role or maybe under a generic
before sections. The instruction: do NOT repeat the job title as a heading and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short
for application window and locations before sections. Thus output:
The application window will be open until at least October 9, 2026. This opportunity will remain online based on business needs which may be before or after the specified date. By applying to this position you will have an opportunity to share your preferred working location from the following: Boulder, CO, USA; Atlanta, GA, USA; Austin, TX, USA; Chicago, IL, USA; Vancouver, BC, Canada.
Then sections:About the role
[the About The Job paragraph]
Responsibilities
- Partner with product teams to translate business priorities into product truth across multiple experiences using usage telemetry and user research.
- Focus on high-value, enterprise problems with an evidence-based approach, supported by a deep understanding of competitive experiences.
- Improve business value by improving end user discoverability and ease of use.
- Unblock enterprise procurement with controls that enable governance and trust without sacrificing usability.
- Launch capabilities that allow Google to recruit and co-innovate with partners enabling customer choice and scale leveraging Marketplace’s favorable economics, and distribution at-scale.
- Turn commercial and operational constraints into differentiated value for customers, partners, and Google.
Requirements
- Bachelor's degree in Business Administration, Engineering, Computer Science, or equivalent practical experience.
- 15 years of experience with technology.
- Experience in a hyperscaler cloud marketplace, with focus on software licensing, procurement, and governance.
- Experience with IaaS/PaaS/SaaS markets, B2B software ecosystem and lifecycle, and cloud-based technologies.
- Experience with AI agent and infrastructure technologies, user experiences, and economics.
Qualifications
- MBA or equivalent.
- Experience managing complex enterprise products through scale distribution platforms.
- Expertise in cloud marketplace dynamics with experience in both supply and demand side domains, with measurable results fostering ecosystem development and enterprise procurement enablement.
- Knowledge of the evidence-driven approach that combines both qualitative and quantitative analysis grounded in cloud economics.
- Technical understanding of AI agents, agentic systems, trust, governance, and interoperability.
- Excellent cross-organizational leadership to influence executive business, product, engineering, and partner stakeholders.
Pay
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. Canada: $232,000 - $237,000 (CAD) + 25% bonus target + equity + benefits. US: $224,000 - $311,000 (USD) + 25% bonus target + equity + benefits.
We should not include Benefits section separately because we already mention benefits in Pay. No Schedule. We must ensure we didn't include any boilerplate like EEO etc. We removed that. Check for duplicated lines: we didn't repeat. Check for any placeholder text: none. Check that we preserved all substantive info: application window, locations, about the job paragraph, responsibilities list, minimum qualifications, preferred qualifications, pay details. Did we miss any? The posting also includes "Learn more about benefits at Google ." That's a link; we removed as boilerplate/application instruction. It's okay. Also there is a sentence: "As the Google Cloud Marketplace AI Partner Solutions Leader, you will grow in a fast-paced environment, develops a strong understanding of internal Google processes, products, and teams, and revels in managing big, complex and strategically important product and operations initiatives for Google Cloud Marketplace." That's part of About The Job paragraph; we included the whole paragraph? We need to ensure we included the entire About The Job paragraph. Let's capture it exactly: "About The Job AI agents are transforming enterprise innovation and productivity. Scaling this value requires a trusted marketplace where enterprises can discover, evaluate, deploy, and govern solutions with confidence. This role sits at the intersection of marketplace business and product strategy, setting roadmap priorities, driving customer adoption, and enabling ecosystem scale As the Google Cloud Marketplace AI Partner Solutions Leader, you will grow in a fast-paced environment, develops a strong understanding of internal Google processes, products, and teams, and revels in managing big, complex and strategically important product and operations initiatives for Google Cloud Marketplace. You will elevate Google's differentiated strengths in AI, cloud, and enterprise products to deliver a market-leading commercial marketplace capabilities built with governance and interoperability in mind, and that will be used by a global partner and customer ecosystem. You will collaborate with cross-functional peers, navigate a rapidly-changing environment, and drive operational excellence across the business will be essential to success. The Global Partnerships organization is responsible for exploring new opportunities with Google's partners. Google’s Global Partnerships team works with a wide range of partners to bring the best of Google to power their business. The Global Partnerships team supports Google’s own Product teams with essential partnerships to help Google’s user experiences in advertising, Search, Assistant, Maps, Travel, Shopping, Payments and more. Teams create product-enabling partnerships, go-to-market strategies and incubate business growth for a variety of products." We need to include that as prose in. Ensure we keep all sentences. The text has some minor grammatical issues but we keep as is