IT Engineer III – Endpoint Management (Jamf & Intune)

We need to output HTML fragment with sections: About the Company, The Role You’ll Play, Experience You Bring (maybe split into Experience and Additional Strengths?), Must have experience with: (list), Compliance & Security Knowledge, Additional Strengths, Pay transparency (maybe as Benefits? Actually pay transparency includes salary range). According to rules: Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content to these headings. However we must only include sections when posting has real specific content. The posting includes About the Company, The Role You’ll Play (responsibilities), Experience You Bring (requirements/qualifications), Must have experience with (specific skills), Compliance & Security Knowledge, Additional Strengths, Pay transparency (salary range). Also maybe Benefits? Not explicit benefits aside from performance bonus, benefits, etc. It mentions "total compensation package may also include a performance bonus, benefits, and/or other applicable incentive compensation plans." That's vague but we can include Pay section with salary range and mention bonus/benefits. Benefits section maybe not needed because not specific. Schedule not mentioned. So we include About the Company (maybe as About the role? Actually About the Company is not exactly About the role but we can treat as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. Let's decide: - About the role: could include About the Company description? Actually About the role is about the role itself, not company. But we have "The Role You’ll Play" which describes responsibilities. That could go under Responsibilities. The About the Company could be omitted? But we need to preserve ALL substantive information. We could put About the Company under About the role? Not ideal but maybe we can create a section About the role that includes company overview? However the instruction says use those headings as examples, not strict list? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. If we have content that matches those headings, we use them. If not, we might need to adapt? Probably we should stick to those headings. Let's map: - About the role: could contain the company overview and role description? But we also have Responsibilities separate. Might be redundant. Maybe we can treat About the role as company overview, Responsibilities as role duties. That seems plausible. - Responsibilities: list of duties from "The Role You’ll Play" bullet points. - Requirements: maybe "Experience You Bring" (years, etc.) plus "Must have experience with:" list. - Qualifications: maybe "Additional Strengths" (communication, stakeholder management) or could be separate. - Skills: maybe the specific technical skills list (Cloud platforms, MDM tools, etc.) but that overlaps with Requirements. - Benefits: not specific; we have mention of performance bonus, benefits, etc. Could include Benefits section with that statement. - Pay: salary range. - Schedule: not present, so omit. We must not create sections with filler. So we include only those with real content. Let's extract content: About the Company paragraph: "At Playlist, life's richest moments happen when people step away from screens to move, connect, explore, and play. We're building the definitive platform for intentional living, connecting people with inspiring experiences in fitness, wellness, and beyond. With popular brands like Mindbody and ClassPass, Playlist empowers businesses and individuals, making it effortless for aspirations to become actions. Join us in reshaping technology's role to foster meaningful, real-world connections." Responsibilities (The Role You’ll Play): list: - Drive the strategy, configuration, and scaling of Playlist’s global Apple and Windows device fleets using Jamf and Intune. - Develop and maintain runbooks for future M&A scenarios—ensuring device management practices can scale securely and efficiently. - Ensure endpoint fleets consistently meet Playlist’s security baselines and implement iterative improvements. - Support integration planning and execution for systems related to mergers and acquisitions. - Own and manage technical projects—including requirements gathering, task tracking, and stakeholder communication. - Partner cross-functionally to identify and resolve technical or workflow-related friction points. - Participate in the IT Engineering “shield” rotation to support escalations from our internal support team. Experience You Bring (requirements): - 6+ years of IT Engineering experience in fast-paced, high-growth environments. - 4+ years of hands-on experience managing MDM tools, especially Jamf and Intune. - Proven track record in automating processes across Cloud SaaS platforms - Advanced knowledge of cloud infrastructure and endpoint management - Strong time management and prioritization skills, with a disciplined approach to documentation and knowledge sharing - Experience influencing both short- and long-term IT strategy and roadmaps. Must have experience with (specific skills): - Cloud platforms: Azure, AWS - MDM tools: Jamf Pro (Connect + Protect), Microsoft Intune - Server & device management: Windows Server, macOS device compliance - SSO & Identity: Experience implementing SSO and managing identity systems - System integration: Proficient in API-based integrations - Compliance & Security Knowledge: Familiarity with leading IT and InfoSec frameworks: ITIL, COBIT, NIST, ISO 27001/27002, CIS Controls PCI, GDPR, HIPAA, SOX, HITRUST - Understanding of regulatory requirements related to: PII, PHI, and financial data - Data residency and international compliance standards Additional Strengths: - Excellent verbal and written communication skills—able to explain complex technical topics to non-technical stakeholders. - Comfortable presenting recommendations and documentation to business and executive audiences. - Stakeholder management Pay transparency: includes base salary range $122,000 - $150,000, plus performance bonus, benefits, other incentive compensation. We could put Benefits section: mention performance bonus, benefits, other incentive compensation plans. Pay section: base salary range. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, application instructions, consent, privacy notices, etc. Also remove "Note: This description outlines key responsibilities..." etc. Now produce HTML fragment with

