Engineering Technology Leader

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not include sections with placeholder like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting. Content: - Opening: "Our client is seeking an Engineering Technology Leader to join their team. As an Engineering Technology Leader, you will be part of the Engineering organization supporting technology delivery and engineering transformation initiatives. The ideal candidate will have engineering technology leadership, the ability to lead engineering teams and drive delivery and code, and strong executive and stakeholder communication skills, which will align successfully in the organization." - Job Title line: "Job Title:Engineering Technology Leader" (should not be heading; we can ignore or maybe include as part of a short p? But 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 we can include location and maybe pay range in a short p. - "Location:New York, NY Pay Range: 50-55 Pay Rate Must attend F2F interview" - "What's the Job?" then bullet-like paragraphs: Provide engineering technology leadership by guiding teams to deliver high-quality software and operational outcomes. Lead engineering teams and drive delivery execution, including hands-on support to improve code quality and engineering practices. Demonstrate strong technical credibility with development teams and translate technical direction into actionable plans. Drive AI / GenAI enablement and adoption, SRE transformation, and engineering productivity improvements. Support architecture reviews and technical governance to ensure modern engineering standards and sustainable delivery. - "What's Needed?" then list: Proven experience in engineering leadership roles such as Engineering Manager, Engineering Director, Platform Engineering Lead, Technology Delivery Leader, SRE Leader, or Engineering Transformation Leader. Hands-on understanding of modern engineering practices, including SDLC modernization and engineering productivity improvements. Strong executive and stakeholder communication skills, with the ability to align teams and influence decisions. Experience with SRE transformation and operational excellence, including observability and reliability practices. Preferred exposure to AI / GenAI enablement (e.g., OpenAI, Copilot, LLM-powered solutions) and DevOps/CI-CD practices. - "What's in it for me?" then list: Opportunity to lead meaningful engineering transformation across AI / GenAI enablement, SRE modernization, and SDLC improvements. Work in a role that combines leadership with hands-on technical guidance to help teams succeed. Engage with stakeholders and executives to shape technology governance and architecture direction. Contribute to engineering productivity and operational excellence through modern practices and continuous improvement. Be part of a team focused on delivering durable engineering outcomes and scalable platforms. - Then some fluff about applying, then about ManpowerGroup etc. That's boilerplate (company description). Should be removed as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About ManpowerGroup" is likely boilerplate; we should drop it. - Then "Upon Completion Of Waiting Period Consultants Are Eligible For Medical and Prescription Drug Plans Dental Plan Vision Plan Health Savings Account Health Flexible Spending Account Dependent Care Flexible Spending Account Supplemental Life Insurance Short Term and Long Term Disability Insurance Business Travel Insurance 401(k), Plus Match Weekly Pay". This is benefits info. So we have Benefits section. - Then "Important Submission & Assignment Details (Please Read)" with many details: Onsite requirement: F2F (in-person) is a must. Start date: 2026-11-03 Background check: MANDATORY Meet and greet: Required for all new hires due to additional onboarding requirements. Local/onsite meeting expectation: Candidates must be willing to go to the closest Capgemini, Client, or onsite location as indicated by the project team to meet with a Capgemini team member prior to starting the assignment. If the candidate is not local, travel is covered by Capgemini. Travel cost note: If travel is involved and, after selection, the candidate declines the offer, costs will be paid by vendor and not Capgemini. Resume submission: Submit candidates under their legal name and use only the Capgemini template. Please submit CVs in FG with complete home address. LinkedIn: LinkedIn account is mandatory. GTD ID: 96T2VK Application Checklist (Required For Consideration) ... etc. This is mostly application instructions and metadata; we should remove as per instruction: remove application instructions. So we drop that. Thus we have substantive content: About the role (maybe we can call it "About the role" or "Overview"), Responsibilities (What's the Job?), Requirements/Qualifications (What's Needed?), Skills (maybe combine), Benefits (the benefits list), Pay (Pay Range: 50-55 Pay Rate), Schedule? Not mentioned. There's mention of "Must attend F2F interview" but that's not schedule. No schedule info. So we should not create Schedule section. We need to decide headings: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have: - About the role: we have introductory paragraph describing role. Could be "About the role". Use

About the role

then

with that prose. - Responsibilities: "What's the Job?" content. Use

Responsibilities

then

• items. - Requirements/Qualifications: "What's Needed?" content. Could be

  Requirements

  or

  Qualifications

  . We need to decide. The instruction list includes both Requirements and Qualifications as possible headings. We can combine? Probably better to have one heading "Requirements". Use

  Requirements

  then
  • . - Skills: maybe we could extract skills from requirements? But we already have requirements covering skills. Could also have a Skills section for technical skills like AI/GenAI, SRE, DevOps/CI-CD, etc. However we might avoid duplication. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Skills into one section, but we have to use headings from list. Could do "Requirements" covering both. Or we could have "Skills" separate if there is distinct content. The "What's Needed?" includes both experience and skills. Might be okay to just have Requirements. - Benefits: we have benefits list. Use

    Benefits

    then
    • . - Pay: we have Pay Range: 50-55 Pay Rate. Use

      Pay

      then

      maybe. We must not include Schedule. We must not include any placeholder like "commensurate with experience". Not present. We must preserve all substantive information. Let's extract details precisely. About the role paragraph: "Our client is seeking an Engineering Technology Leader to join their team. As an Engineering Technology Leader, you will be part of the Engineering organization supporting technology delivery and engineering transformation initiatives. The ideal candidate will have engineering technology leadership, the ability to lead engineering teams and drive delivery and code, and strong executive and stakeholder communication skills, which will align successfully in the organization." We can keep that as is. Responsibilities bullet points: Let's list each sentence: - Provide engineering technology leadership by guiding teams to deliver high-quality software and operational outcomes. - Lead engineering teams and drive delivery execution, including hands-on support to improve code quality and engineering practices. - Demonstrate strong technical credibility with development teams and translate technical direction into actionable plans. - Drive AI / GenAI enablement and adoption, SRE transformation, and engineering productivity improvements. - Support architecture reviews and technical governance to ensure modern engineering standards and sustainable delivery. We should keep each as

    • . Requirements bullet points: From "What's Needed?": - Proven experience in engineering leadership roles such as Engineering Manager, Engineering Director, Platform Engineering Lead, Technology Delivery Leader, SRE Leader, or Engineering Transformation Leader. - Hands-on understanding of modern engineering practices, including SDLC modernization and engineering productivity improvements. - Strong executive and stakeholder communication skills, with the ability to align teams and influence decisions. - Experience with SRE transformation and operational excellence, including observability and reliability practices. - Preferred exposure to AI / GenAI enablement (e.g., OpenAI, Copilot, LLM-powered solutions) and DevOps/CI-CD practices. Note: The last bullet says "Preferred exposure". It's still a requirement/qualification. We'll keep as
    • . Benefits list: From "Upon Completion Of Waiting Period Consultants Are Eligible For ...": List items: - Medical and Prescription Drug Plans - Dental Plan - Vision Plan - Health Savings Account - Health Flexible Spending Account - Dependent Care Flexible Spending Account - Supplemental Life Insurance - Short Term and Long Term Disability Insurance - Business Travel Insurance - 401(k), Plus Match - Weekly Pay We need to parse correctly: The text: "Upon Completion Of Waiting Period Consultants Are Eligible For Medical and Prescription Drug Plans Dental Plan Vision Plan Health Savings Account Health Flexible Spending Account Dependent Care Flexible Spending Account Supplemental Life Insurance Short Term and Long Term Disability Insurance Business Travel Insurance 401(k), Plus Match Weekly Pay" It seems missing commas. We'll split by spaces? Better to list each benefit as separate item: Medical and Prescription Drug Plans, Dental Plan, Vision Plan, Health Savings Account, Health Flexible Spending Account, Dependent Care Flexible Spending Account, Supplemental Life Insurance, Short Term and Long Term Disability Insurance, Business Travel Insurance, 401(k) Plus Match, Weekly Pay. We'll keep as
    • each. Pay: "Pay Range: 50-55 Pay Rate". Likely meaning $50-55 per hour? We'll keep as

      Pay Range: 50-55 Pay Rate

      . We must not include any other metadata like location? The instruction says fold minor metadata into a short

      or drop it. Location is minor metadata; we could include a short p at top:

      Location: New York, NY

      . Also maybe include "Must attend F2F interview" as a note? That's also minor metadata; could be included in same p. But we should avoid duplication. Let's include a short p:

      Location: New York, NY • Must attend F2F interview

      . Or separate. We must not include Job ID etc. Now produce HTML fragment: no or . Just the sections. Order: maybe About the role, Responsibilities, Requirements, Benefits, Pay. Could also include Skills but we covered. Let's craft. We'll output:

      About the role

      Our client is seeking an Engineering Technology Leader to join their team. As an Engineering Technology Leader, you will be part of the Engineering organization supporting technology delivery and engineering transformation initiatives. The ideal candidate will have engineering technology leadership, the ability to lead engineering teams and drive delivery and code, and strong executive and stakeholder communication skills, which will align successfully in the organization.

      Responsibilities

      • Provide engineering technology leadership by guiding teams to deliver high-quality software and operational outcomes.
      • Lead engineering teams and drive delivery execution, including hands-on support to improve code quality and engineering practices.
      • Demonstrate strong technical credibility with development teams and translate technical direction into actionable plans.
      • Drive AI / GenAI enablement and adoption, SRE