Collaboration Solutions Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. Let's parse the posting: - Intro: "Your Job The Koch Technology Employee Services team is hiring an IT Engineer to join our skilled engineering team. This individual will be a part of a global team that focuses on Collaboration Technology along with other related areas for Koch Industries. As a part of this team, you will work to provide modern Identity solutions and services for all Koch businesses. Additionally, there is responsibility for the entire enterprise in designing innovative solutions, creating, and sharing best practices, and providing support for our services." That's about the role. - "Our Team The Employee Services Organization provides value-added strategic partnerships with other Koch companies in ownership and support of several key processes and platforms. We deliver IT products and services that enable employee success and collaboration, foundational accounts and devices, and transformational mobility and XR experiences. As a trusted partner, we focus on people, processes, technology, and data to drive transformation. Our team members are key contributors through the application of frameworks and principles with an emphasis on leveraging critical and economic thinking to drive value." That's also about the team, could be part of About the role or separate. We'll include in About the role. - "Location: This role requires an in-office presence with flexibility in Wichita, KS / Plano, TX / Atlanta, GA / Green Bay, WI. This role is not eligible for VISA sponsorship." Location info: not a required section (Schedule, Pay, Benefits). Could be part of About the role or maybe we can include a short p tag. Not a heading. - "What You Will Do" list: bullet points. - "Who You Are (Basic Qualifications)" list. - "What Will Put You Ahead" list (preferred qualifications). - "At Koch companies, we are entrepreneurs..." that's philosophy, maybe not needed. - "Hiring Philosophy" etc: boilerplate? Might be considered EEO? It's about diversity, but maybe we should remove as it's generic? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The hiring philosophy about diversity might be considered EEO? It's about diversity of thought etc. Might be considered EEO boilerplate. Safer to remove. - "Who We Are" description of Koch: maybe not needed? It's generic company description; could be considered boilerplate? Not exactly EEO but still generic. Might be removed. - "Our Benefits" section: details about benefits. That's substantive; we should include Benefits section. - "Equal Opportunities" etc: remove. Thus sections we will have: - About the role (intro + team description) - Responsibilities (What You Will Do) - Requirements (Basic Qualifications) maybe call Requirements. - Qualifications (What Will Put You Ahead) maybe call Qualifications or Skills? The instruction list includes Skills as a possible heading. We have "What Will Put You Ahead" includes degree, ServiceNow experience. Could be Qualifications. We'll treat as Qualifications. - Benefits (Our Benefits) - Pay: Not provided (only statement about compensation range estimate). The posting says: "Any compensation range provided for a role is an estimate determined by available market data. The actual amount may be higher or lower than the range provided considering each candidate's knowledge, skills, abilities, and geographic location. If you have questions, please speak to your recruiter about the flexibility and detail of our compensation philosophy." No actual range given. So we should NOT create Pay section because no specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we omit Pay. - Schedule: Not mentioned besides in-office presence flexibility. No schedule details like full-time, shift. So omit Schedule. Thus we output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. We need to include location info maybe as a paragraph inside About the role. We must not repeat job title as heading. We must not include Job ID etc. We must not include boilerplate. Let's extract substantive content: About the role prose: - "The Koch Technology Employee Services team is hiring an IT Engineer to join our skilled engineering team. This individual will be a part of a global team that focuses on Collaboration Technology along with other related areas for Koch Industries. As a part of this team, you will work to provide modern Identity solutions and services for all Koch businesses. Additionally, there is responsibility for the entire enterprise in designing innovative solutions, creating, and sharing best practices, and providing support for our services." - Team description: "The Employee Services Organization provides value-added strategic partnerships with other Koch companies in ownership and support of several key processes and platforms. We deliver IT products and services that enable employee success and collaboration, foundational accounts and devices, and transformational mobility and XR experiences. As a trusted partner, we focus on people, processes, technology, and data to drive transformation. Our team members are key contributors through the application of frameworks and principles with an emphasis on leveraging critical and economic thinking to drive value." - Location: "This role requires an in-office presence with flexibility in Wichita, KS / Plano, TX / Atlanta, GA / Green Bay, WI. This role is not eligible for VISA sponsorship." We can combine these into About the role section as paragraphs. Responsibilities (What You Will Do) list: - Be an active member of global team that works with and supports O365 products. - Own administration and support of O365 (SharePoint, Exchange, OneDrive, Yammer, Teams, etc.) as well as PowerPlatform (Flow, Apps, PowerBI). - Apply advanced critical thinking, technical skills, and knowledge to collect needed information to resolve issues in a highly complex and fast-paced environment. - Drive Problem Management through identification of recurrent problems and subsequent root cause to improve processes and drive long term value. - Enable 1st/2nd level support through knowledge sharing opportunities, documentation, troubleshooting, process improvement and training. - Creating documentation that is easily consumed by a global audience by both customers and support organizations. - Responsible for supporting customer requests. Focusing on improving ticket SLAs, volumes, and customer satisfaction. Ensuring prompt resolution. - Escalation point for critical incidents and outages for the products. - Work as part of a global team providing support after hours as required. We need to preserve each bullet as

