Boomi Consultant

We need to output only HTML fragment, no html/body tags. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's parse. The posting includes Overview (intro) – that could be "About the role"? Actually "Overview" describes the unit and role. We could treat as "About the role". The "In the assigned Job Role of Package Project Lead 1, your Area Of Responsibility will be as below:" then bullet list of responsibilities. So we can have a Responsibilities section with those bullet points. Then "Your Contribution To The Team" – could be part of Responsibilities or maybe "Skills"? It lists contributions: proactive risk management, ability to build collaborative relationships, focus to anticipate challenges, commitment to balance project economics. Those are more like competencies/skills. Could be placed under Skills or Requirements. But we have separate sections: Requirements, Qualifications, Skills. We need to decide. "Required Skill And Experience" list: experience in Enterprise integration/middleware, specifically on Boomi AtomSphere; experience architecting complex Application Integration solutions; knowledge of Boomi components; experience leading integration architecture for major ERP/CRM platforms; understanding of API/web services technologies; understanding of integration security; stakeholder management and communication skills. That's required skills/experience. "Preferred Skill And Experience": hands-on experience migrating integrations from MuleSoft to Boomi; Boomi certifications; experience with Boomi API Management/API Gateway, MDM, Flow, or Event Streams; prior hands-on experience with MuleSoft Anypoint Platform; experience in regulated industries; familiarity with CI/CD and DevOps; prior experience as an enterprise integration architect leading multi-platform iPaaS consolidation initiatives. "Additional Required Qualifications": Bachelor’s degree or foreign equivalent required; will also consider three years of progressive experience in the specialty in lieu of every year of education; This position may require relocation and/or travel to work/project location. All applicants authorized to work in the United States are encouraged to apply. "Benefits": list of benefits. "Pay": Not explicitly mentioned; only "competitive pay" mentioned in Benefits line: "Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:" So pay is mentioned as competitive pay but no specifics. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive pay" but not specific numbers. Is that enough? The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive pay, albeit generic. Should we include a Pay section? It says "competitive pay" is stated, so we could include a Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might be better to incorporate pay into Benefits section? But Benefits section already exists; we could include pay as part of Benefits? The rule says we should create Benefits section only when posting actually states them. It does state benefits list. So we can have Benefits section with the list. Pay could be separate but maybe we can combine? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests these are possible headings. We should include a section only when posting has real, specific content for it. For Pay, we have "competitive pay" which is not specific but it's still content. It's not placeholder like "commensurate with experience" etc. It's a statement. I'd include a Pay section with that sentence. Schedule: Not mentioned. So no Schedule section. Now we need to decide sections: About the role (overview), Responsibilities, Skills (maybe combine required and preferred?), Qualifications (education etc.), Benefits, Pay. We could also have Requirements (maybe required skill and experience) and Skills (maybe preferred?). But we have both Required Skill And Experience and Preferred Skill And Experience. Could treat Required as Requirements, Preferred as Skills. Or combine both under Skills. But we have also Additional Required Qualifications (education). That could be Qualifications. Thus sections: - About the role: overview paragraph(s) - Responsibilities: bullet list from "In the assigned Job Role..." - Requirements: bullet list from Required Skill And Experience - Skills: bullet list from Preferred Skill And Experience - Qualifications: bullet list from Additional Required Qualifications (degree, experience in lieu, relocation/travel, work authorization) - Benefits: bullet list from Benefits - Pay: paragraph about competitive pay We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, About Us, etc. Also remove navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines. Also remove "About Us" and "EEO". Also remove "Overview" heading? We'll just use About the role section with the overview text. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe rephrase slightly? But must preserve info; we can keep same wording). Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to output only HTML fragment. Let's extract the overview text: "Overview The Infosys Enterprise Application Integration Services (EAIS) unit is at the forefront of transforming businesses through innovative consulting services. Our team is equipped with robust methodologies and tools, ensuring faster implementations, smoother rollouts, dependable production support, and top-quality product development. We specialize in integrating business applications using leading technologies such as TIBCO, Vitria, webMethods, IBM WBI, and SAP NetWeaver. Join us to be part of a dynamic team that drives excellence and innovation in enterprise application integration. You'll have the opportunity to work with cutting-edge technologies, collaborate with industry experts, and contribute to impactful projects that shape the future of business operations. If you're passionate about technology and eager to make a difference, the EAIS unit is the perfect place for you to grow and thrive." We can put that in

  under About the role. Responsibilities bullet list: - Develop project timelines, proactively identify and address resource discrepancies to ensure timely project completion - Facilitate effective coordination between technical teams and client stakeholders by organizing regular meetings, sprints, and project phases to align expectations and objectives - Support technical teams in executing development, integration, and customization stages of enterprise application packages, ensuring adherence to project requirements - Monitor project deliverables across all phases to meet established quality benchmarks and stakeholder expectations Also there is "Your Contribution To The Team" bullet list: proactive risk management to ensure project delivery. An ability to build collaborative relationships with stakeholders through effective communication Focus to anticipate challenges and deliver innovative solutions. Commitment to balance project economics with adherence to strategic priorities. These could be considered part of Responsibilities or maybe Skills. Since they are contributions, maybe they belong under Skills? But we already have Skills for preferred. However we could incorporate them under Responsibilities as additional bullets. The instruction: preserve ALL substantive information. So we need to include them somewhere. Could add them under Responsibilities as additional bullet points. Or create a separate section like "Team Contributions" but not in allowed headings. Better to add to Responsibilities. Thus Responsibilities bullets will include those four plus the four contribution bullets. Let's list them: 1. Develop project timelines, proactively identify and address resource discrepancies to ensure timely project completion 2. Facilitate effective coordination between technical teams and client stakeholders by organizing regular meetings, sprints, and project phases to align expectations and objectives 3. Support technical teams in executing development, integration, and customization stages of enterprise application packages, ensuring adherence to project requirements 4. Monitor project deliverables across all phases to meet established quality benchmarks and stakeholder expectations 5. Proactive risk management to ensure project delivery. 6. An ability to build collaborative relationships with stakeholders through effective communication 7. Focus to anticipate challenges and deliver innovative solutions. 8. Commitment to balance project economics with adherence to strategic priorities. Note: some have periods; we can keep as is. Now Required Skill And Experience bullets: - Experience in Enterprise integration/middleware, specifically on Boomi AtomSphere. - Experience architecting complex Application Integration solutions (real-time, batch, event-driven, API-led patterns) at enterprise scale. - Knowledge of Boomi components: Connectors, Process Canvas, Maps, Profiles, API Management, Atom/Molecule/Cloud architecture, and environment management. - Experience leading integration architecture for major ERP/CRM platforms (SAP, Oracle, Salesforce, Workday, NetSuite, etc.). - Understanding of API/web services technologies: REST, SOAP, JSON, XML, XSD, WSDL. - Understanding of integration security (OAuth 2.0, SSL/TLS, PGP encryption, certificate management). - Stakeholder management and communication skills, with ability to influence technical strategy at leadership level. Preferred Skill And Experience bullets: - Hands-on experience migrating integrations from MuleSoft to Boomi - Boomi certifications (Professional Developer, Architect). - Experience with Boomi API Management/API Gateway, MDM, Flow, or Event Streams. - Prior hands-on experience with MuleSoft Anypoint Platform (flows, APIs, DataWeave) — useful for migration/assessment work. - Experience in regulated industries (healthcare, finance, retail/supply chain) with B2B compliance needs. - Familiarity with CI/CD and DevOps practices for integration deployments. - Prior experience as an enterprise integration architect leading multi-platform iPaaS consolidation initiatives. Additional Required Qualifications bullets: - Bachelor’s degree or foreign equivalent required from an accredited institution. - Will also consider three years of progressive experience in the specialty in lieu of every year of education. - This position may require relocation and/or travel to work/project location. - All applicants authorized to work in the United States are encouraged to apply. Benefits bullets: - Medical/Dental/Vision/Life Insurance - Long-term/Short-term Disability - Health and Dependent Care Reimbursement Accounts - Insurance (Accident, Critical Illness , Hospital Indemnity, Legal) - 401(k) plan and contributions dependent on salary level - Paid holidays plus Paid Time Off Pay paragraph: "Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:" Actually that sentence includes benefits mention. But we already have Benefits section. The pay mention is just "competitive pay". We could output a

  stating "Competitive pay offered." But we must preserve the exact sentence? The rule: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that sentence exactly as it appears: "Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:" However that sentence also mentions benefits, which we are listing separately. If we include that sentence, we might duplicate benefits mention. But we could keep it as part of Pay section, and then Benefits section separate. The sentence includes "Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:" That's a lead-in to benefits list. If we include it in Pay section, we might be repeating the benefits intro. But we could keep it as is; it's not duplicate content because we still list benefits. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This sentence is not boilerplate; it's part of the posting. It's not duplicated elsewhere exactly. So we can keep it. Thus Pay section:

  Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:

  Then Benefits section with list. Now About the role section: we need heading

  About the role

  then

  with overview text. Responsibilities:

  Responsibilities

  • ... etc