Sr. Software Engineer - C++

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Job You're Considering". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We need to preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. The posting includes location, role description (Your role), skills and experience (Your Skills And Experience), Preferred Skills, compensation range, benefits description. Also includes some generic company description at top and bottom; we need to keep substantive info but remove fluff? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the core job description, responsibilities, skills, preferred skills, compensation, benefits. The introductory paragraph about Capgemini Engineering might be considered substantive? It's generic marketing but maybe we can keep as part of "About the role"? However they said 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. The location is metadata; we can put in a short

. The intro about Capgemini Engineering could be considered part of "About the role" or maybe we can include a brief paragraph under an

About the role. But we need to avoid filler like "commensurate with experience". Not present. We need to decide sections: Could have About the role (intro + location), Responsibilities (Your role), Requirements/Qualifications (Your Skills And Experience), Skills (Preferred Skills), Pay (compensation range), Benefits (benefits description). Schedule not present, so omit. We must not create sections with filler. Ensure each heading has substantive content. We need to use

• for any list of duties/requirements/benefits. So for responsibilities, we can list each bullet as
• . For skills/experience, also list. For preferred skills, list. For benefits, list. We need to use

  for prose. We must not include markdown code fences. Just raw HTML. Let's extract content. Location: Westford, MA (Onsite). We'll put in a

  maybe under About the role. About the role: The introductory paragraph: "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." That's generic but maybe we keep as About the role. Then "About The Job You're Considering We are seeking a Senior Software Engineer to support a leading client in the medical device industry. In this role, you will design, develop, test, and validate software that powers complex laboratory and medical device systems. You will work across the full software development lifecycle, collaborating with multidisciplinary teams to deliver high-quality, compliant, and reliable solutions that support healthcare innovation." We can combine that as About the role. Responsibilities: The bullet list under "Your role". It repeats same as Skills And Experience? Actually "Your Skills And Experience" repeats same list. So we need to deduplicate. The responsibilities list: - Design, develop, and maintain software applications using C++. - Develop and support software that interfaces with hardware and controls device functionality. - Participate in verification and validation (V&V) activities to ensure software quality, performance, and compliance. - Create and execute unit tests and automated test solutions. - Collaborate with cross-functional teams to define requirements, troubleshoot issues, and implement enhancements. - Contribute to technical documentation, code reviews, and design reviews. - Support CI/CD pipelines and Agile software development practices. - Investigate software defects and implement corrective actions in accordance with established engineering processes. We'll output as

  • ... etc. Requirements/Qualifications: The "Your Skills And Experience" list is same as responsibilities; but we need to avoid duplication. Perhaps we treat that as Requirements (mandatory skills). Since it's identical, we could still include but note it's same. However we should not repeat same content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit the duplicate, we lose some info? But the info is same as responsibilities; but it's still substantive. However we could combine responsibilities and requirements into one section? But they ask to use headings for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put the list under Responsibilities, and under Requirements we could note "Same as responsibilities" but that would be summarizing. Better to keep both sections but maybe we can keep the list under Requirements and not duplicate under Responsibilities? However the responsibilities list is explicitly given; we need to preserve that. So we need to include both sections, but we can keep the same list in both; it's not invented, it's preserving detail. It's okay to duplicate as per source. So we will output both sections with same list. Preferred Skills: list: - Experience in regulated industries such as Medical Device, Healthcare, Aerospace, Automotive, or Life Sciences. - Knowledge of software Verification & Validation (V&V) methodologies. - Familiarity with IEC 62304, FDA regulations, Design Controls, and traceability requirements. - Experience with COM, inter-process communication, Jira, and Confluence. - Exposure to C# and state machine design. Pay: The base compensation range: $68,911 - $161,544. Also note about compensation range info etc. We need to preserve all substantive info; we can include a

    with that range and the explanatory text? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The compensation range is specific numbers, so we can include Pay section with that range and maybe the explanatory text about range may be considered boilerplate but it's part of the posting. However it's somewhat generic but still substantive. We'll include a

    with the range and the note that it's base compensation range etc. Might be okay. Benefits: The paragraph about 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'll turn that into a

    • list. We need to remove boilerplate like EEO, disclaimers, legal, etc. Also remove the duplicated lines like "Important Notice: Compensation..." and "Disclaimers" etc. Also remove the final paragraph about Capgemini being global etc. That's boilerplate? It's generic company description; maybe we can keep as part of About the role? But it's at the end; it's also generic. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The final paragraph about Capgemini being global is not legal but it's generic marketing; maybe we can keep as part of About the role? However we already have an intro about Capgemini Engineering; the final paragraph is similar but more generic. Could be considered boilerplate; but it's not explicitly legal. To be safe, we could omit it as it's not specific to the job. The instruction: "Preserve ALL substantive information". Is that substantive? It's about the company, not the job. Might be considered boilerplate. I'd lean to omit it to keep focused on job. Also remove the "Important Notice: Compensation..." etc. Now construct HTML. We'll start with

      About the role

      then

      containing the intro paragraphs and location. We need to avoid repeating job title as heading; we don't. Let's craft:

      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: Westford, MA (Onsite)

      We are seeking a Senior Software Engineer to support a leading client in the medical device industry. In this role, you will design, develop, test, and validate software that powers complex laboratory and medical device systems. You will work across the full software development lifecycle, collaborating with multidisciplinary teams to deliver high-quality, compliant, and reliable solutions that support healthcare innovation.

      Then Responsibilities:

      Responsibilities

      • Design, develop, and maintain software applications using C++.
      • Develop and support software that interfaces with hardware and controls device functionality.
      • Participate in verification and validation (V&V) activities to ensure software quality, performance, and compliance.
      • Create and execute unit tests and automated test solutions.
      • Collaborate with cross-functional teams to define requirements, troubleshoot issues, and implement enhancements.
      • Contribute to technical documentation, code reviews, and design reviews.
      • Support CI/CD pipelines and Agile software development practices.
      • Investigate software defects and implement corrective actions in accordance with established engineering processes.
      Then Requirements (or Qualifications). We'll use

      Requirements

      and same list.

      Requirements

      ... same list ...
      Then Skills (Preferred Skills):

      Skills

      • Experience in regulated industries such as Medical Device, Healthcare, Aerospace, Automotive, or Life Sciences.
      • Knowledge of software Verification & Validation (V&V) methodologies.
      • Familiarity with IEC 62304, FDA regulations, Design Controls, and traceability requirements.
      • Experience with COM, inter-process communication, Jira, and Confluence.
      • Exposure to C# and state machine design.
      Then Pay:

      Pay

      The base compensation range for this role in the posted location is: $68,911 - $161,544. 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