Practice Customer Engineer, Data Analytics, Google Cloud
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate: application window date, fair chance ordinance, location notes, etc. Also remove EEO, accommodation instructions, etc. Keep substantive info: description of role, responsibilities, qualifications, preferred qualifications, benefits, pay, maybe schedule? No schedule info given. So we should not include Schedule heading.
We need to preserve all substantive information: The job description includes paragraphs about role, responsibilities list, minimum qualifications list, preferred qualifications list, benefits list, pay range.
We need to format using for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID.
We must not include filler like "commensurate with experience". Not present.
We need to decide sections: About the role (maybe "About The Job" paragraph). Responsibilities (list). Requirements (maybe Minimum qualifications). Qualifications (maybe Preferred qualifications). Skills? Could combine but we can have Skills section if we have specific skills listed. The posting includes many skill-like items in qualifications. Could put them under Requirements and Preferred qualifications. Could also have a Skills section summarizing technical skills. But we should only create sections if there is real specific content. The posting includes Minimum qualifications and Preferred qualifications as lists. Could treat Minimum qualifications as "Requirements" and Preferred qualifications as "Qualifications". Or we could have "Requirements" for minimum, "Preferred Qualifications" for preferred. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: Requirements = Minimum qualifications. Qualifications = Preferred qualifications. Skills maybe not needed separately if covered. But we could still include Skills if we want to list specific technical skills extracted from qualifications. However we must not invent or summarize away detail; we can keep the lists as is under appropriate headings.
Thus sections:
- About the role (maybe heading "About the role") with prose from "About The Job" paragraph.
- Responsibilities: list from responsibilities bullet points.
- Requirements: list from Minimum qualifications.
- Qualifications: list from Preferred qualifications.
- Benefits: list from benefits.
- Pay: maybe a paragraph with pay range.
We should not include Schedule.
We need to preserve all substantive information: The description includes sentences about role, responsibilities, etc. Ensure we keep all details.
Let's extract:
About The Job paragraph:
"When leading companies choose Google Cloud, it's a huge win for spreading the power of cloud computing globally. Once educational institutions, government agencies, and other businesses sign on to use Google Cloud products, you come in to facilitate making their work more productive, mobile, and collaborative. You listen and deliver what is most helpful for the customer. You assist fellow sales Googlers by problem-solving key technical issues for our customers. You liaise with the product marketing management and engineering teams to stay on top of industry trends and devise enhancements to Google Cloud products. As a Practice Customer Engineer (CE) with a specialty in Data Analytics, you will partner with technical sales teams to differentiate Google Cloud to our customers. You will serve as a technical expert responsible for accelerating technical wins and adoption of complex, specialized workloads. You will leverage your deep expertise in our most strategic product areas, in partnership with Platform CEs, to design data foundation architectures and develop MVPs (Minimum Viable Products) to sell new, highly specialized solutions to customers. You will solve analytics-centered customer challenges and provide a critical feedback loop to unblock customers and influence product development."
That's the prose.
Responsibilities list (after "Responsibilities Learn more about benefits at Google ." Actually there is a weird line: "Responsibilities Learn more about benefits at Google . Support local sales teams..." We need to extract responsibilities:
- Support local sales teams in pursuit of key business opportunities, and with engage customers to address aspects of the data lifecycle.
- Identify business and technical requirements, conduct full technical discovery, and architect client solutions to meet gathered requirements.
- Take responsibility for leading technical projects, including such activities as technology advocacy, supporting bid responses, product and solution briefings, proof-of-concept work, and the coordination of supporting technical resources.
- Work with Google Cloud Platform products to demonstrate and prototype integrations in customer/partner environments.
- Travel as required for meetings, technical reviews, and onsite delivery activities.
- Prepare and deliver product messaging in an effort to highlight the Google Cloud Platform value proposition, using techniques that include whiteboard and slide presentations, product demonstrations, white papers and RFI response documents.
We need to keep each as list items.
Minimum qualifications list:
- Bachelor's degree or equivalent practical experience.
- 10 years of experience with cloud native architecture in a customer-facing or support role.
- Experience with "Big Data" technologies or concepts (e.g., analytics warehousing, data processing, data transformation, data governance, data migrations, ETL, ELT, SQL, Spark, performance or scalability optimizations, batch versus streaming).
- Experience using programming languages (e.g., Python, Spark, SQL) to demo, prototype, or workshop with customers.
- Experience engaging with, and presenting to, technical stakeholders and executive leaders.
Preferred qualifications list:
- Experience in writing code in a common development languages such as Java, Python, JavaScript, C++, Scala, R or Go.
- Experience in technical sales or professional consulting in the fields of cloud computing, data, information lifecycle management, and Big Data.
- Experience with developing data warehousing, data lakes, batch or real-time event processing and ETL workflows solutions (i.e., Informatica, Talend, Alooma, SAP, Data Services) which could include architecture design, implementing, tuning, schema design, and query optimization of scalable and distributed systems.
- Ability to address DNS, TCP, Firewalls, Proxy Servers, Load Balancing, VPN and VPC and working knowledge of Linux.
Benefits list:
- 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: $152000 - $221000 (USD) + 42.86% bonus target + equity + benefits"
We should keep that as a paragraph.
We must not include boilerplate like application window, fair chance, location notes, EEO, accommodation, etc.
Now produce HTML fragment:
About the role
... paragraph ...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $152000 - $221000 (USD) + 42.86% bonus target + equity + benefits
We should not include Schedule.
Check that we didn't miss any substantive info: The note about "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: ..." is location info, but that's maybe considered substantive? It's about location options. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Location list might be considered not boilerplate but it's about where the role may be located. However earlier there were location notes about San Francisco, Playa Vista, Los Angeles County, etc. Those are likely boilerplate/fair chance. The location list at end: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Mountain View, CA, USA; Boulder, CO, USA; Kirkland, WA, USA; Los Angeles, CA, USA; Portland, OR, USA; Phoenix, AZ, USA; Seattle, WA, USA; San Francisco, CA, USA; Sunnyvale, CA, USA." This is substantive location options. Should we keep? The instruction says remove duplicated lines, application instructions. This is not an instruction but a note about location. It might be considered relevant. However the instruction also says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep location info. Where to put? Could be a section "Location" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Location is not listed. But we could incorporate location info into About the role paragraph or maybe as a under About the role. Since we cannot create new headings not in list, we should embed location info in existing section, perhaps About the role. However the About the role currently is just the paragraph about role. We could add a second paragraph after that about location options. That would preserve info without new heading.
Thus About the role section will have two
elements: first the role description, second the location note.
Check if any other substantive info: The line "This opportunity will remain online based on business needs which may be before or after the specified date." is about application window; that's boilerplate/instruction, remove.
The fair chance ordinance lines: remove.
The line "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." is basically intro to benefits; we already have benefits list; we could keep that as a preamble
before benefits list? It's substantive about benefits being available to US employees. Could include as a
inside Benefits section before the list. That would preserve info.
Similarly, the line "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: ..." we can add as a
after the role description.
Now ensure we don't include any duplicated lines.
Now produce final HTML.
Let's craft:
About the role
When leading companies choose Google Cloud, it's a huge win for spreading the power of cloud computing globally. Once educational institutions, government agencies, and other businesses sign on to use Google Cloud products, you come in to facilitate making their work more productive, mobile, and collaborative. You listen and deliver what is most helpful for the customer. You assist fellow sales Googlers by problem-solving key technical issues for our customers. You liaise with the product marketing management and engineering teams to stay on top of industry trends and devise enhancements to Google Cloud products. As a Practice Customer Engineer (CE) with a specialty in Data Analytics, you will partner with technical sales teams to differentiate Google Cloud to our customers. You will serve as a technical expert responsible for accelerating technical wins and adoption of complex, specialized workloads. You will leverage your deep expertise in our most strategic product areas, in partnership with Platform CEs, to design data foundation architectures and develop MVPs (Minimum Viable Products) to sell new, highly specialized solutions to customers. You will solve analytics-centered customer challenges and provide a critical feedback loop to unblock customers and influence product development.
Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Mountain View, CA, USA; Boulder,
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. No Job ID. We must not include filler like "commensurate with experience". Not present. We need to decide sections: About the role (maybe "About The Job" paragraph). Responsibilities (list). Requirements (maybe Minimum qualifications). Qualifications (maybe Preferred qualifications). Skills? Could combine but we can have Skills section if we have specific skills listed. The posting includes many skill-like items in qualifications. Could put them under Requirements and Preferred qualifications. Could also have a Skills section summarizing technical skills. But we should only create sections if there is real specific content. The posting includes Minimum qualifications and Preferred qualifications as lists. Could treat Minimum qualifications as "Requirements" and Preferred qualifications as "Qualifications". Or we could have "Requirements" for minimum, "Preferred Qualifications" for preferred. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: Requirements = Minimum qualifications. Qualifications = Preferred qualifications. Skills maybe not needed separately if covered. But we could still include Skills if we want to list specific technical skills extracted from qualifications. However we must not invent or summarize away detail; we can keep the lists as is under appropriate headings. Thus sections: - About the role (maybe heading "About the role") with prose from "About The Job" paragraph. - Responsibilities: list from responsibilities bullet points. - Requirements: list from Minimum qualifications. - Qualifications: list from Preferred qualifications. - Benefits: list from benefits. - Pay: maybe a paragraph with pay range. We should not include Schedule. We need to preserve all substantive information: The description includes sentences about role, responsibilities, etc. Ensure we keep all details. Let's extract: About The Job paragraph: "When leading companies choose Google Cloud, it's a huge win for spreading the power of cloud computing globally. Once educational institutions, government agencies, and other businesses sign on to use Google Cloud products, you come in to facilitate making their work more productive, mobile, and collaborative. You listen and deliver what is most helpful for the customer. You assist fellow sales Googlers by problem-solving key technical issues for our customers. You liaise with the product marketing management and engineering teams to stay on top of industry trends and devise enhancements to Google Cloud products. As a Practice Customer Engineer (CE) with a specialty in Data Analytics, you will partner with technical sales teams to differentiate Google Cloud to our customers. You will serve as a technical expert responsible for accelerating technical wins and adoption of complex, specialized workloads. You will leverage your deep expertise in our most strategic product areas, in partnership with Platform CEs, to design data foundation architectures and develop MVPs (Minimum Viable Products) to sell new, highly specialized solutions to customers. You will solve analytics-centered customer challenges and provide a critical feedback loop to unblock customers and influence product development." That's the prose. Responsibilities list (after "Responsibilities Learn more about benefits at Google ." Actually there is a weird line: "Responsibilities Learn more about benefits at Google . Support local sales teams..." We need to extract responsibilities: - Support local sales teams in pursuit of key business opportunities, and with engage customers to address aspects of the data lifecycle. - Identify business and technical requirements, conduct full technical discovery, and architect client solutions to meet gathered requirements. - Take responsibility for leading technical projects, including such activities as technology advocacy, supporting bid responses, product and solution briefings, proof-of-concept work, and the coordination of supporting technical resources. - Work with Google Cloud Platform products to demonstrate and prototype integrations in customer/partner environments. - Travel as required for meetings, technical reviews, and onsite delivery activities. - Prepare and deliver product messaging in an effort to highlight the Google Cloud Platform value proposition, using techniques that include whiteboard and slide presentations, product demonstrations, white papers and RFI response documents. We need to keep each as list items. Minimum qualifications list: - Bachelor's degree or equivalent practical experience. - 10 years of experience with cloud native architecture in a customer-facing or support role. - Experience with "Big Data" technologies or concepts (e.g., analytics warehousing, data processing, data transformation, data governance, data migrations, ETL, ELT, SQL, Spark, performance or scalability optimizations, batch versus streaming). - Experience using programming languages (e.g., Python, Spark, SQL) to demo, prototype, or workshop with customers. - Experience engaging with, and presenting to, technical stakeholders and executive leaders. Preferred qualifications list: - Experience in writing code in a common development languages such as Java, Python, JavaScript, C++, Scala, R or Go. - Experience in technical sales or professional consulting in the fields of cloud computing, data, information lifecycle management, and Big Data. - Experience with developing data warehousing, data lakes, batch or real-time event processing and ETL workflows solutions (i.e., Informatica, Talend, Alooma, SAP, Data Services) which could include architecture design, implementing, tuning, schema design, and query optimization of scalable and distributed systems. - Ability to address DNS, TCP, Firewalls, Proxy Servers, Load Balancing, VPN and VPC and working knowledge of Linux. Benefits list: - 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: $152000 - $221000 (USD) + 42.86% bonus target + equity + benefits" We should keep that as a paragraph. We must not include boilerplate like application window, fair chance, location notes, EEO, accommodation, etc. Now produce HTML fragment:
About the role
... paragraph ...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $152000 - $221000 (USD) + 42.86% bonus target + equity + benefits
We should not include Schedule. Check that we didn't miss any substantive info: The note about "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: ..." is location info, but that's maybe considered substantive? It's about location options. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Location list might be considered not boilerplate but it's about where the role may be located. However earlier there were location notes about San Francisco, Playa Vista, Los Angeles County, etc. Those are likely boilerplate/fair chance. The location list at end: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Mountain View, CA, USA; Boulder, CO, USA; Kirkland, WA, USA; Los Angeles, CA, USA; Portland, OR, USA; Phoenix, AZ, USA; Seattle, WA, USA; San Francisco, CA, USA; Sunnyvale, CA, USA." This is substantive location options. Should we keep? The instruction says remove duplicated lines, application instructions. This is not an instruction but a note about location. It might be considered relevant. However the instruction also says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep location info. Where to put? Could be a section "Location" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Location is not listed. But we could incorporate location info into About the role paragraph or maybe as aunder About the role. Since we cannot create new headings not in list, we should embed location info in existing section, perhaps About the role. However the About the role currently is just the paragraph about role. We could add a second paragraph after that about location options. That would preserve info without new heading. Thus About the role section will have two
elements: first the role description, second the location note. Check if any other substantive info: The line "This opportunity will remain online based on business needs which may be before or after the specified date." is about application window; that's boilerplate/instruction, remove. The fair chance ordinance lines: remove. The line "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." is basically intro to benefits; we already have benefits list; we could keep that as a preamble
before benefits list? It's substantive about benefits being available to US employees. Could include as a
inside Benefits section before the list. That would preserve info. Similarly, the line "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: ..." we can add as a
after the role description. Now ensure we don't include any duplicated lines. Now produce final HTML. Let's craft:
About the role
When leading companies choose Google Cloud, it's a huge win for spreading the power of cloud computing globally. Once educational institutions, government agencies, and other businesses sign on to use Google Cloud products, you come in to facilitate making their work more productive, mobile, and collaborative. You listen and deliver what is most helpful for the customer. You assist fellow sales Googlers by problem-solving key technical issues for our customers. You liaise with the product marketing management and engineering teams to stay on top of industry trends and devise enhancements to Google Cloud products. As a Practice Customer Engineer (CE) with a specialty in Data Analytics, you will partner with technical sales teams to differentiate Google Cloud to our customers. You will serve as a technical expert responsible for accelerating technical wins and adoption of complex, specialized workloads. You will leverage your deep expertise in our most strategic product areas, in partnership with Platform CEs, to design data foundation architectures and develop MVPs (Minimum Viable Products) to sell new, highly specialized solutions to customers. You will solve analytics-centered customer challenges and provide a critical feedback loop to unblock customers and influence product development.
Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Mountain View, CA, USA; Boulder,