Mgr, Integration Platforms

We need to output HTML fragment with sections only if posting has real specific content. We must not repeat job title. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if content present. We have content: Primary Purpose Of Job (description) -> could be "About the role". Also "Major Job Accountabilities" and "Core Responsibilities in this Role" etc. Those can go under Responsibilities. Also "Expected Behaviors and Accountabilities" maybe also responsibilities or qualifications? Could be part of Requirements? But we need to map. We have "Experience Required" with Education and Experience. That's Requirements/Qualifications. Also "Required Skills Or Training" with Technical etc. That's Skills. Also "Professional Certifications, Licenses, And/or Registration Requirements" maybe also Skills or Qualifications. Also "EOE..." boilerplate to remove. We have no explicit Benefits, Pay, Schedule content. So we should not include those sections. We need to preserve all substantive information, not invent. So we need to include sections: About the role (from Primary Purpose Of Job + maybe Major Job Accountabilities?), Responsibilities (Core Responsibilities + Expected Behaviors and Accountabilities?), Requirements (Education, Experience), Skills (Technical skills, etc.), maybe Qualifications (but we can combine). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. Probably include About the role, Responsibilities, Requirements, Skills. Possibly Qualifications separate from Requirements? Could treat Requirements as experience/education, Qualifications as certifications? But we have certifications under Professional Certifications. Could put under Qualifications. Let's decide: - About the role: Primary Purpose Of Job paragraph. - Responsibilities: Major Job Accountabilities + Core Responsibilities + Expected Behaviors and Accountabilities (maybe summarizing but we must not summarize away detail; we need to preserve all substantive info. We can list them as bullet points under

