Digital Solutions & Event Technology Manager

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse job description. First, we need to extract sections. Job description includes: - Opening paragraph: "The Digital Solutions & Event Technology Manager will manage the technology platforms, workflow automation, and digital solutions that power Sherwin-Williams' sales meetings, leadership events, and business operations. This role helps direct technology strategy, improves business processes, manages data and platforms, and supports stakeholders to enhance operations and user experiences. We set our team members up for success. The Digital Solutions & Event Technology Manager will receive personalized one-on-one training and support to help get the candidate up to speed on the technologies, business processes, and networking critical to the role." That's about the role. - Additional Details: "This role is not remote/hybrid. This role will report Sherwin-Williams Cleveland Global Headquarters located at 1 Sherwin Way, Cleveland, OH 44115This position will require up to 10% travelThis position is also eligible for [bonus] [commissions] [long-term incentive compensation awards] based on performance and subject to the terms of the Company’s applicable plans. Job duties include contact with other employees and access confidential and proprietary information and/or other items of value, and such access may be supervised or unsupervised. The Company therefore has determined that a review of criminal history is necessary to protect the business and its operations and reputation and is necessary to protect the safety of the Company’s staff, employees, and business relationships." We need to drop boilerplate like EEO, legal, etc. Also drop "Additional Details:" maybe not a heading; we can embed into paragraphs. - "Why Join Our Team?" paragraph: "Innovation, collaboration, and initiative are valued. We provide hands-on training, ongoing career guidance, and professional development opportunities to help you grow. You will have the freedom to take ownership of meaningful projects, collaborate closely with stakeholders across the business, and make a real impact while enjoying a supportive and fun team culture. You’ll succeed in this roll if you have…" Then bullet list of skills/experience: "Certain platform or adjacent event planning software experienceExperience in Microsoft Power Platforms, including Power Apps and Power Automate (a bonus)Built, maintained, and improved automated business processes and workflowsThe capability of managing SharePoint Online sites, lists, libraries, and permissionsKnowledge of Microsoft tools and integrations, including SharePoint, Teams, Planner, and OutlookA solid understanding of user experience (UX) and user-focused solution designStrong troubleshooting, problem-solving, and process improvement skillsSuccessfully managed multiple projects and priorities simultaneouslyEffective communication and management skillsExperience documenting solutions and providing user support and trainingThe ability to work effectively with cross-functional teams and business partnersFamiliarity with Microsoft Copilot and AI-powered productivity tools is a plus" These are likely "Skills" or "Qualifications". The posting also has separate "Responsibilities" and "Qualifications" sections. Responsibilities list: - Event Technology Management: bullet points (Support the Certain.com technology platform..., Support the technology platforms..., Help manage registration..., Troubleshoot issues..., Partner with stakeholders...) - Workflow Automation & Process Excellence: bullet points (Design, develop, and maintain..., Identify opportunities..., Build and manage..., Document..., Continuously evaluate...) - SharePoint Development & Governance: bullet points (Develop and manage..., Create governance..., Ensure content..., Provide ongoing support...) - Stakeholder Enablement & Support: bullet points (Provide technical guidance..., Develop training materials..., Lead onboarding..., Function as liaison...) Qualifications: - Minimum Requirements: list of must-haves (Must be at least eighteen..., Must be legally authorized..., Must be willing to travel..., Must have a Bachelor's degree..., Must have at least three (3) years of experience..., Must have experience with Certain Event Planning Platform..., Must have experience with Sharepoint Online..., Must have experience supporting event technology platforms..., Must have familiarity with Microsoft Copilot..., Must have experience with data governance..., Must have experience with project management..., Must have experience supporting enterprise-wide business applications...) - Preferred Qualifications: list (Have a Bachelor’s degree in marketing, Business, Information Systems, Computer Science, or related field, Have experience with Microsoft Power Apps, Have experience with Microsoft Power Automate, Have experience with Microsoft Lists, Have experience with Microsoft Planner, Have experience with Microsoft Document libraries) We also have "About Us" paragraph describing company mission, benefits, etc. Benefits: mention "wide range of world-class benefits" and link to benefits page. No specific benefits listed, just generic. According to rules: do NOT create Benefits section unless posting actually states them. It mentions benefits generically but not specific. Should we include Benefits? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits generally: "wide range of world-class benefits designed for you. From retirement to health care, from total well-being to your daily commute—it matters to us." That's a statement of benefits, albeit not enumerated. I'd consider that as stating benefits, so we can include a Benefits section with that prose. However we must not invent details; we can include that paragraph as is. Pay: The posting mentions "[bonus] [commissions] [long-term incentive compensation awards]" but not specific numbers. It says "eligible for [bonus] [commissions] [long-term incentive compensation awards] based on performance". That's mention of compensation but not a specific range. The rule: do NOT create Pay section unless posting actually states them. It does mention eligibility for bonus etc. That's some compensation info. However the rule also says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The posting does not give numbers, but says eligible for bonus etc. That's not filler? It's somewhat vague but still states that there is bonus/commissions/LTIC. I'd consider that as stating compensation (bonus etc). So we could include a Pay section with that sentence. Schedule: mentions "up to 10% travel". That's schedule/travel. Could be considered schedule. The rule: include Schedule section only if posting actually states them. It does state travel requirement. So we can include Schedule with that. We must not repeat job title as heading. Not include Job ID etc. We need to output only HTML fragment, no /, no markdown. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip out the EEO paragraph, the "Qualified applicants with arrest or conviction records..." etc, the "Please be aware, Sherwin-Williams recruiting team members..." etc, the "As a VEVRAA Federal Contractor..." etc, the "Sherwin-Williams is proud to be an Equal Employment Opportunity employer..." etc. Also remove the "Additional Details:" heading? We can just incorporate its content into paragraphs. We need to decide sections: About the role (intro paragraph), Responsibilities (the bullet lists under Responsibilities heading), Qualifications (maybe combine Minimum and Preferred into Requirements? Actually we have Requirements and Qualifications sections per instruction. The instruction list includes headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - About the role: intro paragraph(s) describing role. - Responsibilities: the bullet points under Responsibilities heading. - Requirements: maybe the Minimum Requirements? Or we could treat Requirements as the mandatory qualifications (Minimum Requirements). Qualifications could be Preferred Qualifications? Or we could treat Requirements as the "Must have" list, and Qualifications as the "Preferred" list. That seems logical. - Skills: maybe the bullet list under "You’ll succeed in this roll if you have…" which is a list of skills/experience. Could be placed under Skills. - Benefits: the paragraph about benefits. - Pay: the sentence about bonus/commissions/long-term incentive compensation awards. - Schedule: the sentence about up to 10% travel. We must not create sections with filler. Ensure each section has real content. Let's extract content precisely. First, About the role: Paragraph: "The Digital Solutions & Event Technology Manager will manage the technology platforms, workflow automation, and digital solutions that power Sherwin-Williams' sales meetings, leadership events, and business operations. This role helps direct technology strategy, improves business processes, manages data and platforms, and supports stakeholders to enhance operations and user experiences. We set our team members up for success. The Digital Solutions & Event Technology Manager will receive personalized one-on-one training and support to help get the candidate up to speed on the technologies, business processes, and networking critical to the role." We can keep as one

  . Second, Responsibilities: we have four subheadings with bullet points. We need to output a

  • for each duty. Should we keep subheadings? Not required; we can just list all duties as
  • . But we might want to keep grouping? Not required. The instruction: Use
    • for any list of duties/requirements/benefits. So we can flatten. List items: - Support the Certain.com technology platform used for company sales meetings, leadership events, and business conferences - Support the technology platforms used for company sales meetings, leadership events, and business conferences - Help manage registration, attendee communications, reporting, and event-related processes - Troubleshoot issues, assist with testing, and event readiness activities - Partner with stakeholders to ensure a smooth and successful event experience - Design, develop, and maintain automated business processes using Microsoft Power Automate - Identify opportunities to automate manual workflows and improve operational efficiency - Build and manage approval processes, notifications, escalation workflows, change requests, reporting automation, and business process integrations - Document standard operating procedures (SOPs) and process governance standards - Continuously evaluate and improve workflow performance, reliability, and scalability. - Develop and manage SharePoint communication sites, team sites, lists, libraries, and business solutions - Create governance standards, site architecture recommendations, and best practices guidance - Ensure content accuracy, usability, security, and long-term maintainability - Provide ongoing support and enhancements for active SharePoint environments - Provide technical guidance and consulting for business leaders, project teams, and end users - Develop training materials, documentation, FAQs, and self-service resources - Lead onboarding, training, and user adoption initiatives for digital solutions and business platforms - Function as liaison between business stakeholders, vendors, IT teams, and leadership. Note: Some duplicates: first two bullet points are similar; we keep both as they appear. Third, Requirements (Minimum Requirements). List: - Must be at least eighteen (18) years of age - Must be legally authorized to work in the country of employment without needing sponsorship for employment work visa status now or in the future - Must be willing to travel as required by the position - Must have a Bachelor's degree - Must have at least three (3) years of experience in business systems, marketing operations, and/or digital platforms - Must have experience with Certain Event Planning Platform, Touchpoint App or any adjacent type of application - Must have experience with Sharepoint Online - Must have experience supporting event technology platforms and attendee management systems - Must have familiarity with Microsoft Copilot and AI-enabled productivity solutions - Must have experience with data governance and process improvement initiatives - Must have experience with project management and stakeholder management - Must have experience supporting enterprise-wide business applications and operational processes We need to keep as
      • . Fourth, Qualifications (Preferred Qualifications). List: - Have a Bachelor’s degree in marketing, Business, Information Systems, Computer Science, or related field - Have experience with Microsoft Power Apps - Have experience