Go-to-Market (GTM) Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - Intro paragraph: "Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world." That's prose. Could be placed maybe as introductory paragraph before sections? Not required but we can include as

. Then "Job Description About the Role" heading? Actually they have "Job Description About the Role". We'll treat "About the Role" as a section heading

About the Role

and then paragraph(s) describing role. Then "Key Responsibilities" with subheadings: Strategy & Growth, Solution Development & Market Differentiation, Sales Enablement & Pipeline Development, collaboration with HighTouch. Actually there is a line "collaboration with HighTouch." maybe part of previous? We'll treat as bullet list under Responsibilities. We need to use

• for any list of duties/requirements/benefits. Thus we can create a
  for responsibilities items. Then "Experience Required Qualifications" includes bullet list of qualifications (required) and "Preferred Experience". We'll need sections: Requirements (maybe required qualifications) and Qualifications? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which content maps to which. We have: - About the Role: description. - Responsibilities: list of duties. - Requirements: maybe "Experience Required" (required qualifications). Could be "Experience Required Qualifications". We'll treat as Requirements. - Qualifications: maybe "Preferred Experience". Or we could combine required and preferred under Qualifications? But we have both sections headings available. We'll put required under Requirements, preferred under Qualifications. - Skills: maybe not explicitly listed; we could infer from responsibilities but better not to create empty section. So we omit Skills if no specific content. - Benefits: we have benefits paragraph. - Pay: we have compensation range details. - Schedule: not mentioned; omit. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not include empty sections. Now we need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, disclaimers, legal, etc. Also remove duplicated lines. We need to extract substantive content. Let's extract: Intro paragraph: "Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology and build a more sustainable, more inclusive world." About the Role paragraph: "Capgemini is seeking a highly motivated and strategic Go-to-Market (GTM) Lead for the HighTouch to drive the growth, market positioning, and joint business development strategy with HighTouch. This leader will be responsible for building and executing the alliance strategy, creating differentiated market offerings, enabling sales teams, and driving revenue growth through co-selling and joint solution development." That's the About the Role content. Responsibilities: Under "Key Responsibilities" we have sub-sections: Strategy & Growth: - Define and execute Capgemini's GTM strategy for the HighTouch partnership. - Develop joint business plans, growth targets, and market expansion strategies. - Foster executive relationships across Capgemini and HighTouch leadership teams. - Identify new market opportunities and industry-specific use cases that leverage HighTouch capabilities. - Establish and track alliance KPIs, pipeline growth, partner-sourced opportunities, and revenue targets. Solution Development & Market Differentiation: - Collaborate with Capgemini practices to create industry-specific solutions powered by HighTouch. - Develop repeatable offerings focused on Customer Data Platforms (CDP), Composable CDP, AI-driven personalization, customer analytics, and marketing transformation. - Create joint value propositions, accelerators, demos, and reference architectures. - Build thought leadership and market messaging around customer-centric data activation strategies. Sales Enablement & Pipeline Development: - Partner with sales leaders to identify, qualify, and close opportunities. - Develop sales plays, account targeting strategies, and go-to-market campaigns. - Enable account teams through training, workshops, and solution positioning. - Lead joint customer engagements, executive presentations, and strategic pursuits. - Drive partner-influenced and partner-sourced revenue growth. collaboration with HighTouch. (maybe a duplicate?) Actually there is a line "collaboration with HighTouch." after Sales Enablement & Pipeline Development? The text: "collaboration with HighTouch. Partner Management & Governance". It seems there is a missing heading. Let's parse: after Sales Enablement & Pipeline Development bullet list, there is "collaboration with HighTouch." then next heading "Partner Management & Governance". So maybe "collaboration with HighTouch." is a bullet? Actually it's likely a typo; we can treat as part of Partner Management & Governance? But we can include as a bullet under Responsibilities: "collaboration with HighTouch." but that seems vague. Better to incorporate into Partner Management & Governance. Partner Management & Governance: - Establish a governance framework to manage the alliance relationship. - Coordinate executive business reviews and quarterly planning sessions. - Monitor partnership performance and recommend strategic adjustments. - Ensure alignment between alliance objectives and Capgemini business priorities. Thus responsibilities list includes all those bullet points. Now Requirements (Experience Required Qualifications): - 10+ years of experience in alliance management, business development, partner ecosystems, or go-to-market leadership. - Experience working with data platforms, customer data technologies, CRM, marketing automation, or analytics solutions. - Proven track record of driving partner-led revenue growth and strategic alliances. - Experience developing solutions and GTM initiatives with technology partners. - Strong understanding of customer experience, data activation, personalization, and digital transformation. Preferred Experience: - Experience with HighTouch, Segment, Snowflake, Databricks, Salesforce Data Cloud, Adobe Experience Platform, or related ecosystems. - Knowledge of composable CDP architectures and first-party data strategies. - Experience selling or delivering cloud, analytics, MarTech, or customer engagement solutions. - Background in consulting, professional services, or systems integration organizations. - Development of reusable offerings and accelerators. - Achievement of annual alliance business plan objectives. Now Benefits: "Capgemini offers a comprehensive, non-negotiable benefits package to all regular, full-time employees. In the U.S. and Canada, available benefits are determined by local policy and eligibility and may include: - Paid time off based on employee grade (A-F), defined by policy: Vacation: 12-25 days, depending on grade, Company paid holidays, Personal Days, Sick Leave - Medical, dental, and vision coverage (or provincial healthcare coordination in Canada) - Retirement savings plans (e.g., 401(k) in the U.S., RRSP in Canada) - Life and disability insurance - Employee assistance programs - Other benefits as provided by local policy and eligibility" We need to preserve all substantive info. The bullet list includes some run-on sentences; we can split into
  • items. We should not include the "Important Notice: Compensation..." etc. That's about compensation but we have Pay section; we need to include compensation details but not the legal disclaimer? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The "Important Notice: Compensation (including bonuses, commissions, or other forms of incentive pay) is not considered earned..." is legal boilerplate about compensation; we should remove it. Also the disclaimer about EEO etc. Remove. Thus Pay section should include the base compensation range details: "The base compensation range for this role in the posted location is 135549 - 176139". Also maybe the sentence about Capgemini provides compensation range information... but that's also legal? It's explanatory but maybe not boilerplate? It's part of the posting about pay transparency. Might be considered substantive? The instruction: "Prefer a few substantive sections over many thin ones." and "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The compensation range is specific. The explanatory sentences about range may be considered filler but they are part of the posting. However they are somewhat generic but still part of the compensation description. I'd include them as part of Pay section but maybe we can keep just the range and the sentence that Capgemini provides compensation range information... It's not filler; it's explaining why range is shown. I'd include it. Thus Pay section:

    The base compensation range for this role in the posted location is 135,549 - 176,139.

    maybe with commas. Also include: "Capgemini provides compensation range information in accordance with applicable national, state, provincial, and local pay transparency laws. The base compensation range listed for this position reflects the minimum and maximum target compensation Capgemini, in good faith, believes it may pay for the role at the time of this posting. This range may be subject to change as permitted by law. The actual compensation offered to any candidate may fall outside of the posted range and will be determined based on multiple factors legally permitted in the applicable jurisdiction. These may include, but are not limited to: Geographic location, Education and qualifications, Certifications and licenses, Relevant experience and skills, Seniority and performance, Market and business consideration, Internal pay equity. It is not typical for candidates to be hired at or near the top of the posted compensation range. In addition to base salary, this role may be eligible for additional compensation such as variable incentives, bonuses, or commissions, depending on the position and applicable laws." But some of that is legal boilerplate? It's describing how compensation is determined; might be considered substantive. However the instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly EEO but it's about compensation disclosure; might be okay to keep. Safer to keep the range and maybe a brief sentence: "Capgemini provides compensation range information in accordance with applicable pay transparency laws." But we risk removing detail. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep all substantive info about pay. The legal boilerplate about compensation being not earned etc we should remove. The rest is substantive. Thus we will include the paragraph(s) about compensation range and factors. Now Schedule: none. Now we need to output only HTML fragment, no /, no markdown. We'll structure:

    Intro paragraph.

    About the Role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    ...

    We must ensure we don't repeat job title. Now let's craft the content precisely. Intro: "Choosing Capgemini means choosing a company where you will be empowered to shape your career in the way you’d like, where you’ll be supported and inspired by a collaborative community of colleagues around the world, and where you’ll be able to reimagine what’s possible. Join us and help the world’s leading organizations unlock the value of technology