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. Preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Content:
- Application window open until at least Oct 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: (text) 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.
- 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: Learn more about benefits at Google . 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.
- Then there is EEO boilerplate etc which we must remove.
We need to decide sections: About the role (maybe "About The Job" content). Responsibilities (list). Requirements (maybe combine Minimum qualifications and Preferred qualifications? Could separate Qualifications and Skills? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if there is real specific content.
We have content for About the role (the "About The Job" paragraph). Responsibilities (list). Minimum qualifications and Preferred qualifications could go under Requirements or Qualifications. Could combine them into a Requirements section (maybe "Requirements") with sub-lists? But we need to use
- for any list of duties/requirements/benefits. So we can have a Requirements section with
listing each bullet.
We also have Pay info (salary ranges). So we need a Pay section. Benefits? The posting mentions benefits generically: "Learn more about benefits at Google." and also " + equity + benefits". No specific benefits listed. The instruction: never create Benefits section unless posting actually states them. It does mention benefits but not specifics. Should we include a Benefits section? It says "Learn more about benefits at Google." That's a reference but not specific benefits. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist but not detail. Might be considered stating them generically. However we should avoid creating a Benefits section with filler like "not specified". Better to omit Benefits section unless we have specific benefits listed. Since none are listed, we omit Benefits.
Schedule: no mention. Omit.
Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Pay.
We need to decide heading names: "About the role", "Responsibilities", "Requirements", "Pay". Use for each.
Inside each section, we need to put content: For About the role, we have prose paragraphs. Use
for prose. Could combine multiple paragraphs into separate
tags.
For Responsibilities, we have a list of duties. Use
- for each.
For Requirements, we have minimum and preferred qualifications. Could list them as bullet points. Use
- .
For Pay, we have salary ranges. Could present as
with the ranges.
We must not repeat job title as heading. No Job ID.
We must remove boilerplate: EEO, accommodation, etc. Also remove "Learn more about benefits at Google ." Actually that sentence appears in Responsibilities? It appears after "Learn more about benefits at Google ." That's a reference to benefits; we should keep it? It's part of responsibilities? Actually it's a sentence: "Learn more about benefits at Google ." It seems like a stray line maybe from template. It's not a responsibility. Might be considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more about benefits at Google" is not exactly those but could be considered a generic link. Might be considered boilerplate. Safer to remove it. However it's inside the responsibilities block. If we remove it, we lose a sentence but it's not a responsibility. I'd remove it.
Now let's extract responsibilities list:
- 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.
That's six items.
Now About the role prose: We have multiple sentences. Let's break into paragraphs logically.
Paragraph 1: "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."
Paragraph 2: "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."
Note there is a missing space after "scale As". We'll keep as is.
Paragraph 3: "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."
Paragraph 4: "You will collaborate with cross-functional peers, navigate a rapidly-changing environment, and drive operational excellence across the business will be essential to success."
Paragraph 5: "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 could combine some but fine.
Now Requirements: Minimum qualifications bullet list:
- 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 bullet list:
- 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.
We could combine into one list under Requirements, but maybe separate Minimum and Preferred? The instruction says prefer few substantive sections over many thin ones. Could have a single Requirements section with all bullets, maybe label within? But we cannot add extra headings inside. Could just list all bullets; it's fine.
Now Pay: Provide the salary ranges.
We need to output only HTML fragment, no /, no markdown fences.
Thus output:
About the role
...
...
...
Responsibilities
- ...
...
Requirements
- ...
...
Pay
Canada: $232000 - $237000 (CAD) + 25% bonus target + equity + benefits
US: $224000 - $3110
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Application window open until at least Oct 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: (text) 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. - 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: Learn more about benefits at Google . 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. - Then there is EEO boilerplate etc which we must remove. We need to decide sections: About the role (maybe "About The Job" content). Responsibilities (list). Requirements (maybe combine Minimum qualifications and Preferred qualifications? Could separate Qualifications and Skills? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if there is real specific content. We have content for About the role (the "About The Job" paragraph). Responsibilities (list). Minimum qualifications and Preferred qualifications could go under Requirements or Qualifications. Could combine them into a Requirements section (maybe "Requirements") with sub-lists? But we need to use
- for any list of duties/requirements/benefits. So we can have a Requirements section with
- listing each bullet.
We also have Pay info (salary ranges). So we need a Pay section. Benefits? The posting mentions benefits generically: "Learn more about benefits at Google." and also " + equity + benefits". No specific benefits listed. The instruction: never create Benefits section unless posting actually states them. It does mention benefits but not specifics. Should we include a Benefits section? It says "Learn more about benefits at Google." That's a reference but not specific benefits. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist but not detail. Might be considered stating them generically. However we should avoid creating a Benefits section with filler like "not specified". Better to omit Benefits section unless we have specific benefits listed. Since none are listed, we omit Benefits.
Schedule: no mention. Omit.
Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Pay.
We need to decide heading names: "About the role", "Responsibilities", "Requirements", "Pay". Use
- for each.
For Requirements, we have minimum and preferred qualifications. Could list them as bullet points. Use
- .
For Pay, we have salary ranges. Could present as
with the ranges. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, accommodation, etc. Also remove "Learn more about benefits at Google ." Actually that sentence appears in Responsibilities? It appears after "Learn more about benefits at Google ." That's a reference to benefits; we should keep it? It's part of responsibilities? Actually it's a sentence: "Learn more about benefits at Google ." It seems like a stray line maybe from template. It's not a responsibility. Might be considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more about benefits at Google" is not exactly those but could be considered a generic link. Might be considered boilerplate. Safer to remove it. However it's inside the responsibilities block. If we remove it, we lose a sentence but it's not a responsibility. I'd remove it. Now let's extract responsibilities list: - 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. That's six items. Now About the role prose: We have multiple sentences. Let's break into paragraphs logically. Paragraph 1: "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." Paragraph 2: "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." Note there is a missing space after "scale As". We'll keep as is. Paragraph 3: "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." Paragraph 4: "You will collaborate with cross-functional peers, navigate a rapidly-changing environment, and drive operational excellence across the business will be essential to success." Paragraph 5: "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 could combine some but fine. Now Requirements: Minimum qualifications bullet list: - 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 bullet list: - 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. We could combine into one list under Requirements, but maybe separate Minimum and Preferred? The instruction says prefer few substantive sections over many thin ones. Could have a single Requirements section with all bullets, maybe label within? But we cannot add extra headings inside. Could just list all bullets; it's fine. Now Pay: Provide the salary ranges. We need to output only HTML fragment, no /, no markdown fences. Thus output:
About the role
...
...
...Responsibilities
- ... ...
Requirements
- ... ...
Pay
Canada: $232000 - $237000 (CAD) + 25% bonus target + equity + benefits
US: $224000 - $3110
- .
For Pay, we have salary ranges. Could present as
for each. Inside each section, we need to put content: For About the role, we have prose paragraphs. Use
for prose. Could combine multiple paragraphs into separate
tags. For Responsibilities, we have a list of duties. Use
- for each.
For Requirements, we have minimum and preferred qualifications. Could list them as bullet points. Use