MuleSoft Integration Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: "Join Centric Consulting – A Culture You’ll Love" (maybe about company). Then "In this role, you will:" list of responsibilities. Then "Who You Are:" list of qualifications/requirements. Then "Total Rewards:" benefits etc. Also "Who We Are:" maybe about company. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only those headings if content exists. We need to extract content. Job location: Remote (U.S.-based) Travel Expectations: 0% Job Classification: Temporary (W2T); Contractor (1099). This is metadata; we can fold into short

maybe. We must not repeat job title as heading (no title given). No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. At end there is EEO statement, reasonable accommodations, etc. Remove those. We need to preserve all substantive information. Let's parse sections: - Intro: "Join Centric Consulting – A Culture You’ll Love At Centric Consulting, we've cultivated a unique approach to business. Our business is built on three fundamental principles: Enjoy the people you work with, have fun, and do great work. These principles define our consulting model and have crafted one of the most vibrant cultures in the consulting industry – celebrating individuals, collaboration, and lifelong friendships." That's about company culture. Could be "About the role"? Actually "About the role" maybe not; but we have no explicit "About the role" heading. Could use "About the role" for this intro? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create sections as appropriate. The intro could be "About the role" or maybe "About the company". Since they gave example headings, we can use "About the role" to describe the role and company context. That seems okay. Then responsibilities: list after "In this role, you will:" bullet points. Then qualifications: after "Who You Are:" list. Then benefits: after "Total Rewards:" paragraph. Also maybe "Who We Are:" could be another section like "About the company". But we already used About the role. Could add another heading like "About the company" but not in allowed list. The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g.). Likely they expect only those headings. So we should map content to those headings. Thus: - About the role: include the intro about Centric Consulting culture and maybe also the job location/metadata? Could include location line. - Responsibilities: the bullet list after "In this role, you will:". - Requirements: maybe combine "Who You Are:" (qualifications) and also include education, certifications etc. Could split into Requirements and Qualifications but we have both headings allowed. We could put technical experience under Requirements, and education/certifications under Qualifications. Or we could just use Requirements for all. But we need to avoid thin sections. Let's decide: Use Requirements for the bullet list of experience/skills, and Qualifications for education and certifications. Also Skills maybe not needed if covered. Benefits: from Total Rewards. Pay and Schedule: not provided, so omit. Now we need to format lists with

