Senior Sales Representative - CSP
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Include a section only when posting has real specific content for it; never emit heading with filler placeholder. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key content:
- Location: Dallas, TX. Could be a short
maybe under a heading? Not a required heading; we can include location in a paragraph maybe under "About the role"? But we need to decide sections.
The posting includes:
- About The Job (intro paragraph)
- Your Role (list of duties)
- Your Skills And Experience (list of qualifications/skills)
- The base compensation range: $98,497-$233,248 (Pay)
- Benefits description (Benefits)
- No explicit Schedule info.
Thus we can have sections:
- About the role (intro paragraph)
- Responsibilities (list from "Your Role")
- Requirements / Qualifications / Skills (maybe combine? The instruction says use headings for those categories; we can decide to have "Qualifications" and "Skills" separate if content distinct. The "Your Skills And Experience" includes both qualifications (degree, years experience) and skills (technical knowledge, etc.). Could split into Qualifications (education, experience) and Skills (technical, soft skills). But we need to avoid thin sections; maybe combine into one "Qualifications and Skills" but we only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "Qualifications" for education/experience, and "Skills" for technical/soft skills. Or we could use "Requirements" for experience/education and "Skills" for skillset. Let's see.
The content:
Education: Bachelor's degree in Business, Engineering, Marketing, or related field, or equivalent professional experience.
Experience: 10+ years of success in business development, sales, or account management within telecommunications, CSP, or technology services industry.
Demonstrated ability to achieve growth objectives in complex, consultative, or engineering-led sales environments.
Strong understanding of mobile networks, telecom infrastructure, digital transformation, evolving CSP market trends.
Experience building trusted relationships with senior executives and influencing strategic business decisions.
Excellent communication, negotiation, presentation skills, ability to translate complex technical concepts into business value.
Experience with one or more emerging technology areas, such as AI/ML, Generative AI, OSS/BSS modernization, Private Networks, Fixed Wireless Access, Open RAN, cloud-native platforms, or enterprise telecommunications solutions.
Collaborative, growth-oriented mindset with proven ability to drive results, foster partnerships, create long-term client value.
Thus we could have Qualifications: education + years experience + ability to achieve growth objectives (maybe that's skill). But we can split: Qualifications: education + years experience. Skills: technical understanding, relationship building, communication, emerging tech experience, collaborative mindset.
Responsibilities: list from "Your Role".
Pay: compensation range.
Benefits: description.
Schedule: none -> omit.
We also have location; could include in About the role paragraph.
We must not include boilerplate like EEO, disclaimers, etc.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the sections we include.
We must not include filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
At Capgemini Engineering, the world leader in engineering services, we bring together a global team of engineers, scientists, and architects to help the world’s most innovative companies unleash their potential. From autonomous cars to life-saving robots, our digital and software technology experts think outside the box as they provide unique R&D and engineering services across all industries. Join us for a career full of opportunities. Where you can make a difference. Where no two days are the same. Location: Dallas, TX.
Responsibilities
- Develop and execute strategic account plans for major North American CSPs and mobile network operators.
- Drive revenue growth by positioning Capgemini Engineering's engineering, digital transformation, and R&D solutions through a consultative, value-focused approach.
- Build and strengthen relationships with executive stakeholders, including C-suite, VP, and Director-level leaders.
- Serve as a trusted advisor by aligning solutions with client priorities, technology roadmaps, and business objectives.
- Identify and advance new opportunities through account planning, market insights, and industry engagement.
- Lead client discussions, executive presentations, proposals, commercial negotiations, and strategic growth initiatives.
- Partner with solution, delivery, and engineering teams to develop compelling client solutions and ensure successful outcomes.
- Contribute market intelligence and industry perspectives to help shape go-to-market strategies and business growth.
Qualifications
- Bachelor's degree in Business, Engineering, Marketing, or a related field, or equivalent professional experience.
- 10+ years of success in business development, sales, or account management within the telecommunications, CSP, or technology services industry.
Skills
- Demonstrated ability to achieve growth objectives in complex, consultative, or engineering-led sales environments.
- Strong understanding of mobile networks, telecom infrastructure, digital transformation, and evolving CSP market trends.
- Experience building trusted relationships with senior executives and influencing strategic business decisions.
- Excellent communication, negotiation, and presentation skills, with the ability to translate complex technical concepts into business value.
- Experience with one or more emerging technology areas, such as AI/ML, Generative AI, OSS/BSS modernization, Private Networks, Fixed Wireless Access, Open RAN, cloud-native platforms, or enterprise telecommunications solutions.
- A collaborative, growth-oriented mindset with a proven ability to drive results, foster partnerships, and create long-term client value.
Pay
The base compensation range for this role in the posted location is: $98,497-$233,248.
Benefits
- 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 ensure we didn't include any boilerplate like "Capgemini provides compensation range information..." etc. That's part of Pay section but we might need to include that? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The compensation range details include extra sentences about range may be subject to change, etc. Those are substantive? They are part of the posting about compensation. Should we include them? The instruction says include Pay section only if posting actually states them. It does state base compensation range and also includes additional explanation. Should we include that explanation? It is substantive information about compensation. The instruction says "Prefer a few substantive sections over many thin ones." But we should not omit substantive detail. So we should include the full compensation description, not just the range. However, the Pay heading expects we can put prose . We could include multiple paragraphs.
Thus for Pay we could have:
The base compensation range for this role in the posted location is: $98,497-$233,248. 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.
That seems substantive.
Similarly Benefits: we included list but also there is a paragraph about "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:" then list. We could include that as a then list. But we already have list; we could include a preceding
summarizing that. To preserve all substantive info, we should include that sentence.
Thus Benefits section:
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:
...
We also have "Important Notice: Compensation (including bonuses, commissions, or other forms of incentive pay) is not considered earned..." That's also substantive about compensation but maybe belongs under Pay? It's about compensation. Could include under Pay as another paragraph.
But we need to avoid too many thin sections; we can add more paragraphs under Pay.
Thus Pay section could have multiple elements.
Similarly there is a disclaimer about "Disclaimers Capgemini is an Equal Opportunity Employer..." That's boilerplate EEO; we should remove.
Also there is a paragraph about "This is a general description of the Duties, Responsibilities and Qualifications required for this position. Physical, mental, sensory or environmental demands may be referenced..." That's boilerplate; remove.
Also "Capgemini is committed to providing reasonable accommodation..." etc. That's boilerplate; remove.
Also "Please be aware that Capgemini may capture your image..." etc. Remove.
Also "Click the following link for more information on your rights as an Applicant in the United States." Remove.
Also "Capgemini is a global business and technology transformation partner..." That's boilerplate about company; could be considered substantive? It's generic description; maybe not needed as it's not specific to role. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph about Capgemini being global etc might be considered boilerplate; but it's not legal/EEO; it's company overview. Might be considered not specific to role; but it's not explicitly listed as boilerplate to remove. However earlier they gave an intro about Capgemini Engineering at start; that is specific to role context. The later paragraph about "Capgemini is a global business and technology transformation partner..." is more generic; could be considered boilerplate but not sure. Safer to remove as it's not specific to the role and could be considered fluff. The instruction says remove duplicated lines; this is not duplicated but it's generic. I'd lean to remove it to keep focused.
Thus final HTML includes sections: About the role, Responsibilities, Qualifications, Skills, Pay
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. Include a section only when posting has real specific content for it; never emit heading with filler placeholder. Prefer few substantive sections over many thin ones. We need to parse the posting. Key content: - Location: Dallas, TX. Could be a short
maybe under a heading? Not a required heading; we can include location in a paragraph maybe under "About the role"? But we need to decide sections. The posting includes: - About The Job (intro paragraph) - Your Role (list of duties) - Your Skills And Experience (list of qualifications/skills) - The base compensation range: $98,497-$233,248 (Pay) - Benefits description (Benefits) - No explicit Schedule info. Thus we can have sections: - About the role (intro paragraph) - Responsibilities (list from "Your Role") - Requirements / Qualifications / Skills (maybe combine? The instruction says use headings for those categories; we can decide to have "Qualifications" and "Skills" separate if content distinct. The "Your Skills And Experience" includes both qualifications (degree, years experience) and skills (technical knowledge, etc.). Could split into Qualifications (education, experience) and Skills (technical, soft skills). But we need to avoid thin sections; maybe combine into one "Qualifications and Skills" but we only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use "Qualifications" for education/experience, and "Skills" for technical/soft skills. Or we could use "Requirements" for experience/education and "Skills" for skillset. Let's see. The content: Education: Bachelor's degree in Business, Engineering, Marketing, or related field, or equivalent professional experience. Experience: 10+ years of success in business development, sales, or account management within telecommunications, CSP, or technology services industry. Demonstrated ability to achieve growth objectives in complex, consultative, or engineering-led sales environments. Strong understanding of mobile networks, telecom infrastructure, digital transformation, evolving CSP market trends. Experience building trusted relationships with senior executives and influencing strategic business decisions. Excellent communication, negotiation, presentation skills, ability to translate complex technical concepts into business value. Experience with one or more emerging technology areas, such as AI/ML, Generative AI, OSS/BSS modernization, Private Networks, Fixed Wireless Access, Open RAN, cloud-native platforms, or enterprise telecommunications solutions. Collaborative, growth-oriented mindset with proven ability to drive results, foster partnerships, create long-term client value. Thus we could have Qualifications: education + years experience + ability to achieve growth objectives (maybe that's skill). But we can split: Qualifications: education + years experience. Skills: technical understanding, relationship building, communication, emerging tech experience, collaborative mindset. Responsibilities: list from "Your Role". Pay: compensation range. Benefits: description. Schedule: none -> omit. We also have location; could include in About the role paragraph. We must not include boilerplate like EEO, disclaimers, etc. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the sections we include. We must not include filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:
About the role
At Capgemini Engineering, the world leader in engineering services, we bring together a global team of engineers, scientists, and architects to help the world’s most innovative companies unleash their potential. From autonomous cars to life-saving robots, our digital and software technology experts think outside the box as they provide unique R&D and engineering services across all industries. Join us for a career full of opportunities. Where you can make a difference. Where no two days are the same. Location: Dallas, TX.
Responsibilities
- Develop and execute strategic account plans for major North American CSPs and mobile network operators.
- Drive revenue growth by positioning Capgemini Engineering's engineering, digital transformation, and R&D solutions through a consultative, value-focused approach.
- Build and strengthen relationships with executive stakeholders, including C-suite, VP, and Director-level leaders.
- Serve as a trusted advisor by aligning solutions with client priorities, technology roadmaps, and business objectives.
- Identify and advance new opportunities through account planning, market insights, and industry engagement.
- Lead client discussions, executive presentations, proposals, commercial negotiations, and strategic growth initiatives.
- Partner with solution, delivery, and engineering teams to develop compelling client solutions and ensure successful outcomes.
- Contribute market intelligence and industry perspectives to help shape go-to-market strategies and business growth.
Qualifications
- Bachelor's degree in Business, Engineering, Marketing, or a related field, or equivalent professional experience.
- 10+ years of success in business development, sales, or account management within the telecommunications, CSP, or technology services industry.
Skills
- Demonstrated ability to achieve growth objectives in complex, consultative, or engineering-led sales environments.
- Strong understanding of mobile networks, telecom infrastructure, digital transformation, and evolving CSP market trends.
- Experience building trusted relationships with senior executives and influencing strategic business decisions.
- Excellent communication, negotiation, and presentation skills, with the ability to translate complex technical concepts into business value.
- Experience with one or more emerging technology areas, such as AI/ML, Generative AI, OSS/BSS modernization, Private Networks, Fixed Wireless Access, Open RAN, cloud-native platforms, or enterprise telecommunications solutions.
- A collaborative, growth-oriented mindset with a proven ability to drive results, foster partnerships, and create long-term client value.
Pay
The base compensation range for this role in the posted location is: $98,497-$233,248.
Benefits
- 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 could include multiple paragraphs. Thus for Pay we could have:
The base compensation range for this role in the posted location is: $98,497-$233,248. 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.
That seems substantive. Similarly Benefits: we included list but also there is a paragraph about "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:" then list. We could include that as athen list. But we already have list; we could include a preceding
summarizing that. To preserve all substantive info, we should include that sentence. Thus Benefits section:
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:
- ...
elements. Similarly there is a disclaimer about "Disclaimers Capgemini is an Equal Opportunity Employer..." That's boilerplate EEO; we should remove. Also there is a paragraph about "This is a general description of the Duties, Responsibilities and Qualifications required for this position. Physical, mental, sensory or environmental demands may be referenced..." That's boilerplate; remove. Also "Capgemini is committed to providing reasonable accommodation..." etc. That's boilerplate; remove. Also "Please be aware that Capgemini may capture your image..." etc. Remove. Also "Click the following link for more information on your rights as an Applicant in the United States." Remove. Also "Capgemini is a global business and technology transformation partner..." That's boilerplate about company; could be considered substantive? It's generic description; maybe not needed as it's not specific to role. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This paragraph about Capgemini being global etc might be considered boilerplate; but it's not legal/EEO; it's company overview. Might be considered not specific to role; but it's not explicitly listed as boilerplate to remove. However earlier they gave an intro about Capgemini Engineering at start; that is specific to role context. The later paragraph about "Capgemini is a global business and technology transformation partner..." is more generic; could be considered boilerplate but not sure. Safer to remove as it's not specific to the role and could be considered fluff. The instruction says remove duplicated lines; this is not duplicated but it's generic. I'd lean to remove it to keep focused. Thus final HTML includes sections: About the role, Responsibilities, Qualifications, Skills, Pay