• . Requirements (Basic Qualifications) list: - Experience working with Office 365, Active Directory, Exchange. - Experience working both independently and in a team-oriented, collaborative environment. - Experience in writing knowledge base articles based on resolution paths. - Experience working with End users to troubleshoot and resolve their Office 365 issues. - Demonstrated ability to apply AI/GenAI capabilities to improve business outcomes. Qualifications (What Will Put You Ahead) list: - Bachelor’s/Master’s degree in Computer Science/Information Technology, or related field. - Experience with ServiceNow or similar ticketing tool. Also there is a line: "At Koch companies, we are entrepreneurs. This means we openly challenge the status quo, find new ways to create value and get rewarded for our individual contributions." This is more philosophy; could be considered boilerplate? It's not EEO but still generic. Might be removed. The instruction says remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's still generic fluff. Safer to remove? It's not substantive about the role. I'd remove it. Benefits section: "Our Benefits Our goal is for each employee, and their families, to live fulfilling and healthy lives. We provide essential resources and support to build and maintain physical, financial, and emotional strength - focusing on overall wellbeing so you can focus on what matters most. Our benefits plan includes - medical, dental, vision, flexible spending and health savings accounts, life insurance, ADD, disability, retirement, paid vacation/time off, educational assistance, and may also include infertility assistance, paid parental leave and adoption assistance. Specific eligibility criteria is set by the applicable Summary Plan Description, policy or guideline and benefits may vary by geographic region. If you have questions on what benefits apply to you, please speak to your recruiter. Additionally, everyone has individual work and personal needs. We seek to enable the best work environment that helps you and the business work together to produce superior results." We need to preserve all substantive info. That's a paragraph; we can put in

  . The list of benefits includes dash separated items; we could keep as prose or convert to list. The instruction: Use

  • for any list of duties/requirements/benefits. So we should convert benefits list to
    • . However the benefits sentence includes a preamble. We could keep preamble as

      then list. Let's extract benefits list items: - medical - dental - vision - flexible spending and health savings accounts - life insurance - ADD (maybe means accidental death and dismemberment? We'll keep as ADD) - disability - retirement - paid vacation/time off - educational assistance - may also include infertility assistance, paid parental leave and adoption assistance We need to preserve the "may also include" nuance. Could keep as separate items with note. We'll create

      • for each. Now ensure we don't include any boilerplate like Equal Opportunities, etc. Now produce HTML fragment:

        About the role

        ... paragraphs ...

        We may need multiple

        for separate paragraphs. Let's craft: Paragraph 1: The Koch Technology Employee Services team is hiring an IT Engineer to join our skilled engineering team. This individual will be a part of a global team that focuses on Collaboration Technology along with other related areas for Koch Industries. As a part of this team, you will work to provide modern Identity solutions and services for all Koch businesses. Additionally, there is responsibility for the entire enterprise in designing innovative solutions, creating, and sharing best practices, and providing support for our services. Paragraph 2: The Employee Services Organization provides value-added strategic partnerships with other Koch companies in ownership and support of several key processes and platforms. We deliver IT products and services that enable employee success and collaboration, foundational accounts and devices, and transformational mobility and XR experiences. As a trusted partner, we focus on people, processes, technology, and data to drive transformation. Our team members are key contributors through the application of frameworks and principles with an emphasis on leveraging critical and economic thinking to drive value. Paragraph 3: This role requires an in-office presence with flexibility in Wichita, KS / Plano, TX / Atlanta, GA / Green Bay, WI. This role is not eligible for VISA sponsorship. Now Responsibilities:

        Responsibilities

        • Be an active member of global team that works with and supports O365 products.
        • Own administration and support of O365 (SharePoint, Exchange, OneDrive, Yammer, Teams, etc.) as well as PowerPlatform (Flow, Apps, PowerBI).
        • Apply advanced critical thinking, technical skills, and knowledge to collect needed information to resolve issues in a highly complex and fast-paced environment.
        • Drive Problem Management through identification of recurrent problems and subsequent root cause to improve processes and drive long term value.
        • Enable 1st/2nd level support through knowledge sharing opportunities, documentation, troubleshooting, process improvement and training.
        • Creating documentation that is easily consumed by a global audience by both customers and support organizations.
        • Responsible for supporting customer requests. Focusing on improving ticket SLAs, volumes,