• . We must preserve all substantive information: ensure we don't lose any detail. Let's extract responsibilities bullet points: - Lead the design, architecture, and implementation of enterprise integration solutions across a complex application ecosystem. - Establish scalable integration patterns, frameworks, and best practices to support long-term business and technology objectives. - Drive API-led connectivity initiatives using the MuleSoft Anypoint Platform, enabling secure, reusable, and high-performing integration services. - Partner with business stakeholders, enterprise architects, product teams, and developers to translate business requirements into effective integration solutions. - Define integration architecture standards, governance processes, and technical roadmaps that align with enterprise strategy. - Provide technical leadership throughout the full solution lifecycle, including architecture, design reviews, development guidance, testing, deployment, and production support. - Design and implement integrations across cloud, on-premises, SaaS, and third-party applications. - Ensure integration solutions meet security, scalability, reliability, performance, and compliance requirements. - Mentor developers and integration engineers by promoting engineering excellence, knowledge sharing, and adoption of best practices. - Evaluate emerging technologies, integration approaches, and architectural patterns to continuously improve the organization's integration capabilities. - Collaborate across technical and business teams to identify opportunities for process improvement, automation, and increased operational efficiency. - Support project planning, estimation, and delivery activities to ensure successful implementation of integration initiatives. - Work collaboratively with global teams while maintaining availability during U.S. business hours. Now qualifications bullet points from "Who You Are:": - Proven experience designing and delivering enterprise integration solutions using the MuleSoft Anypoint Platform. - Strong understanding of API-led architecture, service-oriented architecture (SOA), event-driven architecture, and modern integration patterns. - Experience architecting integrations across enterprise applications, cloud platforms, SaaS solutions, databases, and third-party systems. - Deep knowledge of MuleSoft components, including API Manager, Runtime Manager, Exchange, Design Center, and Anypoint Studio. - Experience designing and implementing RESTful APIs, web services, and middleware-based integration solutions. - Strong understanding of security, authentication, authorization, and API governance standards, including OAuth, JWT, and related technologies. - Ability to communicate complex technical concepts to both technical and non-technical stakeholders. - Proven track record of providing technical leadership, influencing architectural decisions, and driving successful project outcomes. - Strong problem-solving skills with the ability to balance business needs, technical requirements, and operational considerations. - Experience working in large, complex enterprise environments with multiple applications and integration touchpoints. - Bachelor's degree in Computer Science, Information Systems, Engineering, or a related field, or equivalent combination of education and experience. - MuleSoft certifications are strongly preferred. - Ability to work effectively during U.S. business hours and collaborate across distributed teams. Now benefits from "Total Rewards:": - We proudly offer competitive compensation, a comprehensive and well-rounded benefits package for full-time employees that have been designed to nourish your well-being, such as health coverage, wellness programs, 401K company match, self-managed PTO, and other unique incentives that celebrate your accomplishments. - Remote and Hybrid Work - Time Off When You Need It - Benefits That Flex - Professional Development - While benefits eligibility may vary for roles that are not full-time, we provide unique opportunities for growth, skill development, and more. - Regardless of your role, you’ll be part of a collaborative environment where every team member contributes to our shared success. - Discover more about our benefits by exploring additional details here benefits . We need to preserve the list items. The bullet list after Total Rewards seems to be lines: "Remote and Hybrid Work", "Time Off When You Need It", "Benefits That Flex", "Professional Development". Also earlier sentence includes health coverage etc. We could incorporate that as a
  list. We should not include the link text "benefits" maybe it's a placeholder; but it's part of the sentence: "Discover more about our benefits by exploring additional details here benefits ." That seems like a placeholder; we could keep the sentence but maybe it's boilerplate? It's not exactly boilerplate; it's a call to action. Might be considered application instruction? It's not exactly instruction to apply; it's just a link. Might be okay to keep but it's vague. The instruction: remove application instructions. This is not exactly an application instruction; it's a link to benefits details. Could keep but it's not substantive. Might be safer to omit that sentence as it's not substantive detail. However we need to preserve ALL substantive information; that sentence is not substantive (just a link). I'd omit. Now location metadata: "Job Location: Remote (U.S.- based) Travel Expectations: 0% Job Classification: Temporary (W2T); Contractor (1099)". We can put in a short

  under About the role maybe. Now we need to output only HTML fragment, no markdown. Let's craft:

  About the role

  Job Location: Remote (U.S.-based); Travel Expectations: 0%; Job Classification: Temporary (W2T); Contractor (1099). Join Centric Consulting – A Culture You’ll Love. At Centric Consulting, we've cultivated a unique approach to business. Our business is built on three fundamental principles: Enjoy the people you work with, have fun, and do great work. These principles define our consulting model and have crafted one of the most vibrant cultures in the consulting industry – celebrating individuals, collaboration, and lifelong friendships.

  Responsibilities

  • Lead the design, architecture, and implementation of enterprise integration solutions across a complex application ecosystem.
  • Establish scalable integration patterns, frameworks, and best practices to support long-term business and technology objectives.
  • Drive API-led connectivity initiatives using the MuleSoft Anypoint Platform, enabling secure, reusable, and high-performing integration services.
  • Partner with business stakeholders, enterprise architects, product teams, and developers to translate business requirements into effective integration solutions.
  • Define integration architecture standards, governance processes, and technical roadmaps that align with enterprise strategy.
  • Provide technical leadership throughout the full solution lifecycle, including architecture, design reviews, development guidance, testing, deployment, and production support.
  • Design and implement integrations across cloud, on-premises, SaaS, and third-party applications.
  • Ensure integration solutions meet security, scalability, reliability, performance, and compliance requirements.
  • Mentor developers and integration engineers by promoting engineering excellence, knowledge sharing, and adoption of best practices.
  • Evaluate emerging technologies, integration approaches, and architectural patterns to continuously improve the organization's integration capabilities.
  • Collaborate across technical and business teams to identify opportunities for process improvement, automation, and increased operational efficiency.
  • Support project planning, estimation, and delivery activities to ensure successful implementation of integration initiatives.
  • Work collaboratively with global teams while maintaining availability during U.S. business hours.

  Requirements

  • Proven experience designing and delivering enterprise integration solutions using the MuleSoft Anypoint Platform.
  • Strong understanding of API-led architecture, service-oriented architecture (SOA), event-driven architecture, and modern integration patterns.
  • Experience architecting integrations across enterprise applications, cloud platforms, SaaS solutions, databases, and third-party systems.
  • Deep knowledge of MuleSoft components, including API Manager, Runtime Manager, Exchange, Design Center, and Anypoint Studio.
  • Experience designing and implementing RESTful APIs, web services, and middleware-based integration solutions.
  • Strong understanding of security, authentication, authorization, and API governance standards, including OAuth, JWT, and related technologies.
  • Ability to communicate complex technical concepts to both technical and non-technical stakeholders.
  • Proven track record of providing technical leadership, influencing architectural decisions, and driving successful project outcomes.
  • Strong problem-solving skills with the ability to balance business needs, technical requirements, and operational considerations.
  • Experience working in large, complex enterprise environments with multiple applications and integration touchpoints.

  Qualifications

  • Bachelor's degree in Computer Science, Information Systems, Engineering, or a related field, or equivalent combination of education and experience.