Application Platform Engineer (M365 Support Engineer)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: Purpose of Position (maybe About the role). Tasks And Responsibilities (Responsibilities). Education, Certifications and Licenses, Years Of Experience, Core Competencies, Knowledge, Skills, Abilities And Other (KSAOs) (these could be Requirements/Qualifications/Skills). How NetJets Supports You (Benefits). No explicit Pay or Schedule mentioned. So we should not create Pay or Schedule sections. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like navigation, EEO, etc. The posting includes some boilerplate like "Join the NetJets Team NetJets, the global private aviation leader..." That's about the company; we can include as About the role? Actually "Purpose of Position" is like About the role. We'll create

About the role

with paragraph(s) from Purpose of Position. Responsibilities: from Tasks And Responsibilities bullet list. We'll make

• each bullet. Requirements/Qualifications/Skills: We have Education, Certifications and Licenses, Years Of Experience, Core Competencies, Knowledge, Skills, Abilities And Other (KSAOs). Could combine into sections: maybe

  Qualifications

  with subsections? But we only allowed headings for those specific categories. We could create separate sections: Education (

  Education

  ), Certifications and Licenses (

  Certifications and Licenses

  ), Years Of Experience (

  Years Of Experience

  ), Core Competencies (

  Core Competencies

  ), Knowledge, Skills, Abilities And Other (KSAOs) (

  Knowledge, Skills, Abilities And Other (KSAOs)

  ). However the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we can use those headings. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those specific headings. But we can also use other headings if needed? The examples are just examples; but they say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I'd interpret that we should use those headings when applicable. So we need to map content to those categories. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also Education etc could go under Requirements or Qualifications. Let's decide: - About the role: purpose of position paragraph. - Responsibilities: Tasks And Responsibilities list. - Requirements: Education, Certifications and Licenses, Years Of Experience. - Qualifications: Core Competencies? Actually core competencies could be Skills. But we have Skills section separate. - Skills: Knowledge, Skills, Abilities And Other (KSAOs) list. - Benefits: How NetJets Supports You. We need to avoid filler like "commensurate with experience". Not present. We must preserve all substantive info. So we need to include all details from each category. Let's extract content. About the role: The purpose of position paragraph(s). It starts: "Purpose of Position The Application Platform Engineer (M365 Support) is responsible for resolving complex technical issues using diagnostic tools, analytical tests, and troubleshooting techniques, while managing escalations and collaborating with other technical resources to address end-user and systemic problems in a fast-paced, customer-critical environment. This role also works closely with team members to identify efficiency challenges and drive improvements in processes, standards, documentation, and support strategies. The Application Platform Engineer follows direction from the Application Platform Engineer, Lead, and Team Manager for project assistance and support prioritization. In addition, the Application Platform Engineer executes the day-to-day enhancement, administration, maintenance, governance, and adoption of enterprise platform systems, including Microsoft 365 services such as Exchange, SharePoint, Teams, OneDrive, Entra ID, Power Platform, and Copilot, as well as Proofpoint, Jaspersoft, RightFax, Lucidchart, Webex, Miro, and other SaaS platforms. This includes performing system installations, upgrades, enhancements, configuration changes, monitoring, access reviews, licensing support, and lifecycle activities while helping ensure system availability, secure collaboration, and SLA performance. The engineer supports current team initiatives including Copilot readiness and governance, SharePoint permissions and site lifecycle management, distribution list modernization, Microsoft 365 service health response, SaaS platform administration, and operational automation. The role collaborates with other teams to resolve complex application issues, improve detection and prevention of recurring problems, and support investigation, design, and planning for new enterprise platform capabilities. The Application Platform Engineer works under general supervision on moderately complex to complex projects, supports team members to meet deadlines, and provides 24/7/365 on-call assistance to ensure smooth NetJets operations." We'll put that in

  . Responsibilities: list bullet points under "Tasks And Responsibilities". Let's extract each bullet: - Responsible for installing, patching, upgrading, configuring, and administrating enterprise platforms, including but not limited to Office 365 (e.g., Exchange, Teams, SharePoint,Copilot etc.), Proofpoint, Jaspersoft, RightFax, LucidChart, and other SaaS platforms. - Effectively troubleshoot and resolve complex technical problems for onsite and remote users. - Support Microsoft 365 Copilot and AI platform readiness activities, including admin configuration, feature validation, agent and connector governance, usage reporting, troubleshooting, and coordination with security and business stakeholders. - Maintain SharePoint, Teams, OneDrive, group, and distribution list governance by assisting with permissions reviews, ownership validation, site lifecycle cleanup, secure sharing controls, and documentation that supports least-privilege collaboration. - Create and maintain operational runbooks, support documentation, early-alert processes, and automation to reduce manual effort, improve support consistency, and shorten incident response and resolution times. - Assist with SaaS platform administration, licensing, vendor escalations, platform changes, and operational support across collaboration, communication, reporting, faxing, diagramming, and productivity services. - Participate in small projects from initiation to closure to improve enterprise platforms and ensure feature and security patching is proactively maintained. - Adhere to SLAs for patching of critical systems that limits security risks with minimal impact to system availability in a 24/7/365 global environment. - Ensure compliance with Cyber Security policies and procedures. - Support Service Desk and other teams when issues are escalated and participate on call after-hours support. - Mentor other team members through cross training. - Identify, document, and report design, reliability, and maintenance issues regarding environment stability and availability. - Validate technical information and metrics and release early alerting to highlight potential issues. - Note: "It is not possible to list all required job duties on this form. There may be other important duties assigned, depending on the position. For a list of essential job functions, please refer to the essential functions document for this job." This is boilerplate note; we should remove as per instruction: remove duplicated lines, navigation/legal/EEO etc. This note is like a disclaimer; likely we should drop it. It's not substantive duty. So we omit. Requirements: Education, Certifications and Licenses, Years Of Experience. Education: "Bachelor's in related field" Certifications and Licenses: (none listed?) Actually the heading "Certifications and Licenses" appears but no content after? In the text: "Certifications and Licenses Years Of Experience 2-4 years of experience". It seems they omitted certifications. So we have no specific content; we should not create a section if no specific content. So we skip Certifications and Licenses. Years Of Experience: "2-4 years of experience" Thus Requirements section will include Education and Years Of Experience. Qualifications: maybe we could put Core Competencies here? But we have Skills separate. The instruction list includes Qualifications as a possible heading. We could put Core Competencies under Qualifications. However they also have Skills heading. Let's decide: Qualifications: Core Competencies (Adaptability Collaboration Curiosity Service-Oriented Strives For Positive Results). Skills: Knowledge, Skills, Abilities And Other (KSAOs) list. Thus:

  Qualifications

  with
  • each core competency.

    Skills

    with
    • each KSAO item. Benefits: How NetJets Supports You paragraph list. Extract benefits paragraph: "NetJets is proud to provide a variety of attractive benefits to our employees, including many at no cost. Employees have access to no cost options including Medical, Dental, and Vision benefits, with access to robust networks of nationwide providers. NetJets offers benefits so you can LIVEWELL—a comprehensive package to support your Mind, Body, and Life. Our Comprehensive Suite Of Benefits Include Medical, Dental, and VisionHealthcare AdvocacyEmployee Assistance ProgramFlexible Spending AccountsHealth Savings Account with annual employer contributionWellness Programs & DiscountsPaid Time OffParental Leave of AbsenceLife and Accident InsuranceVoluntary benefits (financial protection plans)401(k) plan, with 67% of every dollar you contribute matched by NetJetsShort and Long-Term DisabilityLegal PlanIdentity Theft Protection PlansPet InsuranceFamily & Caregiving Support" We need to preserve all substantive info. The text seems to have missing spaces (e.g., "VisionHealthcare"). We'll keep as is but maybe we should add spaces for readability? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Changing punctuation might be considered altering? Adding spaces could be considered altering but not adding info. Safer to keep exactly as given. However the original text: "Our Comprehensive Suite Of Benefits Include Medical, Dental, and VisionHealthcare AdvocacyEmployee Assistance ProgramFlexible Spending AccountsHealth Savings Account with annual employer contributionWellness Programs & DiscountsPaid Time OffParental Leave of AbsenceLife and Accident InsuranceVoluntary benefits (financial protection plans)401(k) plan, with 67% of every dollar you contribute matched by NetJetsShort and Long-Term DisabilityLegal PlanIdentity Theft Protection PlansPet InsuranceFamily & Caregiving Support". It's messy but we keep. We'll put that in

      . Now produce HTML fragment: sections in order: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Each section:

      Section Title

      then content. For lists:
      • ...
      . For paragraphs:

      ...

      . Make sure not to include any extra markup like etc. Let's craft. About the role: one paragraph containing the purpose of position text. Ensure we keep line breaks? We'll just put as one

      with the text. Responsibilities:

      with each bullet. Requirements: maybe we need two subpoints: Education and Years Of Experience. Could be
      • Education: Bachelor's in related field
      • Years Of Experience: 2-4 years of experience
      . Or separate

      for each. We'll use

      . Qualifications: core competencies list: Adaptability, Collaboration, Curiosity, Service-Oriented, Strives For Positive Results. We'll put each as
      • . Skills: KSAOs list: many items. Need to extract each bullet from the KSAOs paragraph. The KSAOs section is a long paragraph with many items separated by line breaks? Let's parse