Strategic Partner Development Lead, Flow Enterprise
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the job posting. First, remove boilerplate: the first paragraphs about Fair Chance Ordinance etc. Those are legal boilerplate; we need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the Fair Chance statements and the note about applying location? The note about location might be considered relevant? It says "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Los Angeles, CA, USA; Mountain View, CA, USA; New York, NY, USA; San Francisco, CA, USA." This is location info, maybe relevant but not a section heading. Could be included in a short paragraph under maybe "About the role" or separate? The instruction: "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 location could be minor metadata; we could include in a short
maybe under About the role. But we need to preserve all substantive information. The location note is substantive? It's about where you can work. Might be considered relevant but not a section. We'll include as a paragraph. Next: Minimum qualifications: Bachelor's degree or equivalent practical experience. 7 years of experience in business development, partnerships, sales, management consulting, or investment banking in the media, advertising, technology, apps, or content creation industries. Experience working with C-level executives and cross-functionally across multiple levels of management. Experience managing agreements or partnerships. Preferred qualifications: MBA or Master's degree in a related field. Experience leading cross-functional partnership initiatives with a significant impact on business outcomes. Experience working autonomously in a dynamic, ever-changing, and collaborative environment. Ability to identify potential business opportunities, assess financial/business benefit, structure agreements, and discuss terms with partners. Excellent influencing skills, with a track record of securing favorable terms and building consensus. Excellent communication and presentation skills, with experience presenting to and influencing executives. Then "About The Job" paragraph describing role. Then "The Flow Enterprise Partnerships team will play a critical role..." etc. That's more description. Then "The Global Partnerships organization is responsible..." etc. Then "Individual pay is determined by factors including job-related skills, experience, and relevant education or training. US: $140000 - $203000 (USD) + 15% bonus target + equity + benefits". That's pay and benefits info. Then "Responsibilities Learn more about benefits at Google . Work with cross-product area teams to identify, pitch, discuss, and execute first-of-kind agreement structures for Flow Enterprise customers. Manage negotiations, as well as ongoing partner and customer relationship management.Develop and cultivate relationships with key partners, serving as a trusted advisor and ensuring alignment on key objectives.Discuss and structure partnership agreements, ensuring favorable terms and conditions. Support the establishment of a business pipeline for a specific partner segment, and meet with multiple customers and channel partners per week.Oversee the integration and implementation of partnerships, collaborating with cross-functional teams (e.g., Product, Engineering, Marketing, and Legal) to ensure successful launch and ongoing operations.Monitor, analyze, and optimize partnership performance, identifying areas for improvement and growth to achieve goals." Then EEO boilerplate etc to remove. We need sections: About the role (maybe "About The Job" heading). Responsibilities (list). Requirements (maybe combine minimum qualifications). Qualifications (maybe preferred qualifications). Skills (maybe from preferred qualifications). Benefits (maybe from pay line). Pay (salary range). Schedule (not present, so omit). We should not create sections with filler. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove duplicated lines.
Let's extract substantive content:
- Location note: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Los Angeles, CA, USA; Mountain View, CA, USA; New York, NY, USA; San Francisco, CA, USA." Could be a short paragraph.
- About The Job: multiple paragraphs. We'll combine into maybe one or two
under
About the role
.
- Responsibilities: list of duties. We'll make - each sentence.
- Minimum qualifications: list. Could be under
Requirements
as - .
- Preferred qualifications: list. Could be under
Qualifications
or Skills
. The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (minimum), Qualifications (preferred), Skills (maybe from preferred). But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one? But we need to follow headings list; we can include Qualifications and Skills if they have content. Let's see: Preferred qualifications include MBA, experience leading cross-functional initiatives, ability to identify opportunities, excellent influencing skills, excellent communication and presentation skills. Those could be considered Skills. So we could have Qualifications (education) and Skills (abilities). But we might just put all preferred under Qualifications and not create Skills if it's thin. However we have enough content for Skills: influencing skills, communication/presentation skills. Could be separate.
But we need to avoid filler. Let's decide:
- Requirements (minimum qualifications) as .
- Qualifications (preferred qualifications) as (includes MBA, experience leading cross-functional initiatives, experience working autonomously, ability to identify opportunities, etc.)
- Skills (maybe we can extract influencing skills, communication and presentation skills) but those are already in preferred qualifications. Could be redundant. Better to not create Skills section if it's just repeating. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills and just have Qualifications covering preferred qualifications.
- Benefits: The posting mentions "+ equity + benefits" but no detail. It says "Individual pay is determined by factors ... US: $140000 - $203000 (USD) + 15% bonus target + equity + benefits". That's pay and benefits mention but not specific benefits. We have a Pay section: we can include salary range and bonus target and equity. Benefits: we have only mention of "+ benefits" but no detail; we should not create Benefits section unless posting actually states them. It does not state specific benefits, just says "+ benefits". That's vague; maybe we should not create Benefits section because it's not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "+ benefits" but not details. Is that enough? It states benefits exist but not what they are. Might be considered stating them? The phrase "+ benefits" is a mention but not detail. Safer to omit Benefits section.
- Pay: we have salary range and bonus target and equity. So we can create Pay section with that info.
- Schedule: not present, omit.
Now we need to ensure we don't include boilerplate like EEO etc.
Let's craft HTML.
Structure:
About the role
... (combined paragraphs)
Maybe also include location note as a short paragraph under About the role or separate? Could be a before About the role? But location note is not a heading. We'll include as a
before About the role? The instruction: fold minor metadata into a short
or drop it. So we can add a
for location note.
Then
Responsibilities
- ... each duty
Then Requirements
- ... each minimum qualification
Then Qualifications
- ... each preferred qualification
Then Pay
US: $140000 - $203000 (USD) + 15% bonus target + equity + benefits
We need to ensure we preserve all substantive information: The description about Flow Enterprise Partnerships team, Global Partnerships organization, etc. Should be included in About the role.
Let's extract About the role paragraphs:
"About The Job Google's line of products and services to clients never stops growing. Strategic Partner Managers have the rare opportunity to build a long-lasting relationship with our top partners. You cultivate these existing partnerships to make sure they can take full advantage of Google's ever-growing suite of offerings. You possess strong relationship-building skills and are apt to see mutually beneficial opportunities with partners in order to best represent our users, products and programs. As a Strategic Partner Development Lead, you will open doors with potential partners, lead exploratory discussions and evaluate/develop business opportunities. You will lead cross-functional teams, provide thought leadership and serve as a mentor to managers and associates. You will be comfortable in escalating and presenting business development strategies and key issues to executive management. You will work closely with Google Product, Engineering, Legal and Sales teams on new product initiatives and key relationships that support our online advertising business. The Flow Enterprise Partnerships team will play a critical role to help launch and scale an enterprise-grade version of Flow, Google’s AI-powered, content creation suite. The team will help design the product business model, identify and establish a customer pipeline, and develop the channel partnerships to help bring it to market. The team will collaborate with a variety of cross-functional and product teams to utilize and navigate Google’s existing enterprise offerings. The team’s mission will be to maximize Flow Enterprise Annual Recurring Revenue (ARR). The Global Partnerships organization is responsible for exploring new opportunities with Google's partners. Google’s Global Partnerships team works with a wide range of partners to bring the best of Google to power their business. The Global Partnerships team supports Google’s own Product teams with essential partnerships to help Google’s user experiences in advertising, Search, Assistant, Maps, Travel, Shopping, Payments and more. Teams create product-enabling partnerships, go-to-market strategies and incubate business growth for a variety of products."
We'll combine into maybe two paragraphs for readability but it's okay as one.
Now Responsibilities list:
- Work with cross-product area teams to identify, pitch, discuss, and execute first-of-kind agreement structures for Flow Enterprise customers.
- Manage negotiations, as well as ongoing partner and customer relationship management.
- Develop and cultivate relationships with key partners, serving as a trusted advisor and ensuring alignment on key objectives.
- Discuss and structure partnership agreements, ensuring favorable terms and conditions.
- Support the establishment of a business pipeline for a specific partner segment, and meet with multiple customers and channel partners per week.
- Oversee the integration and implementation of partnerships, collaborating with cross-functional teams (e.g., Product, Engineering, Marketing, and Legal) to ensure successful launch and ongoing operations.
- Monitor, analyze, and optimize partnership performance, identifying areas for improvement and growth to achieve goals.
Note: The original had "Learn more about benefits at Google ." That's a link; we should remove as it's application instruction? It's a link to benefits; we can drop as it's not substantive content? It's a reference; but it's not a duty. We'll drop.
Now Requirements list (minimum qualifications):
- Bachelor's degree or equivalent practical experience.
- 7 years of experience in business development, partnerships, sales, management consulting, or investment banking in the media, advertising, technology, apps, or content creation industries.
- Experience working with C-level executives and cross-functionally across multiple levels of management.
- Experience managing agreements or partnerships.
Now Qualifications list (preferred qualifications):
- MBA or Master's degree in a related field.
- Experience leading cross-functional partnership initiatives with
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove duplicated lines. Let's extract substantive content: - Location note: "Note: By applying to this position you will have an opportunity to share your preferred working location from the following: Los Angeles, CA, USA; Mountain View, CA, USA; New York, NY, USA; San Francisco, CA, USA." Could be a short paragraph. - About The Job: multiple paragraphs. We'll combine into maybe one or two
under
About the role
. - Responsibilities: list of duties. We'll make- each sentence.
- Minimum qualifications: list. Could be under
Requirements
as- .
- Preferred qualifications: list. Could be under
Qualifications
orSkills
. The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements (minimum), Qualifications (preferred), Skills (maybe from preferred). But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one? But we need to follow headings list; we can include Qualifications and Skills if they have content. Let's see: Preferred qualifications include MBA, experience leading cross-functional initiatives, ability to identify opportunities, excellent influencing skills, excellent communication and presentation skills. Those could be considered Skills. So we could have Qualifications (education) and Skills (abilities). But we might just put all preferred under Qualifications and not create Skills if it's thin. However we have enough content for Skills: influencing skills, communication/presentation skills. Could be separate. But we need to avoid filler. Let's decide: - Requirements (minimum qualifications) as- .
- Qualifications (preferred qualifications) as
- ... each duty
- ... each minimum qualification
- ... each preferred qualification
- (includes MBA, experience leading cross-functional initiatives, experience working autonomously, ability to identify opportunities, etc.)
- Skills (maybe we can extract influencing skills, communication and presentation skills) but those are already in preferred qualifications. Could be redundant. Better to not create Skills section if it's just repeating. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills and just have Qualifications covering preferred qualifications.
- Benefits: The posting mentions "+ equity + benefits" but no detail. It says "Individual pay is determined by factors ... US: $140000 - $203000 (USD) + 15% bonus target + equity + benefits". That's pay and benefits mention but not specific benefits. We have a Pay section: we can include salary range and bonus target and equity. Benefits: we have only mention of "+ benefits" but no detail; we should not create Benefits section unless posting actually states them. It does not state specific benefits, just says "+ benefits". That's vague; maybe we should not create Benefits section because it's not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "+ benefits" but not details. Is that enough? It states benefits exist but not what they are. Might be considered stating them? The phrase "+ benefits" is a mention but not detail. Safer to omit Benefits section.
- Pay: we have salary range and bonus target and equity. So we can create Pay section with that info.
- Schedule: not present, omit.
Now we need to ensure we don't include boilerplate like EEO etc.
Let's craft HTML.
Structure:
About the role
... (combined paragraphs)
Maybe also include location note as a short paragraph under About the role or separate? Could be abefore About the role? But location note is not a heading. We'll include as a
before About the role? The instruction: fold minor metadata into a short
or drop it. So we can add a
for location note. Then
Responsibilities
Requirements
Qualifications
Pay
US: $140000 - $203000 (USD) + 15% bonus target + equity + benefits
We need to ensure we preserve all substantive information: The description about Flow Enterprise Partnerships team, Global Partnerships organization, etc. Should be included in About the role. Let's extract About the role paragraphs: "About The Job Google's line of products and services to clients never stops growing. Strategic Partner Managers have the rare opportunity to build a long-lasting relationship with our top partners. You cultivate these existing partnerships to make sure they can take full advantage of Google's ever-growing suite of offerings. You possess strong relationship-building skills and are apt to see mutually beneficial opportunities with partners in order to best represent our users, products and programs. As a Strategic Partner Development Lead, you will open doors with potential partners, lead exploratory discussions and evaluate/develop business opportunities. You will lead cross-functional teams, provide thought leadership and serve as a mentor to managers and associates. You will be comfortable in escalating and presenting business development strategies and key issues to executive management. You will work closely with Google Product, Engineering, Legal and Sales teams on new product initiatives and key relationships that support our online advertising business. The Flow Enterprise Partnerships team will play a critical role to help launch and scale an enterprise-grade version of Flow, Google’s AI-powered, content creation suite. The team will help design the product business model, identify and establish a customer pipeline, and develop the channel partnerships to help bring it to market. The team will collaborate with a variety of cross-functional and product teams to utilize and navigate Google’s existing enterprise offerings. The team’s mission will be to maximize Flow Enterprise Annual Recurring Revenue (ARR). The Global Partnerships organization is responsible for exploring new opportunities with Google's partners. Google’s Global Partnerships team works with a wide range of partners to bring the best of Google to power their business. The Global Partnerships team supports Google’s own Product teams with essential partnerships to help Google’s user experiences in advertising, Search, Assistant, Maps, Travel, Shopping, Payments and more. Teams create product-enabling partnerships, go-to-market strategies and incubate business growth for a variety of products." We'll combine into maybe two paragraphs for readability but it's okay as one. Now Responsibilities list: - Work with cross-product area teams to identify, pitch, discuss, and execute first-of-kind agreement structures for Flow Enterprise customers. - Manage negotiations, as well as ongoing partner and customer relationship management. - Develop and cultivate relationships with key partners, serving as a trusted advisor and ensuring alignment on key objectives. - Discuss and structure partnership agreements, ensuring favorable terms and conditions. - Support the establishment of a business pipeline for a specific partner segment, and meet with multiple customers and channel partners per week. - Oversee the integration and implementation of partnerships, collaborating with cross-functional teams (e.g., Product, Engineering, Marketing, and Legal) to ensure successful launch and ongoing operations. - Monitor, analyze, and optimize partnership performance, identifying areas for improvement and growth to achieve goals. Note: The original had "Learn more about benefits at Google ." That's a link; we should remove as it's application instruction? It's a link to benefits; we can drop as it's not substantive content? It's a reference; but it's not a duty. We'll drop. Now Requirements list (minimum qualifications): - Bachelor's degree or equivalent practical experience. - 7 years of experience in business development, partnerships, sales, management consulting, or investment banking in the media, advertising, technology, apps, or content creation industries. - Experience working with C-level executives and cross-functionally across multiple levels of management. - Experience managing agreements or partnerships. Now Qualifications list (preferred qualifications): - MBA or Master's degree in a related field. - Experience leading cross-functional partnership initiatives with
- .
- Preferred qualifications: list. Could be under