Workspace Sales Specialist III, Enterprise Greenfield, Cloud
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. 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.
Thus we need to parse the posting and extract sections.
Let's identify sections:
- Benefits: described in first paragraph: "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees. 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"
Also note: "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." That's a legal note; we should remove EEO/equal-opportunity boilerplate? This is a specific location note about Fair Chance. Might be considered EEO? It's a legal requirement; but it's not exactly EEO boilerplate; but it's a legal note. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This seems like legal boilerplate; we should remove it. However it's specific to San Francisco applicants; but it's still a legal note. Probably remove.
- "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: In-office locations: New York, NY, USA; Atlanta, GA, USA; Cambridge, MA, USA; Reston, VA, USA; Austin, TX, USA; Chicago, IL, USA; Seattle, WA, USA; Sunnyvale, CA, USA; San Francisco, CA, USA; Washington D.C., DC, USA. Remote location(s): Connecticut, USA; District of Columbia, USA."
That's location info; not a standard section but could be considered part of "About the role"? Might be considered metadata; but we can include as a short paragraph under maybe "About the role" or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. This location info is minor metadata; we could fold into a short
under About the role or maybe a separate "Location" section? Not in list of allowed headings; but we could just include as a paragraph under About the role.
- Minimum qualifications: list: Bachelor's degree or equivalent practical experience. 10 years of experience in a sales role in the enterprise software or cloud space. Experience selling Software as a Service (SaaS), productivity, or collaboration technology solutions to clients.
- Preferred qualifications: list of bullet-like sentences: Experience carrying and exceeding strategic business goals in a sales role. Experience prospecting, and building and maintaining customer relationships from scratch, with excitement for building Greenfield territories, and acquiring new logos at scale and securing the foundational workload(s) to accelerate consumption business. Experience prioritizing, planning, and organizing solution-based sales activity within complex business cycles, including qualifying high value accounts and leveraging our partner ecosystem. Knowledge of market trends, products, and solutions in cloud, and productivity and collaboration. Strong negotiation, problem-solving, communication, presentation and active listening skills.
- About The Job: paragraph(s) describing role.
- Responsibilities: list of bullet points after "Responsibilities Learn more about benefits at Google ." Actually there is a line: "Responsibilities Learn more about benefits at Google ." Then bullet points: Build relationships with customers as a subject matter expert and trusted advisor, managing complex business cycles, identifying solution use cases, and influencing long-term strategic direction of accounts. Deliver against quota and achieve or exceed strategic business and growth goals while forecasting and reporting your territory’s business. Work with Google accounts and cross-functional teams (e.g. Customer Engineering, Marketing, Customer Success, Product, Engineering, Channels) to develop go-to-market strategies, drive pipeline and business growth, close agreements, understand the customer, and provide excellent prospect and customer experience. Construct and execute an effective territory development plan. Lead prospecting, acquisition, and development of new Workspace opportunities in your assigned territory, creating and building customer relationships from scratch, while also maintaining and building current accounts.
- 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"
Thus we have sections: About the role (About The Job), Responsibilities, Minimum qualifications (maybe Requirements?), Preferred qualifications (maybe Qualifications?), Benefits, Pay.
We need to use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have "Minimum qualifications" and "Preferred qualifications". Could combine into "Requirements" and "Qualifications"? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map:
- About the role -> About The Job (use heading About the role)
- Responsibilities -> Responsibilities
- Requirements -> Minimum qualifications (maybe combine with Preferred? But we have both; we could have Requirements for minimum qualifications, and Qualifications for preferred qualifications. That seems appropriate.
- Skills -> maybe not present; we could omit if no specific skills section. The instruction: include a section ONLY when the posting has real, specific content for it. So we should not create Skills if not present.
- Benefits -> Benefits
- Pay -> Pay
- Schedule -> not present; omit.
Thus we will output:
About the role
... (the About The Job paragraph(s) )
Responsibilities
- ... each bullet
Requirements
- Bachelor's degree or equivalent practical experience.
- 10 years of experience in a sales role in the enterprise software or cloud space.
- Experience selling Software as a Service (SaaS), productivity, or collaboration technology solutions to clients.
Qualifications
- Experience carrying and exceeding strategic business goals in a sales role.
- Experience prospecting, and building and maintaining customer relationships from scratch, with excitement for building Greenfield territories, and acquiring new logos at scale and securing the foundational workload(s) to accelerate consumption business.
- Experience prioritizing, planning, and organizing solution-based sales activity within complex business cycles, including qualifying high value accounts and leveraging our partner ecosystem.
- Knowledge of market trends, products, and solutions in cloud, and productivity and collaboration.
- Strong negotiation, problem-solving, communication, presentation and active listening skills.
Benefits
- 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
- Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks
- Baby Bonding Leave: 18 weeks
- Holidays: 13 paid days per year
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 also need to include location info? Could be folded into About the role as a short paragraph. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. So we can add a short paragraph after About the role paragraph about locations.
Thus About the role section could have two paragraphs: first the descriptive paragraph(s) about the job, second a short paragraph about locations.
We need to preserve all substantive information; we must not drop the location info entirely? It's minor metadata but we can fold into a short
. So we will include it.
Now we need to remove boilerplate: EEO statements, "Google is proud to be an equal opportunity workplace..." etc. Also "Learn more about benefits at Google ." appears in Responsibilities line; we should remove that as it's likely a link/instruction. The line: "Responsibilities Learn more about benefits at Google ." Actually the text: "Responsibilities Learn more about benefits at Google . Build relationships..." So we should strip "Learn more about benefits at Google ." from the responsibilities heading? The heading is Responsibilities; after that we have that phrase. We should treat it as boilerplate and remove. So responsibilities list starts after that.
Also we need to remove duplicated lines: there may be duplicates but not seen.
Now ensure we don't include any markdown fences.
Now produce final HTML.
Check that we didn't miss any substantive info: The benefits list includes "Health, dental, vision, life, disability insurance" (might be missing commas but fine). Also "Retirement Benefits: 401(k) with company match". Also "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". Also "Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance". Also "Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks". Also "Baby Bonding Leave: 18 weeks". Also "Holidays: 13 paid days per year". Good.
Pay: includes "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $200000 (
for prose. 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. 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. Thus we need to parse the posting and extract sections. Let's identify sections: - Benefits: described in first paragraph: "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees. 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" Also note: "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." That's a legal note; we should remove EEO/equal-opportunity boilerplate? This is a specific location note about Fair Chance. Might be considered EEO? It's a legal requirement; but it's not exactly EEO boilerplate; but it's a legal note. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This seems like legal boilerplate; we should remove it. However it's specific to San Francisco applicants; but it's still a legal note. Probably remove. - "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: In-office locations: New York, NY, USA; Atlanta, GA, USA; Cambridge, MA, USA; Reston, VA, USA; Austin, TX, USA; Chicago, IL, USA; Seattle, WA, USA; Sunnyvale, CA, USA; San Francisco, CA, USA; Washington D.C., DC, USA. Remote location(s): Connecticut, USA; District of Columbia, USA." That's location info; not a standard section but could be considered part of "About the role"? Might be considered metadata; but we can include as a short paragraph under maybe "About the role" or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. This location info is minor metadata; we could fold into a short
under About the role or maybe a separate "Location" section? Not in list of allowed headings; but we could just include as a paragraph under About the role. - Minimum qualifications: list: Bachelor's degree or equivalent practical experience. 10 years of experience in a sales role in the enterprise software or cloud space. Experience selling Software as a Service (SaaS), productivity, or collaboration technology solutions to clients. - Preferred qualifications: list of bullet-like sentences: Experience carrying and exceeding strategic business goals in a sales role. Experience prospecting, and building and maintaining customer relationships from scratch, with excitement for building Greenfield territories, and acquiring new logos at scale and securing the foundational workload(s) to accelerate consumption business. Experience prioritizing, planning, and organizing solution-based sales activity within complex business cycles, including qualifying high value accounts and leveraging our partner ecosystem. Knowledge of market trends, products, and solutions in cloud, and productivity and collaboration. Strong negotiation, problem-solving, communication, presentation and active listening skills. - About The Job: paragraph(s) describing role. - Responsibilities: list of bullet points after "Responsibilities Learn more about benefits at Google ." Actually there is a line: "Responsibilities Learn more about benefits at Google ." Then bullet points: Build relationships with customers as a subject matter expert and trusted advisor, managing complex business cycles, identifying solution use cases, and influencing long-term strategic direction of accounts. Deliver against quota and achieve or exceed strategic business and growth goals while forecasting and reporting your territory’s business. Work with Google accounts and cross-functional teams (e.g. Customer Engineering, Marketing, Customer Success, Product, Engineering, Channels) to develop go-to-market strategies, drive pipeline and business growth, close agreements, understand the customer, and provide excellent prospect and customer experience. Construct and execute an effective territory development plan. Lead prospecting, acquisition, and development of new Workspace opportunities in your assigned territory, creating and building customer relationships from scratch, while also maintaining and building current accounts. - 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" Thus we have sections: About the role (About The Job), Responsibilities, Minimum qualifications (maybe Requirements?), Preferred qualifications (maybe Qualifications?), Benefits, Pay. We need to use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "Minimum qualifications" and "Preferred qualifications". Could combine into "Requirements" and "Qualifications"? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map:
- About the role -> About The Job (use heading About the role)
- Responsibilities -> Responsibilities
- Requirements -> Minimum qualifications (maybe combine with Preferred? But we have both; we could have Requirements for minimum qualifications, and Qualifications for preferred qualifications. That seems appropriate.
- Skills -> maybe not present; we could omit if no specific skills section. The instruction: include a section ONLY when the posting has real, specific content for it. So we should not create Skills if not present.
- Benefits -> Benefits
- Pay -> Pay
- Schedule -> not present; omit.
Thus we will output:
About the role
... (the About The Job paragraph(s) )
Responsibilities
- ... each bullet
Requirements
- Bachelor's degree or equivalent practical experience.
- 10 years of experience in a sales role in the enterprise software or cloud space.
- Experience selling Software as a Service (SaaS), productivity, or collaboration technology solutions to clients.
Qualifications
- Experience carrying and exceeding strategic business goals in a sales role.
- Experience prospecting, and building and maintaining customer relationships from scratch, with excitement for building Greenfield territories, and acquiring new logos at scale and securing the foundational workload(s) to accelerate consumption business.
- Experience prioritizing, planning, and organizing solution-based sales activity within complex business cycles, including qualifying high value accounts and leveraging our partner ecosystem.
- Knowledge of market trends, products, and solutions in cloud, and productivity and collaboration.
- Strong negotiation, problem-solving, communication, presentation and active listening skills.
Benefits
- 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
- Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks
- Baby Bonding Leave: 18 weeks
- Holidays: 13 paid days per year
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 also need to include location info? Could be folded into About the role as a short paragraph. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. So we can add a short paragraph after About the role paragraph about locations. Thus About the role section could have two paragraphs: first the descriptive paragraph(s) about the job, second a short paragraph about locations. We need to preserve all substantive information; we must not drop the location info entirely? It's minor metadata but we can fold into a short
. So we will include it. Now we need to remove boilerplate: EEO statements, "Google is proud to be an equal opportunity workplace..." etc. Also "Learn more about benefits at Google ." appears in Responsibilities line; we should remove that as it's likely a link/instruction. The line: "Responsibilities Learn more about benefits at Google ." Actually the text: "Responsibilities Learn more about benefits at Google . Build relationships..." So we should strip "Learn more about benefits at Google ." from the responsibilities heading? The heading is Responsibilities; after that we have that phrase. We should treat it as boilerplate and remove. So responsibilities list starts after that. Also we need to remove duplicated lines: there may be duplicates but not seen. Now ensure we don't include any markdown fences. Now produce final HTML. Check that we didn't miss any substantive info: The benefits list includes "Health, dental, vision, life, disability insurance" (might be missing commas but fine). Also "Retirement Benefits: 401(k) with company match". Also "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". Also "Sick Time: 40 hours/year (increased to 69 hours/year for Seattle) including 5 discretionary sick days per instance". Also "Maternity Leave (Short-Term Disability + Baby Bonding): 28-30 weeks". Also "Baby Bonding Leave: 18 weeks". Also "Holidays: 13 paid days per year". Good. Pay: includes "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $138000 - $200000 (