Sr. Mgr, Enterprise Applications (Public Websites)

We need to output HTML fragment with sections: About the role, Responsibilities (maybe "What You'll Do"), Requirements (Education/Experience, Additional Licensing, Certifications, Required Skills/Knowledge), Benefits, Pay, Schedule? The posting includes Salary Range and benefits list. No schedule info. So include Pay and Benefits sections. No Schedule. We must not repeat job title as heading. Use

for each section heading. We need to preserve all substantive info, remove boilerplate like EEO, disclaimer, etc. Also remove navigation, cookie, legal, etc. The posting includes a lot of descriptive text about Horizon, mission, etc. That is likely boilerplate? It's about company description. Should we keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description at start might be considered boilerplate? It's not exactly legal/EEO but it's generic company overview. Might be considered not substantive for the role? Usually we keep "About the role" section. The initial paragraph about Horizon could be considered company overview, maybe not needed. But we could keep as part of "About the role"? The instruction: "Prefer a few substantive sections over many thin ones." Probably we should include About the role (the paragraph after "About The Role") as content. The earlier company description could be omitted as boilerplate. We'll omit the first paragraph. We need to extract sections: - About The Role: The paragraph after "About The Role": "In partnership with business customers, creates technology and digital strategy for company public websites across all market segments, ensuring integration with Horizon’s overall strategic plan. Accountable for driving exceptional user experiences and optimizing technology governance. Maintains, plans and implements major modifications to a technology portfolio up to 35 applications in pursuit of IT and business goals. Accountable for exemplary quality, performance, and availability service levels. Directs and oversees the software development lifecycle for new and existing in-house and vendor off-the-shelf application assets." - What You'll Do: This is a long list of duties. We need to put as

