Agentic Data Cloud Sales Specialist III, Google Cloud

We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, legal, scam warning, duplicated lines, application instructions). Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to parse the posting. Let's extract content: - Location note: "This role may also be located in our Playa Vista, CA campus." Also location options list later: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: San Francisco, CA, USA; Atlanta, GA, USA; Austin, TX, USA; Kirkland, WA, USA; New York, NY, USA; Los Angeles, CA, USA; Reston, VA, USA." - Fair Chance Ordinance statements: "Applicants in the County of Los Angeles: Qualified applications with arrest or conviction records will be considered for employment in accordance with the Los Angeles County Fair Chance Ordinance for Employers and the California Fair Chance Act. Applicants in San Francisco: Qualified applications with arrest or conviction records will be considered for employment in accordance with the San Francisco Fair Chance Ordinance for Employers and the California Fair Chance Act. In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." These are legal statements; they might be considered boilerplate? They are about fair chance and benefits highlight. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Fair Chance Ordinance is legal; likely considered boilerplate and should be removed. Also the Washington state law highlighting benefits package is maybe part of benefits? It says "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." That's a statement about benefits being highlighted due to law; we can keep benefits details but maybe drop the sentence as it's legal boilerplate. We'll keep the benefits list. - Benefits list: "Benefits for this role include: Health, dental, vision, life, disability insuranceRetirement Benefits: 401(k) with company matchPaid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employmentSick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeksBaby Bonding Leave: 18 weeksHolidays: 13 paid days per year" We need to format as list items. - Pay: "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" - Responsibilities: list after "Responsibilities Learn more about benefits at Google ." Actually there is a line: "Responsibilities Learn more about benefits at Google ." Then bullet list: "Deliver against quota and achieve or exceed strategic business and growth goals, driving net-new greenfield logos and workloads in existing accounts through proactive campaigns. Run complex, multi-threaded sales cycles from initial discovery and value hypothesis to Return on Investment (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 Field Sales Representative (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 keep these as list items. - About the job: paragraph(s) after "About the job". Let's extract: "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 are a master of value-selling. 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. 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. You will 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 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 can combine into a few paragraphs. - Minimum qualifications: list: "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: list: "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 Independent Software Vendor (ISVs) to co-sell and accelerate pipeline. Experience closing large-scale data and AI transformation deals 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." - Skills? Not explicitly listed separate; maybe we can combine qualifications into Requirements and Skills? The instruction says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Minimum qualifications and Preferred qualifications. Could treat them as Requirements (minimum) and Qualifications (preferred). Or we could have Requirements (minimum) and Qualifications (preferred). Skills maybe not present; we could omit if no specific content. Schedule: Not mentioned; no schedule info. So we should not create Schedule section. Pay: we have content. Benefits: we have content. About the role: we have About the job content; could map to About the role. Responsibilities: we have. Thus sections: About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred qualifications), Benefits, Pay. We should not include Skills if no content. We must not repeat job title as heading. The job title is "Agentic Data Cloud Sales Specialist" maybe; we must not use that as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, legal, fair chance statements, etc. Also remove "Learn more about benefits at Google ." (that's a link). Also remove duplicated lines. We need to preserve all substantive information: location note? Should we keep location note? It's substantive: "This role may also be located in our Playa Vista, CA campus." Also the list of possible locations. Should we keep that? It's location info; not covered by headings but could be placed in a paragraph maybe under About the role or as a separate paragraph. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep location info. Where to put? Could be a short paragraph under About the role or maybe a separate section like "Location". But we only allowed headings list; we could add a

about location inside About the role or as its own paragraph before sections. Since we cannot add arbitrary headings not in list unless they have real content. Location is real content; we could add a

about location. The 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 says use

for section headings (e.g. those). Likely we should stick to those headings only; other info can be in

paragraphs. Thus we can have an initial

with location note and list of possible locations. Also the Fair Chance statements we should remove as legal boilerplate. Also the Washington state law highlighting benefits package sentence we can drop as legal. Now produce HTML. Structure:

This role may also be located in our Playa Vista, CA campus. Applicants can share their preferred working location from the following: San Francisco, CA, USA; Atlanta, GA, USA; Austin, TX, USA; Kirkland, WA, USA; New York, NY, USA; Los Angeles, CA, USA; Reston, VA, USA.

Then

About the role

followed by paragraphs (maybe split into two

for readability). We'll keep the content as is but maybe break into two paragraphs. Then

Responsibilities

• ... each responsibility. Then

  Requirements

  • ... minimum qualifications. Then

    Qualifications

    • ... preferred qualifications. Then

      Benefits

      • ... each benefit item. Then

        Pay

        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 should not include Schedule. Check for any duplicated lines: Ensure we didn't repeat. Now ensure we removed EEO etc. Also removed "Learn more about benefits at Google ." and the EEO statements. Check for any leftover legal: The Fair Chance statements removed. Also the Washington state law sentence removed. Now ensure we preserved all substantive info: location note, list of locations, about the job paragraphs, responsibilities, minimum qualifications, preferred qualifications, benefits, pay. Check benefits list: we need to split into items: Health, dental, vision, life, disability insurance; Retirement Benefits: 401(k) with company match; Paid Time Off: 20 days of vacation per year, accruing at a rate of 6.15 hours per pay period for the first five years of employment; Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance