Jobs · Engineering · Illinois

Mulesoft Platform Architect

Capgemini · Chicago, IL · 3 wk ago
Engineering$98k–$233k/yrFull-time
We need to output HTML fragment with sections: headings

for sections like 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. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Key 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." - Location: "This is hybrid/onsite role based in either locations - Nashvile,TN, Atlanta,GA, Chicago,IL, Dallas,TX, New York,NY, Jersey City,NJ, Columbia,SC." - About The Job: "You’re Considering Capgemini is seeking fulltime Mulesoft Platform Architect (Sr Manager Level) for fulltime position. This is onsite hybrid role." - Your role (Responsibilities): bullet list? Actually paragraph: "Responsible for Planning, Sizing, and Implementation of MuleSoft Platform for RTF / CloudHub Environments. Architect and Design of MuleSoft Platforms: Design and Size MuleSoft Platform to support production and non-production environments Design and implement networking solutions for communicating with Enterprise Applications running on-prem and on cloud Setup access control for applications, and platform access using SSO with IDM providers. Build and maintain CI/CD pipelines to support automated provisioning and deployments in a DevOps environment Work with cross-functional teams including Business, Functional, Networking, Security and Infrastructure teams to understand Enterprise integration requirements Developed operational, monitoring and reliability procedures and processes for large cluster" - Your Skills And Experience: bullet list? Actually numbered list: "10+ years of Middleware/Integration experience (any platform). Required 3 full life cycles of MuleSoft Platform setup and operationalization. (Design, Configuring, Implementation, and Operationalization) Must have MuleSoft Integration Architect and MuleSoft Platform Architect certifications Experience in various MuleSoft Platforms including RTF, CloudHub 2.0, Flex Gateway. Experience in implementing MuleSoft Platform on-prem, public and private cloud environment A bachelor’s degree in computer science, Engineering, or a related field, with significant experience in software development" - Compensation: "The base compensation range for this role in the posted location is: $98,487 - $233,248" plus explanation about range. - 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" - Then there is a long disclaimer about compensation, EEO, etc. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, legal disclaimer about compensation not earned, etc. Also remove "Important Notice: Compensation (including bonuses, commissions, or other forms of incentive pay) is not considered earned..." That's boilerplate legal. Also "Disclaimers" section about EEO, PAIR, etc. Also "Click the following link for more information on your rights as an Applicant in the United States." Also the paragraph about Capgemini being a global business etc. That's boilerplate about company description; might be considered not substantive? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company description may be considered boilerplate? It's not exactly legal/EEO but it's generic marketing. Might be considered boilerplate? The instruction says to remove legal/EEO/equal-opportunity/scam-warning boilerplate. The company description is not explicitly listed, but it's generic fluff. Might be considered not substantive? However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The company description is not specific to the job; it's generic about Capgemini. Likely we should remove it as boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't explicitly say to remove generic company overview, but it's not substantive to the role. However "Preserve ALL substantive information" - the company overview is not substantive to the job specifics. I'd lean to remove it. Thus we keep: - Intro paragraph (maybe as

    ). - Location (maybe as

    ). - About the role? Actually we have "About The Job" heading but we should not repeat job title as heading. The section "About The Job" could be considered a heading for role description. We can use

    About the role

    maybe. The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly Schedule if present (not). We need to decide which sections have real content. We have: - About the role: we have intro paragraph about Capgemini and the role? Actually "About The Job You’re Considering Capgemini is seeking fulltime Mulesoft Platform Architect (Sr Manager Level) for fulltime position. This is onsite hybrid role." That's about the role. Could be placed under About the role. - Responsibilities: we have bullet list of duties. - Requirements: maybe we have "Your Skills And Experience" which includes experience, certifications, education. Could be split into Requirements and Qualifications and Skills. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements (including experience, certifications, education), Benefits, Pay. We need to decide if we need Skills separate. The "Your Skills And Experience" includes skills and experience; we could treat that as Requirements. Could also split into Requirements (experience, certifications) and Qualifications (education). But that may be thin. Better to combine into one Requirements section. Thus sections: - About the role (

    About the role

    ) with paragraph(s): intro + maybe the "About The Job" sentence. - Responsibilities (

    Responsibilities

    ) with
    • items. - Requirements (

      Requirements

      ) with
      • items: 10+ years middleware, 3 full life cycles, certifications, experience with platforms, bachelor's degree. - Benefits (

        Benefits

        ) with
        • items: Paid time off based on grade (vacation 12-25 days), company paid holidays, personal days, sick leave, medical/dental/vision, retirement savings, life/disability insurance, employee assistance programs, other benefits as per local policy. - Pay (

          Pay

          ) with

          containing the base compensation range and maybe note about variable incentives? The posting mentions "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's substantive. So include that. We should not include Schedule (no info). Not include Qualifications separate. We must remove boilerplate: legal disclaimer about compensation not earned, EEO, etc. Also remove the "Important Notice" and "Disclaimers" sections. Also remove the company description paragraph at end. Also remove duplicated lines: there may be duplicate sentences like "This is hybrid/onsite role based in either locations - ..." appears maybe only once. Also "This is onsite hybrid role." appears in About The Job line. We'll keep only once. Now craft HTML. We need to output only HTML fragment, no /, no markdown fences. We'll 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.

          This is a hybrid/onsite role based in Nashville, TN; Atlanta, GA; Chicago, IL; Dallas, TX; New York, NY; Jersey City, NJ; Columbia, SC.

          Capgemini is seeking a full‑time MuleSoft Platform Architect (Sr Manager Level).

          But we need to avoid repeating job title as heading; it's okay to include in paragraph. Now Responsibilities:

          Responsibilities

          • Plan, size, and implement MuleSoft Platform for RTF / CloudHub environments.
          • Design and size MuleSoft Platform to support production and non‑production environments.
          • Design and implement networking solutions for communicating with enterprise applications running on‑prem and in the cloud.
          • Set up access control for applications and platform access using SSO with IDM providers.
          • Build and maintain CI/CD pipelines to support automated provisioning and deployments in a DevOps environment.
          • Work with cross‑functional teams (Business, Functional, Networking, Security, Infrastructure) to understand enterprise integration requirements.
          • Develop operational, monitoring, and reliability procedures and processes for large clusters.
          Now Requirements:

          Requirements

          • 10+ years of middleware/integration experience (any platform).
          • Completed 3 full life cycles of MuleSoft Platform setup and operationalization (design, configuration, implementation, operationalization).
          • MuleSoft Integration Architect and MuleSoft Platform Architect certifications required.
          • Experience with various MuleSoft platforms including RTF, CloudHub 2.0, and Flex Gateway.
          • Experience implementing MuleSoft Platform on‑prem, public, and private cloud environments.
          • Bachelor’s degree in computer science, engineering, or a related field, with significant software development experience.
          Now Benefits:

          Benefits

          • Paid time off based on employee grade (A‑F): 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 (

Similar jobs