Senior Strategy and Operations Principal, Data Cloud, GTM Operations
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
The posting includes:
- About This Role (benefits description). Actually "About This Role" includes benefits. So we can treat that as "About the role" section.
- Minimum qualifications: list.
- Preferred Qualifications: list.
- About The Job: description of role.
- Responsibilities: list.
- Pay: "Individual pay is determined by factors including job‑related skills, experience, and relevant education or training. US: $222000 \- $308000 (USD) \+ 25% bonus target \+ equity \+ benefits". So we have pay info.
- Benefits: described in "About This Role" includes health, dental, vision, life, disability insurance, retirement benefits, PTO, sick time, maternity leave, baby bonding, holidays. So we have benefits.
- Schedule: not mentioned. So we should not include Schedule.
- Skills: maybe we can extract from qualifications: experience with R, SQL, spreadsheets, etc. Also communication skills. Could be a Skills section. But we need to decide if we have enough specific content. The instructions: Prefer a few substantive sections over many thin ones. We could combine qualifications and skills into Requirements/Qualifications sections. They said use headings for: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have multiple sections.
We need to avoid repeating job title as heading. Not needed.
We need to strip boilerplate: EEO, accommodation, etc. Also remove "Learn More About Benefits At Google." etc.
We need to preserve all substantive information.
Let's extract content:
About the role: The benefits paragraph. Also note about location: "By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA." That's location info, could be part of About the role. Should we include? It's substantive. Yes.
Thus About the role section: include benefits and location options.
Responsibilities: list bullet points.
Requirements: maybe minimum qualifications.
Qualifications: preferred qualifications.
Skills: maybe we can extract from preferred qualifications: Experience with R, SQL, spreadsheets, or similar analytics tools. Demonstrated experience in strategy, operations, product management, or a customer‑facing technical advisory, leadership role within high‑growth enterprise tech, cloud environments. Exceptional communication and relationship‑building skills, with a proven ability to influence cross‑functional teams and executive stakeholders without direct authority. Proven track record of driving complex initiatives from ambiguity to completion with a strong bias for action.
But some of those are also qualifications. Could treat them as Skills. However we might combine Qualifications and Skills to avoid thin sections. But instructions: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred), Benefits, Pay. That's 6 sections. Skills could be omitted if we incorporate into Qualifications. But they said we can use Skills heading if we have content. We could still include Skills if we have distinct content. Let's see if we have distinct skill content not already in qualifications: The preferred qualifications include experience with R, SQL, spreadsheets, etc. That's a skill. Also exceptional communication and relationship-building skills. That's also skill. Proven track record of driving complex initiatives... that's more experience. Could be considered skill.
But we already have Qualifications (preferred) which includes those. So maybe we don't need separate Skills.
Thus sections: About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred), Benefits, Pay.
Check if any content for Schedule: none.
Now we need to format lists with - . For prose use
.
We need to preserve all substantive information: ensure we don't lose any details.
Let's extract each piece.
About the role:
Original: "About This Role 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 instanceMaternity Leave (Short\-Term Disability \+ Baby Bonding): 28\-30 weeksBaby Bonding Leave: 18 weeksHolidays: 13 paid days per year Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA."
We need to format nicely. There's missing spaces due to formatting. We'll reconstruct.
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
Location note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA.
We'll put that as a paragraph.
Now Responsibilities:
List:
- Act as a key proxy for the Data Cloud leadership in engaging with customers and field organizations.
- Take ownership of cross‑functional initiatives, commitments, and action items generated from leadership reviews and customer engagements, ensuring they are tracked and driven to completion in a timely manner.
- Translate customer feedback into technical gap analyses and collaborate with Product and Engineering leadership to accelerate prioritization, decision‑making, and closure for executive stakeholders.
- Demonstrate excellent execution discipline and follow‑through.
- Leverage your technical background to deeply understand the Data Cloud product portfolio, architecture, and competitive landscape. Help shape product positioning narratives and ensure alignment between field realities and product roadmaps.
Now Requirements (minimum qualifications):
- Bachelor's degree or equivalent practical experience.
- 15 years of experience in management consulting, product management and strategy, or analytics in a technology company.
- Experience working with and analyzing data, and managing multiple cross‑functional programs or projects.
Now Qualifications (preferred):
- Advanced degree or equivalent practical experience.
- Experience with R, SQL, spreadsheets, or similar analytics tools.
- Demonstrated experience in strategy, operations, product management, or a customer‑facing technical advisory, leadership role within high‑growth enterprise tech, cloud environments.
- Exceptional communication and relationship‑building skills, with a proven ability to influence cross‑functional teams and executive stakeholders without direct authority.
- Proven track record of driving complex initiatives from ambiguity to completion with a strong bias for action.
Now Benefits: we already covered in About the role. But we could also have a Benefits section separate. However the About the role already includes benefits. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have About the role (maybe just a brief intro) and Benefits separate. But we already put benefits in About the role. To avoid duplication, we could keep About the role as a short description (maybe the location note) and then Benefits section with the list. However the posting's "About This Role" is primarily benefits. So we could treat that as Benefits section and have About the role be a brief summary? But the instructions say we should include a section ONLY when the posting has real, specific content for it. So we can have both About the role and Benefits if they have distinct content. The About the role currently includes benefits and location note. If we split, we might duplicate benefits. Better to keep About the role as a short intro (maybe the location note) and Benefits separate with the list. But the location note is minor; we could incorporate location note into About the role paragraph, and Benefits section list the benefits.
Let's do that:
About the role: paragraph: "By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA."
Benefits: list as above.
Now we need to ensure we don't lose the introductory sentence about Washington state law and highlighting benefits. That is part of benefits context; we could include that as a paragraph before the list in Benefits section.
Thus Benefits section: start with a paragraph: "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." Then the list.
Now About the role: just location note.
Now Responsibilities: list.
Requirements: list.
Qualifications: list.
Pay: paragraph: "Individual pay is determined by factors including job‑related skills, experience, and relevant education or training. US: $222,000 - $308,000 (USD) + 25% bonus target + equity + benefits." We need to preserve the formatting: original had "$222000 \- $308000 (USD) \+ 25% bonus target \+ equity \+ benefits". We'll format nicely with commas.
Now we need to output HTML fragment only.
Let's craft:
About the role
By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA.
Benefits
In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees.
- 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
Responsibilities
- Act as a key proxy for the Data Cloud leadership in engaging with customers and field organizations.
- Take ownership of cross‑functional initiatives, commitments, and action items generated from leadership reviews and customer engagements, ensuring they are tracked and driven to completion in a timely manner.
- Translate customer feedback into technical gap analyses and collaborate with Product and Engineering leadership to accelerate prioritization, decision‑making, and closure for executive stakeholders.
- Demonstrate excellent execution discipline and follow‑through.
- Leverage your technical background to deeply understand the Data Cloud product portfolio, architecture, and competitive landscape. Help shape product positioning narratives and ensure alignment between field realities and product roadmaps.
Requirements
- Bachelor's degree or equivalent practical experience.
- 15 years of experience in management consulting, product management and strategy,
. We need to preserve all substantive information: ensure we don't lose any details. Let's extract each piece. About the role: Original: "About This Role 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 instanceMaternity Leave (Short\-Term Disability \+ Baby Bonding): 28\-30 weeksBaby Bonding Leave: 18 weeksHolidays: 13 paid days per year Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA." We need to format nicely. There's missing spaces due to formatting. We'll reconstruct. 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 Location note: By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA. We'll put that as a paragraph. Now Responsibilities: List: - Act as a key proxy for the Data Cloud leadership in engaging with customers and field organizations. - Take ownership of cross‑functional initiatives, commitments, and action items generated from leadership reviews and customer engagements, ensuring they are tracked and driven to completion in a timely manner. - Translate customer feedback into technical gap analyses and collaborate with Product and Engineering leadership to accelerate prioritization, decision‑making, and closure for executive stakeholders. - Demonstrate excellent execution discipline and follow‑through. - Leverage your technical background to deeply understand the Data Cloud product portfolio, architecture, and competitive landscape. Help shape product positioning narratives and ensure alignment between field realities and product roadmaps. Now Requirements (minimum qualifications): - Bachelor's degree or equivalent practical experience. - 15 years of experience in management consulting, product management and strategy, or analytics in a technology company. - Experience working with and analyzing data, and managing multiple cross‑functional programs or projects. Now Qualifications (preferred): - Advanced degree or equivalent practical experience. - Experience with R, SQL, spreadsheets, or similar analytics tools. - Demonstrated experience in strategy, operations, product management, or a customer‑facing technical advisory, leadership role within high‑growth enterprise tech, cloud environments. - Exceptional communication and relationship‑building skills, with a proven ability to influence cross‑functional teams and executive stakeholders without direct authority. - Proven track record of driving complex initiatives from ambiguity to completion with a strong bias for action. Now Benefits: we already covered in About the role. But we could also have a Benefits section separate. However the About the role already includes benefits. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have About the role (maybe just a brief intro) and Benefits separate. But we already put benefits in About the role. To avoid duplication, we could keep About the role as a short description (maybe the location note) and then Benefits section with the list. However the posting's "About This Role" is primarily benefits. So we could treat that as Benefits section and have About the role be a brief summary? But the instructions say we should include a section ONLY when the posting has real, specific content for it. So we can have both About the role and Benefits if they have distinct content. The About the role currently includes benefits and location note. If we split, we might duplicate benefits. Better to keep About the role as a short intro (maybe the location note) and Benefits separate with the list. But the location note is minor; we could incorporate location note into About the role paragraph, and Benefits section list the benefits.
Let's do that:
About the role: paragraph: "By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA."
Benefits: list as above.
Now we need to ensure we don't lose the introductory sentence about Washington state law and highlighting benefits. That is part of benefits context; we could include that as a paragraph before the list in Benefits section.
Thus Benefits section: start with a paragraph: "In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees." Then the list.
Now About the role: just location note.
Now Responsibilities: list.
Requirements: list.
Qualifications: list.
Pay: paragraph: "Individual pay is determined by factors including job‑related skills, experience, and relevant education or training. US: $222,000 - $308,000 (USD) + 25% bonus target + equity + benefits." We need to preserve the formatting: original had "$222000 \- $308000 (USD) \+ 25% bonus target \+ equity \+ benefits". We'll format nicely with commas.
Now we need to output HTML fragment only.
Let's craft:
About the role
By applying to this position you will have an opportunity to share your preferred working location from the following: Sunnyvale, CA, USA; Kirkland, WA, USA.
Benefits
In accordance with Washington state law, we are highlighting our comprehensive benefits package, which is available to all eligible US based employees.
- 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
Responsibilities
- Act as a key proxy for the Data Cloud leadership in engaging with customers and field organizations.
- Take ownership of cross‑functional initiatives, commitments, and action items generated from leadership reviews and customer engagements, ensuring they are tracked and driven to completion in a timely manner.
- Translate customer feedback into technical gap analyses and collaborate with Product and Engineering leadership to accelerate prioritization, decision‑making, and closure for executive stakeholders.
- Demonstrate excellent execution discipline and follow‑through.
- Leverage your technical background to deeply understand the Data Cloud product portfolio, architecture, and competitive landscape. Help shape product positioning narratives and ensure alignment between field realities and product roadmaps.
Requirements
- Bachelor's degree or equivalent practical experience.
- 15 years of experience in management consulting, product management and strategy,