headings and appropriate

or

• . We need to decide which sections to include: - About the role (company overview) - Responsibilities - Requirements (maybe combine Experience You Bring and Must have experience with? Could split into Requirements and Qualifications? But we have both headings. Let's assign: - Requirements: the years of experience, MDM experience, automation, cloud infrastructure, time management, influencing strategy. - Qualifications: the specific skills list (Cloud platforms, MDM tools, etc.) plus Compliance & Security Knowledge maybe part of Qualifications? Or we could have Skills heading for technical skills, and Qualifications for compliance etc. But we need to avoid thin sections. Perhaps better: Requirements = Experience You Bring; Skills = Must have experience with (technical skills); Qualifications = Compliance & Security Knowledge + Additional Strengths? Hmm. But we have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: company overview paragraph. - Responsibilities: the bullet list from The Role You’ll Play. - Requirements: Experience You Bring (years, MDM, automation, cloud infra, time mgmt, influencing strategy). - Qualifications: Additional Strengths (communication, presenting, stakeholder management). - Skills: Must have experience with list (cloud platforms, MDM tools, server/device mgmt, SSO, system integration). - Benefits: mention performance bonus, benefits, other incentive compensation. - Pay: base salary range. - Schedule: omitted. We also have Compliance & Security Knowledge; could be part of Skills or Qualifications. Since it's about knowledge frameworks, could go under Skills as well. Let's include it under Skills as part of the list. Thus Skills section will include: - Cloud platforms: Azure, AWS - MDM tools: Jamf Pro (Connect + Protect), Microsoft Intune - Server & device management: Windows Server, macOS device compliance - SSO & Identity: Experience implementing SSO and managing identity systems - System integration: Proficient in API-based integrations - Compliance & Security Knowledge: Familiarity with leading IT and InfoSec frameworks: ITIL, COBIT, NIST, ISO 27001/27002, CIS Controls, PCI, GDPR, HIPAA, SOX, HITRUST - Understanding of regulatory requirements related to: PII, PHI, and financial data - Data residency and international compliance standards We need to preserve all substantive information; we must not lose any. Now produce HTML. We must not include markdown fences. Just raw HTML. Let's craft:

  About the role

  At Playlist, life's richest moments happen when people step away from screens to move, connect, explore, and play. We're building the definitive platform for intentional living, connecting people with inspiring experiences in fitness, wellness, and beyond. With popular brands like Mindbody and ClassPass, Playlist empowers businesses and individuals, making it effortless for aspirations to become actions. Join us in reshaping technology's role to foster meaningful, real-world connections.

  Responsibilities

  • Drive the strategy, configuration, and scaling of Playlist’s global Apple and Windows device fleets using Jamf and Intune.
  • Develop and maintain runbooks for future M&A scenarios—ensuring device management practices can scale securely and efficiently.
  • Ensure endpoint fleets consistently meet Playlist’s security baselines and implement iterative improvements.
  • Support integration planning and execution for systems related to mergers and acquisitions.
  • Own and manage technical projects—including requirements gathering, task tracking, and stakeholder communication.
  • Partner cross-functionally to identify and resolve technical or workflow-related friction points.
  • Participate in the IT Engineering “shield” rotation to support escalations from our internal support team.

  Requirements

  • 6+ years of IT Engineering experience in fast-paced, high-growth environments.
  • 4+ years of hands-on experience managing MDM tools, especially Jamf and Intune.
  • Proven track record in automating processes across Cloud SaaS platforms.
  • Advanced knowledge of cloud infrastructure and endpoint management.
  • Strong time management and prioritization skills, with a disciplined approach to documentation and knowledge sharing.
  • Experience influencing both short- and long-term IT strategy and roadmaps.

  Qualifications

  • Excellent verbal and written communication skills—able to explain complex technical topics to non-technical stakeholders.
  • Comfortable presenting recommendations and documentation to business and executive audiences.
  • Stakeholder management.

  Skills

  • Cloud platforms: Azure, AWS.
  • MDM tools: Jamf Pro (Connect + Protect), Microsoft Intune.
  • Server & device management: Windows Server, macOS device compliance.
  • SSO & Identity: Experience implementing SSO and managing identity systems.
  • System integration: Proficient in API-based integrations.
  • Compliance & Security Knowledge: Familiarity with leading IT and InfoSec frameworks: ITIL, COBIT, NIST, ISO 27001/27002, CIS Controls, PCI, GDPR, HIPAA, SOX, HITRUST.
  • Under