Agentic Data Cloud Sales Specialist III, Cloud
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading. Do not include Job ID. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. Benefits section only if posting actually states them. The posting includes: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $200000 (USD) + 100% bonus target + equity + benefits". So we have pay info. Benefits: mention "benefits" but not details. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay and mentions benefits but not specifics. Should we include Benefits section? It says "benefits" but no detail. Might be considered filler? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but no detail. Might be okay to include a Benefits section with generic statement? But they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "benefits" is vague but it's stated. Could include a Benefits section with a short
that says "Eligible for Google's benefits package." However that might be considered invented detail. Safer to omit Benefits section because no specific benefits listed. Pay section we have specific range and bonus target + equity. So include Pay.
Schedule: not mentioned, so omit.
Now sections: About the role (maybe "About the job"): we have a paragraph describing the job. Use
About the role
then with that prose.
Responsibilities: we have bullet list after "Responsibilities". Need to extract list items.
Let's parse responsibilities block:
"Responsibilities Learn more about benefits at Google . Deliver against quota and achieve or exceed strategic business and growth goals. Drive net-new greenfield logos and workloads in existing accounts through proactive campaigns. Run complex, multi-threaded business cycles from initial discovery and value hypothesis to ROI business case creation and commercial close.Engage Line of Business leaders, Chief Data Officer, Chief Financial Officer, Chief Marketing Officer, Chief AI Officer, through value-selling, tying modern Data and AI capabilities to quantified business outcomes.Align cross-functionally with FSRs and Partners to execute joint Data+AI plays, driving platform standardization and co-sell motions.Whiteboard modern architectures (BigQuery, Spark, Spanner, AlloyDB) to demonstrate how unified data foundations power high-performance, hallucination-free AI agents."
We need to split into list items. Likely each sentence is a responsibility. So list:
- Deliver against quota and achieve or exceed strategic business and growth goals.
- Drive net-new greenfield logos and workloads in existing accounts through proactive campaigns.
- Run complex, multi-threaded business cycles from initial discovery and value hypothesis to ROI business case creation and commercial close.
- Engage Line of Business leaders, Chief Data Officer, Chief Financial Officer, Chief Marketing Officer, Chief AI Officer, through value-selling, tying modern Data and AI capabilities to quantified business outcomes.
- Align cross-functionally with FSRs and Partners to execute joint Data+AI plays, driving platform standardization and co-sell motions.
- Whiteboard modern architectures (BigQuery, Spark, Spanner, AlloyDB) to demonstrate how unified data foundations power high-performance, hallucination-free AI agents.
Also there is "Learn more about benefits at Google ." That's a link/instruction; should be removed as application instruction? It's not a responsibility but maybe part of responsibilities block. It's likely boilerplate; we should remove it.
Now Requirements / Qualifications: The posting includes "Minimum qualifications:" and "Preferred qualifications:" plus some earlier bullet-like statements before "About The Job". Let's capture.
Before "About The Job" we have:
"Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Atlanta, GA, USA; Addison, TX, USA.Minimum qualifications: Bachelor's degree or equivalent practical experience.10 years of quota-carrying enterprise sales experience.Experience building business cases through workshops or product demos to business executives.Experience developing partnerships with technical stakeholders (e.g., Enterprise Architects, Data Engineers, Data Scientists).Experience positioning and selling technical solutions in data management, analytics, infrastructure, or AI/ML. Preferred qualifications: Experience positioning modern cloud data platforms, lakehouses, real-time streaming, or GenAI platforms against legacy or other proprietary enterprise systems.Experience working with Global System Integrators, hyperscalers, or ISVs to co-sell and accelerate pipeline.Experience managing large-scale data and AI transformation agreements within specific regulated or high-growth enterprise verticals (e.g., Financial Services, Healthcare/Life Sciences, Retail, or Manufacturing).Practical understanding of how modern cloud architectures, data governance (e.g., cataloging, lineage, compliance), and clean data estates enable AI and real-time analytics."
We need to separate Minimum qualifications and Preferred qualifications into sections. Could combine into Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (maybe minimum qualifications) and Qualifications (preferred). Or we could have Requirements for minimum, Qualifications for preferred. We'll do that.
Thus:
Requirements
with - for each minimum qualification.
Minimum qualifications list:
- Bachelor's degree or equivalent practical experience.
- 10 years of quota-carrying enterprise sales experience.
- Experience building business cases through workshops or product demos to business executives.
- Experience developing partnerships with technical stakeholders (e.g., Enterprise Architects, Data Engineers, Data Scientists).
- Experience positioning and selling technical solutions in data management, analytics, infrastructure, or AI/ML.
Preferred qualifications list:
- Experience positioning modern cloud data platforms, lakehouses, real-time streaming, or GenAI platforms against legacy or other proprietary enterprise systems.
- Experience working with Global System Integrators, hyperscalers, or ISVs to co-sell and accelerate pipeline.
- Experience managing large-scale data and AI transformation agreements within specific regulated or high-growth enterprise verticals (e.g., Financial Services, Healthcare/Life Sciences, Retail, or Manufacturing).
- Practical understanding of how modern cloud architectures, data governance (e.g., cataloging, lineage, compliance), and clean data estates enable AI and real-time analytics.
Now About the role: we need to extract the prose after "About The Job". Let's capture that paragraph(s). The text:
"About The Job The Google Cloud Platform team helps customers transform and build what's next for their business — all with technology built in the cloud. Our products are developed for security, reliability and scalability, running the full stack from infrastructure to applications to devices and hardware. Our teams are dedicated to helping our customers — developers, small and large businesses, educational institutions and government agencies — see the benefits of our technology come to life. As part of an entrepreneurial team in this rapidly growing business, you will play a key role in understanding the needs of our customers and help shape the future of businesses of all sizes use technology to connect with customers, employees and partners. As an Agentic Data Cloud Sales Specialist, you will be at the forefront of driving Google Cloud's most critical data and AI growth. In this role, you will drive growth by securing net-new greenfield logos and identify untapped, uncommitted workloads. You will partner with Field Sales Representatives, Customer Engineers, and Partners to execute joint Data+AI plays that establish long-term data platform standardization. You will engage with line-of-business (LoB) leaders, CDO, CAIO, and CFO to discover critical pain points, build robust business cases (ROI/TCO reduction), and demonstrate the quantifiable business value of modernizing data estates on GCP. Additionally, you will guide technical stakeholders and position Google Cloud's Agentic Data Cloud suite (BigQuery, Knowledge Catalog, Borderless Lakehouse, Spanner, AlloyDB) as the premium data intelligence platform for AI. Present demos that showcase how unified, well-governed data foundations power secure, hallucination-free AI agents and real-time experiences. Google Cloud accelerates every organization’s ability to digitally transform its business and industry. We deliver enterprise-grade solutions that leverage Google’s cutting-edge technology, and tools that help developers build more sustainably. Customers in more than 200 countries and territories turn to Google Cloud as their trusted partner to enable growth and solve their most critical business problems."
We need to put that into
(maybe multiple paragraphs but we can combine into one
or split). Use
for prose. Could split into multiple
for readability but not required. We'll output a single
containing the whole block.
Now Pay section: we have "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $200000 (USD) + 100% bonus target + equity + benefits". We'll put in
Pay
then with that sentence.
We should not include Benefits separate.
Now ensure we removed boilerplate: EEO, accommodation, etc. Also removed "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Atlanta, GA, USA; Addison, TX, USA." That's location note; maybe we could keep as metadata? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location is minor metadata; we could include a short
at top maybe. But they said "fold minor metadata into a short
or drop it." Could include a
with location info. However they also said "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a short
for location. But is location considered minor metadata? Probably yes. We'll include a
at start: "Preferred work locations: Atlanta, GA, USA; Addison, TX, USA." However the note also mentions "By applying to this position you will have an opportunity to share your preferred working location". That's a bit fluff. We could just include the locations.
But we need to decide whether to include it. The instruction says we can fold minor metadata into a short
or drop it. It's optional. I'd include a short
for location.
Now ensure no duplicated lines.
Now produce HTML fragment:
Preferred work locations: Atlanta, GA, USA; Addison, TX, USA.
About the role
... (the about job paragraph) ...
Responsibilities
- Deliver against quota and achieve or exceed strategic business and growth goals.
- Drive net-new greenfield logos and workloads in existing accounts through proactive campaigns.
- Run complex, multi-threaded business cycles from initial discovery and value hypothesis to ROI business case creation and commercial close.
- Engage Line of Business leaders, Chief Data Officer, Chief Financial Officer, Chief Marketing Officer, Chief AI Officer, through value-selling, tying modern Data and AI capabilities to quantified business outcomes.
- Align cross-functionally with FSRs and Partners to execute joint Data+AI plays, driving platform standardization and co-sell motions.
- Whiteboard modern architectures (BigQuery, Spark, Spanner, AlloyDB) to demonstrate how unified data foundations power high-performance, hallucination-free AI
for prose. Do not repeat job title as heading. Do not include Job ID. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. Benefits section only if posting actually states them. The posting includes: "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $200000 (USD) + 100% bonus target + equity + benefits". So we have pay info. Benefits: mention "benefits" but not details. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay and mentions benefits but not specifics. Should we include Benefits section? It says "benefits" but no detail. Might be considered filler? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but no detail. Might be okay to include a Benefits section with generic statement? But they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "benefits" is vague but it's stated. Could include a Benefits section with a short
that says "Eligible for Google's benefits package." However that might be considered invented detail. Safer to omit Benefits section because no specific benefits listed. Pay section we have specific range and bonus target + equity. So include Pay. Schedule: not mentioned, so omit. Now sections: About the role (maybe "About the job"): we have a paragraph describing the job. Use
About the role
thenwith that prose. Responsibilities: we have bullet list after "Responsibilities". Need to extract list items. Let's parse responsibilities block: "Responsibilities Learn more about benefits at Google . Deliver against quota and achieve or exceed strategic business and growth goals. Drive net-new greenfield logos and workloads in existing accounts through proactive campaigns. Run complex, multi-threaded business cycles from initial discovery and value hypothesis to ROI business case creation and commercial close.Engage Line of Business leaders, Chief Data Officer, Chief Financial Officer, Chief Marketing Officer, Chief AI Officer, through value-selling, tying modern Data and AI capabilities to quantified business outcomes.Align cross-functionally with FSRs and Partners to execute joint Data+AI plays, driving platform standardization and co-sell motions.Whiteboard modern architectures (BigQuery, Spark, Spanner, AlloyDB) to demonstrate how unified data foundations power high-performance, hallucination-free AI agents." We need to split into list items. Likely each sentence is a responsibility. So list: - Deliver against quota and achieve or exceed strategic business and growth goals. - Drive net-new greenfield logos and workloads in existing accounts through proactive campaigns. - Run complex, multi-threaded business cycles from initial discovery and value hypothesis to ROI business case creation and commercial close. - Engage Line of Business leaders, Chief Data Officer, Chief Financial Officer, Chief Marketing Officer, Chief AI Officer, through value-selling, tying modern Data and AI capabilities to quantified business outcomes. - Align cross-functionally with FSRs and Partners to execute joint Data+AI plays, driving platform standardization and co-sell motions. - Whiteboard modern architectures (BigQuery, Spark, Spanner, AlloyDB) to demonstrate how unified data foundations power high-performance, hallucination-free AI agents. Also there is "Learn more about benefits at Google ." That's a link/instruction; should be removed as application instruction? It's not a responsibility but maybe part of responsibilities block. It's likely boilerplate; we should remove it. Now Requirements / Qualifications: The posting includes "Minimum qualifications:" and "Preferred qualifications:" plus some earlier bullet-like statements before "About The Job". Let's capture. Before "About The Job" we have: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Atlanta, GA, USA; Addison, TX, USA.Minimum qualifications: Bachelor's degree or equivalent practical experience.10 years of quota-carrying enterprise sales experience.Experience building business cases through workshops or product demos to business executives.Experience developing partnerships with technical stakeholders (e.g., Enterprise Architects, Data Engineers, Data Scientists).Experience positioning and selling technical solutions in data management, analytics, infrastructure, or AI/ML. Preferred qualifications: Experience positioning modern cloud data platforms, lakehouses, real-time streaming, or GenAI platforms against legacy or other proprietary enterprise systems.Experience working with Global System Integrators, hyperscalers, or ISVs to co-sell and accelerate pipeline.Experience managing large-scale data and AI transformation agreements within specific regulated or high-growth enterprise verticals (e.g., Financial Services, Healthcare/Life Sciences, Retail, or Manufacturing).Practical understanding of how modern cloud architectures, data governance (e.g., cataloging, lineage, compliance), and clean data estates enable AI and real-time analytics." We need to separate Minimum qualifications and Preferred qualifications into sections. Could combine into Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (maybe minimum qualifications) and Qualifications (preferred). Or we could have Requirements for minimum, Qualifications for preferred. We'll do that. Thus:
Requirements
with- for each minimum qualification.
Minimum qualifications list:
- Bachelor's degree or equivalent practical experience.
- 10 years of quota-carrying enterprise sales experience.
- Experience building business cases through workshops or product demos to business executives.
- Experience developing partnerships with technical stakeholders (e.g., Enterprise Architects, Data Engineers, Data Scientists).
- Experience positioning and selling technical solutions in data management, analytics, infrastructure, or AI/ML.
Preferred qualifications list:
- Experience positioning modern cloud data platforms, lakehouses, real-time streaming, or GenAI platforms against legacy or other proprietary enterprise systems.
- Experience working with Global System Integrators, hyperscalers, or ISVs to co-sell and accelerate pipeline.
- Experience managing large-scale data and AI transformation agreements within specific regulated or high-growth enterprise verticals (e.g., Financial Services, Healthcare/Life Sciences, Retail, or Manufacturing).
- Practical understanding of how modern cloud architectures, data governance (e.g., cataloging, lineage, compliance), and clean data estates enable AI and real-time analytics.
Now About the role: we need to extract the prose after "About The Job". Let's capture that paragraph(s). The text:
"About The Job The Google Cloud Platform team helps customers transform and build what's next for their business — all with technology built in the cloud. Our products are developed for security, reliability and scalability, running the full stack from infrastructure to applications to devices and hardware. Our teams are dedicated to helping our customers — developers, small and large businesses, educational institutions and government agencies — see the benefits of our technology come to life. As part of an entrepreneurial team in this rapidly growing business, you will play a key role in understanding the needs of our customers and help shape the future of businesses of all sizes use technology to connect with customers, employees and partners. As an Agentic Data Cloud Sales Specialist, you will be at the forefront of driving Google Cloud's most critical data and AI growth. In this role, you will drive growth by securing net-new greenfield logos and identify untapped, uncommitted workloads. You will partner with Field Sales Representatives, Customer Engineers, and Partners to execute joint Data+AI plays that establish long-term data platform standardization. You will engage with line-of-business (LoB) leaders, CDO, CAIO, and CFO to discover critical pain points, build robust business cases (ROI/TCO reduction), and demonstrate the quantifiable business value of modernizing data estates on GCP. Additionally, you will guide technical stakeholders and position Google Cloud's Agentic Data Cloud suite (BigQuery, Knowledge Catalog, Borderless Lakehouse, Spanner, AlloyDB) as the premium data intelligence platform for AI. Present demos that showcase how unified, well-governed data foundations power secure, hallucination-free AI agents and real-time experiences. Google Cloud accelerates every organization’s ability to digitally transform its business and industry. We deliver enterprise-grade solutions that leverage Google’s cutting-edge technology, and tools that help developers build more sustainably. Customers in more than 200 countries and territories turn to Google Cloud as their trusted partner to enable growth and solve their most critical business problems."
We need to put that into
(maybe multiple paragraphs but we can combine into one
or split). Use
for prose. Could split into multiple
for readability but not required. We'll output a single
containing the whole block. Now Pay section: we have "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $200000 (USD) + 100% bonus target + equity + benefits". We'll put in
Pay
thenwith that sentence. We should not include Benefits separate. Now ensure we removed boilerplate: EEO, accommodation, etc. Also removed "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Atlanta, GA, USA; Addison, TX, USA." That's location note; maybe we could keep as metadata? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location is minor metadata; we could include a short
at top maybe. But they said "fold minor metadata into a short
or drop it." Could include a
with location info. However they also said "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a short
for location. But is location considered minor metadata? Probably yes. We'll include a
at start: "Preferred work locations: Atlanta, GA, USA; Addison, TX, USA." However the note also mentions "By applying to this position you will have an opportunity to share your preferred working location". That's a bit fluff. We could just include the locations. But we need to decide whether to include it. The instruction says we can fold minor metadata into a short
or drop it. It's optional. I'd include a short
for location. Now ensure no duplicated lines. Now produce HTML fragment:
Preferred work locations: Atlanta, GA, USA; Addison, TX, USA.
About the role
... (the about job paragraph) ...
Responsibilities
- Deliver against quota and achieve or exceed strategic business and growth goals.
- Drive net-new greenfield logos and workloads in existing accounts through proactive campaigns.
- Run complex, multi-threaded business cycles from initial discovery and value hypothesis to ROI business case creation and commercial close.
- Engage Line of Business leaders, Chief Data Officer, Chief Financial Officer, Chief Marketing Officer, Chief AI Officer, through value-selling, tying modern Data and AI capabilities to quantified business outcomes.
- Align cross-functionally with FSRs and Partners to execute joint Data+AI plays, driving platform standardization and co-sell motions.
- Whiteboard modern architectures (BigQuery, Spark, Spanner, AlloyDB) to demonstrate how unified data foundations power high-performance, hallucination-free AI