Manager - Deskside Support

We need to output HTML fragment with sections only when there is real specific content. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no boilerplate, no navigation, legal, EEO, etc. Must not create sections with filler like "commensurate with experience". Must only include sections where posting has real specific content. Let's parse the posting. We have: - Intro paragraph about Perrigo mission etc. That's likely "About the role"? Actually description overview: "Overview The Manager, Global Field Service Operations leads Perrigo’s onsite IT support function across offices, manufacturing facilities, and distribution centers worldwide. This role oversees both internal team members and managed service providers (MSPs) to ensure high-quality technical support, efficient service delivery, and a positive end-user experience. The position is responsible for daily operations, resource management, service performance, continuous improvement initiatives, and maintaining service levels across multiple locations. Occasional travel may be required." That's description of role. Could be "About the role" or "Overview". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. We have sections: Description Overview (role description) -> could be "About the role". Then "Scope of the Role" with bullet-like sentences: Service Operations Lead..., Team & Vendor Leadership..., End User & Workplace Technology Support..., Continuous Improvement..., Stakeholder Management... Those are responsibilities. So we can put under

Responsibilities

with

• items. Then "Required Experience" includes required qualifications: Bachelor's degree..., 7+ years..., 3+ years leadership..., Experience supporting multi-site..., Strong understanding..., Excellent communication... That's requirements/qualifications. Could be under

  Requirements

  or

  Qualifications

  . The instruction says we have both headings possible. We need to decide which to use. Probably combine required experience under Requirements, and preferred experience under Qualifications? Or we could put required under Requirements and preferred under Qualifications. Let's see: Required Experience list: Bachelor's degree..., 7+ years..., 3+ years leadership..., Experience supporting multi-site..., Strong understanding..., Excellent communication... That's required. Preferred Experience list: Experience supporting manufacturing..., Experience with ServiceNow..., Knowledge of Microsoft 365..., ITIL certification..., Experience managing global managed service providers. That's preferred qualifications. Thus we can have

  Requirements

  for required, and

  Qualifications

  for preferred (or vice versa). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use both. Then "What Success Looks Like" could be considered Skills? Or maybe it's more about performance expectations; could be under Skills? But we have a Skills heading. Could we put success metrics under Skills? Not exactly. Might be better to treat as "Skills" but it's more about outcomes. However we could also omit Skills if no specific skill list. The posting does not have a separate skills list; but we could extract skills from required/experience: communication, analytical, stakeholder management, IT service management, etc. But we should not invent. Better to not create a Skills section if no explicit skill list. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we don't have explicit skills, we should not add Skills section. Benefits: There's a Benefits paragraph: "We believe our people are our greatest asset. Alongside competitive compensation, we offer benefits tailored to supporting you and your family, as well as career development opportunities to ensure you feel valued and supported, both professionally and personally. Find out more about Total Rewards at Perrigo." That's benefits description but no specific benefits listed (like health insurance, 401k). It's vague but still mentions benefits. It's not filler like "competitive compensation" is somewhat generic but still a statement. The instruction says do not create Benefits section unless posting actually states them. It does state benefits: "Alongside competitive compensation, we offer benefits tailored to supporting you and your family, as well as career development opportunities". That's real content, albeit generic. Should we include? Probably yes, as it's a benefits statement. We'll include Benefits section with that paragraph. Pay: No mention of salary or pay. So we should not include Pay section. Schedule: There's mention of hybrid work: "Hybrid Working Approach We love our offices and the setting they provide for in-person collaboration and celebration. But we also appreciate the opportunity to work remotely can energise you too, so we promote flexibility with the ability to work two days a week from home in many roles." Also earlier: "Work Environment This role requires regular engagement with onsite teams and business stakeholders and offers a flexible hybrid work environment. Some domestic and international travel may be required to support business needs and global operations." So schedule/hybrid info exists. We can put under Schedule heading. We also have "About the role" maybe from the introductory mission statement? The first paragraph about Perrigo mission is more about company, not role. But we could treat that as About the role? Actually About the role should describe the role. The "Description Overview" is the role overview. So we can put that under About the role. Thus sections: - About the role: description overview paragraph. - Responsibilities: list from Scope of the Role bullet points. - Requirements: required experience bullet points. - Qualifications: preferred experience bullet points. - Benefits: benefits paragraph. - Schedule: hybrid working approach and work environment paragraph (including travel). We must not repeat job title. Must not include navigation/legal/EEO etc. Must remove boilerplate like "We are an equal opportunity employer..." etc. Also remove "Applicants please note: To apply..." etc. Also remove "#weareperrigo". Also remove "Find out more about Total Rewards at Perrigo." maybe keep as part of benefits? It's a link suggestion but we can keep the sentence. It's not boilerplate? It's a call to action but maybe okay. However instruction: remove application instructions. "Find out more about Total Rewards at Perrigo." is not exactly application instruction but could be considered a link. Might be okay to keep. But safer to remove any "Find out more" lines? The instruction says remove application instructions, not general info. It's not an application instruction. It's a reference to benefits. I'd keep it. Also remove "We are proud to be included in the Forbes list of "America's Best Employers by State 2024". Find out more here". That's maybe not boilerplate but could be considered extra. It's not about role, but it's about company. Could be considered fluff. Might be okay to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. It's a company accolade. Might be okay to keep but could be considered not substantive to role. However we need to preserve ALL substantive information; does that include company accolades? Probably yes, it's substantive about the company. But we have limited sections; we could include it in About the role or Benefits? Might be better to include in About the role as extra context. However the About the role section currently only has description overview. We could add that accolade as a separate paragraph within About the role. But we must not invent headings. It's okay to add more paragraphs under About the role. But we need to ensure we don't include duplicated lines. There's no duplication. Now format: Use

  for each section heading. Use

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

    for prose. Thus:

    About the role

    At Perrigo, we are driven by our mission to Makes Lives Better Through Trusted Health and Wellness Solutions, Accessible to All. We are proud to be a Top 10 player in the European Consumer Self-Care market and the largest U.S. store brand provider of over the counter and infant formula. Dedicated to providing The Best Self-Care for Everyone, we are the people behind the brands you trust. We are Opill®, Compeed®, Solpadeine®, NiQuitin®, and many more. We Are Perrigo. We are committed to enhancing the wellbeing of our colleagues and consumers alike. We pride ourselves on fostering an inclusive, collaborative culture where each person can experience a sense of belonging. Join us on our One Perrigo journey as we evolve to win in self-care. Overview The Manager, Global Field Service Operations leads Perrigo’s onsite IT support function across offices, manufacturing facilities, and distribution centers worldwide. This role oversees both internal team members and managed service providers (MSPs) to ensure high-quality technical support, efficient service delivery, and a positive end-user experience. The position is responsible for daily operations, resource management, service performance, continuous improvement initiatives, and maintaining service levels across multiple locations. Occasional travel may be required.

    But note we repeated the mission statement and then "Overview". Might be okay. Alternatively we could split: first paragraph about company, then overview as separate paragraph. That's fine. Now Responsibilities: we need to extract bullet points from Scope of the Role. Let's list them: - Service Operations Lead day-to-day field service support activities across global locations. - Manage ticket queues, escalations, prioritization, and resolution performance. - Ensure service requests and incidents are completed within established SLAs and KPIs. - Monitor service quality, resource capacity, and operational performance. - Communicate effectively during major incidents and support-related changes. - Team & Vendor Leadership Lead and develop Field Service team members and oversee MSP partners. - Establish clear service expectations, priorities, and accountability measures. - Conduct regular performance reviews with service providers. - Support onboarding, training, and cross-functional knowledge sharing. - End User & Workplace Technology Support Oversee deployment, replacement, and support of end-user devices and workplace technology. - Manage support for peripherals, printers, conference rooms, and collaboration tools. - Partner with Asset Management to ensure accurate inventory and device lifecycle management. - Continuous Improvement Identify opportunities to enhance service quality, efficiency, and user satisfaction. - Standardize processes, documentation, and support procedures globally. - Use service metrics and trends to drive operational improvements and root cause resolution. - Collaborate with IT teams to improve support readiness and service delivery. - Stakeholder Management Serve as a key partner to IT teams, site leadership, business stakeholders, and service providers. - Support technology deployments, refresh initiatives, office moves, and other site-based projects. - Provide regular reporting on service performance, risks, and improvement initiatives. We need to put each as
  • . Might be long but okay. Now Requirements: required experience list: - Bachelor's degree in Information Technology, Computer Science, Business, or a related field, or equivalent experience. - 7+ years of experience in IT operations, field services, end-user computing, or workplace technology support. - 3+ years of leadership experience, including managing technical teams and/or service providers. - Experience supporting multi-site or global operations. - Strong understanding of IT service management processes, including incident, request, asset, and change management. - Excellent communication, analytical, and stakeholder management skills. We'll put each as
  • . Qualifications: preferred experience: - Experience supporting manufacturing, warehouse, or 24/7 operational environments. - Experience with ServiceNow or similar IT service management platforms. - Knowledge of Microsoft 365, Intune, Teams Rooms, endpoint management, and device lifecycle processes. - ITIL certification. - Experience managing global managed service providers. Now Benefits: paragraph: "We believe our people are our greatest asset. Alongside competitive compensation, we offer benefits tailored to supporting you and your family, as well as career development opportunities to ensure you feel valued and