• . Must keep details. - Requirements: Education and Experience (bullet list). - Qualifications: Professional Certifications (maybe also mention preferred certifications). - Skills: Required Skills Or Training (Technical, etc.) plus maybe other skills like leadership etc. We'll include bullet list. We must not include filler like "commensurate with experience". Not present. We need to remove boilerplate: EOE, disability/veterans, contact info, etc. We must not include duplicated lines. Let's extract content. Primary Purpose Of Job paragraph: "The Manager of Integration Platform, Automation, and Cloud Services leads the design, implementation, and operation of integration platforms, automation workflows, and cloud-based services that connect disparate systems, streamline operations, and enable scalable, secure, and efficient data and process flows across an organization. The demands of this role is strong and growing, driven by cloud/SaaS adoption, API economies, and digital transformation. The role is increasingly strategic, with opportunities to leverage AI and automation to enhance integration and operational efficiency." We'll put that in

  . Major Job Accountabilities paragraph: "IT Managers lead teams of technology professionals to deliver business value. The role combines people leadership, technical oversight, and business partnership. Managers are accountable for team performance, talent development, and delivery outcomes. Effective IT leaders balance multiple demands: developing their people while delivering results, maintaining technical credibility while delegating technical decisions, and advocating for their teams while supporting organizational priorities. They create environments where talented people can do their best work. Career progression moves from managing a single team, to leading multiple teams or a department, to executive roles accountable for entire technology functions. At each level, the scope of accountability expands and the leadership challenges grow more complex." We'll include as bullet points? It's prose; we can keep as

  or break into

  • for each sentence? The instruction: Use
    • for any list of duties/requirements/benefits, and

      for prose. This is not a list but prose; we can keep as

      . However we might want to split into bullet list for readability but not required. We'll keep as

      . Core Responsibilities in this Role: It's a heading then a list of items separated by periods? Actually it's a paragraph with colon-separated items: "Integration Strategy & Platform Leadership: Own the integration platform strategy, ensuring it aligns with enterprise IT and business goals. Oversee API, event streaming, middleware, and cloud integration services that connect SaaS, cloud, and on-premises systems. Automation & Workflow Design: Architect and manage automation solutions (e.g., RPA, workflow orchestration) to reduce manual processes, improve accuracy, and accelerate operations. Cloud Services Management: Lead cloud integration and automation services, ensuring scalability, reliability, and cost-efficiency. Work with cloud providers (Azure) to deploy and manage integration environments. Cross-Functional Leadership: Lead and mentor integration engineers, automation specialists, and cloud architects; coordinate with the systems operations team, application teams, data engineers, business analysts, and executive stakeholders. Project & Change Management: Plan, execute, and deliver integration and automation projects on time, within scope, and within budget. Manage change management to ensure adoption and minimize disruption. Technical Oversight: Ensure data consistency, system compatibility, and secure, compliant integration environments. Monitor performance, troubleshoot issues, and implement enhancements. Technology Evaluation: Assess and adopt new integration, automation, and cloud tools to improve capabilities and support future growth. Stakeholder Communication: Present integration and automation strategies, progress, and risks to leadership and business units; provide training and documentation for teams and end-users." We can treat each colon-separated item as a bullet point. That would be a list of duties. So we will output

      • for each. Expected Behaviors and Accountabilities: It's a heading then categories with bullet-like sentences. We could also treat as list. But we might combine with Responsibilities? The instruction: Prefer a few substantive sections over many thin ones. We could merge Expected Behaviors into Responsibilities as well, but they are distinct. However we could keep Responsibilities section covering both Core Responsibilities and Expected Behaviors (since both are about responsibilities/accountabilities). That would be fewer sections. Let's do that: Responsibilities section includes both Core Responsibilities (list) and Expected Behaviors (list). We'll combine them into one
        • list. Thus we need to extract each bullet. From Core Responsibilities we have items: - Own the integration platform strategy, ensuring it aligns with enterprise IT and business goals. - Oversee API, event streaming, middleware, and cloud integration services that connect SaaS, cloud, and on-premises systems. - Architect and manage automation solutions (e.g., RPA, workflow orchestration) to reduce manual processes, improve accuracy, and accelerate operations. - Lead cloud integration and automation services, ensuring scalability, reliability, and cost-efficiency. - Work with cloud providers (Azure) to deploy and manage integration environments. - Lead and mentor integration engineers, automation specialists, and cloud architects; coordinate with the systems operations team, application teams, data engineers, business analysts, and executive stakeholders. - Plan, execute, and deliver integration and automation projects on time, within scope, and within budget. - Manage change management to ensure adoption and minimize disruption. - Ensure data consistency, system compatibility, and secure, compliant integration environments. - Monitor performance, troubleshoot issues, and implement enhancements. - Assess and adopt new integration, automation, and cloud tools to improve capabilities and support future growth. - Present integration and automation strategies, progress, and risks to leadership and business units; provide training and documentation for teams and end-users. From Expected Behaviors and Accountabilities we have categories with sentences. Let's extract each sentence as bullet? Might be too granular but okay. Leadership: - Models organizational values and leadership competencies. - Cultivates high-performance culture within team. - Provides clear direction and expectations. - Recognizes and rewards contribution. - Builds psychological safety for team. Development / Learning: - Recruits, develops, and retains talent. - Coaches and develops team members. - Conducts performance management and feedback. - Identifies skill gaps and training needs. - Builds diverse and inclusive teams. Customer / Business Orientation: - Focuses on internal and external customer requirements. - Demonstrates understanding of customer IT needs. - Defines architecture across business area. - Identifies process improvement opportunities. - Delivers on commitments to business partners. Project / Portfolio Management: - Maintains project plans across multiple projects. - Executes appropriate planning based on project characteristics. - Develops operational plans across technologies. - Manages resources and capacity. - Removes blockers for teams. Problem Solving: - Understands broader implications of situations. - Identifies potential problems and executes solutions before they escalate. - Prioritizes problems and solutions at workgroup level. - Builds team problem-solving capability. Systems Development / Engineering: - Ensures technical solutions are sound and well-integrated. - Ensures appropriate development methodology. - Recommends process and method improvements. - Drives engineering practices adoption. Testing / Deliverable Quality: - Ensures systems are functionally appropriate and technically sound. - Ensures infrastructure and test plans are in place. - Understands implications of changes. - Drives quality practices. Production Support: - Provides effective follow-up on problems. - Anticipates and communicates business impacts. - Works with support teams to meet business needs. - Drives operational improvements. Financial Accountability: - Assists in financial control for targeted areas. - Seeks opportunities for cost savings. - Manages team budgets. - Identifies and implements efficiency improvements. We'll include these as bullet points under Responsibilities as well. Now Requirements: Education and Experience. Education: "Bachelor’s degree in Computer Science, Software Engineering, Information Systems, or related field. MBA or MS preferred. Equivalent combination of education and experience accepted." Experience: "5–7 years total experience in IT environment. 2+ years leading teams and providing work direction in integration engineering or related roles. Experience with performance management." We'll put as
          • . Skills: Required Skills Or Training includes many bullet-like sentences. Let's extract each sentence. Technical: - Proficiency in integration platforms (e.g., MuleSoft, Dell Boomi, Azure Integration Services). - Automation tools (e.g., UiPath, Power Automate, workflow engines). - Cloud platforms (AWS, Azure, GCP). - API design, middleware, and event streaming technologies. - Strong project management, analytical, and problem-solving skills. - Oversees technical delivery across teams. - Drives technical roadmap alignment. - Excellent communication and leadership abilities. - Proficient in various programming languages. - Solid grasp of data structures, algorithms, design patterns. - Knows testing frameworks and practices. - Understands security, performance, scalability. - Leads technical discussions and decisions. - Mentors and develops team members. - Influences technology investment priorities. - Accountable for technical ROI. - Drives efficiency at scale and engineering excellence. - Ensures delivered applications meet corporate standards for security, correctness, platform readiness and performance. - Builds quality culture. - Accountable for technical quality. Maturity: - Deals with complex organizational issues. - Makes appropriate decisions and trade-offs. - Balances team needs with organizational priorities. - Handles difficult conversations professionally. Core Knowledge: - Thorough knowledge of management and leadership principles. - General knowledge of HR practices and regulations. - Solid knowledge of software development practices and methodologies. - Understands financial management basics. Critical Skills: - Effective people leadership and team building. - Clear communication up, down, and across. - Coaching and feedback skills. - Conflict resolution. - Prioritization and delegation. - Stakeholder management. We'll put these as bullet list under Skills. Qualifications: Professional Certifications: "Preferred certifications: MuleSoft Certified Developer/Architect, Azure Integration Services, or similar." We'll put as
            • . Now we need to output HTML fragment only, no extra text. Structure:

              About the role

              ...

              Responsibilities