Google Co-Sell Lead
About the role
thenwith summary. Then Responsibilities: list bullet points. Requirements: list bullet points. Benefits: list bullet points. Pay: we have target compensation range; we can include Pay section with that info. Schedule: travel 30% maybe schedule? Not exactly schedule but travel expectation. Could include Schedule section with travel expectation. However guidelines: only include sections when posting has real, specific content. Travel 30% is specific, so schedule section could contain that. Pay section: we have target compensation range. Provide that. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. Also remove duplicated lines. Ensure we preserve all substantive info. Let's extract content. Job Summary paragraph: "The Google Co‑sell Lead is responsible for executing day‑to‑day Alliance co‑sell activities that support pipeline creation and partner‑sourced revenue. This role works closely with Sales, Alliances, and Google field teams to manage opportunities, maintain co‑sell hygiene, and ensure deals are properly registered, tracked, and advanced through Google channels.This is a hands‑on, execution‑focused role that supports existing co‑sell strategy through operational coordination and follow‑through." We can combine into one paragraph. Responsibilities: list bullet points from "Role & Responsibilities" section. Let's extract each bullet: - Support Sales, Presales, Channel and Alliances teams with deal intake, opportunity qualification, and Google alignment - Partner with Business Excellence to develop and execute internal training, certification, and Google program enablement. Educate internal teams on Google incentives, co-sell pathways, funding programs, sales plays, and marketplace offerings to unlock incremental revenue. - Build business cases for co-op, SPF, and incremental Google investment to support regional growth priorities. - Serve as the primary escalation, coordination, and communication point for Google across NORAM sales, delivery, and leadership teams. - Manage customer retention strategy, ensuring strong relationships, minimized churn, and effective Google support alignment. - Coordinate with Google field sellers to track active opportunities, next steps, and required documentation - Maintain accurate co‑sell pipeline data, reporting, and status updates - Ensure opportunities meet Google co‑sell eligibility and compliance requirements - Prepare deal summaries, win reports, and pipeline updates for internal stakeholders - Support joint account planning by tracking actions and following up on execution items - Expected Travel: 30% (maybe schedule) Requirements: list bullet points from "Job Requirements What You Offer" - 10 years total experience with a high level of business acumen and comfort working with Sales and other Senior Leaders - Experience in partner management, alliances, or channel sales, preferably in technology services, cloud, or software sales environments - Strong working knowledge of the Google ecosystem: Azure, Copilot, Security, MCAPS structure, incentives, co-sell, marketplace, and partner programs. - Proven experience driving partner-led revenue growth (ACR, cross-sell, upsell, and recapture). - Experience working with Google partners, channel programs, or co‑sell motions required; Experience using Google Partner Center or supporting Google partner programs preferred - Exposure to partner-sourced revenue tracking or deal registration processes - Familiarity with CRM systems and pipeline management - Strong organizational skills with attention to detail and follow‑through along with excellent verbal, written, and presentation skills - Comfortable working cross‑functionally with Sales, Alliances, and Operations teams Success Criteria maybe could be part of Requirements? But we can include as part of Requirements or separate? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Success Criteria maybe not needed; could be part of Requirements or omitted. We'll ignore. Benefits: list bullet points from "What we offer" - Generous pay with bonus structure - Independent environment without a lot of red tape where you are empowered to make decisions - Winning culture, inclusive environment, and friendly people all over the world - A remote-friendly organization, with colleagues working remotely either part or full-time - Substantial benefits package that includes: - Full suite of medical coverage with A+ carriers, Dental, and Vision with strong employer contributions plus additional voluntary coverage available for Pets, Identity Theft Protection, Accident & Critical Illness - 401k program with employer matching 50% up to the first 10% of employee’s contributions - Wellness plan that includes credits to premiums and employer contributions towards the savings plan of your choice - Access to EAP and concierge services plus pre-paid legal at no cost - Abundant time off that includes paid holidays, floating holidays, your birthday off, a volunteer day, and discretionary time off (DTO) - Employee stock purchase plan - Learning and development opportunities galore, tuition reimbursement, and much more! - Specific to Nashville and Milwaukee-based office employees: company-paid parking - As a culture first organization, being together is how we learn and grow. We come together in-person for at least 3 days for collaboration, support, and to have some fun. Where there is no physical location, we give all our employees equal cultural experiences through a remote setting. We need to keep bullet list; nested list for benefits subitems maybe okay but we can flatten. Pay: "Target compensation for this role will be $210K-240K USD (mix of base salary and bonus). Actual offers may be higher or lower than this range and will be determined based on a variety of factors, including (but not limited to) candidates’ qualifications, experience, education, and work location." Schedule: travel 30% maybe. We also have "Reports to: Director of Alliances, NORAM and dotted lines to Sales Leadership" and "Collaborates with: all areas on NORAM sales as the lead driver of Google alliance and strategy." Could be part of About the role or Responsibilities? Could be included in About the role paragraph. We must not include boilerplate like "The preceding job profile has been designed..." etc. Remove that. Also remove "We are not able to consider candidates residing in the state of Hawaii currently." That's substantive? It's a restriction; maybe we should keep? It's a requirement about location. Could be part of Requirements? It's a restriction. Might be considered substantive. But guidelines: preserve ALL substantive information; do not invent or summarize away detail. So we should keep that restriction. Could be placed in Requirements as a bullet. Also company description paragraph at end: we could include as About the company? Not a required heading; but we could incorporate into About the role? Might be extra. The instruction: Prefer a few substantive sections over many thin ones. We could add an "About the company" section? Not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings. Could incorporate company description into About the role paragraph? Might be okay but it's not about the role. Might be considered extra but not prohibited. However we should avoid adding unrelated content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep company description somewhere. Could add a
after the sections? But we must only output HTML fragment; we could add a
with company description after sections, without a heading. That's allowed as prose. So we can add a paragraph for company description. Similarly, we have "Where there is no physical location..." that's part of benefits description; we already included. Now construct HTML. We'll have:
About the role
... (summary plus reports to/collaborates)
Responsibilities
- ... each
Requirements
- ... each
Benefits
- ... each
Pay
Target compensation for this role will be $210K-240K USD (mix of base salary and bonus). Actual offers may be higher or lower than this range and will be determined based on a variety of factors, including (but not limited to) candidates’ qualifications, experience, education, and work location. We are not able to consider candidates residing in the state of Hawaii currently.
Schedule
Expected travel: 30%.
Then company description paragraph. Make sure to not include duplicate lines. Let's craft the content precisely. About the role paragraph: combine summary and reporting/collab. "The Google Co‑sell Lead is responsible for executing day‑to‑day Alliance co‑sell activities that support pipeline creation and partner‑sourced revenue. This role works closely with Sales, Alliances, and Google field teams to manage opportunities, maintain co‑sell hygiene, and ensure deals are properly registered, tracked, and advanced through Google channels. This is a hands‑on, execution‑focused role that supports existing co‑sell strategy through operational coordination and follow‑through. The role reports to the Director of Alliances, NORAM with dotted lines to Sales Leadership and collaborates with all areas of NORAM sales as the lead driver of Google alliance and strategy." Now responsibilities list: ensure each bullet is a complete sentence. Let's list: - Support Sales, Presales, Channel and Alliances teams with deal intake, opportunity qualification, and Google alignment - Partner with Business Excellence to develop and execute internal training, certification, and Google program enablement; educate internal teams on Google incentives, co‑sell pathways, funding programs, sales plays, and marketplace offerings to unlock incremental revenue - Build business cases for co‑op, SPF, and incremental Google investment to support regional growth priorities - Serve as the primary escalation, coordination, and communication point for Google across NORAM sales, delivery, and leadership teams - Manage customer retention strategy, ensuring strong relationships, minimized churn, and effective Google support alignment - Coordinate with Google field sellers to track active opportunities, next steps, and required documentation - Maintain accurate co‑sell pipeline data, reporting, and status updates - Ensure opportunities meet Google co‑sell eligibility and compliance requirements - Prepare deal summaries, win reports, and pipeline updates for internal stakeholders - Support joint account planning by tracking actions and following up on execution items Now requirements list: - 10 years total experience with a high level of business acumen and comfort working with Sales and other senior leaders - Experience in partner management, alliances, or channel sales, preferably in technology services, cloud, or software sales environments - Strong working knowledge of the Google ecosystem: Azure, Copilot, Security, MCAPS structure, incentives, co‑sell, marketplace, and partner programs - Proven experience driving partner‑led revenue growth (ACR, cross‑sell, upsell, and recapture) - Experience working with Google partners, channel programs, or co‑sell motions required; experience using Google Partner Center or supporting Google partner programs preferred - Exposure to partner‑sourced revenue tracking or deal registration processes - Familiarity with CRM systems and pipeline management - Strong organizational skills with attention to detail and follow‑through, along with excellent verbal, written, and presentation skills - Comfortable working cross‑functionally with Sales, Alliances, and Operations teams - Not able to consider candidates residing in the state of Hawaii (maybe we moved to Pay). Actually we placed Hawaii restriction in Pay. Could also be in Requirements. We'll keep in Pay. Now benefits list: need to capture each bullet. We'll flatten: - Generous pay with bonus structure - Independent environment without a lot of red tape where you are empowered to make decisions - Winning culture, inclusive environment, and friendly people all over the world - Remote‑friendly