Manager Enterprise Applications

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, there is a description: "MSA is seeking a strategic and people-focused Manager, Enterprise Applications to lead the operations, governance, and product lifecycle of MSA’s enterprise business applications. This role oversees the Microsoft business applications ecosystem, including Dynamics 365 Finance & Operations, Customer Engagement, and Power BI, while partnering closely with leaders, stakeholders, vendors, and IT team members across the organization. Reporting to the Chief Information Officer, this role plays a key part in shaping secure, scalable, and effective technology solutions that support MSA’s business operations, financial systems, reporting needs, and long-term growth. MSA Professional Services is 100% employee-owned, meaning every employee has a direct stake in the success of the company. This ownership mindset drives our collaborative culture, long-term thinking, and commitment to delivering high-quality work for the communities we serve. Come join the ownership team at MSA! Employee Testimonial: ..." We need to remove boilerplate like employee testimonial? The testimonial is part of description but maybe we keep? It's not a section heading. We can keep as prose under About the role? The instruction: "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." So we can have an introductory paragraph. Then we have sections: Responsibilities (multiple bullet points). Then Qualifications (Education, Experience). Then Skills. Then Work Environment? Not required heading but could be part of About? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (intro). Responsibilities. Qualifications (maybe combine Education and Experience). Skills. Benefits (they list Additional Benefits and Compensation Range). Pay (they have Compensation Range). Schedule? Not mentioned explicitly; they mention Flex Time Program under Work Environment. That's schedule-ish but not explicit schedule. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. They state Compensation Range, so Pay section is appropriate. Benefits: they list benefits. Schedule: they mention Flex Time Program but not explicit schedule like "Full-time" etc. Might be considered schedule? The instruction says only include if posting actually states them. It mentions "Eligible for MSA’s Flex Time Program". That's a schedule benefit but not explicit schedule like "Monday-Friday, 9-5". Might be okay to include Schedule? Safer to not include Schedule unless explicit. We'll omit Schedule. We need to preserve all substantive information. So we need to include details about responsibilities, qualifications, skills, benefits, pay. We need to format lists with