• items. The text includes headings like People Leader, Customer Liaison and Strategic Driver, Application Development..., Application Portfolio Management..., Vendor and contract management, Administrative, fiscal and budget management. We can treat each bullet as a list item, maybe grouping sub-bullets? The instruction: Use
  • for any list of duties/requirements/benefits. So we can make a single list with each duty as
  • . Could also nest but not required. Simpler: each major duty as
  • . We'll split by the headings. List items: - People Leader: Accountable for workforce management ensuring the necessary balance of internal and external technology talent, in terms of budget and skill, to appropriately meet customer demands. Team management and engagement including; interviewing and hiring, training and skills development, performance management, communication, and overall compliance with Horizon regulatory requirements, policies, and procedures. Transformational leader able to guide teams through culture transition. Manage multiple application teams up to (approximately) 50 full time equivalents; both Horizon employees and on/offshore contingent resources. - Customer Liaison and Strategic Driver: Foster effective partnerships with business customers to enhance and maintain digital and technology roadmaps as aligned to a technology product (application portfolio). Implement and maintain cohesive and transparent demand management practices within a technology team. - Application Development and Software Lifecycle Management – In house development and vendor off-the-shelf software implementation and integration: Ensure software development best practices and quality standards are embedded within all lifecycle phases and consistently utilized for software architecture, engineering, integration, testing and acceptance, and implementation. Experience with SDLC methodologies. Maintain close alignment with the business ensuring functional and nonfunctional requirements are collected and met and delivery commitments are upheld. Partners with EBTS managers (IT, Infrastructure & Operations, Information Security) as directed, to align on and implement divisional goals. Make certain of best practice artifact development, maintenance, and availability. Establish and maintain governance frameworks for public websites, including content management standards, publishing workflows, accessibility compliance, branding standards, component libraries, design systems, and approval processes. Lead continuous optimization of web platforms through data-driven decision making utilizing web analytics, user behavior insights, customer feedback, and search analytics. - Application Portfolio Management and Service Level Availability: Ensure technology roadmaps are maintained, managed, and implemented for the entirety of the application product line within span of control. Align team members to enterprise, information security, and data governance standards on architecture. Maintain 24x7x365 production support and agreed upon service levels for performance, availability, and quality. Accountable for the operational health of the application portfolio, including production monitoring, incident and problem management, root-cause analysis, capacity and performance management, and vulnerability remediation. Establish and monitor operational performance indicators, identify trends and systemic issues, and drive corrective actions that improve application availability, reliability, performance, security, and cost efficiency. Lead application optimization efforts across infrastructure, application code, integrations, databases, and third-party services in partnership with Infrastructure & Operations, Information Security, architecture, engineering, and vendor teams. - Vendor and contract management: Maintain a vendor strategy supportive of budgeted demand that aligns to the EBTS workforce strategy. Participate with corporate Legal and Procurement experts to ensure favorable terms and thorough vendor contracts. Foster effective vendor relationships, overseeing resource numbers/skill mix for capacity services relationships and delivery metrics for fixed priced contracts. Ensure month over month vendor adherence to contractual SLAs, contract terms, and quality of delivery. Uphold controls over the processes and transactions under areas of responsibility including the completeness and accuracy of financial information, business transactions, compliance with applicable laws and regulations, and the effectiveness and efficiency of operations. - Administrative, fiscal and budget management: Monthly and yearly management of budgets approximately $1.5M inclusive of any chargeback. Direct strategies that increase efficiency and throughput while maintaining cost and quality. Ensure employee and vendor time reporting practices are upheld and compliance activities are accomplished. - Education/Experience (What You Bring): High School Diploma/GED required. Bachelor's degree preferred or relevant experience in lieu of degree. 5 years of experience leading or building/implementing software, information technology projects and/or programs showing increasing responsibilities over a period of time. Preferred prior experience in the business and technology of health payer. - Additional Licensing, Certifications, Registrations: Preferred but not required: Lean Six Sigma, Project Management, Agile/Scaled Agile training and related certifications. - Required Skills/Knowledge: Demonstrated experience with Agile frameworks (Scrum, Kanban) and ability to oversee Agile teams and ceremonies such as PI planning, sprint planning, daily stand-ups, reviews, and retrospectives strongly preferred. Software development lifecycle expertise. Experience in software engineering, development and maintenance. Demonstrated experience in designing and implementing customer-facing portals, ensuring intuitive navigation and responsive design across devices strongly preferred. Familiarity with UX design and guided support tools to enhance user journeys and reduce friction strongly preferred. Familiarity with CI/CD pipelines, automated builds, and web/mobile deployment strongly preferred. Proven ability to deliver quality software products and applications on time and within budget. Demonstrated leadership of technology programs, projects, and teams. Strong organizational and problem solving skills. Strong technical acumen in modern web and mobile application platforms highly preferred, including responsive web architecture, native and cross-platform mobile development, APIs and system integrations, cloud-hosted services, content delivery, identity and access management, observability, and application security. Demonstrated ability to evaluate technical designs, architecture decisions, engineering tradeoffs, production risks, and operational readiness for customer-facing web and mobile applications. Experience with monitoring and observability practices, including application performance monitoring, logging, alerting, dashboards, and the use of operational data to identify performance degradation and optimization opportunities. Experience managing enterprise-scale public websites, digital experience platforms, content management systems, web analytics, search engine optimization (SEO), accessibility compliance (WCAG), digital marketing integrations, personalization technologies, and customer acquisition platforms. - Why Horizon? (maybe we can include as a section? It's more about company culture; could be considered boilerplate but it's specific to the posting. Might keep as a section "Why Horizon?" but it's not a standard heading; we could treat as a paragraph. However instruction: include a section ONLY when the posting has real, specific content for it. This is specific content. Could include as a section "Why Horizon?" but not in the list of headings given (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those. So we can add other headings if appropriate. But we might combine "Why Horizon?" into a

    under Benefits or something. Safer to omit as it's more fluff. But it's substantive about mission. Could include as a

    after Benefits. I'd include a section "Why Horizon?" as

    Why Horizon?

    with paragraph. - Salary Range: $138,000 - $188,370. Also description about compensation factors. We'll include Pay section with that range and maybe note that it's based on factors. Keep the description. - Benefits: list: Comprehensive health benefits (Medical/Dental/Vision), Retirement Plans, Generous PTO, Incentive Plans, Wellness Programs, Paid Volunteer Time Off, Tuition Reimbursement. We should not include disclaimer about NJ residency etc. That's likely boilerplate/legal. Remove. Now construct HTML:

    About the Role

    ... (the paragraph)

    Responsibilities

    • People Leader: ...
    ...

    Requirements

    Maybe combine Education/Experience, Additional Licensing, Required Skills/Knowledge into Requirements? Or separate sections: Education/Experience, Licenses/Certifications, Skills. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could have Requirements (education/experience), Qualifications (licenses/certs), Skills. But we can also combine. Safer to follow the example: Use headings for those categories. We'll create:

    Education and Experience

    ...

    Preferred Licenses and Certifications

    • Lean Six Sigma
    ... etc

    Required Skills and Knowledge

    ... each skill as
    But the instruction says use
    • for any list of duties/requirements/benefits. So for skills we can list as
      • . For education/experience we can use

        or

        . It's a list of items; we can use
        . Now Benefits:

        Benefits

        • Comprehensive health benefits (Medical/Dental/Vision)
        ... etc
        Pay:

        Pay

        Salary Range: $138,000 - $188,370. This compensation range is specific to the job level and takes into account the wide range of factors that are considered in making compensation decisions, including but not limited to: education, experience, licensure, certifications, geographic location, and internal equity. This range has been created in good faith based on information known to Horizon at the time of posting. Compensation decisions are dependent on the circumstances of each case.

        We should not include the disclaimer about Horizon also provides a comprehensive compensation and benefits package which includes: ... Actually we already listed benefits; the sentence after salary range mentions that. We can incorporate that into Pay section or Benefits. We'll keep the sentence about Horizon also provides a comprehensive compensation and benefits package which includes: then list benefits. But we already have Benefits section; we could incorporate that sentence into Benefits intro. Let's keep Benefits section with list; we can preface with a short paragraph: "Horizon