Vendor Manager
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. The posting includes: - Intro paragraph about Capgemini (maybe "About the role"? Actually it's more about company culture. Could be "About the role" or maybe "About Capgemini". But we only have allowed headings; we can use "About the role" for that intro. - Location: "The job is located at Smithfield, RI. This job requires onsite participation." This is location info; not a standard heading; we could embed in a
maybe under About the role or separate? There's no heading for location; we can just include as a paragraph. - Job Description - Grade Specific Bachelor's degree in Computer Science, Information Technology, or related field 8+ years of technical, hands-on experience building scalable enterprise applications including Web applications, API, Event Driven, Batch, Database and Cloud solutions. Experience leading, coaching, mentoring, and developing teams in a geographically dispersed organization. Practical experience with software engineering fundamentals and tools such as requirements analysis and documentation (Jira), system design, API integration (SOAP/REST), cloud architecture, CI/CD pipelines (Jenkins), version control (GitHub), agile methodologies, stakeholder communication, and aligning technical deliverables with business goals. Technology leadership, critical thinking, and influencing skills across diverse organizational structures. Series 99, operations professional licensing desired. Strong commitment to quality, documentation, and engineering excellence. Proven experience in technical design and estimation, ensuring alignment with enterprise architecture and governance controls. Deep understanding of technology standards and best practices including design principles, security, reliability, resilience, performance, etc. Excellent interpersonal and communication skills to build and maintain strong cross-functional relationships at all levels of the organization. Decision making experience using a data-focused approach in day-to-day leadership situations and strategic tradeoff analyses. Demonstrated experience in optimizing delivery through flow efficiency, quality improvements, tech debt management, AI and tooling enhancements Commitment to associate skill development aligned with technology roadmap and organizational goals That seems like a list of responsibilities/requirements/qualifications/skills. We need to separate into sections: Responsibilities, Requirements, Qualifications, Skills. However we need to avoid thin sections; maybe combine. We have a compensation range: "The base compensation range for this role in the posted location is: 86129 to 127189". That's Pay section. 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". That's Benefits. Schedule: Not explicitly mentioned besides "onsite participation". No schedule details like full-time, part-time, shift. So we should not create Schedule section because no specific content. We also have some boilerplate about EEO etc which we must remove. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can format into HTML. We need to avoid repeating job title as heading (not present). Do not put Job ID/requisition numbers as headings (none). We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:
About the role
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.
Location: Smithfield, RI. This job requires onsite participation.
Then maybeResponsibilities
with a- of duties. But we need to decide what belongs to responsibilities vs requirements vs qualifications vs skills. The posting mixes them. We could create a single section "Responsibilities and Requirements" but we have limited headings; we could use multiple headings if we have substantive content for each.
We have details: Bachelor's degree, 8+ years experience, leading teams, practical experience with tools, technology leadership, critical thinking, Series 99 licensing desired, commitment to quality, proven experience in technical design, deep understanding of standards, excellent interpersonal skills, decision making using data-focused approach, demonstrated experience optimizing delivery, commitment to associate skill development.
These could be considered Requirements/Qualifications/Skills. Could split:
- Requirements: Bachelor's degree, 8+ years experience, leading teams, practical experience with tools (list), Series 99 licensing desired.
- Qualifications: Strong commitment to quality, proven experience in technical design, deep understanding of technology standards, excellent interpersonal skills, decision making using data-focused approach, demonstrated experience optimizing delivery, commitment to associate skill development.
- Skills: Technology leadership, critical thinking, influencing skills, etc. But overlapping.
Given instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine into one section "Requirements and Qualifications" using
- Build scalable enterprise applications including Web applications, API, Event Driven, Batch, Database and Cloud solutions.
- Lead, coach, mentor, and develop teams in a geographically dispersed organization.
- Perform requirements analysis and documentation (Jira).
- Design systems and integrate APIs (SOAP/REST).
- Work with cloud architecture.
- Implement CI/CD pipelines (Jenkins).
- Use version control (GitHub).
- Apply agile methodologies.
- Communicate with stakeholders and align technical deliverables with business goals.
- Demonstrate technology leadership, critical thinking, and influencing skills across diverse organizational structures.
- Ensure quality, documentation, and engineering excellence.
- Perform technical design and estimation, aligning with enterprise architecture and governance controls.
- Maintain deep understanding of technology standards and best practices (design principles, security, reliability, resilience, performance, etc.).
- Build and maintain strong cross-functional relationships via excellent interpersonal and communication skills.
- Make decisions using a data-focused approach in day-to-day leadership and strategic tradeoff analyses.
- Optimize delivery through flow efficiency, quality improvements, tech debt management, AI and tooling enhancements.
- Commit to associate skill development aligned with technology roadmap and organizational goals.
- Bachelor's degree in Computer Science, Information Technology, or related field.
- 8+ years of technical, hands-on experience building scalable enterprise applications.
- Series 99, operations professional licensing desired.