• . Use

  for prose. We must not include boilerplate like EEO, Reasonable Accommodation Statement, etc. Remove those. Also remove duplicated lines. Let's extract content. Intro paragraph: combine first paragraphs up to before "Responsibilities". Include the employee testimonial? Might be considered part of description but could be kept. It's not boilerplate. We'll include as part of About the role. So About the role paragraph: "MSA is seeking a strategic and people-focused Manager, Enterprise Applications to lead the operations, governance, and product lifecycle of MSA’s enterprise business applications. This role oversees the Microsoft business applications ecosystem, including Dynamics 365 Finance & Operations, Customer Engagement, and Power BI, while partnering closely with leaders, stakeholders, vendors, and IT team members across the organization. Reporting to the Chief Information Officer, this role plays a key part in shaping secure, scalable, and effective technology solutions that support MSA’s business operations, financial systems, reporting needs, and long-term growth. MSA Professional Services is 100% employee-owned, meaning every employee has a direct stake in the success of the company. This ownership mindset drives our collaborative culture, long-term thinking, and commitment to delivering high-quality work for the communities we serve. Come join the ownership team at MSA! Employee Testimonial: “As an employee-owned company (100% ESOP), working at MSA is not just a job. We're genuine co-owners, and this ESOP setup promotes a culture of collaboration and engagement throughout MSA because we all have a direct financial interest as owners.”" Now Responsibilities: list bullet points under "Responsibilities". The posting has headings: Responsibilities Enterprise Applications Leadership, Product Strategy & Business Partnership, Project, Vendor & Operational Management, People Leadership & Team Development. Each with bullet points. We'll combine all bullet points under a single Responsibilities section? Could split but instruction: prefer few substantive sections over many thin ones. So we can have one Responsibilities section with all bullets. List bullets: - Own the technical and product governance for MSA’s Microsoft business applications ecosystem, including Dynamics 365 Finance & Operations, Customer Engagement, and Power BI - Lead application architecture, integration strategy, and solution design to ensure secure, scalable, and supportable platforms - Manage the full lifecycle of ERP-related enhancements, releases, customizations, support, and vendor-delivered work - Establish controls for security, compliance, environment management, testing, documentation, and operational support - Direct the product management process for the ERP portfolio, including business intake, backlog prioritization, roadmap planning, release coordination, and stakeholder communication - Partner with leaders and decision makers across departments to identify, recommend, develop, implement, and support cost-effective technology solutions - Analyze complex business needs and recommend technical solutions that align with enterprise standards and business goals - Establish governance for reporting and analytics solutions connected to ERP and CRM systems, including KPI alignment, data quality, and reporting consistency - Produce detailed timelines for application releases and implementations, monitor progress, and communicate project status - Oversee third-party vendors and implementation partners to ensure timely delivery, quality outcomes, knowledge transfer, and adherence to MSA standards - Develop business case justifications and cost/benefit analyses for IT initiatives - Support IT operational planning, including staffing, budgeting, software/hardware purchasing, resource allocation, and service delivery - Lead, coach, mentor, and develop direct reports while creating a positive employee experience - Foster accountability, continuous improvement, open communication, and high performance across the team - Participate in recruiting efforts and employment decisions for direct reports Now Qualifications: includes Education and Experience. We'll combine under Qualifications section. Education bullet? It's not a list but we can put as

  or

  . Since it's a qualification, we can list. Education: Bachelor’s degree in Information Systems, Business, or a related field; Equivalent combination of education and experience may be considered. Experience: Five years of progressive technology experience required; Experience within the IT and finance functions of an Architecture/Engineering/Construction firm preferred; Experience leading enterprise applications, ERP platforms, business systems, or related technology portfolios preferred; Experience with Microsoft Dynamics 365 Finance & Operations, Customer Engagement, Power BI, or similar enterprise platforms preferred. We'll put as
  • each. Now Skills: list bullet points. Skills bullet list: - Strong leadership, coaching, communication, and relationship-building skills - Ability to communicate with empathy and effectiveness in individual and group settings - Strong organizational and project management skills with the ability to manage changing priorities and complex initiatives - Ability to analyze business needs, evaluate solutions, and drive technology decisions aligned with organizational goals - Ability to negotiate persuasively, build trust, and demonstrate high personal and professional standards - Proficiency in Microsoft Office Now Benefits: they list Additional Benefits: Compensation Range: $112,000 - $179,500 a year; Employee Stock Ownership Plan (ESOP); Flex Time; 401(k) Retirement Plan; Medical, Dental & Vision Insurance; Paid Time Off; Paid Holidays; Paid Parental Leave; Employer-Paid Insurance; Short-Term Incentive Program (STIP). We need separate Pay section for compensation range, Benefits section for other benefits. Pay: Compensation Range: $112,000 - $179,500 a year. Benefits: list the rest. We should not include "Equal Opportunity Employer" etc. Work Environment: maybe not needed as separate heading; could be part of About? But we have Flex Time already in benefits. Work Environment description: "This position is performed in an office environment, with regular travel to other company officesEligible for MSA’s Flex Time Program". We already have Flex Time in benefits; we could add office environment and travel as a short paragraph under About or maybe under a Work Environment section but not required. Since we already have Benefits covering Flex Time, we could add a short paragraph about office environment and travel under About the role or maybe a separate "Work Environment" heading not in list but allowed? The instruction says use 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

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for those sections; we could add other headings but better to stick to those. So we can incorporate office environment and travel into About the role paragraph. Thus final HTML:

    About the role

    ... (intro paragraph)

    Responsibilities

    • ... each

    Qualifications

    • Bachelor’s degree in Information Systems, Business, or a related field
    • Equivalent combination of education and experience may be considered
    • Five years of progressive technology experience required
    • Experience within the IT and finance functions of an Architecture/Engineering/Construction firm preferred
    • Experience leading enterprise applications, ERP platforms, business systems, or related technology portfolios preferred
    • Experience with Microsoft Dynamics 365 Finance & Operations, Customer Engagement, Power BI, or similar enterprise platforms preferred

    Skills

    • Strong leadership, coaching, communication, and relationship-building skills
    • Ability to communicate with empathy and effectiveness in individual and group settings
    • Strong organizational and project management skills with the ability to manage changing priorities and complex initiatives
    • Ability to analyze business needs, evaluate solutions, and drive technology decisions aligned with organizational goals
    • Ability to negotiate persuasively, build trust, and demonstrate high personal and professional standards
    • Proficiency in Microsoft Office

    Pay

    Compensation Range: $112,000 - $179,500 a year

    Benefits

    • Employee Stock Ownership Plan (ESOP)
    • Flex Time
    • 401(k) Retirement Plan
    • Medical, Dental & Vision Insurance
    • Paid Time Off
    • Paid Holidays
    • Paid Parental Leave
    • Employer-Paid Insurance
    • Short-Term Incentive Program (STIP)
    We need to ensure we didn't miss any substantive info: The "Why MSA" section includes bullet points: 100% employee-owned firm with 100+ years of community impact, Collaborative culture with in-house experts for all disciplines across the firm, Flexible work-life integration, Ongoing learning and professional growth opportunities for all positions, Commitment to fostering a work environment where employees have a